Hi
I think I figure out the problem.
Here is the scenario,
1 Start producers and consumers in server 1.
2 Send requests to first server, everything will be processed.
3 Start producers and consumers in server 2.
4 Send requests to first server, everything will be processed.
But if we send requests to second server,the message is processed at
CAMEL_ONE_QUEUE and reply is kept on CAMEL_ONE_QUEUE_REP
As first server's consumers are also listening to same reply queue, it's
processed by that consumers and it is ignoring with invalid correlation id.
Here is the log message :
WARN 06 Aug 2013 17:47:58,428
org.apache.camel.component.jms.reply.PersistentQueueReplyManager - Reply
received for unknown correlationID
[Camel-ID-fsschnd12298-2458-1375791411312-0-3]. The message will be ignored:
ActiveMQTextMessage {commandId = 167006, responseRequired = false, messageId
= ID:FSSCHN61-39193-1375789791590-1:3:93:1:1, originalDestination = null,
originalTransactionId = null, producerId =
ID:FSSCHN61-39193-1375789791590-1:3:93:1, destination =
queue://CAMEL_ONE_QUEUE_REP, transactionId = null, expiration = 0, timestamp
= 1375791482060, arrival = 0, brokerInTime = 1375791482061, brokerOutTime =
1375791482061, correlationId = Camel-ID-fsschnd12298-2458-1375791411312-0-3,
replyTo = queue://CAMEL_ONE_QUEUE_REP, persistent = true, type = null,
priority = 4, groupID = null, groupSequence = 0, targetConsumerId = null,
compressed = false, userID = null, content = null, marshalledProperties =
org.apache.activemq.util.ByteSequence@783d783d, dataStructure = null,
redeliveryCounter = 0, size = 0, properties = {CamelJmsDeliveryMode=2,
breadcrumbId=ID-fsschnd12298-2458-1375791411312-0-1}, readOnlyProperties =
true, readOnlyBody = true, droppable = false, text =
C1123454712345678901210000000201234}
Do we have to set prefetch for reply queue also ?
If yes how can we set ?
-----
Regards
kiran Reddy
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-Activemq-strange-behaviour-tp5736812p5736846.html
Sent from the Camel - Users mailing list archive at Nabble.com.
