Use Camel DSL with HTTP4, I'm seeing a confusing Jetty EOF exception. Here's the exception
2011-04-25 10:49:01,589 DEBUG org.eclipse.jetty.util.log - EOF
org.eclipse.jetty.io.EofException: null
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:321) ~[jetty-http-7.3.1.v20110307.jar:7.3.1.v20110307]
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:214) ~[jetty-http-7.3.1.v20110307.jar:7.3.1.v20110307]
at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411) ~[jetty-server-7.3.1.v20110307.jar:7.3.1.v20110307]
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:526) ~[jetty-io-7.3.1.v20110307.jar:7.3.1.v20110307]
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:41) jetty-io-7.3.1.v20110307.jar:7.3.1.v20110307
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:528) jetty-util-7.3.1.v20110307.jar:7.3.1.v20110307
at java.lang.Thread.run(Thread.java:662) na:1.6.0_24
The point in the routing where this is generated is a CHOICE processor, but the route appears to continue normally.
What I'm doing here that may be confusing things is implementing a loop by polling an HTTP destination for a specific response, and then sending the message back to the input queue if status is pending. ie something like this
from usr="seda:statusQueue"
to uri=http4:blahblah QueryStatus.aspx
choice
when
simple ${in.header.RequestStatus} == 'Pending'
to uri="seda:statusQueue"
/when
when
to uri="seda:nextQueue"
/when
See any problem with this?
Thx, Jim
Edited by: heatlamp on Apr 25, 2011 6:22 PM
