Hi, I'm using version 3.1-incubating. So do you mean to say that http component has a time out of its own when its MEP is set as in-out ? In my service the cb su has a time out of 130 sec (time which it will wait for getting the reply from the external service). Now imagine the http time out is 65 secs, and if for some reason the external service did not reply for 80 secs, will my http component throw an illegal state exception: Exchange not found ?
Thanks Varun gnodet wrote: > > I've fixed lots of problems related to timeout issues in > servicemix-http recently. > Are you using the latest 3.3 version ? > > On Wed, Dec 10, 2008 at 00:54, unni_varun <[email protected]> wrote: >> >> Hi all, >> >> The EIP flow of my service is as follows: >> >> http su <---> xslt,lw su's <---> cb su >> >> Of these cb su is not an out of the box se provided by apache. This su >> communicates with another service say s1. So what happened was the >> service >> s1 was having some issues and was responding slow. Now in cb su we have >> set >> a time out period of 130 sec. some requests took more than that and we >> got a >> time out which is properly handled in cb su. But since s1 was responding >> slow I was getting the following exception. >> >> java.lang.IllegalStateException: Exchange not found >> at >> org.apache.servicemix.http.processors.ConsumerProcessor.process(ConsumerProcessor.java:187) >> at >> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:71) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) >> at >> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) >> at >> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) >> at >> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >> at >> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211) >> at >> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) >> at >> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) >> at org.mortbay.jetty.Server.handle(Server.java:313) >> at >> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506) >> at >> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:375) >> at >> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) >> at >> org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectChannelConnector.java:511) >> at >> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) >> >> >> I believe this is because http component was set as an in-out and it was >> expecting a reply back. Since the reply was delayed after particular time >> (which i'm not sure how much) it was throwing this exception. So my >> question >> is whether each service mix component set as in-out has any time limit >> which >> it waits for a reply and after which if it did not get a reply throws out >> this exception. >> >> I hope I have made clear the scenario here. Any thoughts or help would be >> much appreciated. Thanks in anticipation. >> >> Varun >> -- >> View this message in context: >> http://www.nabble.com/Doubts-on-Illegal-State-Exception-tp20926404p20926404.html >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > -- View this message in context: http://www.nabble.com/Doubts-on-Illegal-State-Exception-tp20926404p20970000.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
