Sadly, 7.0.35 did not resolve this issue. I still see the exception, albeit with more information this time:
Jan 16, 2013 3:39:41 PM org.apache.coyote.AbstractProtocol$AbstractConnectionHandler process SEVERE: Error reading request, ignored java.lang.IllegalStateException: Calling [asyncPostProcess()] is not valid for a request with Async state [STARTED] at org.apache.coyote.AsyncStateMachine.asyncPostProcess(AsyncStateMachine.java:204) at org.apache.coyote.AbstractProcessor.asyncPostProcess(AbstractProcessor.java:116) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:593) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1680) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) java.lang.NullPointerException at org.apache.catalina.core.AsyncContextImpl.dispatch(AsyncContextImpl.java:172) at org.eclipse.jetty.continuation.Servlet3Continuation.resume(Servlet3Continuation.java:153) at org.cometd.server.transport.LongPollingTransport$LongPollScheduler.schedule(LongPollingTransport.java:560) at org.cometd.server.ServerSessionImpl.flush(ServerSessionImpl.java:526) at org.cometd.server.ServerSessionImpl.doDeliver(ServerSessionImpl.java:276) at org.cometd.server.ServerSessionImpl.deliver(ServerSessionImpl.java:218) at org.cometd.server.ServerSessionImpl.deliver(ServerSessionImpl.java:227) at com.avaya.pc.webagent.dialer.DialerChannel.receiveMessage(DialerChannel.java:270) at com.avaya.pc.webagent.dialer.PipelinedMsgParser.run(PipelinedMsgParser.java:106) at java.lang.Thread.run(Unknown Source) I will provide a write-up of how to recreate the problem as soon as I can. Unfortunately, my first priority is to get this working. The suggestion from the CometD team is to try our application on Jetty, and I need to turn my attention to that now. Thanks, Satyen On Tue, Jan 15, 2013 at 11:26 AM, Mark Thomas <ma...@apache.org> wrote: > On 15/01/2013 17:19, Satyen Hingorani wrote: > > Hi Chris, > > > > Thanks for your response. > > > > I don't see 7.0.35 on the download site; 7.0.34 is the latest. > > Where can I get 7.0.35 to try? > > Chris is suffering from an off-by-one error. > > 7.0.34 is currently the latest. > > 7.0.35 will probably start appearing on the mirrors in the next ~6 > hours or so. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
