ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Time lag before requeue

Post new topic  Reply to topic
 Time lag before requeue « View previous topic :: View next topic » 
Author Message
mnair77
PostPosted: Tue May 20, 2014 10:52 am    Post subject: Time lag before requeue Reply with quote

Newbie

Joined: 02 Oct 2013
Posts: 4

Hi,

WMB 8.0.0.2, MQ 7.5

I am observing a time lag between a message rollback and the message getting re-read as part of retry processing. The following user trace snapshot shows the issue. The input node is MQInput.

Code:

2014-05-20 11:13:15.059193     5780   UserException  BIP2951I: Event generated by user code. Additional information : ''out of range'' 'TestFlow.Compute' '{2}' '{3}' '{4}' '{5}' '{6}' '{7}' '{8}' '{9}'
                                       The event was generated by an SQL LOG or THROW statement. This is the normal behavior of these statements.
                                       Since this is a user generated event, the user action is determined by the message flow and the type of event.
2014-05-20 11:13:15.059212     5780   UserTrace   BIP11507W: Rolled back a local transaction.
                                       A local transaction has been rolled back for work done on the message flow thread.
2014-05-20 11:13:16.098134     5780   UserTrace   BIP11501I: Received data from input node ''MQ Input''.
                                       The input node ''MQ Input'' has received data and has propagated it to the message flow ''TestFlow''.
2014-05-20 11:13:16.098674     5780   Error       BIP2648E: Message backed out to a queue; node 'TestFlow.MQ Input'.
                                       Node 'TestFlow.MQ Input' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
                                       Examine previous messages and the message flow to determine why the message is being backed out.  Correct this situation if possible.  Perform any local error recovery processing required.


Note the delay of nearly 1 second between the exception and requeue. This test was with no catch/failure connections. If I connect the catch terminal and re-throw, I see the 1-second delay before failure terminal processing as well as message getting backed out, leading to total processing time of 2+ seconds. What could be the reason for this delay?

EDIT: I didn't realize this went to the wrong forum. Moderator, Kindly move to Message Broker support.
Back to top
View user's profile Send private message
mnair77
PostPosted: Mon Jun 30, 2014 12:10 pm    Post subject: Reply with quote

Newbie

Joined: 02 Oct 2013
Posts: 4

I had opened a PMR for this issue. The response from IBM is that there is a hardcoded delay of 1 second in the rollback processing in WMB. There is no way to avoid it if you're depending on broker's rollback.

To work around this, I modified my exception handling subflow to end with an MQOutput instead of a Throw node, to explicitly commit messages into my backout queue.
Back to top
View user's profile Send private message
McueMart
PostPosted: Tue Jul 01, 2014 12:58 am    Post subject: Reply with quote

Chevalier

Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere

Yes I had also spoken to development about this and was informed of this hardcoded delay of 1s.

In my opinion this is a defect as it should be at least be a configurable value. I believe the intention of the 1s delay is to prevent poison messages causing 100% CPU utilisation. But it has the knock on effect that when your flows are encountering exceptions, it rate-limits the flow to 1 tps (causing massive message backlogs - I would prefer all the messages to be processed fast and processed by our exception handling process!)


I wonder if as part of your PMR you could request that this value be made configurable?
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Tue Jul 01, 2014 3:09 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

McueMart wrote:
I wonder if as part of your PMR you could request that this value be made configurable?


If someone submitted this as a Request For Enhancement and shared the link on this forum, it would probably get a lot of votes. That's the best way to initiate change in the product.

http://www.ibm.com/developerworks/rfe/
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
mnair77
PostPosted: Tue Jul 01, 2014 3:13 pm    Post subject: Reply with quote

Newbie

Joined: 02 Oct 2013
Posts: 4

Thanks for the suggestion. I have submitted an RFE for this topic:

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=55561

On the PMR I had requested making this configurable or at least documenting this delay, but the engineer did not agree, saying this delay was not a product feature.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Jul 01, 2014 6:40 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

mnair77 wrote:
Thanks for the suggestion. I have submitted an RFE for this topic:

http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=55561

On the PMR I had requested making this configurable or at least documenting this delay, but the engineer did not agree, saying this delay was not a product feature.


If you are using the developer edition you're limited to 1 tps anyway...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Time lag before requeue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.