PQ48365: NULL POINTER EXCEPTIONS THROWN WHEN MULTIPLE REQUESTS ARE MADE FOR SAME CACHE-ABLE SERVLET, W/ CACHING ENABLED


APAR

APAR status
Closed as program error.

Error description
This is a problem with JspServlet in both JSP 1.0 and JSP 1.1.
There is a timing window between loadIfNecessary, load(), and
servlet.init().  The problem is that theServlet variable is
set to non-null before the theServlet.init() is called and
therefore another thread can execute into loadIfNecessary,
it appears everything is ok and then trys to execute the
JSP before init().  This results in NullPointerExceptions
in PageContextImpl.
defect 92917
Local fix
Problem summary
NullPointerException when multiple requests are made with
caching enabled.  The problem is due to a long interval between
JSP instantiation and initialization.
Problem conclusion
org/apache/jasper/runtime/JspServlet.java
com/sun/jsp/runtime/JspServlet.java
Temporary fix
Comments
APAR information
APAR numberPQ48365
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2001-05-01
Closed date2001-05-09
Last modified date2001-05-09

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
JSP
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ48365
IBM Group: Software Group
Modified date: 2001-05-09