| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Message Flow not processing the messages - Discussion Level |
« View previous topic :: View next topic » |
| Author |
Message
|
| Sam Uppu |
 Posted: Wed Jan 21, 2009 8:25 am Post subject: |
 |
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| RaviKrG wrote: |
Thanks Vitor, I feel the link provided will surely give an idea if the messgaes are uncommited and so that goes for the application error which is putting the messages to the input queue.
But mqjeff post "But it is clear that you can't browse uncommitted messages" if this is the case that the uncommitted messages canot be browsed so in my case I browsed all the three messages and the messages looked to be fine. and then the problem lies some where else.
"some kind of long running loop inside the flow or a long running transaction against a database." this might be a possible cause.
"someone told the message flow to stop, and didn't tell RaviKrG that they had done so" - is this really good to see these that too on production and does not log any entry.
But again if the messages are committed then can these be a possible reason 1) MF is hung 2) message is poison message |
Just a thought:
Can you copy those 3 msgs from the input queue and write them to a file and resend those 3 msgs thru lower level environments and see whether the msgs are processing. That confirms there is no problem with the msg. Then you look into the environmental issues. If those msgs are not processing in lower level environments, then you can talk to application team.
Thanks. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Jan 21, 2009 2:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| RaviKrG wrote: |
Thanks fjb, at present this can not be done in production but sure i will try this on my normal pre env system.
also BOTHRESh is zero. and since the BO queue is defined why this should go to the DLQ.
Since the backout queue is defined why the message was not put to BO queue when it was not processed. |
BOTHRESH =0 review the meaning for that value in the manual. 
I rest my case.... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 21, 2009 6:46 pm Post subject: Re: Message Flow not processing the messages - Discussion Le |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| RaviKrG wrote: |
Hi, I would like to keep this on the discussion level only.
|
What other level is there on a message board? Don't worry, we all won't show up at your workplace to fix it!
| RaviKrG wrote: |
3) Message flow was running
|
You still haven't proven to us the flow is even running. Just because the q is open for input doesn't prove anything.
Also, what is the backout count of the first message on the q?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Thu Jan 22, 2009 10:56 pm Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Peter,
I checked through the command mqsilist brokername -e executiongroup and then ps -ef | grep messageflow.
Is there any way by which we can prove that the flow is running ?
Also the backout count is 0.
fjb,
any comment on bothresh |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jan 23, 2009 3:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| Quote: |
BOTHRESH(integer)
The backout threshold.
This parameter is supported only on local and model queues.
Start of changeUse this parameter to set or change the value of the BackoutThreshold attribute of a local or model queue. Apart from allowing its value to be queried, the queue manager takes no action based on the value of this attribute. However, the Application Server Facilities (ASF) of WebSphere MQ classes for Java Message Service (WebSphere MQ JMS) use the attribute to determine how many times to allow a message to be backed out before transferring the message to the queue specified by the BackoutRequeueQName attribute.End of change
Specify a value in the range zero through 999 999 999.
|
and about the handling of poison messages in JMS
| Quote: |
| If the threshold is zero, poison message handling is disabled, and poison messages remain on the input queue. Otherwise, when the backout count reaches the threshold, the message is sent to the named requeue queue. If the backout count reaches the threshold, but the message cannot go to the requeue queue, the message is sent to the dead-letter queue or discarded. This situation occurs if the requeue queue is not defined, or if the ConnectionConsumer cannot send the message to the requeue queue. See Removing messages from the queue for further details. |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Mon Jan 26, 2009 7:21 pm Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
