Fix (APAR):  JR37034

Status:  Fix

Release:  6.2.0.2

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

Supersedes Fixes:  

CMVC Defect:  JR37034

Byte size of APAR:  13703

Date: 2010-08-30

Abstract:  Slow response time from remote SCA Exports when the payload contains nested XML elements

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

ERROR DESCRIPTION:                                              
When the SCA bindings are invoked across different JVM's, the   
message is deserialized at the target which takes around 3-4    
mins to parse a 400KB large data which is performance           
bottleneck. Need to optimize the parsing logic.                 

LOCAL FIX:                                                      
None.                                                           

PROBLEM SUMMARY

USERS AFFECTED:
 ALL

PROBLEM DESCRIPTION:
Slow response time from remote
SCA Exports when the payload contains
nested XML elements

RECOMMENDATION:
None

The XML processing algorithm used by the SCA binding does not
efficiently handle XML which is nested within xs:string fields
of business objects. When XML is nested within such fields,
the processing algorithm requires additional computation to
locate elements integral to execution of the request. This
additional computation consumes large amounts of CPU resources.

PROBLEM CONCLUSION:                                             
To improve efficiency, the algorithm was restructured in such   
a way that this additional computation is no longer necessary.  


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: