Hello,
I am using servicemix 3.3.2 and facing exception "java.lang.Exception: HTTP
request has timed out" with servicemix-http(2010.01).
I am not yet able to reproduce this exception. But when it happens,
exception keeps on popping up at regular intervals even when no request is
sent to HTTP-component;
But at the same time if valid request is sent to HTTP component then it gets
processed successfully.
I have used HTTP SU which recieves the HTTP request (SOAP message thru perl
script/JBI component) and forwards it to other service-engine.
As per the mail chain - was this bug ever raised and fixed? (I couldn't
trace it in Jira)
*******Exception************
java.lang.Exception: HTTP request has timed out
at
org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:98)
at
org.apache.servicemix.soap.SoapEndpoint.process(SoapEndpoint.java:400)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:627)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:598)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:535)
at
org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:632)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:185)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Unknown Source)
2010-10-27 06:13:01,631 | WARN | 1315643...@qtp-1962516546-344 | jetty
| ervicemix.http.jetty.JCLLogger 96 | /gephttpservice/
java.lang.IllegalStateException: component is not owner when trying to set
error: java.lang.IllegalStateException: component is not owner
at
org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setError(MessageExchangeImpl.java:264)
at
org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:239)
at
org.apache.servicemix.http.HttpBridgeServlet.service(HttpBridgeServlet.java:56)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:938)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: java.lang.IllegalStateException: component is not owner
at
org.apache.servicemix.jbi.messaging.MessageExchangeImpl.setStatus(MessageExchangeImpl.java:251)
at
org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:236)
... 16 more
******/Exception*************
Thanks,
Deep
Ryan Moquin wrote:
>
>>>
>>> Hi, I've been hitting an issue with the servicemix-http component.
>>>> Certain
>>>> machines that we run a servicemix-http consumer endpoint on, seem to
>>>> always
>>>> have a problem with connection timeouts when a response is returned
>>>> from
>>>> the
>>>> target SE. The server is only being hit by a single user. First off,
>>>> here
>>>> is the exception:
>
--
View this message in context:
http://servicemix.396122.n5.nabble.com/servicemix-http-always-times-out-due-to-continuation-not-being-able-to-be-resumed-tp407223p3238594.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
