Thanks for the quick response
Our use case:
We are using comet to process mobile messages and in some corner cases we are getting after the issue occurs 100% CPU utilization .
1. Each mobile register to the Context with unique name
2. When mobile disconnects from server the connection released normally by utilizing the onTerminate() and removed from the engine .
3. When mobile device is shutdown and there is no normal device disconnection process, no event is received at the server side and methods onTerminate and onInterrupt are not invoked so the mobile remains registered in the CometEngine.
4. When mobile try to reconnect we find out that the same context name already exist in the system so need to removed it manually by invoking CometEngine.getEngine().unregister(contextPath);
5. Executing this action cause CPU jump to 100% and stay there until the java process is killed .
Is this issue is known?
Please advice, maybe I am using it in wrong way , I also saw that in new version some methods are deprecated, but I don't understand how to integrated it to the glassfish server .
WBR
Alex Kalnitski
Lead R&D Server Side
AT&T | Interwise
From: Oleksiy Stashok [mailto:oleksiy.stashok_at_oracle.com]
Sent: Wednesday, January 25, 2012 4:00 PM
To: Alex Kalnitski
Cc: users_at_grizzly.java.net
Subject: Re: FW: Glassfish issue
Hi Alex,
you can send issue details to users_at_grizzly.java.net<mailto:users_at_grizzly.java.net> (CC'ed) and we'll try to help.
Thanks.
WBR,
Alexey.
On 01/25/2012 02:55 PM, Alex Kalnitski wrote:
Hi ;
We are using an Glassfish server open source edition v3.1.1 for our benchmarking with Comet technology and we have something that looks like a bug .
Please advice what should I do next and where should I go further .
BR
Alex
Lead R&D
AT&T Interties .