| Author |
Message
|
| guest468 |
 Posted: Fri Apr 03, 2009 9:17 am Post subject: qstatus repots wrong status |
 |
|
Centurion
Joined: 30 May 2006
Posts: 146
Location: NY
|
Hi,
When I run qs on one broker input queue it reports only IPPROCS (that is for dataflowengine) but no OPPROCS. In fact the queue is accumulating since there was a sudden flood of incoming message load.
Is this a bug or something?
This is in 6.0.2.2.
Thanks.
1 : dis qs(TESTQ) all
AMQ8450: Display queue status details.
QUEUE(TESTQ) TYPE(QUEUE)
CURDEPTH(127256) IPPROCS(1)
LGETDATE(2009-04-03) LGETTIME(17.14.15)
LPUTDATE(2009-04-03) LPUTTIME(17.14.15)
MONQ(MEDIUM) MSGAGE(1819)
OPPROCS(0) QTIME(235050857, 15622357)
UNCOM(YES)
1 : dis qs(TESTQ) all
AMQ8450: Display queue status details.
QUEUE(TESTQ) TYPE(QUEUE)
CURDEPTH(127271) IPPROCS(1)
LGETDATE(2009-04-03) LGETTIME(17.15.1
LPUTDATE(2009-04-03) LPUTTIME(17.15.1
MONQ(MEDIUM) MSGAGE(1839)
OPPROCS(0) QTIME(362601440, 40351906)
UNCOM(YES) |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Apr 03, 2009 9:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
AFAIK the MQOutput node does a PUT1, so you're probably not catching it with the queue open.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Apr 03, 2009 9:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
AFAIK, the MQOutput node does not do an MQPUT1.
AFAIK, nobody should wire an MQOutput to the same queue they've wired an MQInput, unless they're intending to cause their server to halt and catch fire.
Even channel MCAs will leave a queue with OPProcs as long as the current session is running.
Two points of data on depth is not enough to provide a pattern. Yes, one only needs two points to define a line, but in this case we really need to find out in what manner something has gone non-linear.
Maybe this is all message rollback. |
|
| Back to top |
|
|
| guest468 |
| Posted: Fri Apr 03, 2009 9:36 am Post subject: |
|
|
Centurion
Joined: 30 May 2006
Posts: 146
Location: NY
|
Thanks Vitor.
Makes sense. BTW, it's actually WAS application doing the put. Broker is only consuming from the queue.
I ran qs several times and at one time I did catch the OPPROCS from the app.
Actually PUT1 is not a good option in our environment since there is always at least a message every second. I will have to ask the APP team to change it to put.
Thanks again. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Apr 03, 2009 10:22 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| guest468 wrote: |
Thanks Vitor.
Makes sense. BTW, it's actually WAS application doing the put. Broker is only consuming from the queue.
I ran qs several times and at one time I did catch the OPPROCS from the app.
Actually PUT1 is not a good option in our environment since there is always at least a message every second. I will have to ask the APP team to change it to put.
Thanks again. |
As you are in WAS I would think that the message producer is using an anonymous sender. This may be the legitimate thing to do if WAS hosts a server type app.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| guest468 |
| Posted: Fri Apr 03, 2009 9:21 pm Post subject: |
|
|
Centurion
Joined: 30 May 2006
Posts: 146
Location: NY
|
Thanks Saper,
I will check with the WAS admin and app team. I would guess the app is coded to do put1. Apparently this is the only app in our entire project doing this. |
|
| Back to top |
|
|
|
|
