You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Florent <fl...@sopragroup.com> on 2007/12/19 15:39:32 UTC
servicemix-cxf-bc DeliveryChannel - Waiting for exchange to be
answered
Hello,
I'm sometimes getting an error when using cxf-bc as a bridge : i got a main
class, doing a few service calls (most of the time, the call is OK).
Servicemix log :
DEBUG - CxfBcComponent - Received exchange: status: Done,
role:provider
DEBUG - CxfBcComponent - Retrieved correlation id:
ID:172.xx.xxx.xxx-116f2ba0394-4:59
DEBUG - DeliveryChannelImpl - Notified:
ID:172.xx.xxx.xxx-116f2ba0394-4:60(e95c63) in
DeliveryChannel{servicemix-cxf-bc} from sendSync
DEBUG - DeliveryChannelImpl - Exchange
ID:172.xx.xxx.xxx-116f2ba0394-4:60 has been aborted
19 dÚc. 2007 15:23:46 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
INFO: Interceptor has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault
at
org.apache.servicemix.cxfbc.CxfBcConsumer$JbiPostInvokerInterceptor.handleMessage(CxfBcConsumer.java:454)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207)
at
org.apache.cxf.phase.PhaseInterceptorChain.resume(PhaseInterceptorChain.java:184)
at
org.apache.servicemix.cxfbc.CxfBcConsumer.process(CxfBcConsumer.java:183)
at
org.apache.servicemix.cxfbc.CxfBcConsumer$JbiInvokerInterceptor.handleMessage(CxfBcConsumer.java:430)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:297)
at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:243)
at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:54)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:722)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:324)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:730)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
19 dÚc. 2007 15:23:46
org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose
INFO: Outbound Message
---------------------------
Encoding:
Headers: <soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Fault
occurred while
processing.</faultstring></soap:Fault></soap:Body></soap:Envelope>
--------------------------------------
Any idea about this error?
It's looks like an error due to a timeout...
Best regards,
Florent.
--
View this message in context: http://www.nabble.com/servicemix-cxf-bc-DeliveryChannel---Waiting-for-exchange-to-be-answered-tp14418096s12049p14418096.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: servicemix-cxf-bc DeliveryChannel - Waiting for exchange to be
answered
Posted by Florent <fl...@sopragroup.com>.
Hi again,
WAS & ServiceMix are now running on a dedicated AIX server. Previously, they
were both running on my own computer (Windows XP).
I've done thousands of sequential calls, but i didn't even get the error a
single time...
But i got the following error many times :
java.lang.IllegalStateException: component is not owner
at
org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setMessage(MessageExchangeImpl.java:338)
at
org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageObserver.java:131)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1957)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1791)
at
org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:166)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:167)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:797)
Followed by the "classic" :
javax.jbi.messaging.MessagingException: Out not supported
at
org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setMessage(MessageExchangeImpl.java:357)
at
org.apache.servicemix.cxfbc.CxfBcProviderMessageObserver.onMessage(CxfBcProviderMessageObserver.java:131)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1957)
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1791)
at
org.apache.servicemix.cxfbc.CxfBcProvider.process(CxfBcProvider.java:166)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:538)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:490)
at
org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:610)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:170)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:167)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:797)
I also got this error on Windows.
Anyway, my DTO is correctly built : so the response message seems to be
correctly sent.
The error seems to be occurring during the "send / accept done status".
Any idea about it?
Btw, there is no error in WAS log.
Best regards,
Florent.
Florent wrote:
>
>
> Hi Freeman,
>
> There is no error log in my AS. And i got this error may be once every 5
> calls.
> I'll do a few more test today : i'm currently running WAS + servicemix on
> my own computer; i'll install my app & servicemix on a dedicated server.
>
> Btw, i'm using Webpshere AS 6.1.
>
> Best regards,
> Florent.
>
>
> Freeman Fang-2 wrote:
>>
>> Hi Florent,
>> Quick question, when you see this error in servicemix, can you see any
>> error log in your weblogic server?
>> Thanks
>>
>> Freeman
>>
>> Florent wrote:
>>> Hello,
>>>
>>> I'm sometimes getting an error when using cxf-bc as a bridge : i got a
>>> main
>>> class, doing a few service calls (most of the time, the call is OK).
>>>
>>> Servicemix log :
>>>
>>> DEBUG - CxfBcComponent - Received exchange: status:
>>> Done,
>>> role:provider
>>> DEBUG - CxfBcComponent - Retrieved correlation id:
>>> ID:172.xx.xxx.xxx-116f2ba0394-4:59
>>> DEBUG - DeliveryChannelImpl - Notified:
>>> ID:172.xx.xxx.xxx-116f2ba0394-4:60(e95c63) in
>>> DeliveryChannel{servicemix-cxf-bc} from sendSync
>>> DEBUG - DeliveryChannelImpl - Exchange
>>> ID:172.xx.xxx.xxx-116f2ba0394-4:60 has been aborted
>>> 19 dÚc. 2007 15:23:46 org.apache.cxf.phase.PhaseInterceptorChain
>>> doIntercept
>>> INFO: Interceptor has thrown exception, unwinding now
>>> org.apache.cxf.interceptor.Fault
>>> at
>>> org.apache.servicemix.cxfbc.CxfBcConsumer$JbiPostInvokerInterceptor.handleMessage(CxfBcConsumer.java:454)
>>> at
>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207)
>>> at
>>> org.apache.cxf.phase.PhaseInterceptorChain.resume(PhaseInterceptorChain.java:184)
>>> at
>>> org.apache.servicemix.cxfbc.CxfBcConsumer.process(CxfBcConsumer.java:183)
>>> at
>>> org.apache.servicemix.cxfbc.CxfBcConsumer$JbiInvokerInterceptor.handleMessage(CxfBcConsumer.java:430)
>>> at
>>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207)
>>> at
>>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
>>> at
>>> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:297)
>>> at
>>> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:243)
>>> at
>>> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:54)
>>> at
>>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:722)
>>> at
>>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
>>> at
>>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
>>> at org.mortbay.jetty.Server.handle(Server.java:324)
>>> at
>>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
>>> at
>>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
>>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:730)
>>> at
>>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
>>> at
>>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
>>> at
>>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
>>> at
>>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
>>> 19 dÚc. 2007 15:23:46
>>> org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose
>>> INFO: Outbound Message
>>> ---------------------------
>>> Encoding:
>>> Headers: <soap:Envelope
>>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Fault
>>> occurred while
>>> processing.</faultstring></soap:Fault></soap:Body></soap:Envelope>
>>> --------------------------------------
>>>
>>>
>>> Any idea about this error?
>>> It's looks like an error due to a timeout...
>>>
>>> Best regards,
>>> Florent.
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/servicemix-cxf-bc-DeliveryChannel---Waiting-for-exchange-to-be-answered-tp14418096s12049p14440619.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: servicemix-cxf-bc DeliveryChannel - Waiting for exchange to be
answered
Posted by Florent <fl...@sopragroup.com>.
Hi Freeman,
There is no error log in my AS. And i got this error may be once every 5
calls.
I'll do a few more test today : i'm currently running WAS + servicemix on my
own computer; i'll install my app & servicemix on a dedicated server.
Btw, i'm using Webpshere AS 6.1.
Best regards,
Florent.
Freeman Fang-2 wrote:
>
> Hi Florent,
> Quick question, when you see this error in servicemix, can you see any
> error log in your weblogic server?
> Thanks
>
> Freeman
>
> Florent wrote:
>> Hello,
>>
>> I'm sometimes getting an error when using cxf-bc as a bridge : i got a
>> main
>> class, doing a few service calls (most of the time, the call is OK).
>>
>> Servicemix log :
>>
>> DEBUG - CxfBcComponent - Received exchange: status: Done,
>> role:provider
>> DEBUG - CxfBcComponent - Retrieved correlation id:
>> ID:172.xx.xxx.xxx-116f2ba0394-4:59
>> DEBUG - DeliveryChannelImpl - Notified:
>> ID:172.xx.xxx.xxx-116f2ba0394-4:60(e95c63) in
>> DeliveryChannel{servicemix-cxf-bc} from sendSync
>> DEBUG - DeliveryChannelImpl - Exchange
>> ID:172.xx.xxx.xxx-116f2ba0394-4:60 has been aborted
>> 19 dÚc. 2007 15:23:46 org.apache.cxf.phase.PhaseInterceptorChain
>> doIntercept
>> INFO: Interceptor has thrown exception, unwinding now
>> org.apache.cxf.interceptor.Fault
>> at
>> org.apache.servicemix.cxfbc.CxfBcConsumer$JbiPostInvokerInterceptor.handleMessage(CxfBcConsumer.java:454)
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207)
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.resume(PhaseInterceptorChain.java:184)
>> at
>> org.apache.servicemix.cxfbc.CxfBcConsumer.process(CxfBcConsumer.java:183)
>> at
>> org.apache.servicemix.cxfbc.CxfBcConsumer$JbiInvokerInterceptor.handleMessage(CxfBcConsumer.java:430)
>> at
>> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207)
>> at
>> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
>> at
>> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:297)
>> at
>> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:243)
>> at
>> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:54)
>> at
>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:722)
>> at
>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
>> at
>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
>> at org.mortbay.jetty.Server.handle(Server.java:324)
>> at
>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
>> at
>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:730)
>> at
>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
>> at
>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
>> at
>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
>> at
>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
>> 19 dÚc. 2007 15:23:46
>> org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose
>> INFO: Outbound Message
>> ---------------------------
>> Encoding:
>> Headers: <soap:Envelope
>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Fault
>> occurred while
>> processing.</faultstring></soap:Fault></soap:Body></soap:Envelope>
>> --------------------------------------
>>
>>
>> Any idea about this error?
>> It's looks like an error due to a timeout...
>>
>> Best regards,
>> Florent.
>>
>
>
--
View this message in context: http://www.nabble.com/servicemix-cxf-bc-DeliveryChannel---Waiting-for-exchange-to-be-answered-tp14418096s12049p14432937.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: servicemix-cxf-bc DeliveryChannel - Waiting for exchange to be
answered
Posted by Freeman Fang <fr...@iona.com>.
Hi Florent,
Quick question, when you see this error in servicemix, can you see any
error log in your weblogic server?
Thanks
Freeman
Florent wrote:
> Hello,
>
> I'm sometimes getting an error when using cxf-bc as a bridge : i got a main
> class, doing a few service calls (most of the time, the call is OK).
>
> Servicemix log :
>
> DEBUG - CxfBcComponent - Received exchange: status: Done,
> role:provider
> DEBUG - CxfBcComponent - Retrieved correlation id:
> ID:172.xx.xxx.xxx-116f2ba0394-4:59
> DEBUG - DeliveryChannelImpl - Notified:
> ID:172.xx.xxx.xxx-116f2ba0394-4:60(e95c63) in
> DeliveryChannel{servicemix-cxf-bc} from sendSync
> DEBUG - DeliveryChannelImpl - Exchange
> ID:172.xx.xxx.xxx-116f2ba0394-4:60 has been aborted
> 19 dÚc. 2007 15:23:46 org.apache.cxf.phase.PhaseInterceptorChain doIntercept
> INFO: Interceptor has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault
> at
> org.apache.servicemix.cxfbc.CxfBcConsumer$JbiPostInvokerInterceptor.handleMessage(CxfBcConsumer.java:454)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.resume(PhaseInterceptorChain.java:184)
> at
> org.apache.servicemix.cxfbc.CxfBcConsumer.process(CxfBcConsumer.java:183)
> at
> org.apache.servicemix.cxfbc.CxfBcConsumer$JbiInvokerInterceptor.handleMessage(CxfBcConsumer.java:430)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:207)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:297)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:243)
> at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:54)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:722)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:324)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:730)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:450)
> 19 dÚc. 2007 15:23:46
> org.apache.cxf.interceptor.LoggingOutInterceptor$LoggingCallback onClose
> INFO: Outbound Message
> ---------------------------
> Encoding:
> Headers: <soap:Envelope
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Fault
> occurred while
> processing.</faultstring></soap:Fault></soap:Body></soap:Envelope>
> --------------------------------------
>
>
> Any idea about this error?
> It's looks like an error due to a timeout...
>
> Best regards,
> Florent.
>