| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| backout to backout requeue but no errors indicated |
« View previous topic :: View next topic » |
| Author |
Message
|
| rahoor |
 Posted: Wed Nov 28, 2007 9:14 am Post subject: backout to backout requeue but no errors indicated |
 |
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
All;
Doing baselines in preperation for upgrade to WBI/MB 6.0 from MQSI 2.1 CSD4.
At this point, still on MQSI 2.1, I have come across a situation with baseline but am stumped as to how to identify the cause.
The situation is that a message gets backed out w/o any errors in the trace file.
1. Messages gets dropped into input node using rfhutil
2. Message gets processed and is successfully dropped in the output queue, to be picked by SAP adaptor.
3. message is rolled back
It appears as though the message has received a rollback from the putting application (RFHUTIL) or was put under syncpoint and then rolled back.
This does not happen every time, only if I send multiple messages at once in quick succession!
Here is a trace:
The trace node 'DATA_TO_SAP_DEV_20050215.DATA_TO_SAP_BAS_200502111.DATA_TO_SAP_IDOC_BAS_200502101.Trace4' has output the specified trace data.
This is an information message provided by the message flow designer. The user response will be determined by the local environment.
2007-11-28 10:42:23.316995 4113 UserTrace BIP4067I: Message propagated to output terminal for trace node 'DATA_TO_SAP_DEV_20050215.DATA_TO_SAP_BAS_200502111.DATA_TO_SAP_IDOC_BAS_200502101.Trace4'.
The trace node 'DATA_TO_SAP_DEV_20050215.DATA_TO_SAP_BAS_200502111.DATA_TO_SAP_IDOC_BAS_200502101.Trace4' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2007-11-28 10:42:23.326307 4113 UserTrace BIP2638I: The MQ output node 'DATA_TO_SAP_DEV_20050215.IDOC Output' attempted to write a message to the specified queue 'QL.NC.MQLINK.TO.SAP.DV' connected to queue manager 'SAPQM1'. The MQCC was 0 and the MQRC was 0.
2007-11-28 10:42:23.326375 4113 UserTrace BIP2622I: Message successfully output by MQ output node 'DATA_TO_SAP_DEV_20050215.IDOC Output' to queue 'QL.NC.MQLINK.TO.SAP.DV' on queue manager 'SAPQM1'.
2007-11-28 10:42:23.678848 4113 UserTrace BIP2638I: The MQ output node 'DATA_TO_SAP_DEV_20050215.MQInput1' attempted to write a message to the specified queue 'SYSTEM.DEAD.LETTER.QUEUE' connected to queue manager 'SAPQM1'. The MQCC was 0 and the MQRC was 0.
2007-11-28 10:42:23.678989 4113 UserTrace BIP2615I: The MQSeries input node 'DATA_TO_SAP_DEV_20050215.MQInput1' has backed out the message to the backout requeue or the dead letter queue.
Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the MQSeries queue manager and queue configuration.
No user action required.
Threads encountered in this trace:
The output queue is put/get enabled, and can get messages, the trace in its entirety shows no errors. There are no errors in the MQ logs, and no FDCs are created. There is no recent cores.
My question:
What is the best way to find out why the backout took place?
thanks |
|
| Back to top |
|
 |
| rahoor |
| Posted: Wed Nov 28, 2007 10:41 am Post subject: |
|
|
Apprentice
Joined: 21 Jul 2003
Posts: 34
|
|
| 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
|
|
|
|
