Re: AsynchronousCloseException in jetty:

[Coda Hale]

This is a Jetty error, so you'd need to ask the Jetty folks what this means.

Generally, though, debug errors in Jetty aren't worth tracking down.

On Wed, Jun 12, 2013 at 3:11 AM, Andrea <a.bag...@stormreply.com> wrote:

Hi, 

I'm experiencing a weird error only when the error level is set to DEBUG

DEBUG [2013-06-12 09:59:08,792] org.eclipse.jetty.io.nio.ChannelEndPoint: Exception while filling

! java.nio.channels.AsynchronousCloseException: null

! at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205) ~[na:1.7.0_17]

! at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:386) ~[na:1.7.0_17]

! at org.eclipse.jetty.io.nio.ChannelEndPoint.fill(ChannelEndPoint.java:235) ~[osupdater-service-0.2-STAGING.jar:na]

! at org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.fill(BlockingChannelConnector.java:242) [osupdater-service-0.2-STAGING.jar:na]

! at org.eclipse.jetty.http.HttpParser.fill(HttpParser.java:1040) [osupdater-service-0.2-STAGING.jar:na]

! at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:280) [osupdater-service-0.2-STAGING.jar:na]

! at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) [osupdater-service-0.2-STAGING.jar:na]

! at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) [osupdater-service-0.2-STAGING.jar:na]

! at org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.run(BlockingChannelConnector.java:298) [osupdater-service-0.2-STAGING.jar:na]

! at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) [osupdater-service-0.2-STAGING.jar:na]

! at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) [osupdater-service-0.2-STAGING.jar:na]

! at java.lang.Thread.run(Thread.java:722) [na:1.7.0_17]

Why I can see this error only when the logging level is set to DEBUG, it seems that the  underlying channel for an I/O operation is closed by another thread. So 

could dropwizard be involved in this strange behavior?   

Did someone have experienced the same issue?

Thanks

--
You received this message because you are subscribed to the Google Groups "dropwizard-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-us...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Coda Hale
http://codahale.com