Dear All
Hope you are fine.
Issue:
https://grizzly.dev.java.net/issues/show_bug.cgi?id=282
has been fixed for *glassfish*-v3-prelude-b28(
Grizzly-*Comet*-1.8.6.1).
I am currently using Glassfish v2.1.1 b31g with grizzly1.0.28
Running in cluster environment. I have a multi-servlet, multi-context
application. When I unregister a context, onIteruppt is called for all
handlers and connections are resumed.
On a single node, everything works fine.
The exception I get is
[#|2010-05-05T16:09:06.210+0500|SEVERE|sun-appserver2.1|GRIZZLY|_ThreadID=27;_ThreadName=httpSSLWorkerThread-38080-4;_RequestID=ba59286d-4bc0-4210-8af7-f6f3037d27c2;|CometSelector
java.lang.IllegalStateException: Invalid Response State. SocketChannel
cannot be null.
at
com.sun.enterprise.web.connector.grizzly.OutputWriter.flushChannel(OutputWriter.java:82)
at
com.sun.enterprise.web.connector.grizzly.OutputWriter.flushChannel(OutputWriter.java:65)
at
com.sun.enterprise.web.connector.grizzly.SocketChannelOutputBuffer.flushChannel(SocketChannelOutputBuffer.java:170)
at
com.sun.enterprise.web.connector.grizzly.async.AsynchronousOutputBuffer.flushChannel(AsynchronousOutputBuffer.java:81)
at
com.sun.enterprise.web.connector.grizzly.SocketChannelOutputBuffer.flushBuffer(SocketChannelOutputBuffer.java:203)
at
com.sun.enterprise.web.connector.grizzly.async.AsynchronousOutputBuffer.flushBuffer(AsynchronousOutputBuffer.java:113)
at
com.sun.enterprise.web.connector.grizzly.SocketChannelOutputBuffer.endRequest(SocketChannelOutputBuffer.java:194)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.action(DefaultProcessorTask.java:941)
at org.apache.coyote.Response.action(Response.java:237)
at org.apache.coyote.Response.finish(Response.java:362)
at
org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:339)
at
org.apache.coyote.tomcat5.CoyoteWriter.close(CoyoteWriter.java:170)
at
com.common.web.servlets.CounterHandler.removeThisFromContext(CounterHandler.java:73)
at
com.common.web.servlets.CounterHandler.onInterrupt(CounterHandler.java:54)
at
com.sun.enterprise.web.connector.grizzly.comet.CometContext.interrupt(CometContext.java:770)
at
com.sun.enterprise.web.connector.grizzly.comet.CometSelector.cancelKey(CometSelector.java:275)
at
com.sun.enterprise.web.connector.grizzly.comet.CometTask.doTask(CometTask.java:285)
at
com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
at
com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
|#]
It seems as though it was a bug in Grizzly-*Comet*-1.8.6.1 which is fixed
now. But don't know the status for grizzly-1.0.x, more over in a clustered
environment.
Any help will be highly appreciated. Need urgent help.
Regards,
Umar Farman
Software Engineer
PakVista Technologies Co. (Pvt) Ltd.
Office No.18, 3rd Floor, Select Center,
F-11 Markaz - Islamabad.
Office: +92 51 831 4504-5
Cell : +92 3333 525 4003
URL: www.pakvistatech.com <
http://www.pakvistatech.com/>