Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.6DR#2
-
Component/s: Framework
-
Labels:None
-
Environment:Tomcat, websphere, weblogic, jboss
-
ICEsoft Forum Reference:
-
Support Case References:
Description
Session expiry when bringing up an application for the first time.
Note that in JBoss environments, this is generally an indication that there is no HttpSessionListener registered to be notified of the session creation, and thus, no handler registered to handle the requests. The exception can, when it's reporting that the session is expired before even bringing up the application, be a bit of a red herring.
However, there seems to be consensus that the exception occurs in some environments even when the Listener is properly configured in web.xml.
Note that in JBoss environments, this is generally an indication that there is no HttpSessionListener registered to be notified of the session creation, and thus, no handler registered to handle the requests. The exception can, when it's reporting that the session is expired before even bringing up the application, be a bit of a red herring.
However, there seems to be consensus that the exception occurs in some environments even when the Listener is properly configured in web.xml.
Activity
Greg Dick
created issue -
Deryk Sinotte
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Mircea Toma [ mircea.toma ] |
Philip Breau
made changes -
Support Case References | https://www.icesoft.ca:4443/supportilla/show_bug.cgi?id=4007 | |
Support Customer Ref. #s | 723 |
Ken Fyten
made changes -
Fix Version/s | 1.6DR#3 [ 10050 ] | |
Assignee Priority | P2 |
Ken Fyten
made changes -
Assignee Priority | P2 | P1 |
Mircea Toma
made changes -
Fix Version/s | 1.6DR#4 [ 10060 ] | |
Fix Version/s | 1.6DR#3 [ 10050 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #13630 | Mon Apr 23 11:15:31 MDT 2007 | mircea.toma | Use strings (the session ID) as keys -- |
Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/core/src/com/icesoft/faces/webapp/http/servlet/SessionDispatcher.java
|
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Fix Version/s | 1.6 [ 10031 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee Priority | P1 | |
Assignee | Mircea Toma [ mircea.toma ] |
Assigning to Mircea.
I saw this testing something unrelated on WebSphere. It appears that this logic in SessionDispatcher:
...
if (sessionBoundServers.containsKey(session)) {
...
is always returning false. I put in some logging and it appears that the session it is looking for IS in the map but I guess the equals() logic for Session objects is not reliable and/or container specific. I tried switching over the logic of the SessionDispatcher to rely on session.getId() instead and that did the trick for me.