Monday, 15 March 2010

cxf - Why does my camel route try to reply to the JMS consumer? -



cxf - Why does my camel route try to reply to the JMS consumer? -

i have apache camel route configured in spring takes message jms (activemq) queue, transforms message , uses cxf component send results web service. works fine exception thrown @ end of route cxf response object isn't synchronizable, referring fact it's trying convert exchange/message body jms message. why?

here's camel context extract:-

<route> <from uri="jms:queue:transactions" /> <process ref="converttoformatforcxf" /> <to uri="cxf:bean:myservice?defaultoperationname=process" /> <stop /> </route>

and here's snippet logs:-

endpointmessagelistener warn execution of jms message listener failed. caused by: [org.apache.camel.runtimecamelexception - java.lang.runtimeexception: net.sophis.soa.dataexchange.logoutresponse] org.apache.camel.runtimecamelexception: java.lang.runtimeexception: net.sophis.soa.dataexchange.logoutresponse @ org.apache.camel.util.objecthelper.wrapruntimecamelexception(objecthelper.java:1363) @ org.apache.camel.component.jms.endpointmessagelistener.onmessage(endpointmessagelistener.java:124)

even doesn't prevent stack trace. i've found out if add together disablereplyto=true jms consumer stacktrace doesn't show excellent.

i suppose i'm trying work out happening? cxf response object going added 'transactions' jms queue? intention flow stop 1 time cxf producer had completed.

can help understanding please? camel documentation wasn't much help on this.

was cxf response object going added 'transactions' jms queue?

no. have been added temporary queue.

from http://camel.apache.org/jms.html#jms-request-replyoverjms

the jmsproducer detects inout , provides jmsreplyto header reply destination used. default camel uses temporary queue, can utilize replyto alternative on endpoint specify fixed reply queue (see more below fixed reply queue). camel automatic setup consumer hear on reply queue, should not anything.

jms cxf apache-camel activemq

No comments:

Post a Comment