I have made a small servlet that triggers this behavior, it can be found
here:
http://www.cubeia.com/docs/misc/NonSafeCometServlet.java
On occasion, the servlet will fail to respond on the comet notification as
stated previously in this thread. If you try to deploy it, remember to add a
threadpool named 'workpool' =)
Jeanfrancois Arcand-2 wrote:
>
> Can you try to synchronize your CometHandler onEvent to see if that help?
> public synchronize void onEvent(...);
> or do:
> CometContext.setBlockingNotification(true);
>
synchronizing onEvent -> No change
CometContext.setBlockingNotification(true) -> No change
The responses fails and times out in about 1 out of 30 requests. Note that
the implementation uses one comet handler per request.
--
View this message in context: http://www.nabble.com/Grizzly---Comet-concurrency-issue-tp23197357p23256278.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.