|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Issue in Convert XML to MRM in JCN |
« View previous topic :: View next topic » |
Author |
Message
|
mahesh2069 |
Posted: Wed Jul 10, 2013 6:16 am Post subject: Issue in Convert XML to MRM in JCN |
|
|
Centurion
Joined: 26 Jun 2013 Posts: 103
|
Hi All,
My Flow is
MQ input --> JCN ----> MQ output
I need to convert XML Message to MRM message in JCN.
I gave XML input to JCN ,In JCN I have parse the XML message ,I create MRM parser with MbMRM, and I have created message set , I set message set to that mrm ,after I add some mb elements to MRM paser, I got correct structure fro JCN ,But It cannot write inside MQ output node. Error is came while write the message in MQ output node.Flow go to infinite loop.
Error is :
<com.ibm.broker.plugin.MbBrokerException source:BIPmsgs key:2230 message:[BIPmsgs:2230]BIP2230E: Error detected whilst processing a message in node 'Caught exception and rethrowing'.
The message broker detected an error whilst processing a message in node 'Caught exception and rethrowing'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error. : Caught exception and rethrowing > _________________ Thanks & Regards
Mahesh Mediboyina
WMB Developer |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jul 10, 2013 6:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Here's a simple procedure for troubleshooting anything - Determine if a problem exists or not
- Identify what the problem is
- Consult any available documentation about the tools or systems you are using, including looking for information that relates to the specific problem you have discovered
- Review the source code or program or system that you have built, that is exhibiting a problem.
- Compare the actions of the source code against the documentation
- Think, very hard
- Determine a first step to take to produce more specific information about exactly where the problem is occuring
- Review the documentation and the source again.
- Think some more
- Repeat the last several steps until you can determine an initial change to make
- Make that change
- Determine if the change has solved the problem or not.
- If the change has not solved the problem, repeat all troubleshooting steps
If you follow this procedure for all cases where you are being told "it doesn't work", then eventually you will learn how to create things that work better the first time.
In specific, something about your code is wrong. Nobody can tell you what it is, based on what you have said.
Please troubleshoot yourself.
Best of Luck. |
|
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
|
|
|
|