I have a problem with Request/Reply over WebSphere MQ. Sitation is that the Request is comming from WMQ and has to go back to WMQ. Everything works fine, the message is handeld correctly as InOut, the reply is prepared but not sent to WMQ even if there is no exception or any hint for that in the trace.
It works with ActiveMQ instead of WMQ. What I've found out is that the header JMSReplyTo in the case of WMQ has the following pattern*: queue://[QueueManagerName]/[QueueName]?targetClient=1 It seems that the endpoint cannot cope with the QueueManagerName in the URI. I already have a WMQ specific DestinationResolver in place. I've also found out that the overriden method /public Destination resolveDestinationName(Session session, String destinationName, boolean isPubSubDomain)/ was never called for the ReplyDestination. Do you have any idea? Patrick * The mapping to the URI pattern with QueueManagerName works designed by IBM: http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.csqzaw.doc%2Fjm25500_.htm -- View this message in context: http://camel.465427.n5.nabble.com/WebSphere-MQ-Reply-tp5724835.html Sent from the Camel - Users mailing list archive at Nabble.com.
