camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nigel <nigel.long...@pimco.com>
Subject SJMS component and IBM Websphere MQ quirks
Date Mon, 30 Sep 2013 18:33:17 GMT
Guys,
I've bumped into a bug using sjms with IBM MQ. All works fine using topics,
but with queues my reply messages are rejected as with a 2027 error (no
reply destination).  One of the MQ headers is the JMS_IBM_MsgType, which,
because the incoming message wants a reply, is of type MQMT_REQUEST. IBM
expects messages of this type to have the JMSReplyTo property set as well.
The SJMS component doesn't copy the replyTo property from the exchange
headers to the reply message and so causes the exception. Looking at the JMS
component I see that it copies the reply destination into the reply and all
the other MQ specific headers, so it works - however it makes no sense to
copy the reply into the reply! Anyhow I thought I'd try adding a
headerFilterStrategy to remove all the IBM specific properties - but alas it
seems the SJMS component doesn't actually use the filter anywhere. 
Is there an alternative approach. My other hack was to force the
JMS_IBM_MsgType to 2 in the reply (which is what IBM wants it to be
(http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/index.jsp?topic=%2Fcom.ibm.mq.msc.doc%2Fprp_jms_ibm_msgtype.html).

Cheers
Nigel
BTW - I much prefer the sjms over the jms - had weird infinite loops when an
app sends a message to one of its own queues wanting a reply - I suspect
this is due to the reply destination copying!!!



--
View this message in context: http://camel.465427.n5.nabble.com/SJMS-component-and-IBM-Websphere-MQ-quirks-tp5740588.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message