Details
Description
The following warning message can be shown many times in the sever logs:
SessionExpired WARNING An exception occurred while trying to invoke @PreDestroy on window scoped beans: null
This is being reported to occur when a users session has timed out. There are no Windows scoped beans being used nor is the @PreDestroy annotaton being used. The warning doesn't have any functional impact but can clog up the server logs depending on the user load.
SessionExpired WARNING An exception occurred while trying to invoke @PreDestroy on window scoped beans: null
This is being reported to occur when a users session has timed out. There are no Windows scoped beans being used nor is the @PreDestroy annotaton being used. The warning doesn't have any functional impact but can clog up the server logs depending on the user load.
Activity
Arran Mccullough
created issue -
Arran Mccullough
made changes -
Field | Original Value | New Value |
---|---|---|
Salesforce Case Reference | 5007000000SPHTkAAP |
Ken Fyten
made changes -
Assignee | Deryk Sinotte [ deryk.sinotte ] | |
Fix Version/s | 3.3 [ 10370 ] | |
Assignee Priority | P2 [ 10011 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #33990 | Wed Mar 20 11:26:24 MDT 2013 | deryk.sinotte | |
Files Changed | ||||
MODIFY
/icefaces3/trunk/icefaces/core/src/main/java/org/icefaces/impl/application/WindowScopeManager.java
|
Deryk Sinotte
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Not sure why the older case was marked fixed.
This doesn't seem to be easy to replicate with our standard examples. As per the original customer comments, my theory was that the session had to be created and invalidated outside of most of the ICEfaces processing. Our SessionExpiredListener will still operate in this type of environment but the majority of the WindowScope processing will not meaning the appropriate "state" is never added to the session.
To mimic this behaviour, I simply changed the index.jsp of our basic example to:
Doing this creates a session and invalidates it before the WindowScopeManager has a chance to set things up. However, our SessionExpiredListener still runs so then you get the following logged:
There are a couple of things we could do:
1) Since the log is at WARNING level, we could just turn this down as the involved code is basically already doing its job in catching the exception and moving on:
2) Deal with the NullPointerException at the source as I originally suggested:
For now I've opted for #2 and left the log level at WARNING as it may catch other behaviours we want to know about.