PQ82970: IN A JSP IF TWO ADDHEADERS ARE SET & NO EXPIRATION HEADER, NULLPOINTEREXCEPTION IS THROWN

 Fixes are available

5.1.0.5: WebSphere Application Server Express 5.1 Cumulative Fix 5
PQ82970; 4.0.7: NullPointerException when servlet or JSP calls addHeader twice
5.0.2.7: WebSphere Application Server Express 5.0.2 Cumulative Fix 7
5.1.1: WebSphere Application Server Version 5.1 Fix Pack 1 (Version 5.1.1)
5.0.2.12: WebSphere Application Server 5.0.2 Cumulative Fix 12
5.0.2.13: WebSphere Application Server 5.0.2 Cumulative Fix 13
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for AIX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Solaris
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for HP-UX
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Windows
5.0.2.14: WebSphere Application Server 5.0.2 Cumulative Fix 14 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Windows
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Solaris
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for AIX
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for Linux
5.0.2.15: WebSphere Application Server 5.0.2 Cumulative Fix 15 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for HP-UX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for AIX
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Solaris
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Windows
5.1.1.9: WebSphere Application Server V5.1.1 Cumulative Fix 9 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for AIX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for HP-UX
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Linux
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Windows
5.0.2.16: WebSphere Application Server 5.0.2 Cumulative Fix 16 for Solaris
5.0.2.8: WebSphere Application Server V5.0.2 Cumulative Fix 8
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for HP-UX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for AIX
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Solaris
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Windows
5.1.1.10: WebSphere Application Server V5.1.1 Cumulative Fix 10 for Linux
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Windows
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Solaris
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for HP-UX
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for Linux
5.0.2.17: WebSphere Application Server 5.0.2 Cumulative Fix 17 for AIX



APAR status
Closed as program error.

Error description
JSP PAGE SETTING THE CONTENT-LANGUAGE HEADER CAUSES NULL
POINTER EXCEPTION UNLESS EXPERIATION HEADER IS SET
Problem summary: In a jsp if one calls two addHeader and sets NO
expiration header, there is a NullPointerException thrown. If on
two addHeader and DOES set an expiration header, all works fine.
interesting fact is that if one uses the setHeader, no exception
thrown, it works.
Local fix
The problem is that the jsp add content language header twice. O
response can only have one content-language header. Thus web con
have to remove one and left a hole in headers. That hole causes
NullPointerException.

As a workaround, customer can remove one addHeader("Content-Lang
...).
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server servlet or JSP  *
*                 users.                                       *
****************************************************************
* PROBLEM DESCRIPTION: A servlet or jsp that calls             *
*                      removeHeader will leave a hole (null)   *
*                      in the header list. That causes a       *
*                      NullPointerException.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A servlet or jsp that calls removeHeader will leave a hole
(null) in the header list due to an incorrect algorithm  to
remove headers. This hole causes a NullPointerException.
Problem conclusion
Fixing the algorithm of removing headers fixed the problem.
Temporary fix
Fixtest posted on 
pq99999.
Comments
APAR information
APAR number PQ82970
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2004-01-07
Closed date 2004-03-10
Last modified date 2004-03-10

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WEBENG          

SRLS

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ82970
IBM Group: Software Group
Modified date: Mar 10, 2004