Forum Home » Fuse Distributions » Fuse Mediation Router

Thread: jetty EOFException

This question is not answered. Helpful answers available: 2. Correct answers available: 1.

Permlink Replies: 2 - Last Post: Apr 26, 2011 2:42 AM Last Post By: heatlamp

Posts: 10
Registered: 04/25/11
jetty EOFException
Posted: Apr 25, 2011 6:21 PM
  Click to reply to this thread Reply
Use Camel DSL with HTTP4, I'm seeing a confusing Jetty EOF exception. Here's the exception

2011-04-25 10:49:01,589 qtp20755142-13 DEBUG org.eclipse.jetty.util.log - EOF null
at org.eclipse.jetty.http.HttpParser.parseNext( ~jetty-http-7.3.1.v20110307.jar:7.3.1.v20110307
at org.eclipse.jetty.http.HttpParser.parseAvailable( ~jetty-http-7.3.1.v20110307.jar:7.3.1.v20110307
at org.eclipse.jetty.server.HttpConnection.handle( ~jetty-server-7.3.1.v20110307.jar:7.3.1.v20110307
at ~jetty-io-7.3.1.v20110307.jar:7.3.1.v20110307
at$ jetty-io-7.3.1.v20110307.jar:7.3.1.v20110307
at org.eclipse.jetty.util.thread.QueuedThreadPool$ jetty-util-7.3.1.v20110307.jar:7.3.1.v20110307
at 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
simple ${in.header.RequestStatus} == 'Pending'
to uri="seda:statusQueue"
to uri="seda:nextQueue"

See any problem with this?

Thx, Jim

Edited by: heatlamp on Apr 25, 2011 6:22 PM

Posts: 572
Registered: 09/17/07
Re: jetty EOFException
Posted: Apr 26, 2011 12:19 AM   in response to: heatlamp in response to: heatlamp
  Click to reply to this thread Reply
What's your request message body looks like?
Did you try to enable the stream cache[1] ?



Posts: 10
Registered: 04/25/11
Re: jetty EOFException
Posted: Apr 26, 2011 2:42 AM   in response to: njiang in response to: njiang
  Click to reply to this thread Reply
Thanks for the reply and the StreamCache suggestion (which made no difference).

I removed the CHOICE noted above, and the stack dump still occurs. There are, however, prior HTTP operations in the route. I'll try to remote bits of the route until the problem disappears, will post a note if I find the problem