You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by MS <ma...@gmail.com> on 2015/05/08 13:38:05 UTC
QueueReplyManager - reply received for unknown correlationID
The idea is to create simple proxy with WS at one end and JMS(ActiveMQ) at
the other.
Use case goes like this:
1. send request using CXF endpoint
2. message is forwarded to activemq request queue
3. response is read from activemq response queue
4. received rsp. message is returned back to CXF endpoint as response
<route>
<from uri="cxf:bean:amqBridgeEndpoint" />
<transform>
<simple>${body[0]}</simple>
</transform>
<marshal ref="jxb"/>
<removeHeaders pattern="CamelHttp*"/>
<to
uri="activemq:queue:request?replyTo=response&replyToType=Exclusive" />
<unmarshal ref="jxb"/>
</route>
The route works but I also receive following WARN message:
reply.QueueReplyManager WARN Reply received for unknown
correlationID [Camel-ID-HR00089234-50027-1431082752364-0-6] on reply
destination [queue://response]. Current correlation map size: 0. The message
will be ignored: ActiveMQTextMessage
How did the message arrive at WS endpoint if this queue manager states that
it'll be ignored.
How can I resolve this issue (warning).
--
View this message in context: http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: QueueReplyManager - reply received for unknown correlationID
Posted by Claus Ibsen <cl...@gmail.com>.
If the correlation id do not match then the incoming message is dropped.
On Thu, May 14, 2015 at 9:28 AM, Henrique Viecili <vi...@gmail.com> wrote:
> Hi Claus,
>
> In this scenario, what would happen with the second message? Especially
> when the route uses a Shared Reply queue.
>
> Regards,
> Henrique Viecili
>
> Henrique Viecili
>
> On 13 May 2015 at 04:31, Claus Ibsen <cl...@gmail.com> wrote:
>
>> Hi
>>
>> If you get duplicate reply messages then it smells like the other
>> party is sending 2 reply messages with the same JMSCorrelationID.
>>
>> On Mon, May 11, 2015 at 10:11 AM, MS <ma...@gmail.com> wrote:
>> > These are some of the dependencies:
>> > mvn dependencies:list
>> >
>> > org.apache.activemq:activemq-broker:jar:5.11.1:compile
>> > org.apache.activemq:activemq-camel:jar:5.6.0:compile
>> > org.apache.activemq:activemq-client:jar:5.11.1:compile
>> > org.apache.activemq:activemq-core:jar:5.6.0:compile
>> > org.apache.activemq:activemq-kahadb-store:jar:5.11.1:compile
>> > org.apache.activemq:activemq-openwire-legacy:jar:5.11.1:compile
>> > org.apache.activemq:activemq-pool:jar:5.6.0:compile
>> > org.apache.activemq:activemq-spring:jar:5.11.1:compile
>> > org.apache.activemq:kahadb:jar:5.6.0:compile
>> > org.apache.activemq.protobuf:activemq-protobuf:jar:1.1:compile
>> > org.apache.camel:camel-core:jar:2.15.2:compile
>> > org.apache.camel:camel-cxf:jar:2.15.2:compile
>> > org.apache.camel:camel-cxf-transport:jar:2.15.2:compile
>> > org.apache.camel:camel-http:jar:2.15.2:compile
>> > org.apache.camel:camel-jaxb:jar:2.15.2:compile
>> > org.apache.camel:camel-jetty:jar:2.15.2:compile
>> > org.apache.camel:camel-jetty-common:jar:2.15.2:compile
>> > org.apache.camel:camel-jetty8:jar:2.15.2:compile
>> > org.apache.camel:camel-jms:jar:2.15.2:compile
>> > org.apache.camel:camel-spring:jar:2.15.2:compile
>> > org.apache.camel:camel-test:jar:2.15.2:compile
>> > org.apache.camel:camel-test-spring:jar:2.15.2:test
>> > org.apache.cxf:cxf-core:jar:3.0.1:compile
>> > org.apache.cxf:cxf-rt-bindings-soap:jar:3.0.1:compile
>> > org.apache.cxf:cxf-rt-bindings-xml:jar:3.0.4:compile
>> > org.apache.cxf:cxf-rt-databinding-jaxb:jar:3.0.1:compile
>> > org.apache.cxf:cxf-rt-features-clustering:jar:3.0.4:compile
>> > org.apache.cxf:cxf-rt-frontend-jaxrs:jar:3.0.4:compile
>> > org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.0.4:compile
>> > org.apache.cxf:cxf-rt-frontend-simple:jar:3.0.4:compile
>> > org.apache.cxf:cxf-rt-rs-client:jar:3.0.4:compile
>> > org.apache.cxf:cxf-rt-rs-security-oauth:jar:3.0.4:compile
>> > org.apache.cxf:cxf-rt-transports-http:jar:3.0.1:compile
>> > org.apache.cxf:cxf-rt-transports-http-jetty:jar:3.0.1:compile
>> > org.apache.cxf:cxf-rt-transports-jms:jar:3.0.1:compile
>> > org.apache.cxf:cxf-rt-ws-addr:jar:3.0.4:compile
>> > org.apache.cxf:cxf-rt-ws-policy:jar:3.0.4:compile
>> > org.apache.cxf:cxf-rt-wsdl:jar:3.0.1:compile
>> >
>> > I'm using external ActiveMQ instance version 5.11.1.
>> >
>> > Yes. this WARN is for every message sent to WS endpoint.
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856p5766955.html
>> > Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> Red Hat, Inc.
>> Email: cibsen@redhat.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>> hawtio: http://hawt.io/
>> fabric8: http://fabric8.io/
>>
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: QueueReplyManager - reply received for unknown correlationID
Posted by Henrique Viecili <vi...@gmail.com>.
Hi Claus,
In this scenario, what would happen with the second message? Especially
when the route uses a Shared Reply queue.
Regards,
Henrique Viecili
Henrique Viecili
On 13 May 2015 at 04:31, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> If you get duplicate reply messages then it smells like the other
> party is sending 2 reply messages with the same JMSCorrelationID.
>
> On Mon, May 11, 2015 at 10:11 AM, MS <ma...@gmail.com> wrote:
> > These are some of the dependencies:
> > mvn dependencies:list
> >
> > org.apache.activemq:activemq-broker:jar:5.11.1:compile
> > org.apache.activemq:activemq-camel:jar:5.6.0:compile
> > org.apache.activemq:activemq-client:jar:5.11.1:compile
> > org.apache.activemq:activemq-core:jar:5.6.0:compile
> > org.apache.activemq:activemq-kahadb-store:jar:5.11.1:compile
> > org.apache.activemq:activemq-openwire-legacy:jar:5.11.1:compile
> > org.apache.activemq:activemq-pool:jar:5.6.0:compile
> > org.apache.activemq:activemq-spring:jar:5.11.1:compile
> > org.apache.activemq:kahadb:jar:5.6.0:compile
> > org.apache.activemq.protobuf:activemq-protobuf:jar:1.1:compile
> > org.apache.camel:camel-core:jar:2.15.2:compile
> > org.apache.camel:camel-cxf:jar:2.15.2:compile
> > org.apache.camel:camel-cxf-transport:jar:2.15.2:compile
> > org.apache.camel:camel-http:jar:2.15.2:compile
> > org.apache.camel:camel-jaxb:jar:2.15.2:compile
> > org.apache.camel:camel-jetty:jar:2.15.2:compile
> > org.apache.camel:camel-jetty-common:jar:2.15.2:compile
> > org.apache.camel:camel-jetty8:jar:2.15.2:compile
> > org.apache.camel:camel-jms:jar:2.15.2:compile
> > org.apache.camel:camel-spring:jar:2.15.2:compile
> > org.apache.camel:camel-test:jar:2.15.2:compile
> > org.apache.camel:camel-test-spring:jar:2.15.2:test
> > org.apache.cxf:cxf-core:jar:3.0.1:compile
> > org.apache.cxf:cxf-rt-bindings-soap:jar:3.0.1:compile
> > org.apache.cxf:cxf-rt-bindings-xml:jar:3.0.4:compile
> > org.apache.cxf:cxf-rt-databinding-jaxb:jar:3.0.1:compile
> > org.apache.cxf:cxf-rt-features-clustering:jar:3.0.4:compile
> > org.apache.cxf:cxf-rt-frontend-jaxrs:jar:3.0.4:compile
> > org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.0.4:compile
> > org.apache.cxf:cxf-rt-frontend-simple:jar:3.0.4:compile
> > org.apache.cxf:cxf-rt-rs-client:jar:3.0.4:compile
> > org.apache.cxf:cxf-rt-rs-security-oauth:jar:3.0.4:compile
> > org.apache.cxf:cxf-rt-transports-http:jar:3.0.1:compile
> > org.apache.cxf:cxf-rt-transports-http-jetty:jar:3.0.1:compile
> > org.apache.cxf:cxf-rt-transports-jms:jar:3.0.1:compile
> > org.apache.cxf:cxf-rt-ws-addr:jar:3.0.4:compile
> > org.apache.cxf:cxf-rt-ws-policy:jar:3.0.4:compile
> > org.apache.cxf:cxf-rt-wsdl:jar:3.0.1:compile
> >
> > I'm using external ActiveMQ instance version 5.11.1.
> >
> > Yes. this WARN is for every message sent to WS endpoint.
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856p5766955.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8: http://fabric8.io/
>
Re: QueueReplyManager - reply received for unknown correlationID
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
If you get duplicate reply messages then it smells like the other
party is sending 2 reply messages with the same JMSCorrelationID.
On Mon, May 11, 2015 at 10:11 AM, MS <ma...@gmail.com> wrote:
> These are some of the dependencies:
> mvn dependencies:list
>
> org.apache.activemq:activemq-broker:jar:5.11.1:compile
> org.apache.activemq:activemq-camel:jar:5.6.0:compile
> org.apache.activemq:activemq-client:jar:5.11.1:compile
> org.apache.activemq:activemq-core:jar:5.6.0:compile
> org.apache.activemq:activemq-kahadb-store:jar:5.11.1:compile
> org.apache.activemq:activemq-openwire-legacy:jar:5.11.1:compile
> org.apache.activemq:activemq-pool:jar:5.6.0:compile
> org.apache.activemq:activemq-spring:jar:5.11.1:compile
> org.apache.activemq:kahadb:jar:5.6.0:compile
> org.apache.activemq.protobuf:activemq-protobuf:jar:1.1:compile
> org.apache.camel:camel-core:jar:2.15.2:compile
> org.apache.camel:camel-cxf:jar:2.15.2:compile
> org.apache.camel:camel-cxf-transport:jar:2.15.2:compile
> org.apache.camel:camel-http:jar:2.15.2:compile
> org.apache.camel:camel-jaxb:jar:2.15.2:compile
> org.apache.camel:camel-jetty:jar:2.15.2:compile
> org.apache.camel:camel-jetty-common:jar:2.15.2:compile
> org.apache.camel:camel-jetty8:jar:2.15.2:compile
> org.apache.camel:camel-jms:jar:2.15.2:compile
> org.apache.camel:camel-spring:jar:2.15.2:compile
> org.apache.camel:camel-test:jar:2.15.2:compile
> org.apache.camel:camel-test-spring:jar:2.15.2:test
> org.apache.cxf:cxf-core:jar:3.0.1:compile
> org.apache.cxf:cxf-rt-bindings-soap:jar:3.0.1:compile
> org.apache.cxf:cxf-rt-bindings-xml:jar:3.0.4:compile
> org.apache.cxf:cxf-rt-databinding-jaxb:jar:3.0.1:compile
> org.apache.cxf:cxf-rt-features-clustering:jar:3.0.4:compile
> org.apache.cxf:cxf-rt-frontend-jaxrs:jar:3.0.4:compile
> org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.0.4:compile
> org.apache.cxf:cxf-rt-frontend-simple:jar:3.0.4:compile
> org.apache.cxf:cxf-rt-rs-client:jar:3.0.4:compile
> org.apache.cxf:cxf-rt-rs-security-oauth:jar:3.0.4:compile
> org.apache.cxf:cxf-rt-transports-http:jar:3.0.1:compile
> org.apache.cxf:cxf-rt-transports-http-jetty:jar:3.0.1:compile
> org.apache.cxf:cxf-rt-transports-jms:jar:3.0.1:compile
> org.apache.cxf:cxf-rt-ws-addr:jar:3.0.4:compile
> org.apache.cxf:cxf-rt-ws-policy:jar:3.0.4:compile
> org.apache.cxf:cxf-rt-wsdl:jar:3.0.1:compile
>
> I'm using external ActiveMQ instance version 5.11.1.
>
> Yes. this WARN is for every message sent to WS endpoint.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856p5766955.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: QueueReplyManager - reply received for unknown correlationID
Posted by MS <ma...@gmail.com>.
These are some of the dependencies:
mvn dependencies:list
org.apache.activemq:activemq-broker:jar:5.11.1:compile
org.apache.activemq:activemq-camel:jar:5.6.0:compile
org.apache.activemq:activemq-client:jar:5.11.1:compile
org.apache.activemq:activemq-core:jar:5.6.0:compile
org.apache.activemq:activemq-kahadb-store:jar:5.11.1:compile
org.apache.activemq:activemq-openwire-legacy:jar:5.11.1:compile
org.apache.activemq:activemq-pool:jar:5.6.0:compile
org.apache.activemq:activemq-spring:jar:5.11.1:compile
org.apache.activemq:kahadb:jar:5.6.0:compile
org.apache.activemq.protobuf:activemq-protobuf:jar:1.1:compile
org.apache.camel:camel-core:jar:2.15.2:compile
org.apache.camel:camel-cxf:jar:2.15.2:compile
org.apache.camel:camel-cxf-transport:jar:2.15.2:compile
org.apache.camel:camel-http:jar:2.15.2:compile
org.apache.camel:camel-jaxb:jar:2.15.2:compile
org.apache.camel:camel-jetty:jar:2.15.2:compile
org.apache.camel:camel-jetty-common:jar:2.15.2:compile
org.apache.camel:camel-jetty8:jar:2.15.2:compile
org.apache.camel:camel-jms:jar:2.15.2:compile
org.apache.camel:camel-spring:jar:2.15.2:compile
org.apache.camel:camel-test:jar:2.15.2:compile
org.apache.camel:camel-test-spring:jar:2.15.2:test
org.apache.cxf:cxf-core:jar:3.0.1:compile
org.apache.cxf:cxf-rt-bindings-soap:jar:3.0.1:compile
org.apache.cxf:cxf-rt-bindings-xml:jar:3.0.4:compile
org.apache.cxf:cxf-rt-databinding-jaxb:jar:3.0.1:compile
org.apache.cxf:cxf-rt-features-clustering:jar:3.0.4:compile
org.apache.cxf:cxf-rt-frontend-jaxrs:jar:3.0.4:compile
org.apache.cxf:cxf-rt-frontend-jaxws:jar:3.0.4:compile
org.apache.cxf:cxf-rt-frontend-simple:jar:3.0.4:compile
org.apache.cxf:cxf-rt-rs-client:jar:3.0.4:compile
org.apache.cxf:cxf-rt-rs-security-oauth:jar:3.0.4:compile
org.apache.cxf:cxf-rt-transports-http:jar:3.0.1:compile
org.apache.cxf:cxf-rt-transports-http-jetty:jar:3.0.1:compile
org.apache.cxf:cxf-rt-transports-jms:jar:3.0.1:compile
org.apache.cxf:cxf-rt-ws-addr:jar:3.0.4:compile
org.apache.cxf:cxf-rt-ws-policy:jar:3.0.4:compile
org.apache.cxf:cxf-rt-wsdl:jar:3.0.1:compile
I'm using external ActiveMQ instance version 5.11.1.
Yes. this WARN is for every message sent to WS endpoint.
--
View this message in context: http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856p5766955.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: QueueReplyManager - reply received for unknown
correlationID
Posted by Willem Jiang <wi...@gmail.com>.
Can you show us the camel route that you have?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On May 11, 2015 at 4:46:02 PM, MS (matija.slivonja@gmail.com) wrote:
> CXF uses Http transport. Message is afterwords forwarded to ActiveMQ request
> queue.
> After response is read from 'response' queue message is relayed back to WS
> endpoint.
>
> > serviceClass="proxy.bridge.amq.AmqBridgePortType"
> address="http://localhost:{{port}}/bridge/amq"
> wsdlURL="wsdl/amq-bridge.wsdl"
> endpointName="s:amqBridge"
> serviceName="s:BridgeService"
> xmlns:s="http://proxy/bridge/amq"/>
>
>
> > class="org.apache.activemq.ActiveMQConnectionFactory">
> > />
>
>
> > class="org.apache.camel.component.jms.JmsConfiguration">
>
>
>
>
> > class="org.apache.activemq.camel.component.ActiveMQComponent">
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856p5766956.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
Re: QueueReplyManager - reply received for unknown correlationID
Posted by MS <ma...@gmail.com>.
CXF uses Http transport. Message is afterwords forwarded to ActiveMQ request
queue.
After response is read from 'response' queue message is relayed back to WS
endpoint.
<cxf:cxfEndpoint id="amqBridgeEndpoint"
serviceClass="proxy.bridge.amq.AmqBridgePortType"
address="http://localhost:{{port}}/bridge/amq"
wsdlURL="wsdl/amq-bridge.wsdl"
endpointName="s:amqBridge"
serviceName="s:BridgeService"
xmlns:s="http://proxy/bridge/amq"/>
<bean id="jmsConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="tcp://${amq.hostname}:${amq.port}"
/>
</bean>
<bean id="jmsConfig"
class="org.apache.camel.component.jms.JmsConfiguration">
<property name="connectionFactory" ref="jmsConnectionFactory" />
<property name="concurrentConsumers" value="10"/>
</bean>
<bean id="activemq"
class="org.apache.activemq.camel.component.ActiveMQComponent">
<property name="configuration" ref="jmsConfig"/>
</bean>
--
View this message in context: http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856p5766956.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: QueueReplyManager - reply received for unknown
correlationID
Posted by Willem Jiang <wi...@gmail.com>.
The CorrelationID is quite important when the message exchange pattern is InOut.
What’s the transport that you use in CXF endpoint?
If it uses the JMS transport, I guess that could cause some trouble in your route.
Regards,
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On May 11, 2015 at 8:14:38 AM, Henrique Viecili (viecili@gmail.com) wrote:
> Is there any documentation about uncorrelated messages sent to reply
> destinations?
>
> How does it behave when the reply destination is shared/exclusive/temporary?
>
> Regards,
> Henrique Viecili
>
> Henrique Viecili
>
> On 9 May 2015 at 16:54, Claus Ibsen wrote:
>
> > Hi
> >
> > What Camel and AMQ version do you use?
> >
> > And do you see this WARN for every request/reply you do? eg it seems
> > as if you get a duplicate message?
> >
> >
> > On Fri, May 8, 2015 at 1:38 PM, MS wrote:
> > > The idea is to create simple proxy with WS at one end and JMS(ActiveMQ)
> > at
> > > the other.
> > > Use case goes like this:
> > > 1. send request using CXF endpoint
> > > 2. message is forwarded to activemq request queue
> > > 3. response is read from activemq response queue
> > > 4. received rsp. message is returned back to CXF endpoint as response
> > >
> > >
> > >
> > >
> > >
> > > ${body[0]}
> > >
> > >
> > >
> > >
> > > > > > uri="activemq:queue:request?replyTo=response&replyToType=Exclusive"
> > />
> > >
> > >
> > >
> > >
> > > The route works but I also receive following WARN message:
> > > reply.QueueReplyManager WARN Reply received for unknown
> > > correlationID [Camel-ID-HR00089234-50027-1431082752364-0-6] on reply
> > > destination [queue://response]. Current correlation map size: 0. The
> > message
> > > will be ignored: ActiveMQTextMessage
> > >
> > > How did the message arrive at WS endpoint if this queue manager states
> > that
> > > it'll be ignored.
> > > How can I resolve this issue (warning).
> > >
> > >
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856.html
> > > Sent from the Camel - Users mailing list archive at Nabble.com.
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > Email: cibsen@redhat.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
> > hawtio: http://hawt.io/
> > fabric8: http://fabric8.io/
> >
>
Re: QueueReplyManager - reply received for unknown correlationID
Posted by Henrique Viecili <vi...@gmail.com>.
Is there any documentation about uncorrelated messages sent to reply
destinations?
How does it behave when the reply destination is shared/exclusive/temporary?
Regards,
Henrique Viecili
Henrique Viecili
On 9 May 2015 at 16:54, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> What Camel and AMQ version do you use?
>
> And do you see this WARN for every request/reply you do? eg it seems
> as if you get a duplicate message?
>
>
> On Fri, May 8, 2015 at 1:38 PM, MS <ma...@gmail.com> wrote:
> > The idea is to create simple proxy with WS at one end and JMS(ActiveMQ)
> at
> > the other.
> > Use case goes like this:
> > 1. send request using CXF endpoint
> > 2. message is forwarded to activemq request queue
> > 3. response is read from activemq response queue
> > 4. received rsp. message is returned back to CXF endpoint as response
> >
> >
> > <route>
> > <from uri="cxf:bean:amqBridgeEndpoint" />
> > <transform>
> > <simple>${body[0]}</simple>
> > </transform>
> > <marshal ref="jxb"/>
> >
> > <removeHeaders pattern="CamelHttp*"/>
> > <to
> > uri="activemq:queue:request?replyTo=response&replyToType=Exclusive"
> />
> >
> > <unmarshal ref="jxb"/>
> > </route>
> >
> > The route works but I also receive following WARN message:
> > reply.QueueReplyManager WARN Reply received for unknown
> > correlationID [Camel-ID-HR00089234-50027-1431082752364-0-6] on reply
> > destination [queue://response]. Current correlation map size: 0. The
> message
> > will be ignored: ActiveMQTextMessage
> >
> > How did the message arrive at WS endpoint if this queue manager states
> that
> > it'll be ignored.
> > How can I resolve this issue (warning).
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> Email: cibsen@redhat.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
> hawtio: http://hawt.io/
> fabric8: http://fabric8.io/
>
Re: QueueReplyManager - reply received for unknown correlationID
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
What Camel and AMQ version do you use?
And do you see this WARN for every request/reply you do? eg it seems
as if you get a duplicate message?
On Fri, May 8, 2015 at 1:38 PM, MS <ma...@gmail.com> wrote:
> The idea is to create simple proxy with WS at one end and JMS(ActiveMQ) at
> the other.
> Use case goes like this:
> 1. send request using CXF endpoint
> 2. message is forwarded to activemq request queue
> 3. response is read from activemq response queue
> 4. received rsp. message is returned back to CXF endpoint as response
>
>
> <route>
> <from uri="cxf:bean:amqBridgeEndpoint" />
> <transform>
> <simple>${body[0]}</simple>
> </transform>
> <marshal ref="jxb"/>
>
> <removeHeaders pattern="CamelHttp*"/>
> <to
> uri="activemq:queue:request?replyTo=response&replyToType=Exclusive" />
>
> <unmarshal ref="jxb"/>
> </route>
>
> The route works but I also receive following WARN message:
> reply.QueueReplyManager WARN Reply received for unknown
> correlationID [Camel-ID-HR00089234-50027-1431082752364-0-6] on reply
> destination [queue://response]. Current correlation map size: 0. The message
> will be ignored: ActiveMQTextMessage
>
> How did the message arrive at WS endpoint if this queue manager states that
> it'll be ignored.
> How can I resolve this issue (warning).
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/QueueReplyManager-reply-received-for-unknown-correlationID-tp5766856.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/