| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSI2.1 : Message getting routed to Failure Queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| wbiman |
 Posted: Tue Aug 31, 2004 9:28 am Post subject: MQSI2.1 : Message getting routed to Failure Queue |
 |
|
Voyager
Joined: 13 Jul 2004
Posts: 84
|
Hi Friends,
Here's my Problem
During the fail-over testing in clustered veritas "Hot standby"
environment, MQSI message flow failed to process a message correctly
and wrote it to the failure Queue. In other words when MQSI broker and
message flow got rolled over to new hardware, they were processing
input message from the queue and after rolling over to new hardware
that incomplete processed message got routed to failure queue, and
also got deleted from input queue.
As we thought/understand , MQSI broker/message flow only deletes input
message from the queue after processing. Since fail-over condition can
happen any time, so its necessary to process that incomplete message
otherwise we will have problems of incomplete records in output results
Please suggest if there's any other solution we can use to solve this problem
Thanks for your help
Ravi Ram |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Aug 31, 2004 9:44 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The message on the input queue gets "removed" when the transaction that the MQInput node opens gets committed.
That is, an MQInput node will open a queue with syncpoint, and get each message in a unit of work. There are several ways that the unit of work involving a message can get committed instead of backed out.
If you have stuff hooked up to the failure terminal on the MQInput node instead of the catch terminal, or if you have stuff hooked up to the catch terminal and the flow along that path doesn't end in a throw node, these can cause the transaction to be committed.
If you have a backout requeue name configured on the input queue, and a backout count, and the message fails and gets retried more often than the backout count, the message will get removed from the input queue and comitted to the backout queue as well. This is the POINT of the backout queue - it prevents a single bad message from holding up the processing of all your other messages.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wbiman |
| Posted: Tue Aug 31, 2004 9:57 am Post subject: MQSI |
|
|
Voyager
Joined: 13 Jul 2004
Posts: 84
|
thanks for your help and now I fully understand based on your comments.
But how can we prevent that things to happen , I mean what should we do to make message roll back to input queue incase of veritas ' Hot standy" environment switch over ?
we really want only bad message to go in failure queue... not due to environment roll over.
Thanks
Ravi Ram |
|
| 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
|
|
|
|
