users@grizzly.java.net

Re: Comet context doesn't expire

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Thu, 18 Jun 2009 09:50:58 -0400

Salut,

Czarek Zadorocki wrote:
> 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 I will take a look. Yes I recall we have added better support for
onTerminate.

Thanks

-- Jeanfrancois



>
>
> Thanks
> Czarek