Hello,
I am using camel version 2.10.0.redhat-60024 ( the redhat version of the jar
) and jboss-a-mq-6.2.0.redhat-133 as my JMS provider and trying to do a
simple request reply pattern with the following two routes
*Producer side*
from(endPointUrl).routeId("2")
.setHeader
>From my study of literature, as long as there is a JMSReplyTo set in the
header of the JMS message, there is nothing special that needs to be done on
the subscribe side. and also the mssage is making back to the output, just
that the producer sent the message after it timed out.
--
View this me
I am pretty sure, since I traced the message at all the 3 hops and ensured it
has the same correlation id
1. tracer on the producer side
2. On the AMQ console
3. tracer on the consumer side
It might be a misleading exception, also, the same thing works if I use an
instantiated connection factory v
After going through with a fine tooth comb, I think the issue might be the
instance of connection factory. The only difference between your test case
and what I am doing is that I am getting the connection factory by doing a
jndi lookup on a resource adapter that is configured in my jboss j2ee
cont
