Fix (APAR):  JR27678

Status:  Fix

Release:  6.0.2.2

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  JR27678

Byte size of APAR:  15801

Date: 2007-11-15

Abstract:  First Failure Data Capture (FFDC) logging of IOException causes leads to OutOfMemoryError.

Description/symptom of problem:  
JR27678 resolves the following problem:

ERROR DESCRIPTION:                                              
This is a failure scenario when there errors occur in           
serializing and deserializing business objects.                 
                                                                
If these errors are not handled with business logic, they       
will be handled by the  WebSphere Process Server error system.  
This  will log messages using the First Failure Data            
Capture (FFDC) system. Currently, the processing for this       
logging might consume and require large memory allocations      
(10MB, 20MB, 30MB allocations) when processing these errors.    
These large memory allocations might lead to an Out Of Memory   
exception.                                                      
                                                                
This FFDC logging behavior will be changed so that the entire   
object is not logged.  This will remove the need for these large
allocations.                                                    
                                                                
The stack trace example for this error is as follows.           
                                                                
                                                                
Allocation request for 33562632 bytes                           
 at java.io.StringWriter.write(StringWriter.java(Compiled Code))
 at                                                             
java.io.BufferedWriter.flushBuffer(BufferedWriter.java(Compiled 
Code))                                                          
 at java.io.BufferedWriter.flush(BufferedWriter.java(Compiled   
Code))                                                          
 at java.io.PrintWriter.flush(PrintWriter.java(Compiled Code))  
 at                                                             
com.ibm.ws.sca.logging.ObjectDumper.dump(ObjectDumper.java:450) 
 at                                                             
com.ibm.ws.sca.logging.impl.JSR47LogImpl.ffdc(JSR47LogImpl.java:
218)                                                            
 at                                                             
com.ibm.ws.sca.internal.managed.WASLogImpl.ffdc(WASLogImpl.java:
44)                                                             
 at                                                             
com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl.load(XMLFile
ServiceI                                                        
mpl.java(Compiled Code))                                        
 at                                                             
com.ibm.ws.sca.internal.sdo.impl.XMLFileServiceImpl.access$000(X
MLFileSe                                                        
rviceImpl.java:68)                                              

LOCAL FIX:                                                      
Implemement business logic to programatically handle the error  
scenario.                                                       
                                                                
A fix is also available which changes the logging behavior      

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server and WebSphere
Enterprise Service Bus version 6.0.2.2
users.

PROBLEM DESCRIPTION:
First Failure Data Capture (FFDC)
logging of IOException causes leads
to OutOfMemoryError.

RECOMMENDATION:
None

Logging of IOException caught during business Object
serialization/deserialization consumes large memory (upto 30
MB per failure). Overtime this leads WebSphere Process Server
to crash with OutOfMemoryError.

PROBLEM CONCLUSION:                                             
Apply iFix to resolve the large memory consumption.             


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: