| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| URGENT PLEASE HELP MQSI 2.0.2 broker problem on Solaris |
« View previous topic :: View next topic » |
| Author |
Message
|
| MVO |
 Posted: Sun Jun 02, 2002 7:19 am Post subject: URGENT PLEASE HELP MQSI 2.0.2 broker problem on Solaris |
 |
|
Centurion
Joined: 09 Sep 2001
Posts: 131
|
Hi,
My broker broker1 has 2 exec groups, EG1 and EG2.
When I issued mqsistop broker1, lately it cannot shut down EG1 properly. I killed the process so that the broker can come down.
I then restarted the broker, it looked like everything came up OK (runmqsc QM and DIS QLOCAL(qname1) showed IPPROCS(1)),
But when I started putting messages to the queue, the first message was lost then the 2nd message never got processed. Not the broker hang.
mqsistop resulted same error with exec group EG1.
Same error when I repeatedly stop then start the broker.
I removed EG1, created a new exec group EG3, deployed. Now EG2 is in trouble...
Removed EG2, created EG4, deployed. Looked OK at first, but stopping and string the broker brought me to the same error. Worst of all, now the Control Center does not show 2 exec groups any more, it showed only one exec group !!!!
I am really confused... I am thinking of recreating the broker but rather find out the root of the problem .
Any help will be very appreciated !!!
I removed  |
|
| Back to top |
|
 |
| kirani |
| Posted: Sun Jun 02, 2002 9:45 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
MVO,
Most probably there is a problem with your message flow.
First time when you stopped your broker before deleting EG1, did you check your input queue for your lost message? You should not loose your message unless your message flow is discarding it. May be your message have gone to the DLQ or backed out on the input queue. Next time when you restarted the broker, it will pick up the message on the input queue for processing. For some reason your message flow is going into infinite loop so it is not picking up the next message.
Try removing your message flows from the EG's and then checkin all EG's before doing a complete deploy of the broker. After deploy completes goto operations pannel and do a refresh. See how many EG's are there. Next time you restart the broker you will see the same number of EG's. Go thru your message flow and make sure you don't have any infinite loop (like while loop or so) in it before assigning it to any of the EG.
Regards,
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
