APAR status
Closed as program error.
Error description
In order to serialize access to a HTTP session, the customer
turned on
the "Allow serial access" option on "Application
Server->server1->Web
Container->Session Management". However, the serialization
doesn't seem
to occur. The syncronization doesn't seem to occur. This doesn't
behave as we discribed in infocenter,
Here is what the InfoCenter says about this "Allow serial
access"
option:
The Servlet API supports concurrent access to a session in a
given
server instance. WebSphere Application Server provides an option
to
prevent the concurrent access to a session in a given server
instance so
Local fix
that concu rent modification of a session does not occur in a
given
server instance. This prevention is achieved by synchronizing
the
requests based on session. When this feature is turned on, a
session is
obtained for the request before invoking the servlet and
requests are
synchronized by locking the session for the servlet execution
time.
LOCAL FIX:ン
N/A
Problem summary
****************************************************************
* USERS AFFECTED: Null pointer exception occurs after allow *
* serial access has been enabled. *
****************************************************************
* PROBLEM DESCRIPTION: com.ibm.ws.webcontainer.httpsession. *
* SessionContext.sessionPreInvoke *
* (SessionContext.java:2363) exception *
* occurs after allow serial access has *
* been enabled. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When "Enable serial access" is enabled in the admin console,
the user experiences this error:
Error - : java.lang.NullPointerException
at com.ibm.ws.webcontainer.httpsession.SessionContext.
sessionPreInvoke(SessionContext.java:2363)
at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.
sessionPreInvoke(WebAppDispatcherContext.java:216)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.
dispatch(WebAppRequestDispatcher.java:503)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.
forward(WebAppRequestDispatcher.java:176)
Problem conclusion
The code was changed to address this problem. We have added
new synchronizing lock in the session manager, so that session
data access is serialized across all application servers.
Temporary fix
PQ74549_Test.jar
Need to apply WAS_Sessions_06-11-2003_5.0.1-5.0.0
_Cumulative_Fix first.
Comments
APAR information |
APAR number |
PQ74549 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-05-23 |
Closed date |
2004-01-12 |
Last modified date |
2004-01-12 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
|