Fix (APAR):  JR28406

Status:  Fix

Release:  6.1,6.0.2.3,6.0.2.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  143832

Date: 2008-05-02

Abstract:  Large Number of map transformations cause a build error "STATIC INITIALIZER EXCEEDS THE 65535 BYTES LIMIT"

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

ERROR DESCRIPTION:                                              
If you have large number of  map transformation in a single     
submap ( ~1400) , you will see following failure in WID         
environment .                                                   
                                                                
 "The code for  the static initializer is exceeding the 65535   
 bytes limit".                                                  
                                                                
Each transformation in the map will have multiple static        
variables initialized  in the generated code.                   
When you have large number of transformation , the amount of    
Java class bytecode per method will exceed  limit  65535 bytes  
and you will see the above serviceDeploy failure.               

LOCAL FIX:                                                      
You can work around this issue by creating submaps to reduce the
number of transformation in a single MAP.                       

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server v6.1 users using a
large number of map transformations (around
100 or greater.

PROBLEM DESCRIPTION:
Large Number of map transformations
cause a build error "STATIC
INITIALIZER EXCEEDS THE 65535 BYTES
LIMIT"

RECOMMENDATION:
None

For each transformation in the map, static Event Points are
initialized. If the user has a large number of map
transformations the generated Map code exceeds the limit of
65535 bytes for static initializers.

PROBLEM CONCLUSION:                                             
Applying this interim fix changes the code generation design    
to create a static array that initializes the static variables. 


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. 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: