Author |
Message
|
krisrock |
Posted: Fri Oct 26, 2007 5:14 am Post subject: Broker not picking messages frm queues |
|
|
Acolyte
Joined: 11 Sep 2007 Posts: 65
|
Hi
I have a Broker, which connects to a queue manager.
It was working fine until suddenly it stopped picking messages from the queues.
Logs showed no problem with the brokers.
How do i figure out what can be the pblms?
Or what can be reasons for broker not picking messages, when it is functioning properly?
Please let me know.
The issue is quite urgent.
thanks
Rakesh |
|
Back to top |
|
 |
vsr |
Posted: Fri Oct 26, 2007 5:28 am Post subject: |
|
|
Centurion
Joined: 04 Apr 2006 Posts: 104
|
Is the flow (which is not picking up messages) running ? Check this with mqsilist Broker. Check the qstatus for qdepth and input/output count and any processes holding the queue.
Do you see any errors in broker logs? |
|
Back to top |
|
 |
Gaya3 |
Posted: Fri Oct 26, 2007 5:34 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Hi
What is the version and on which OS its running
Check the Dataflow engine is running or not
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
krisrock |
Posted: Fri Oct 26, 2007 5:43 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2007 Posts: 65
|
No messages on logs...
How do i check whether the dataflow engine is running?
there r no processes holding the queues...
Version 6.0.
OS Solaris... |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Oct 26, 2007 5:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
On unix you can do "ps |grep DataFlow".
You might have to use ps -ef or ps -aux _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
Gaya3 |
Posted: Fri Oct 26, 2007 5:48 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Hi
ps -ef | grep -i <broker name>
paste it here.....
if there are no process holding the queue, then i think the data flow is not running.
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Oct 26, 2007 6:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
also, it doesn't harm anything to just run "mqsistart BROKERNAME".
If the broker is already running, then it will come back and tell you that. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
krisrock |
Posted: Fri Oct 26, 2007 7:26 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2007 Posts: 65
|
All this happened when the database went down and came back up...
I restarted the broker...
Broker seems fine...but it doesnt pick messages from the queues
issue is critical |
|
Back to top |
|
 |
bower5932 |
Posted: Fri Oct 26, 2007 7:28 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
Use the display qstatus command to make sure that the queue is actually open by the broker and has messages. |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Oct 26, 2007 7:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If the issue is critical, you should be on the phone with IBM Support.
Confirm that there is enough space on the file system holding the system log that broker is reporting to. If that is full, then you won't get any new log messages. To resolve this you will have to free up space, somehow (or add more), and then restart broker again.
Again, confirm that there are DataFlowEngine processes running. If there aren't, then confirm that there are any processes that start with "bip" running, again using "ps -ef|grep bip".
If you don't see bipservice and bipbroker, then broker is not actually running.
You can use "top" to get a view that is like the Windows task manager. Here you could maybe see if DataFlowEngine processes are getting started and then failing immediately.
Confirm that the Database is actually started successfully.
Confirm that no passwords have been changed, without also running mqsichangebroker or mqsisetdbparms. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
krisrock |
Posted: Fri Oct 26, 2007 7:44 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2007 Posts: 65
|
Database is not running then I would be getting errors on logs...
Log is not full....it has entries for other brokers...
Can the broker get corrupted anyway? |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Oct 26, 2007 7:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If the Broker Database gets changed by something other than the Broker, then yes, the Broker can get "corrupted".
One significant possibility here is that your broker doesn't think anything is deployed to it, regardless of what the ConfigMgr thinks.
I repeat - you should be working with IBM on this. You should have opened a Severity 1 call, if this is actually "critical". They should be walking you through a lot of things at the same time.
what does "mqsilist BROKERNAME" show? Does it show the ExecutionGroups it should show?
If so, does "mqislist BROKERNAME -e EGNAME" show the flows that should be deployed? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri Oct 26, 2007 9:09 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
|
Back to top |
|
 |
BCBS |
Posted: Wed Nov 07, 2007 11:34 am Post subject: |
|
|
 Apprentice
Joined: 12 Jul 2006 Posts: 37
|
Have you checked the input queue property for GET- enabled or disabled? _________________ _________________________________ |
|
Back to top |
|
 |
|