Author |
Message
|
tatyeong |
Posted: Tue Jul 06, 2010 10:57 pm Post subject: Message from MQ to JMS |
|
|
Acolyte
Joined: 16 Apr 2010 Posts: 52
|
In my client's environment, there is a JMS program that picks up XML message from a MQ queue through jms listener.
The XML message is well-formed when it is placed in the MQ queue. We have also set the MQMD format to MQFMT_STRING so that JMS receive the XML as a test message
However, when the XML message is picked up by JMS, the XML becomes malformed. Random "!" and breakline appears all over the XML.
Is there other settings that I missed out? |
|
Back to top |
|
 |
zpat |
Posted: Wed Jul 07, 2010 4:37 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Examine the message on the queue, is the CCSID value correct for the data content?
Try browsing it with MO71 with and without the convert option (context menu) does it remain readable after conversion?
If everything is OK using MO71 then the problem is in the application. |
|
Back to top |
|
 |
tatyeong |
Posted: Wed Jul 07, 2010 4:48 am Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010 Posts: 52
|
Is using RFHUTILC the same as using MO71? |
|
Back to top |
|
 |
zpat |
Posted: Wed Jul 07, 2010 5:44 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
RFHUTILC is support pac IH03
You can examine the message with this. But I have found the convert check box does not seem to work as I would expect though.
MO71 does many useful things, it's worth getting to know. |
|
Back to top |
|
 |
calanais |
Posted: Thu Jul 08, 2010 12:05 am Post subject: |
|
|
Apprentice
Joined: 12 Mar 2010 Posts: 32
|
Check out the CCSID settings of the sending and the consuming side. It could be a codepage conversion issue here.
One suggest when dealing with codepages - try and keep it as simple as possible and MQ and JMS to do all the heavy lifting for you. |
|
Back to top |
|
 |
tatyeong |
Posted: Thu Jul 08, 2010 7:57 pm Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010 Posts: 52
|
Apparently the XML message contains some fields with URL, and the MDB did not handle it properly when parsing the message |
|
Back to top |
|
 |
tatyeong |
Posted: Thu Jul 08, 2010 8:06 pm Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010 Posts: 52
|
Thanks all for the suggestions and pointers |
|
Back to top |
|
 |
|