Fix (APAR):  PQ82970

Status:  Fix

Release:  4.0.7

Operating System:  All

Supersedes Fixes:  

CMVC Defect:  PQ82970

Byte size of APAR:  1067564

Date: 2004-07-06

Abstract:  Add same header twice may cause NullPointerException

Description/symptom of problem:  Add same header twice may cause NullPointerException when the header duplication is not allowed. Most headers defined in HTTP/1.1 spec can not be duplicated.
In such case, IOException may be seen because written data is less than the length specified.



Directions to apply fix:  
1) Create temporary "fix" directory to store the jar file:
   Unix: /tmp/WebSphere/fix
   Windows: c:\temp\WebSphere\fix

2) Copy jar file to the directory

3) Shutdown WebSphere

4)Create a <WASHOME>/Fix directory if one does not already exist

5) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name> -backupJar <WASHOME>/Fix/<jar file name>_backup.jar

6) Restart WebSphere

7) The temp directory may be removed but the jar file should be saved.  Do not remove
	any files created and stored in the <WASHOME>/Fix directory.
   These files are required if a fix is to be removed.




Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS
 		ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be
			 removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.


1) Change directory to the fix location (<WASHOME>/Fix).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
	java -jar <backup_fix#>

4) Restart WebSphere




Directions to re-apply fix:  
Follow the instructions for applying a fix.

If the backup files still exist (from the previous fix application), you will be prompted to overwrite.

Answer "yes" at the overwrite prompts.



Additional Information:  It is not a good practice to addHeader twice for HTTP/1.1 defined headers. The final response will only have one such header even if more than one has been added. All others will be removed and no guarentee which one is left. Thus, addHeader twice is stronly discuraged especially for headers defined in HTTP/1.1 spec.