Looks quite weird. Did you change the thread pool setting so that not enough thread are available to service the request ? Also, is there anything before of after this log entry ?
On Fri, Sep 12, 2008 at 11:52 AM, raulvk.soa <[EMAIL PROTECTED]> wrote: > > Hi everyone, > > After having experimented with cxf:consumer, http:consumer and > http:soap-consumer, switching the useJbiWrapper attribute on and off to > check the outcume, I have decided I like the behaviour of the > http:soap-consumer because it only forwards the actual message when > useJbiWrapper=false. > > However, when testing my config, it turns out that the message is not > forwarded on to the specified JBI endpoint. The SOAP consumer receives the > message and prints the following line on the log: > > 10:36:04,478 | DEBUG - > org.apache.servicemix.http.jetty.JettyContextManager$ThreadPoolWrapper - > Dispatching job: [EMAIL PROTECTED],io=0,w=true,b=false|false] > > But that's all! It doesn't forward the message to the specified JBI endpoint > on the targetService attribute. > > The config I am using is the following: > > <http:soap-consumer service="xxx:ChannelService" > > endpoint="ChannelServiceSOAP" > > targetService="xxxjbi:camelFlow" > > locationURI="http://localhost:8192/ChannelService"; > > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; > useJbiWrapper="false" > > wsdl="file:///D:/Resources/ChannelService/definition.wsdl" > /> > > There is a Camel flow listening on xxxjbi:camelFlow. > > If I browse to http://localhost:8192/ChannelService?wsdl, I get the WSDL > correctly. > > Any ideas? > > Thanks! > -- > View this message in context: > http://www.nabble.com/http%3Asoap-consumer-doesn%27t-send-message-forward-tp19452824p19452824.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
