APAR status
Closed as program error.
Error description
The Java Servlet Specification Version 2.3 section "SRV.2.3.3.2
Exceptions During Request Handling" states "If a permanent
unavailability is indicated by the UnavailableException, the
servlet container must remove the servlet from service, call its
destroy method, and release the servlet instance."
Currently the servlet's destroy method is not being called when
a permanent unavailability is indicated by the
UnavailableException.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: webSphere user whoes servlet throw *
* permanently UnavailableException *
****************************************************************
* PROBLEM DESCRIPTION: When a servlet throws permanently *
* UnavailableException, WebSphere does *
* not destroy the servlet. This *
* behavior does not follow the servlet *
* specification. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
WebSphere does not destroy the servlet after a permanently
UnavailableException is thrown
Problem conclusion
WebSphere will now destory the servlet after the servlet throws
a permanently UnavailableException.
Temporary fix
fix is up
Comments
APAR information |
APAR number |
PQ79193 |
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-10-03 |
Closed date |
2003-10-16 |
Last modified date |
2003-10-16 |
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 |
|