Details
Bug
Major
Description
When the session expires, instead of the SessionExpiredException catch code in
BlockingServlet handling the probem, a NullPointerExcepetion is thrown
beforehand, which keeps any response from being sent. On the browser end, the
Javascript just sees that there's no response from the socket, until some
timeout occurs, and it's shown as a disconnected socket. We need to properly
trap the condition that leads to the NPE, and do the session timeout handling.
Deryk and Ted think it's because the call to HttpServletRequest.getSession()
will create an empty bogus HttpSession, when instead we should use
HttpServletRequest.getSession(false), and trap the null session.
Tested using the latest build of ICEfaces 1.5.2 (from Jan 10, 2007 in the
evening) and running with the HEAD Facelets component-showcase inside of JBoss
4.0.4 GA.
BlockingServlet handling the probem, a NullPointerExcepetion is thrown
beforehand, which keeps any response from being sent. On the browser end, the
Javascript just sees that there's no response from the socket, until some
timeout occurs, and it's shown as a disconnected socket. We need to properly
trap the condition that leads to the NPE, and do the session timeout handling.
Deryk and Ted think it's because the call to HttpServletRequest.getSession()
will create an empty bogus HttpSession, when instead we should use
HttpServletRequest.getSession(false), and trap the null session.
Tested using the latest build of ICEfaces 1.5.2 (from Jan 10, 2007 in the
evening) and running with the HEAD Facelets component-showcase inside of JBoss
4.0.4 GA.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| issue.field.bugzillaimportkey | 1223 | 12440 |
| Status | Resolved [ 5 ] | Closed [ 6 ] |