camel-cxf and synchronous vs. asynchronous endpoints

[Jens <sm...@dzbank.de>]

Hi,

I have a very simple route of the form

from("cxf:bean:router").to("cxf:bean:realEP?synchronous=true")

The "realEP" endpoint uses JMS. If the "router" endpoint uses HTTP things
work as expected (presumably because HTTP is synchronous by default) but if
the "router" endpoint is JMS as well (and therefore async by default) the
route "hangs" after calling the "realEP" and never returns the response to
the caller. Switching the "router" endpoint to synchronous operation as well
seems to fix that, but is this behaviour to be expected? Is there another
way to make it work?

Thanks,
Jens



--
View this message in context: http://camel.465427.n5.nabble.com/camel-cxf-and-synchronous-vs-asynchronous-endpoints-tp5733246.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camel-cxf and synchronous vs. asynchronous endpoints

[Willem Jiang <wi...@gmail.com>]

Hi 

It's a known issue, CXF jms transport doesn't support the asynchronous invocation well. 


发自我的 iPhone

在 2013-5-27，下午5:59，Jens <sm...@dzbank.de> 写道：

> Hi,
> 
> I have a very simple route of the form
> 
> from("cxf:bean:router").to("cxf:bean:realEP?synchronous=true")
> 
> The "realEP" endpoint uses JMS. If the "router" endpoint uses HTTP things
> work as expected (presumably because HTTP is synchronous by default) but if
> the "router" endpoint is JMS as well (and therefore async by default) the
> route "hangs" after calling the "realEP" and never returns the response to
> the caller. Switching the "router" endpoint to synchronous operation as well
> seems to fix that, but is this behaviour to be expected? Is there another
> way to make it work?
> 
> Thanks,
> Jens
> 
> 
> 
> --
> View this message in context: http://camel.465427.n5.nabble.com/camel-cxf-and-synchronous-vs-asynchronous-endpoints-tp5733246.html
> Sent from the Camel - Users mailing list archive at Nabble.com.