Hi.

We are sending a 'heart beat' on a JMS topic with am OutOnly publisher. This
results in local  log WARNs for related messages. Are we configuring this
incorrectly or how can we avoid these problems?

Many thanks. / m



The route is defined/initialized as             

from(from).setExchangePattern(pattern).threads(poolSize).process(xmlProcessor_).to(to)
.setId(routeId);

with:
            pattern = ExchangePattern.OutOnly;
            from = "direct:local_" + UUID.randomUUID().toString();
            to = route_; // some JMS destination queue/topic
            producer_ = camelCtx_.createProducerTemplate();
            destination_ = from; // Send to direct endpoint. Camel takes it from
there...

At runtime we see the following in the log (mixed camel/implementation):

2011-02-02 19:06:36,488 | DEBUG | e.bus.connector.camel.CamelInterfaceImpl |
send             | tion_data_broker | [esbStatusPublisher] Publishing
[OutOnly:
direct:local_44bfccc7-5e1b-4a08-be3e-e9723868c7d9/jms:topic:esb_topic_status/EsbStatus]
2011-02-02 19:06:36,488 | DEBUG | org.apache.camel.impl.ProducerCache      |
doInProducer     | tion_data_broker | >>>>
Endpoint[direct://local_44bfccc7-5e1b-4a08-be3e-e9723868c7d9]
Exchange[Message: EsbMessage[id=f5de05ef-6ceb-49a7-b634-b032015a41e2,...]]
2011-02-02 19:06:36,489 | DEBUG | ra.fi.mbs.esb.core.bus.util.XmlProcessor |
process          | read 2 - Threads | [esbStatusPublisher_context] in(obj):
EsbMessage[id=f5de05ef-6ceb-49a7-b634-b032015a41e2,...]
2011-02-02 19:06:36,492 | DEBUG | org.apache.camel.processor.SendProcessor |
oInAsyncProducer | read 2 - Threads | >>>>
Endpoint[jms://topic:esb_topic_status] Exchange[Message: <?xml version="1.0"
encoding="UTF-8" standalone="yes"?><ns2:EsbMessage ... ... [Body clipped
after 1000 chars, total length is 1854]]
2011-02-02 19:06:36,493 | DEBUG | nt.jms.JmsConfiguration$CamelJmsTemplate |
execute          | read 2 - Threads | Executing callback on JMS Session:
Cached JMS Session: com.tibco.tibjms.TibjmsxSessionImp@84cc70e

Now actually sending... Why is the JMSDestination = null and why is there a
ReplyTo on an OutOnly message?
2011-02-02 19:06:36,493 | DEBUG | nt.jms.JmsConfiguration$CamelJmsTemplate |
doSend           | read 2 - Threads | Sending JMS message to:
Topic[esb_topic_status] with message: TextMessage={ Header={
JMSMessageID={null} JMSDestination={null}
JMSReplyTo={Queue[$TMP$.EMS-JUSD-FIANALYTICS1.2E124CDB255A38FBC.2]}
JMSDeliveryMode={PERSISTENT} JMSRedelivered={false}
JMSCorrelationID={ID-njfidevapp13-37121-1296691575036-1-6} JMSType={null}
JMSTimestamp={0} JMSExpiration={0} JMSPriority={4} } Properties={ }
Text={<?xml version="1.0" encoding="UTF-8"
standalone="yes"?><ns2:EsbMessage... </ns2:EsbMessage>} }

Now a listener, which we did not explicitly start is receiving the message
locally:
2011-02-02 19:06:36,502 | DEBUG | ent.jms.reply.TemporaryQueueReplyManager |
onMessage        | tenerContainer-1 | Received reply message with
correlationID: ID-njfidevapp13-37121-1296691575036-1-6 -> ObjectMessage={
Header={ JMSMessageID={ID:EMS-JUSD-FIANALYTICS1.2E124CDB255A38D8D:2444}
JMSDestination={Queue[$TMP$.EMS-JUSD-FIANALYTICS1.2E124CDB255A38FBC.2]}
JMSReplyTo={Queue[$TMP$.EMS-JUSD-FIANALYTICS1.2E124CDB255A38FBC.2]}
JMSDeliveryMode={PERSISTENT} JMSRedelivered={false}
JMSCorrelationID={ID-njfidevapp13-37121-1296691575036-1-6} JMSType={null}
JMSTimestamp={Wed Feb 02 19:06:36 EST 2011} JMSExpiration={0}
JMSPriority={4} } Properties={ CamelJmsDeliveryMode={Integer:2} }
Object={EsbMessage[id=f5de05ef-6ceb-49a7-b634-b032015a41e2,...]} }
2011-02-02 19:06:36,507 | DEBUG | ent.jms.reply.TemporaryQueueReplyManager |
processReply     | tenerContainer-1 | Reply received. Setting reply as OUT
message: EsbMessage[id=f5de05ef-6ceb-49a7-b634-b032015a41e2,...]
2011-02-02 19:06:36,749 | DEBUG | ent.jms.reply.TemporaryQueueReplyManager |
onMessage        | tenerContainer-1 | Received reply message with
correlationID: ID-njfidevapp13-37121-1296691575036-1-6 -> ObjectMessage={
Header={ JMSMessageID={ID:EMS-JUSD-FIANALYTICS1.2E124CDB255A3233E:91266}
JMSDestination={Queue[$TMP$.EMS-JUSD-FIANALYTICS1.2E124CDB255A38FBC.2]}
JMSReplyTo={Queue[$TMP$.EMS-JUSD-FIANALYTICS1.2E124CDB255A38FBC.2]}
JMSDeliveryMode={PERSISTENT} JMSRedelivered={false}
JMSCorrelationID={ID-njfidevapp13-37121-1296691575036-1-6} JMSType={null}
JMSTimestamp={Wed Feb 02 19:06:36 EST 2011} JMSExpiration={0}
JMSPriority={4} } Properties={ CamelJmsDeliveryMode={Integer:2} }
Object={EsbMessage[id=f5de05ef-6ceb-49a7-b634-b032015a41e2,...]} }

And finally unknown correlationID:
2011-02-02 19:06:36,752 | WARN  | ent.jms.reply.TemporaryQueueReplyManager |
ndleReplyMessage | tenerContainer-1 | Reply received for unknown
correlationID [ID-njfidevapp13-37121-1296691575036-1-6] -> ObjectMessage={
Header={ JMSMessageID={ID:EMS-JUSD-FIANALYTICS1.2E124CDB255A3233E:91266}
JMSDestination={Queue[$TMP$.EMS-JUSD-FIANALYTICS1.2E124CDB255A38FBC.2]}
JMSReplyTo={Queue[$TMP$.EMS-JUSD-FIANALYTICS1.2E124CDB255A38FBC.2]}
JMSDeliveryMode={PERSISTENT} JMSRedelivered={false}
JMSCorrelationID={ID-njfidevapp13-37121-1296691575036-1-6} JMSType={null}
JMSTimestamp={Wed Feb 02 19:06:36 EST 2011} JMSExpiration={0}
JMSPriority={4} } Properties={ CamelJmsDeliveryMode={Integer:2} }
Object={EsbMessage[id=f5de05ef-6ceb-49a7-b634-b032015a41e2,...]} }



-- 
View this message in context: 
http://camel.465427.n5.nabble.com/After-publish-OutOnly-Reply-received-for-unknown-correlationID-tp3368679p3368679.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to