Hi Bongjae Chang,
I didn't use 'GrizzlyWebServerDeployer '. Kindly send the code snippet for
using GrizzlyWebServerDeployer so that I can check it out.
I used 'grizzly-comet-webserver-1.9.17-SNAPSHOT' to deploy the war file .
This is the startup command.
java -jar grizzly-comet-webserver-1.9.17-SNAPSHOT.jar -p 8181 -a
grizzly-comet-chat.war com.sun.grizzly.samples.comet.AjaxCometServlet
Please find below the startup logs
Listening for transport dt_socket at address: 8000
Jun 16, 2009 9:08:35 PM com.sun.grizzly.standalone.StandaloneMainUtil
appendWarContentToClassPath
INFO: Servicing resources from:
C:\DOCUME~1\abey.tom\LOCALS~1\Temp\grizzly-comet-chat
Launching Servlet: com.sun.grizzly.samples.comet.AjaxCometServlet
Jun 16, 2009 9:08:35 PM com.sun.grizzly.http.SelectorThread
displayConfiguration
INFO:
Grizzly configuration for port 8181
Thread Pool: StatsThreadPool[name=http, min-threads=5,
max-threads=5, max-queue-size=2147483647, is-shutdown=false, port=8181]
Read Selector: 0
ByteBuffer size: 8192
maxHttpHeaderSize: 8192
maxKeepAliveRequests: 256
keepAliveTimeoutInSeconds: 30
Static File Cache enabled: true
Static resources directory:
C:\DOCUME~1\abey.tom\LOCALS~1\Temp\grizzly-comet-chat
Adapter : com.sun.grizzly.http.servlet.ServletAdapter
Asynchronous Request Processing enabled: true
Jun 16, 2009 9:08:35 PM com.sun.grizzly.standalone.StandaloneMainUtil$1
listen
INFO: Server started in 469 milliseconds.
And finally the thread dump for the above stuck request:
http://www.nabble.com/file/p24057218/stuck_today.txt stuck_today.txt
Please fee free to ask if you have any queries.
Thanks,
Abey Tom
--
View this message in context: http://www.nabble.com/grizzly-comet-webserver-gets-stuck-sometime-while-processing-request-tp24033280p24057218.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.