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 fixProblem 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 fixComments
APAR information | APAR number | PQ48365 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-05-01 | Closed date | 2001-05-09 | Last modified date | 2001-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 APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|