It looks like a bug of camel-cxf component. Can you submit a simple test case to the JIRA[1] so we can keep digging the issue.
BTW, you can disable the async invocation by setting the option "synchronous=false" [1]http://issues.apache.org/jira/browse/CAMEL -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Wednesday, April 10, 2013 at 6:58 AM, Smith-John wrote: > Hi, > > I have a strange (at least for me) issue with my route respectively the cxf > component in it. > > The route looks like > from("cxf:XXX?wsdlURL=YYY&...")....to(...)...to("cxf:${header[ReplyTo]}?wsdlURL=YYY&..."); > > I get a one way SOAP message, do some work with it and send a response back > to the callback address specified. > > In principle this works perfect. > But sending requests with a short interval, I would say less than 5 seconds > between the requests, the messaging fails. > Sending requests every > 5 seconds: no problem. > Sending requests with time between them < 5 seconds: all except the first > one fail. > > I'm using camel 2.10.4 and for sending the requests SoapUI. > > Unfortunately the console shows no errors. The only difference between a > working and a not working try is the last DEBUG notification that is > [default-workqueue-1] DEBUG o.a.c.c.cxf.CxfClientCallback - > default-workqueue-1 calling handleResponse > for a working one and > [default-workqueue-2] DEBUG o.a.c.c.cxf.CxfClientCallback - > default-workqueue-2 calling handleException > for a failing one. > > Is this a bug or normal behaviour? Is there something to prevent this? > > Best regards. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/cxf-producer-needs-a-break-tp5730612.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
