APAR status
Closed as program error.
Error description
May get 500 ERROR, NULLPOINTEREXCEPTION when application is
calling include(req,res).
The webcontainer is setting an object to null in a re-usable
object. Subsequent requests which get the re-usable object then
suffer the NPE until such time as the object is re-set in the
re-usable object.
The relevant call stack for the application include() problem
is:
ExtendedMessage: RuntimeException caught in
WebAppRequestDispatcher.include()java.util.EmptyStackException
at java.util.Stack.peek(Stack.java)
at com.ibm.ws.webcontainer.srt.SRTRequestContext.
isWithinModule(SRTRequestContext.java
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.
setupSecurityChecks(WebAppRequestDispatcher.java)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.
include(WebAppRequestDispatcher.java(Compiled Code))
at com.rmc.dynamic.RSVYieldsHTML.PG005(RSVYieldsHTML.java:444)
at com.rmc.dynamic.RSVYieldsHTML.doPost(RSVYieldsHTML.java:37)
at com.rmc.dynamic.RSVYieldsHTML.doGet(RSVYieldsHTML.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service
(ServletWrapper.java(Compiled Code))
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server *
* V6.0.1 for z/OS *
****************************************************************
* PROBLEM DESCRIPTION: If an unexpected exception occurs in *
* processing a forward or an include *
* request the webcontainer may cause *
* further unexpected exceptions. Such an *
* unexpected exception could be caused, *
* for example, by bad parameters being *
* passed as part of the forward or *
* include requests. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When processing a forward or an include request, in the event
of an unexpected exception the webcontainer attempts to clean
up the request thread before returning. However is does not
track the work done in processing up to the point of the
exception and as a result may attempt to clean up work which
has not been done. This leads to further unexpected exceptions.
Problem conclusion
Forward and include processing has been updated to track work
completed. In the event of an unexpected exception the
webcontainer only cleans up work which was completed prior to
the exception.
APAR PK34536 is currently targeted for inclusion in Service
Level (Fix Pack) 6.0.2.21 of WebSphere Application Server V6.0.1
for z/OS.
Temporary fix Comments
APAR information |
APAR number |
PK34536 |
Reported component name |
WEBSPHERE FOR Z |
Reported component ID |
5655I3500 |
Reported release |
601 |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2006-11-13 |
Closed date |
2007-04-24 |
Last modified date |
2007-08-03 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PK34539
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WEBSPHERE FOR Z |
Fixed component ID |
5655I3500 |
Applicable component levels |
R500 PSN |
UP |
R601 PSY UK27100 |
UP07/07/25 P F707 |
R610 PSY |
UP |
Fix is available |
Select the PTF appropriate for your component level. You will be
required to sign in. Distribution on physical media is not available in
all countries. |
|