users@grizzly.java.net

Re: Comet context doesn't expire

From: Czarek Zadorocki <Cezary.Zadorocki_at_bzwbk.pl>
Date: Thu, 18 Jun 2009 03:41:10 -0700 (PDT)

Salut!

I've attached grizzly-framework-http-1.0.29.jar file to the classpath
prefix.
The classes overide grizzly module classes because the following is in the
server.log file:
[#|2009-06-18T11:45:58.921+0200|INFO|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=14;_ThreadName=SelectorThread-8080;|Grizzly
1.0.29|#]

The problem is that my application uses a quartz job that frequently
notifies a comet context.
The application works fine on Glassfish v2.1_02 (build b04-fcs) beacuse the
comet context is terminated.
But when deployed onto v2.1-b60e the context is not terminated.
I attach the simple http://www.nabble.com/file/p24090476/SampleComet.ear
SampleComet.ear test application accessible via URL
http://localhost:8080/FxLoaderWeb/FxLoaderServlet


Thanks
   Czarek
-- 
View this message in context: http://www.nabble.com/Comet-context-doesn%27t-expire-tp24072882p24090476.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.