Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Invalid
-
Affects Version/s: 3.3, 4.0
-
Fix Version/s: EE-4.1.0.GA
-
Component/s: Framework
-
Labels:None
-
Environment:Weblogic 12
-
Assignee Priority:P1
Description
The ExtendedExceptionHandler class, who's responsibility is to interpret when a ViewExpiredException thrown by JSF implementation is caused by session expiration or indeed by an expired view, falsely reports a session expired when in fact the session is freshly created.
Activity
Mircea Toma
created issue -
Mircea Toma
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Mircea Toma [ mircea.toma ] |
Mircea Toma
made changes -
Fix Version/s | 4.1 [ 11375 ] |
Mircea Toma
made changes -
Affects Version/s | 4.0 [ 11382 ] |
Mircea Toma
made changes -
Affects Version/s | 3.3 [ 10370 ] |
Ken Fyten
made changes -
Fix Version/s | EE-4.1.0.GA [ 12171 ] | |
Fix Version/s | 4.1 [ 11375 ] |
Ken Fyten
made changes -
Assignee Priority | P1 [ 10010 ] |
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Invalid [ 6 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
After running the tests I managed to reproduce this issue. The issue will occur only if previously the browser has already a JSESSIONID cookie set by other application server (for the same IP/domain). Because the JSESSIONID format is not the same Weblogic will not recognise it and assign another JSESSIONID cookie. Now when any interaction is initiated both cookies are sent, but the first one (set by another server) will be read by Weblogic and since it's not recognised it will throw a ViewExpiredException which eventually is interpeted as a session expiration.
The solution is to cleanup the old JSESSIONID cookie before using Weblogic and everything will work fine from then on.