Author |
Message
|
Ramukjar |
Posted: Fri Feb 18, 2011 12:12 pm Post subject: RFH2 Header Cauing Malformation of SOAP |
|
|
Newbie
Joined: 18 Feb 2011 Posts: 3
|
Hi,
I am pretty new to the MQ World. I have a Java Based System that acts as a End System of MQ Messages. The clients post their messages to the queues of the Java System.
This Java System is running on Unix(Solaris) and Linux(Red Hat). When a MQ Message with RFH2 header comes along, the Unix system is able to seperate the Message from Payload, but In Linux it somehow turns out that the RFH2 header sticks to the payload. Since, the message is validated to SOAP Validity, the flow breaks.
Any help here would be great.
Thanks & Regards! |
|
Back to top |
|
 |
Vitor |
Posted: Fri Feb 18, 2011 12:26 pm Post subject: Re: RFH2 Header Cauing Malformation of SOAP |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Ramukjar wrote: |
In Linux it somehow turns out that the RFH2 header sticks to the payload. Since, the message is validated to SOAP Validity, the flow breaks. |
Whatever's reading the message is using basic WMQ functionality. The RFH2 is part of the payload to WMQ, only the MQMD is considered a header. Java applications using JMS automatically add an RFH2 to carry the JMS properties that don't map to the MQMD (this mapping is in the WMQ InfoCenter).
So when a message sent using JMS arrives on a queue, it will always have an MQMD and a payload, the first part of which is an RFH2. The reading application needs to code for this, or use JMS / XMS to read the message off correctly. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Feb 18, 2011 12:31 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Upgrade your queue managers to v7.
This issue will go away.
And you'll still be supported in a year's time. |
|
Back to top |
|
 |
Ramukjar |
Posted: Mon Feb 21, 2011 3:45 am Post subject: |
|
|
Newbie
Joined: 18 Feb 2011 Posts: 3
|
Thanks for both the replied. The Version of both the QMGRs seem to be 7. But, i see that the CCSID in Unix is 819, whereas in Linux it seems to be 1208. Do you think this could be the reason ? |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Feb 21, 2011 5:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
If the queue managers are at v7, it's not clear why there is an RFH2 header in the first place. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Feb 21, 2011 5:18 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Ramukjar wrote: |
The Version of both the QMGRs seem to be 7. |
Seems to be? They either are, or they are not. It's not a fuzzy question.
Ramukjar wrote: |
But, i see that the CCSID in Unix is 819, whereas in Linux it seems to be 1208. Do you think this could be the reason ? |
Do I think the difference in code page is preventing an application from processing a header? No.
Are you claiming that identical Java applications are running on both platforms? But one works and one doesn't?
You mention a "flow breaking" - is this "Java System" actually a WMB running a JCN? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Ramukjar |
Posted: Tue Feb 22, 2011 9:23 pm Post subject: |
|
|
Newbie
Joined: 18 Feb 2011 Posts: 3
|
The working Unix is having MQ 7.0.1.2. The Not Working Linux is MQ 7.0.1.3.
The Java application is having the same version running on both Unix and Linux.
Its not an WMB, its a Non Websphere& Non IBM product . |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Feb 22, 2011 9:36 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Ramukjar wrote: |
The working Unix is having MQ 7.0.1.2. The Not Working Linux is MQ 7.0.1.3.
The Java application is having the same version running on both Unix and Linux.
Its not an WMB, its a Non Websphere& Non IBM product . |
Lots of JMS fixes in 7.0.1.4 Please upgrade.
Also let us know the property attribute mode of the queue (prmode?) being used. Could it be that you are forcing an RFH on the queue in Linux but the client is not set up do deal with it?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|