Hi
You can set a custom JMSCorrelationID which is 24 chars or less. Just
add it as a Camel Header.
In the future you can plugin a different UUID generator and have one
which comply with 24 chars or less.
On Wed, May 26, 2010 at 3:46 PM, omarito wrote:
>
> Hi Claus,
>
> The MQ version that we a
Hi Claus,
The MQ version that we are using is 6.1.
I thing this is not a restriction in JMS but in IBM MQ itself. I didn't add
this in the first post but the communication is from a JMS client to a non
JMS MQ. Using a destination resolver I was able to add this property on the
destination queue
Hi
I spoke to a couple of AMQ committers and they do not recall any
restrictions etc on the length of the correlation ID in the JMS spec.
So why would IBM restrict it to only 24 chars?
Do you know of any such restrictions in the JMS spec?
And do you have a link to some online IBM docs which spec
The exchange pattern that I am using is InOut in the JMS Endpoint. My route
basically recieves a byte[] from a mina endpoin, transform the data, prepare
the data, send it to MQ thorugh JMS endpoint, do som postprocessing after
receiving the data from MQ and return it back through mina endpoint.
Can I have a look at your camel route configure?
What's your message exchange pattern ?
Willem
omarito wrote:
HI to all,
I am having some difficulties getting back the response received on the
ReplyTo queue from our Websphere MQ Server. Using the MQ explorer I see the
message in the ReplyTo que
