[jetty-users] Getting a java.util.concurrent.RejectedExecutionException

[Jeff Smyth <jds@xxxxxxxxxxxx>]

Jetty Users Group,

I have recently been facing an issue with my Production Server which runs on Jetty. I hope this is the correct location to ask for assistance. The following is the error that is being thrown:

app/web.4: 2014-09-30 03:42:36,794 [pool-2-thread-1 Selector0] WARN org.eclipse.jetty.io.nio - Dispatched Failed! SCEP@5ebab0e9{l(/172.16.96.233:57773)<->r(/172.16.96.234:24302),s=-1,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=1r}-{AsyncHttpConnection@32b4c195,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=0},r=0} to org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager@45544e03

app/web.4: 2014-09-30 03:42:36,794 [pool-2-thread-1 Selector0] WARN org.eclipse.jetty.util.thread.ExecutorThreadPool -

app/web.4: java.util.concurrent.RejectedExecutionException

app/web.4:  at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1992)

app/web.4:  at org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager.dispatch(SelectChannelConnector.java:300)

app/web.4:  at org.eclipse.jetty.io.nio.SelectChannelEndPoint.dispatch(SelectChannelEndPoint.java:236)

app/web.4:  at org.eclipse.jetty.io.nio.SelectChannelEndPoint.schedule(SelectChannelEndPoint.java:195)

app/web.4:  at org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:619)

app/web.4:  at org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:290)

app/web.4:  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)

app/web.4:  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

app/web.4:  at java.lang.Thread.run(Thread.java:679)

This error spits out over 100 times a second. When the server is brought up, it runs fine for about 4-8 hours until this error starts showing, and the application is soon unresponsive.

The application runs on a Heroku server, it is on Java 1.6, using Jetty Version 7.6.16.v20140903

I also found this (seemingly) related bug: https://jira.codehaus.org/browse/JETTY-1423 , however, since I am using Jetty 1.6 I am not using an affected version.

Any help or insight into what may be causing this issue would be appreciated.

Thanks!