You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by prueegg <pa...@raiffeisen.ch> on 2013/01/03 15:12:42 UTC
WebSphere MQ Reply
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.
Re: WebSphere MQ Reply
Posted by prueegg <pa...@raiffeisen.ch>.
Hi Claus
I'm using 2.10.1.
Since I saw, that there was a fix [ CAMEL-5464
<https://issues.apache.org/jira/browse/CAMEL-5464> ] in 2.10.3 dealing with
jms replies I tried also with 2.10.3 with the same result.
Today I will enable the debug log, to get more information about it.
I'll post as soon as I have more information.
Patrick
--
View this message in context: http://camel.465427.n5.nabble.com/WebSphere-MQ-Reply-tp5724835p5725029.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: WebSphere MQ Reply
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
What version of Camel do you use?
On Thu, Jan 3, 2013 at 3:12 PM, prueegg <pa...@raiffeisen.ch> wrote:
> 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.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen