Hello Vinay,

If you send an RFH2 to MQJMS it has to conform completely to the
description in chapter 12 of the "Using Java" book. If you are not sure
which part of the RFH2 is causing JMS problems you might find it useful
to take a JMS trace (run your receiving application with java
-DMQJMS_TRACE_LEVEL=on). During the conversion of the incoming message
to a JMSMessage there is a sequence of calls to the methods
_parseMcdFolder,  _parseJmsFolder and _parseUsrFolder (or their utf8
optimised versions) and it seems likely that it is one of these that is
failing. This would let you narrow your investigation and you could
proceed by comparing your custom built folder with one generated by MQJMS.

Regards,
James.

vinay_tiwari wrote:

Hi James,

Thanks for your response.It was really useful. Currently we have an existing application which builds RFH2 header using MQSEries native Java APIs and expects some user specific info in the response also. New application which we are building
is going to use JMS.Thats why I am trying to access the <Usr> folder in the income message.

When I build the <usr> folder in the JMS response I am able to get the info in the client application.Basically JMS to MQSeries RFh2 header translation is working fine but from MQSeries to JMS RFh2 header translation seems to have some issue.

Let me know your inputs.

Thanks & Regards,
Vinay


Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to