Fix (APAR):  PQ76673

Status:  Fix

Release:  4.0.6,4.0.5

Operating System:  All

Supersedes Fixes:  



CMVC Defect:  PQ76673

Byte size of APAR:  1073622

Date: 2003-09-15, updated 2004-06-22

Abstract:  
On WebSphere 4.0.4, the customer is getting NullPointerException
coming from java.lang.String.<init> from the servlet engine 
com.ibm.servlet.engine.srt.SRTRequestUtils.getJvmConverter.


Description/symptom of problem:  

Error description
On WebSphere 4.0.4, the customer is getting NullPointerException
coming from java.lang.String.<init> from the servlet engine com.
ibm.servlet.engine.srt.SRTRequestUtils.getJvmConverter.

Local fix
 
Problem summary

USERS AFFECTED: 
WebSphere Application Server uses default property files without a 
locale suffix.

PROBLEM DESCRIPTION: 
When users have default property files loaded dynamically, 
the server gets a NullPointerException and the property
file is not loaded. If the file name is appended with the 
default locale, it will work properly.

RECOMMENDATION:
The SRTServletResponse.setCharacterEncoding method allows a null
to be set as an encoding parameter. This will cause a
NullPointerException when the response tries to use the null to
construct an encoding string, and loading of the properties file
will be aborted.

Problem conclusion
Added checking logic for a null input in setCharacterEncoding,
and set to default encoding when it is null.
The default encoding is en_US as hard coded in the class.


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: