Test failure: java.util.concurrent.RejectedExecutionException: Worker has already been shutdown

[danc86]

I'm working on packaging Webbit for Fedora (review bug) but at the moment it fails to build in Fedora rawhide due to a test failure. I'm pretty sure this is due to building with newer netty (3.6.6) because the problem doesn't happen when building for Fedora 18 which has netty 3.5.11.

Running org.webbitserver.handler.PostTest
Jun 17, 2013 10:54:54 AM org.jboss.netty.channel.DefaultChannelPipeline
WARNING: An exception was thrown by an exception handler.
java.util.concurrent.RejectedExecutionException: Worker has already been shutdown
    at org.jboss.netty.channel.socket.nio.AbstractNioSelector.registerTask(AbstractNioSelector.java:115)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.executeInIoThread(AbstractNioWorker.java:73)
    at org.jboss.netty.channel.socket.nio.NioWorker.executeInIoThread(NioWorker.java:36)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.executeInIoThread(AbstractNioWorker.java:57)
    at org.jboss.netty.channel.socket.nio.NioWorker.executeInIoThread(NioWorker.java:36)
    at org.jboss.netty.channel.socket.nio.AbstractNioChannelSink.execute(AbstractNioChannelSink.java:34)
    at org.jboss.netty.channel.Channels.fireExceptionCaughtLater(Channels.java:496)
    at org.jboss.netty.channel.AbstractChannelSink.exceptionCaught(AbstractChannelSink.java:46)
    at org.jboss.netty.channel.Channels.write(Channels.java:704)
    at org.jboss.netty.channel.Channels.write(Channels.java:671)
    at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248)
    at org.webbitserver.netty.NettyHttpResponse.write(NettyHttpResponse.java:208)
    at org.webbitserver.netty.NettyHttpResponse.flushResponse(NettyHttpResponse.java:196)
    at org.webbitserver.netty.NettyHttpResponse.error(NettyHttpResponse.java:169)
    at org.webbitserver.netty.NettyHttpChannelHandler$3.run(NettyHttpChannelHandler.java:94)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:722)
Jun 17, 2013 10:54:54 AM org.jboss.netty.channel.DefaultChannelPipeline
WARNING: An exception was thrown by an exception handler.
java.util.concurrent.RejectedExecutionException: Worker has already been shutdown
    at org.jboss.netty.channel.socket.nio.AbstractNioSelector.registerTask(AbstractNioSelector.java:115)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.executeInIoThread(AbstractNioWorker.java:73)
    at org.jboss.netty.channel.socket.nio.NioWorker.executeInIoThread(NioWorker.java:36)
    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.executeInIoThread(AbstractNioWorker.java:57)
    at org.jboss.netty.channel.socket.nio.NioWorker.executeInIoThread(NioWorker.java:36)
    at org.jboss.netty.channel.socket.nio.AbstractNioChannelSink.execute(AbstractNioChannelSink.java:34)
    at org.jboss.netty.channel.Channels.fireExceptionCaughtLater(Channels.java:496)
    at org.jboss.netty.channel.AbstractChannelSink.exceptionCaught(AbstractChannelSink.java:46)
    at org.jboss.netty.channel.Channels.write(Channels.java:704)
    at org.jboss.netty.channel.Channels.write(Channels.java:671)
    at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248)
    at org.webbitserver.netty.NettyHttpResponse.write(NettyHttpResponse.java:208)
    at org.webbitserver.netty.NettyHttpResponse.flushResponse(NettyHttpResponse.java:196)
    at org.webbitserver.netty.NettyHttpResponse.error(NettyHttpResponse.java:169)
    at org.webbitserver.netty.NettyHttpChannelHandler$3.run(NettyHttpChannelHandler.java:94)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:722)
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 15.064 sec <<< FAILURE!
request_body_longer_than_max_content_length_causes_500_and_does_not_invoke_handlers(org.webbitserver.handler.PostTest)  Time elapsed: 15.019 sec  <<< ERROR!
java.net.SocketException: Unexpected end of file from server
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:718)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
    at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:715)
    at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:579)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1322)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
    at org.webbitserver.handler.PostTest.request_body_longer_than_max_content_length_causes_500_and_does_not_invoke_handlers(PostTest.java:108)

[aslakhellesoy]

Webbit 0.4.15 (which seems to be what you're trying to build) depends on Netty 3.5.5. See the pom.

Netty is a highly volatile library and building it with any other version is likely to produce test failures.

Webbit's HEAD of master depends on Netty 3.6.5, which builds fine according to Travis. It does not build with Netty 3.6.6, apparently because it changes the behaviour for too long HTTP frames.

I spent a few hours trying to make Webbit HEAD work with Netty 3.6.6 so I could make a new release, but I was unsuccessful. I'm probably not going to spend any more time on getting past Netty 3.6.5 unless someone sends a patch/pull request.

[danc86]

Okay, thanks. I understand it's hard to keep up with dependencies which are not stable. Unfortunately I need to get Webbit building against the latest Netty release if it's to be accepted as a Fedora package, so I was hoping you might have some ideas. It's helpful to know that Webbit's master branch works with Netty 3.6.5 since that should make it a lot easier to track down what is causing the breakage with Netty 3.6.6.