On Tue, Feb 1, 2011 at 3:45 PM, tnk <[email protected]> wrote:
>
> <route id="ActiveMq_to_IBM">
> <from uri="activemq:queue:RESPONSE.TEST?disableReplyTo=true" />
> <setExchangePattern pattern="InOnly" />
> <convertBodyTo type="java.lang.String" />
> <recipientList>
> <!-- simple>${in.headers.RPL_TO_DST2}</simple-->
>
> <simple>ibmmq:queue://<qmngr>/<queueName>?targetClient=1</simple>
> </recipientList>
> </route>
>
I assume <qmngr>/<queueName> is something you have put to not reveal
the real name?
The naming of JMS destination shouldn't contain < > chars.
Also make sure the ibmmq bean is some IBM WebSphere component.
You should configure the ?targetClient=1 on the ibmmq instead.
So the expression is something like this:
<simple>ibmmq://queue:myManager/myQueue</simple>
There has been plenty of people around using IBM MQ with Camel. So you
should be able to search
and find previous talks how to do this.
> LOG:
>
> 17:07:04,984 | ERROR | tenerContainer-1 | EndpointMessageListener
> | rg.apache.camel.processor.Logger 248 | 68 -
> org.apache.camel.camel-core - 2.4.0
> .fuse-01-00 | Caused by:
> [org.apache.camel.ResolveEndpointFailedException - Failed to resolve
> endpoint: ibmmq://queue://<qmngr>/<queueName>?targetClient=1 due to:
> Failed to resolve endpoint:
> ibmmq://queue://<qmngr>/<queueName>?targetClient=1 due to: There are 1
> parameters
> that couldn't be set on the endpoint. Check the uri if the parameters
> are spelt correctly and that they are properties of the endpoint.
> Unknown parameters=[
> {targetClient=1}]]
> org.apache.camel.ResolveEndpointFailedException: Failed to resolve
> endpoint: ibmmq://queue://<qmngr>/<queueName>?targetClient=1 due to:
> Failed to resolve endpoint:
> ibmmq://queue://<qmngr>/<queueName>?targetClient=1 due to: There are 1
> parameters that couldn't be set on th
> e endpoint. Check the uri if the parameters are spelt correctly and
> that they are properties of the endpoint. Unknown
> parameters=[{targetClient=1}]
>
>
>
>
>
>
> On Tue, Feb 1, 2011 at 4:32 PM, Claus Ibsen-2 [via Camel]
> <[email protected]> wrote:
>> Hi
>>
>> Post the route configuration for the route which is supposed to do the
>> reply that fails with the targetClient.
>>
>>
>>
>> On Tue, Feb 1, 2011 at 3:27 PM, tnk <[hidden email]> wrote:
>>>
>>> Hello,
>>>
>>> I have several IBM MQ brokers, who are sending messages through MQ hub.
>>> Messages arriving to Camel have JMSReplyTo property of format
>>> queue://QManager/QueueName. I need to define two Camel routes: first route
>>> reads requests from MQ queue and puts messages to ActiveMQ
>>> (IBMMQ2ActiveMQ),
>>> and the seconds route takes response from ActiveMQ queue and sends back to
>>> IBM MQ (ActiveMQ2IBMMQ). Response message must be delivered to the same
>>> QManager, which sent the request.
>>> The first route IBMMQ2ActiveMQ works fine (it also stores JMSReplyTo value
>>> in message headers).
>>> The problem in with ActiveMQ2IBMMQ route. Messages are not delivered to
>>> IBM
>>> MQ. I am getting error:
>>> Failed to resolve endpoint: ibmmq://queue://<qmngr>/<queue>?targetClient=1
>>> due to:
>>> Failed to resolve endpoint: ibmmq://queue://<qmngr>/<queue>?targetClient=1
>>> due to: There are 1 parameters that couldn't be set on th
>>> e endpoint. Check the uri if the parameters are spelt correctly and that
>>> they are properties of the endpoint. Unknown parameters=[{targetClient=1}]
>>>
>>> (it is strange why camel puts too many "//" in ibmmq://queue://....)
>>>
>>> Without targetClient=1, error is returned:
>>> javax.jms.InvalidDestinationException: MQJMS2008: failed to open MQ queue
>>> <qmngr>/<queue>; nested exception is com.ibm.mq.MQExce
>>> ption: MQJE001: Completion Code 2, Reason 2085
>>>
>>> The test route, which justs returns the same message to IBM MQ works
>>> without
>>> problems:
>>> <route id="IMBMQ_echo">
>>> <from uri="ibmmq:queue:<queue>?useMessageIDAsCorrelationID=true" />
>>> <setExchangePattern pattern="InOut" />
>>> <convertBodyTo type="java.lang.String" />
>>> </route>
>>>
>>> Has anyone experienced similar problems and could help with solution?
>>> Is it possible, that camel can't handle endpoint with
>>> uri="ibmmq:queue://<qmngr>/<queue>"?
>>> Thanks.
>>> --
>>> View this message in context:
>>> http://camel.465427.n5.nabble.com/IBM-Websphere-MQ-Camel-routes-tp3366282p3366282.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: [hidden email]
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>>
>> ________________________________
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://camel.465427.n5.nabble.com/IBM-Websphere-MQ-Camel-routes-tp3366282p3366287.html
>> To unsubscribe from IBM Websphere MQ <--> Camel routes, click here.
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/IBM-Websphere-MQ-Camel-routes-tp3366282p3366318.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-----------------
FuseSource
Email: [email protected]
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
