[GLASSFISH-18676] Http Session gets invalidated Created: 02/May/12 Updated: 08/Apr/13 Resolved: 08/Apr/13
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
glassfish 3.1.2 Release, Windows 7, FF or IE.
We have an issue in a Atmosphere application using streaming or long-polling.
Unfortunately my app I cannot deliver because of the complexity(app using a db connection) and license reasons.
|Comment by Ryan Lubke [ 02/May/12 ]|
Could you please back up your $GF_HOME/modules/web-core.jar and replace it with the web-core.jar I've attached to this issue? This should show us where the session is being invalidated from.
|Comment by Ryan Lubke [ 07/May/12 ]|
|Comment by vasim [ 09/May/12 ]|
Sorry for answering so late.
Actually are 2 errors:
2. throwing the error 503 in the web app is generating the session invalidation. The error 503 was thrown by Atmosphere and now we took it out. Actually in my opinion glassfish is here wrong implemented, why in this error case the session should be invalidated ? In the case the application is doing another request after such an error, then the seesion will be of course used and the app is not allowed to do anything any more. This means the app needs a new login and I don't find this normal.
You need some log files from me, in adition to this new informations ?
|Comment by oleksiys [ 30/May/12 ]|
yes, pls. send GF server.log file, when session invalidation happens again.
Regarding point 1) you mentioned a thread.sleep... it might be a bug by design, cause in Grizzly Comet (Jeanfrancois has to know about that ) ) the actual "suspend" initialization happens after you exit Servlet.service(...) method. So if this initialization clashes w/ broadcaster thread - it may cause problems. IMO possible fix will include changes on both Grizzly and Atmosphere sides.
|Comment by oleksiys [ 12/Jun/12 ]|
changing the priority to major.