|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
reset content description unexpected behaviour BIP2176S |
« View previous topic :: View next topic » |
Author |
Message
|
jhalstead |
Posted: Tue Jan 10, 2006 12:41 pm Post subject: reset content description unexpected behaviour BIP2176S |
|
|
 Master
Joined: 16 Aug 2001 Posts: 258 Location: London
|
Hi. Bit of a funny one, maybe sombody has seen it...
I pass a nicely formed XML message from a compute node to a reset content descriptor node.
In debug trace I see the propagation - however then RCD node throws a bit of a wobbler.
From syslog:
BIP2230E: Error detected whilst processing a message in node 'IB1_v1.JRH_IB1.Call Routing Service.ResetToMRM_Locator'.
BIP0000I: Message has no properties folder
In the debug trace I see:
BIP4124I: Message propagated to 'out' terminal of compute node 'IB1_v1.JRH_IB1.Build Routing Locator Message'.
BIP4081I: Message propagated to catch terminal from try-catch node 'IB1_v1.JRH_IB1.TryCatch4'. The try-catch node 'IB1_v1.JRH_IB1.TryCatch4' has caught an exception which occurred in a node connected to its try terminal. The message has been augmented with an exception list and is propagating it to any nodes connected to its catch terminal for further processing. See the following messages for details of the exception list. No user action required.
BIP2230E: Error detected whilst processing a message in node 'IB1_v1.JRH_IB1.Call Routing Service.ResetToMRM_Locator'. The message broker detected an error whilst processing a message in node 'IB1_v1.JRH_IB1.Call Routing Service.ResetToMRM_Locator'. An exception has been thrown to cut short the processing of the message. See the following messages for details of the error.
BIP2176S: Could not find message 0 in catalogue /usr/opt/mqsi/messages/En_US/BIPv500.cat, inserts are Root CIB_CBP5_IB1_v1.CIB_CBP5_IB1.Call Routing Service.ResetToMRM_Locator {2} {3} {4} {5} {6}
This BIP3176S is really a bit of an odd one - I've expect this type of thing if NLS path not set correctly or I have been monkeying around with custom message catalogues...
I put a trace before the call ot the RCD node and the message was nicely formed with Properties, MQMD & Body.
Dunno if this rings any bells - however would appreciate any help that can be offered!
Jamie |
|
Back to top |
|
 |
JT |
Posted: Tue Jan 10, 2006 2:17 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT.
|
Quote: |
The message has been augmented with an exception list and is propagating it to any nodes connected to its catch terminal for further processing. |
What does the ExceptionList say ? |
|
Back to top |
|
 |
elvis_gn |
Posted: Tue Jan 10, 2006 9:27 pm Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi jhalstead,
In your compute node, just before the RETURN TRUE, be in the debug mode and check the structure of the message...
Quote: |
BIP0000I: Message has no properties folder |
I am hoping that the OutputRoot.Properties does not exist.....
Regards. |
|
Back to top |
|
 |
jhalstead |
Posted: Wed Jan 11, 2006 3:36 am Post subject: |
|
|
 Master
Joined: 16 Aug 2001 Posts: 258 Location: London
|
elvis_gn & JT. thanks for the ideas!
finally managed to track it down (after a nights sleep).
whilst there was all the properties, MQMD & Body bita and bobs were there a node significantly upstream of the error has accidentally slipped something in ahead of the properties folder due to a REFERENCE not being specified correctly ... oops!
Thanks
Jamie |
|
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
|
|
|
|