PQ82970; 4.0.7: NullPointerException when servlet or
JSP calls addHeader twice
Downloadable files
Abstract
When a servlet or JavaServer Page™ (JSP™) sets addHeader
twice, but does not set an expiration header, a NullPointerException
results.
Download Description
PQ82970 resolves the following problem:
ERROR DESCRIPTION:
A servlet or JSP that sets the content-language header twice causes a
NullPointerException unless an expiration header is set.
PROBLEM SUMMARY:
If a servlet or JSP calls addHeader twice and NO expiration header, a
NullPointerException is thrown. If the servlet or JSP calls addHeader
twice and DOES set an expiration header, all works fine. If setHeader is
used, no exception is thrown.
USERS AFFECTED:
WebSphere Application Server V4.0.7 servlet or JSP users.
PROBLEM DESCRIPTION:
A servlet or jsp that calls removeHeader will leave a hole (null) in the
header list. This also causes a NullPointerException.
RECOMMENDATION:
Apply interim fix PQ82970.
Prerequisites
NONE
Installation instructions
Please review the readme.txt for detailed installation
instructions.