| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| back out queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| jaipal |
 Posted: Mon Sep 07, 2015 2:42 am Post subject: back out queue |
 |
|
Newbie
Joined: 07 Sep 2015
Posts: 1
|
| when i'm trying to put messages in local queue the destination local queue is full and that local queue having back out queue but messages is not going to the BOQ [/b] |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Sep 07, 2015 5:20 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Moving messages to the backout queue - is NOT a function of the queue manager.
If you get MQRC 2053 - up to your code to decide what to do with the message (i.e. wait and retry, or stop processing, or rollback the transaction, or put to the backout queue (or some other queue), or put to the DLQ (adding DLH)) etc.
Backout queues are more normally associated with getting messages (not putting them) and are used for "poison" messages that are rolled back.
I've not heard of anyone using a backout queue as an overflow storage queue. It certainly is not automatic.
MQ does nothing more than provide a place to store a backout queue name and backout requeue threshold.
Anything acting on this is an application (such as message broker).
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 08, 2015 5:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The MQInput node will handle backout for you.
Under the correct conditions, including making sure that the message actually gets to the MQinput node again.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| inMo |
| Posted: Tue Sep 08, 2015 5:27 am Post subject: |
|
|
Master
Joined: 27 Jun 2009
Posts: 216
Location: NY
|
| In your description, an application is attempting to put a message to a queue. That queue is full, so the attempted put fails, and that application must decide what to do with the message. MQ in this case never accepted the message, so don't plan on it doing anything for you. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 08, 2015 5:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| inMo wrote: |
| In your description, an application is attempting to put a message to a queue. That queue is full, so the attempted put fails, and that application must decide what to do with the message. MQ in this case never accepted the message, so don't plan on it doing anything for you. |
The point here (which I think my most worthy associate has picked up on) is that this has been posted in the WMB section, indicating that the "application" doing the put is WMB.
As he and yourself have alluded to, the question now becomes what does the OP's flow do when it encounters the 2053?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| inMo |
| Posted: Tue Sep 08, 2015 12:55 pm Post subject: |
|
|
Master
Joined: 27 Jun 2009
Posts: 216
Location: NY
|
As I was referred to as a most worthy associate by the Grand High Poobah, I figured I better add something here.
I'd suggest the OP consider the original input protocol as it will likely influence what options and expectations exist for on-error processing. In example, if the flow starts with HTTP, a controlled response likely needs to be returned to the caller. If it is MQ, it is likely expected that the error not interfere with subsequent processing and awareness of the error is raised. |
|
| 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
|
|
|
|
