| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Exception in Broker V6.0 after migration the MF of MQSI 2.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| dipankar |
 Posted: Thu Nov 10, 2005 3:10 am Post subject: Exception in Broker V6.0 after migration the MF of MQSI 2.1 |
 |
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
WINDOWS 2000, Message Broker 6.0 and WINDOWS 2000, WMQI Broker 2.1,CSD 8
I have migrated the message flow of WMQI 2.1 to Message Broker 6.0. However It creates an exception in Broker 6.0 while processing the following code
| Code: |
IF CARDINALITY(Environment.File.Status[]) > 0 THEN
--Update Audit logging table
UPDATE Database.INTERFACE_LOGGING AS T SET
TRANSACTION_ID = Environment.TransactionID WHERE T.GUID = Environment.uuid;
SET OutputDestinationList.Destination.RouterList.DestinationData[1].Labelname = 'Processed';
PROPAGATE;
RETURN FALSE;
END IF; |
Here is the trace of exception
| Quote: |
RecoverableException BIP2230E: Error detected whilst processing a message in node 'VOUCHER_UK_APINT2_A.Validation Node'.
The message broker detected an error whilst processing a message in node 'VOUCHER_UK_APINT2_A.Validation Node'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2005-11-09 17:30:45.345855 3804 RecoverableException BIP2488E: ('.VOUCHER_UK_APINT2_A_Validation Node.main', '23.1') Error detected whilst executing the SQL statement ''PROPAGATE FINALIZE DEFAULT DELETE DEFAULT;''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
2005-11-09 17:30:45.345878 3804 RecoverableException BIP2112E: Message broker internal error: diagnostic information '', '{1}'.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center. |
In WMQI 2.1 it does not create any exception. if I remove the PROPAGATE statement after the labelname, then it is fine for Broker 6.0.
Any idea? |
|
| Back to top |
|
 |
| mgk |
| Posted: Thu Nov 10, 2005 3:56 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Can you post your full ESQL for this node, also also the type of node the PROPAGATE statement is propagating too (compute, etc)
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| dipankar |
| Posted: Thu Nov 10, 2005 4:17 am Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Hi mgk,
This is compute node.
The message flow is like
MQInputNode-->Compute Node1 --> RouteToLabel
Label1--Compute Node ---
Label2--Compute Node----
Label3--Compute Node---
It is impossible for me to post all ESQL as it is very large.
The ESQL is like -
| Code: |
SET Environment.File.Status[] = (SELECT L.PROCESSDATE FROM Database.INTERFACE_LOGGING AS L WHERE L.TRANSACTION_ID = Environment.GAIPSHeader AND L.STATUS = 'PROCESSED');
IF CARDINALITY(Environment.File.Status[]) > 0 THEN
SET OutputDestinationList.Destination.RouterList.DestinationData[1].Labelname = 'Label1';
PROPAGATE;
RETURN FALSE;
END IF;
--ESQL CODE---
--ESQL CODE---
--ESQL CODE---
--send the msg for the next label
IF CARDINALITY(Environment.ErrorData[]) < 1 THEN
SET OutputDestinationList.Destination.RouterList.DestinationData[1].Labelname = 'Label2';
ELSE
SET OutputDestinationList.Destination.RouterList.DestinationData[1].Labelname = 'Label3';
END IF; |
My requirements were-
If the file has been previously processed successfully, WBI will not check the remaining code below RETURN FALSE; That's why I used PROPAGATE after the Routing. It creates exception in Broker 6.0
Thanks a lot. |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Nov 10, 2005 5:14 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi, could you change the flow to not wire up the failure terminal(s) so the exception gets all the way back to the event log. Then for ALL events that occur because of this error (there are at least two) could you please post the full text of the Description: and Data: sections in order from the event log (make sure you select Words in the radio button for the Data section before copying the text)
Thanks,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| dipankar |
| Posted: Thu Nov 10, 2005 8:18 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
There are 5 events in the event log.
Here are the descriptions and data:
1) Descriptions
| Quote: |
( WB_BROKER.UK_Execution_Group ) Message backed out to a queue; node 'VOUCHER_UK_APINT2_A.From_DataBaseReaderAdapter'.
Node 'VOUCHER_UK_APINT2_A.From_DataBaseReaderAdapter' 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. |
1) data
| Quote: |
0000: 00340033 00360035 00570000 005f0042
0010: 00520042 004b004f 00520045 0030002e
0020: 00350033 00380032 00370035 002d0034
0030: 00370030 00310030 0030002d 00300030
0040: 002d0030 00300030 00300038 0064002d
0050: 00630030 00350064 00350038 00330065
0060: 00610031 00000033 003a0046 0062005c
0070: 00690075 0064006c 0053005c 00300030
0080: 005f0030 005c0050 00720073 005c0063
0090: 00610044 00610074 006c0046 0077006f
00a0: 006e0045 00690067 0065006e 0049005c
00b0: 0062006d 0071004d 006e0049 00750070
00c0: 004e0074 0064006f 002e0065 00700063
00d0: 00000070 00380031 00390031 00490000
00e0: 0062006d 006f0043 006d006d 006e006f
00f0: 006e0049 00750070 004e0074 0064006f
0100: 003a0065 0065003a 0069006c 00690067
0110: 006c0062 00460065 0072006f 00430042
0120: 006d006f 00620049 004d006d 00490051
0130: 0070006e 00740075 006f004e 00650064
0140: 00560000 0055004f 00480043 00520045
0150: 0055005f 005f004b 00500041 004e0049
0160: 00320054 0041005f 00460023 004d0043
0170: 006f0043 0070006d 0073006f 00740069
0180: 0065 |
2) Descriptions
| Quote: |
( WB_BROKER.UK_Execution_Group ) Message broker internal error: diagnostic information '', '%3'.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center. |
2) data
| Quote: |
0000: 00340033 00360035 00570000 005f0042
0010: 00520042 004b004f 00520045 0030002e
0020: 00350033 00380032 00370035 002d0034
0030: 00370030 00310030 0030002d 00300030
0040: 002d0030 00300030 00300038 0064002d
0050: 00630030 00350064 00350038 00330065
0060: 00610031 00000033 003a0046 0062002f
0070: 00690075 0064006c 0053002f 00300030
0080: 005f0030 002f0050 00780065 006f0070
0090: 00740072 0078002f 00360038 006e005f
00a0: 005f0074 002f0034 00730075 002f0072
00b0: 006e0069 006c0063 00640075 005c0065
00c0: 006d0049 004d0062 00730065 00610073
00d0: 00650067 0069002e 006c006e 00310000
00e0: 00350037 00490000 0062006d 0065004d
00f0: 00730073 00670061 003a0065 0052003a
0100: 00610065 00430064 00720075 006f0073
0110: 003a0072 006d003a 00730065 00610073
0120: 00650067 00000000 0000 |
3)Descriptions
(
| Quote: |
WB_BROKER.UK_Execution_Group ) ('.VOUCHER_UK_APINT2_A_Validation Node.main', '23.1') Error detected whilst executing the SQL statement ''PROPAGATE FINALIZE DEFAULT DELETE DEFAULT;''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error. |
3) Data
| Quote: |
0000: 00340033 00360035 00570000 005f0042
0010: 00520042 004b004f 00520045 0030002e
0020: 00350033 00380032 00370035 002d0034
0030: 00370030 00310030 0030002d 00300030
0040: 002d0030 00300030 00300038 0064002d
0050: 00630030 00350064 00350038 00330065
0060: 00610031 00000033 003a0046 0062005c
0070: 00690075 0064006c 0053005c 00300030
0080: 005f0030 005c0050 00720073 005c0063
0090: 00610044 00610074 006c0046 0077006f
00a0: 006e0045 00690067 0065006e 0049005c
00b0: 0062006d 00640052 005c006c 006d0049
00c0: 00520062 006c0064 00740053 00740061
00d0: 006d0065 006e0065 00470074 006f0072
00e0: 00700075 0063002e 00700070 00350000
00f0: 00390038 00530000 006c0071 00740053
0100: 00740061 006d0065 006e0065 00470074
0110: 006f0072 00700075 003a003a 00780065
0120: 00630065 00740075 00000065 006f0043
0130: 0049006d 006d0062 006f0043 0070006d
0140: 00740075 004e0065 0064006f 00000065
0150: 004f0056 00430055 00450048 005f0052
0160: 004b0055 0041005f 00490050 0054004e
0170: 005f0032 00230041 00430046 0043004d
0180: 006d006f 006f0070 00690073 00650074 |
4) Descriptions
| Quote: |
( WB_BROKER.UK_Execution_Group ) Error detected whilst processing a message in node 'VOUCHER_UK_APINT2_A.Validation Node'.
The message broker detected an error whilst processing a message in node 'VOUCHER_UK_APINT2_A.Validation Node'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error. |
4)Data
| Quote: |
0000: 00340033 00360035 00570000 005f0042
0010: 00520042 004b004f 00520045 0030002e
0020: 00350033 00380032 00370035 002d0034
0030: 00370030 00310030 0030002d 00300030
0040: 002d0030 00300030 00300038 0064002d
0050: 00630030 00350064 00350038 00330065
0060: 00610031 00000033 003a0046 0062005c
0070: 00690075 0064006c 0053005c 00300030
0080: 005f0030 005c0050 00720073 005c0063
0090: 00610044 00610074 006c0046 0077006f
00a0: 006e0045 00690067 0065006e 0049005c
00b0: 0062006d 006f0043 0070006d 00740075
00c0: 004e0065 0064006f 002e0065 00700063
00d0: 00000070 00360034 00000034 006d0049
00e0: 00430062 006d006f 00750070 00650074
00f0: 006f004e 00650064 003a003a 00760065
0100: 006c0061 00610075 00650074 00430000
0110: 006d006f 00620049 0043006d 006d006f
0120: 00750070 00650074 006f004e 00650064
0130: 00560000 0055004f 00480043 00520045
0140: 0055005f 005f004b 00500041 004e0049
0150: 00320054 0041005f 00460023 004d0043
0160: 006f0043 0070006d 0073006f 00740069
0170: 0065 |
5)Descriptions
| Quote: |
( WB_BROKER.UK_Execution_Group ) Exception condition detected on input node 'VOUCHER_UK_APINT2_A.From_DataBaseReaderAdapter'.
The input node 'VOUCHER_UK_APINT2_A.From_DataBaseReaderAdapter' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages. |
5) Data
| Quote: |
0000: 00340033 00360035 00570000 005f0042
0010: 00520042 004b004f 00520045 0030002e
0020: 00350033 00380032 00370035 002d0034
0030: 00370030 00310030 0030002d 00300030
0040: 002d0030 00300030 00300038 0064002d
0050: 00630030 00350064 00350038 00330065
0060: 00610031 00000033 003a0046 0062005c
0070: 00690075 0064006c 0053005c 00300030
0080: 005f0030 005c0050 00720073 005c0063
0090: 00610044 00610074 006c0046 0077006f
00a0: 006e0045 00690067 0065006e 0049005c
00b0: 0062006d 006f0043 006d006d 006e006f
00c0: 006e0049 00750070 004e0074 0064006f
00d0: 002e0065 00700063 00000070 00300031
00e0: 00330031 00490000 0062006d 006f0043
00f0: 006d006d 006e006f 006e0049 00750070
0100: 004e0074 0064006f 003a0065 0072003a
0110: 006e0075 00430000 006d006f 00620049
0120: 004d006d 00490051 0070006e 00740075
0130: 006f004e 00650064 00560000 0055004f
0140: 00480043 00520045 0055005f 005f004b
0150: 00500041 004e0049 00320054 0041005f
0160: 00460023 004d0043 006f0043 0070006d
0170: 0073006f 00740069 0065 |
|
|
| 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
|
|
|
|
