| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBIMB broker hangs |
« View previous topic :: View next topic » |
| Author |
Message
|
| jonny |
 Posted: Thu Mar 24, 2005 7:46 am Post subject: WBIMB broker hangs |
 |
|
Acolyte
Joined: 03 Jul 2003
Posts: 57
|
Hi,
WBIMB CSD04, Solaris 8, WM% V5.3 CSD 8
WBIMB broker stopped working - Whenever I issue a command on the broker it just hangs. I tried mqsilist, mqsistop, I then killed off the processes (kill -9) and I tried to restart the broker using mqsistart, but it doesn't start properly. I get the message (successfull command initiation) but execution groups don't start, nor the HTTP listener process
I enabled the service trace (setting the MQSI_TRACE_UTILITY) to debug, but I can't see any errors reported, what I have notices that for all of the command, the last thing I can see in the formatted trace is a SELECT statement on table BROKERAAEG, to list execution groups details. I have also seen this SELECT statement on the odbctrace file. I have never come across this problem, normally it would be the SYSTEM.BROKER queues where I would have to stop broker, then stop config manager then start broker first and then config manager.
odbc connection to the broker database is fine, there are no errors in the syslog, nor on the MQ error log. channels are working fine between configuration manager and broker.
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Mar 24, 2005 8:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Are there messages sitting in any of the SYSTEM.BROKER.* queues?
Can you connect to the broker database using regular DB tools?
Can you run the same Select command, and get what appears to be reasonable results?
Can you do a full deploy of the broker from the Toolkit?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jonny |
| Posted: Thu Mar 24, 2005 8:55 am Post subject: |
|
|
Acolyte
Joined: 03 Jul 2003
Posts: 57
|
Jeff,
Yes I did try the same SELECT statment from a command line and it worked and there were no messages on SYSTEM.BROKER queues, and I couldn't do full deployof the broker.
Any way the problem was to do with the broker database (sybase) transactional log being full
Thanks for your response |
|
| 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
|
|
|
|
