Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 1.5.1
-
Fix Version/s: 1.6DR#1
-
Component/s: Sample Apps
-
Labels:None
-
Environment:Operating System: All
Platform: All
Description
After several days there are no longer any anonymous accounts available.
After much testing and isolating a similar problem with WebMC the problem has
been diagnosed. The Tomcat and Jboss Servlet containers do not behave the same
way when the session destroyed callback is called. In Tomcat it would appear
that the session has not yet been destroyed when the callback is called. However
JBoss destroys the session then calls the callback method.
Because of ambiguity in the Servlet spec the preferred way to handle a session
destroyed callback is to get the session id from the callback parameter. The
application must then use this session id to do any clean up or unlocking. We
historically try to do some resource disposing but as it turns out there is no
guarantee that the session beans are still around.
After much testing and isolating a similar problem with WebMC the problem has
been diagnosed. The Tomcat and Jboss Servlet containers do not behave the same
way when the session destroyed callback is called. In Tomcat it would appear
that the session has not yet been destroyed when the callback is called. However
JBoss destroys the session then calls the callback method.
Because of ambiguity in the Servlet spec the preferred way to handle a session
destroyed callback is to get the session id from the callback parameter. The
application must then use this session id to do any clean up or unlocking. We
historically try to do some resource disposing but as it turns out there is no
guarantee that the session beans are still around.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion