APAR status
Closed as program error.
Error description
java.lang.NullPointerException when setContentType is called
in a multi threaded environment.
Local fix
None stated.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server using its own *
* thread to interact with request and *
* response objects. *
****************************************************************
* PROBLEM DESCRIPTION: When a servlet/jsp creates its own *
* thread and uses the thread to access a *
* response object a NullPointerException *
* is thrown. *
****************************************************************
* RECOMMENDATION: Users should avoid creating new thread to *
* deal with response or request objects. *
****************************************************************
ResponseContext is thread specific. In a servlet that spans
threads, ResponseContext is not accessible and causes
NullPointerException when trying to use it.
Devleopment is looking at a long term solution for all thread
related problems.
Problem conclusion
The current solution is adding checks on points to get
ResponseContext. If the context is null, avoid any further use.
Temporary fix
Test fix provided on Oct 3.
Comments
APAR information |
APAR number |
PQ79079 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-10-01 |
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 |
|