I have downloaded
http://download.java.net/maven/2/com/sun/grizzly/grizzly-framework-http/1.0.30-SNAPSHOT/grizzly-framework-http-1.0.30-SNAPSHOT.jar
and put it into $GLASSFISH_HOME/lib/ext
The jar file is referenced in domain.xml which is traced in the server.log
file:
2009-06-26 08:00:27 com.sun.enterprise.admin.servermgmt.launch.ASLauncher
buildCommand
INFO:
D:/java/jdk1.6.0/jre/..\bin\java
-Dcom.sun.aas.instanceRoot=D:/java/app-servers/glassfish-v2.1-b60e/glassfish/domains/domain1
-Dcom.sun.aas.ClassPathPrefix=d:/java/app-servers/glassfish-v2.1-b60e/glassfish/lib/ext/grizzly-framework-http-1.0.30-SNAPSHOT.jar
But later on I can see that Grizzly 1.0.29 is enabled
[#|2009-06-26T08:00:35.295+0200|INFO|sun-appserver2.1|GRIZZLY|_ThreadID=10;_ThreadName=main;|Enabling
Grizzly ARP Comet support.|#]
[#|2009-06-26T08:00:35.357+0200|INFO|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;8080;|WEB0712:
Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080|#]
[#|2009-06-26T08:00:35.357+0200|INFO|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=15;_ThreadName=SelectorThread-8080;|Grizzly
1.0.29|#]
Is it OK?
Still, after this update, the comet context is not expired.
Thanks,
Czarek
--
View this message in context: http://www.nabble.com/Comet-context-doesn%27t-expire-tp24072882p24215469.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.