On 15/11/2011 17:00, Matthew Tyson wrote: > Hey Guys, > > We are seeing the following errors (in production of course, testing didn't > reveal this) after switching to NIO protocol. > > This is Tomcat 7.0.22 on CentOS 6. There is a load balancer sending only > comet traffic to port 8080, where the NIO protocol is used. > > Nov 15, 2011 8:39:29 AM org.apache.tomcat.util.net.NioEndpoint processSocket > SEVERE: Error allocating socket processor > java.lang.NullPointerException > Nov 15, 2011 8:39:51 AM org.apache.tomcat.util.net.NioEndpoint processSocket > SEVERE: Error allocating socket processor > java.lang.NullPointerException > at > org.apache.tomcat.util.net.NioEndpoint.processSocket(NioEndpoint.java:712) > at > org.apache.tomcat.util.net.NioEndpoint$Poller.processKey(NioEndpoint.java:1200) > at > org.apache.tomcat.util.net.NioEndpoint$Poller.run(NioEndpoint.java:1136) > at java.lang.Thread.run(Thread.java:662) > Nov 15, 2011 8:39:52 AM > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler process > SEVERE: null > java.lang.IllegalStateException: Calling [asyncPostProcess()] is not valid > for a request with Async state [STARTED] > at > org.apache.coyote.AsyncStateMachine.asyncPostProcess(AsyncStateMachine.java:202) > at > org.apache.coyote.AbstractProcessor.asyncPostProcess(AbstractProcessor.java:104) > at > org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:519) > at > org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1550) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Exception in declaration() > > I see more of the "Calling [asyncPostProcess()] is not valid for a request > with Async state [STARTED]" error by itself also. Here is the connector > setup: > > <Connector port="8080" protocol="org.apache.coyote.http11.Http11NioProtocol" > connectionTimeout="20000" > redirectPort="8443" /> > > Any direction on where to look for the cause?
It could be a bug somewhere in the NIO connector. There has been a lot of refactoring to reduce duplication between the connectors. In the long term that should reduce the bugs and makes those that remain easier to fix. In the short term, there have been a couple of regressions. What we really need is a reproducible test case. The simpler, the better. It could also be an application bug. A test case would help identify that too. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
