Posted: Tue Sep 23, 2014 8:06 am Post subject: Wrong JMS message type & garbled body after WAS 8.5 upgr
Novice
Joined: 02 Aug 2005 Posts: 14
Hi,
We have had a JMS app running in WAS 6.1 on CentOS for years. It serves as an interface between my company and a client. Their z/OS WMQ sends us messages on a request queue which an MDB in our app processes and returns a response in a response queue. The client application is not a JMS application so we have set the Client Type of the request and response queue definitions in the WAS configuration to "MQ". We have to use CCSID 819. The MDB has thus far always received JMS messages of type TextMessage.
Due to the end of service of WAS 6.1 we have just migrated to WAS 8.5. Messages are still being delivered to the MDB but now the messages being received are interpreted as JMS BytesMessage messages and the text read from the message is garbled. WAS config settings appear to be the same for the queue definitions. Both WAS configs specifiy the "MQ" Client Type and CCSID 819.
The two WAS machines are two different CentOS machines, the old one running WAS 6.1 on CentOS 5.10 and the new one running WAS 8.5.5.2 on CentOS 6.5. Both use the same queue definitions on our WMQ 7.1.0.0 server on AIX 6.1 (64bit) but only one or the other is running at any one time, not in parallel.
Because nothing has changed on the WMQ server during the WAS upgrade, I assume the problem lies in the WAS configuration. We assume the client has not changed their message format but we will check this. Is there anything I need to additionally configure in WAS 8.5 that wasn't necessary in 6.1?
(The unix user under which WAS runs has been added to the user group on the WMQ server so the authentication change introduced with the WMQ 7 client (which appeared in WAS 8.5) is working correctly.)
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