Fix (APAR):  PI10107

Status:  Fix

Release:  8.5.5.1,8.5.0.2

Operating System:  AIX,HP-UX,IBM i,Linux,Mac OS,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  744806

Date: 2014-03-28

Abstract:  slow performance when manipulating ebas and cus

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

ERROR DESCRIPTION:                                              
Editing, browsing and manipulating EBAs and Composition Units   
is generally slow.                                              

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 All users of IBM WebSphere Application
Server OSGi Applications

PROBLEM DESCRIPTION:
Working with EBAs and Composition
Units exhibits poor performance and
long delays.

RECOMMENDATION:
None

OSGi applications must parse the contents of EBA files for
modules, configuration XML etc. when they are manipulated.
This takes a long time.
Objects created during parsing of the EBAs are not cached, but
are often needed repeatedly while manipulating and working
with EBAs and Compsition Units.
The operations are also performed on a single thread.

PROBLEM CONCLUSION:                                             
This APAR introduces two new JVM custom properties.  When not   
set there is no change in behaviour.                            
                                                                
com.ibm.ws.eba.bla.proxies.archiveCacheSize (default 0,         
minimum 0, maximum 10000) - this property controls the size of  
a cache that is used for Archive objects parsed from an EBA.    
If an Archive is created, and the cache size is greater than    
0, it may be cached so that it can later be reused.  Typically  
a cache size of 500 is sufficient.  The cache is a soft cache   
and so its efficiency is affected by the amount of free heap    
space.                                                          
                                                                
com.ibm.ws.eba.bla.concurrency (default 1, minimum 1, maximum   
8) - this property controls the concurrency with which steps    
during the manipulation of EBAs might be performed.             
Typically, increasing this number from the default 1 will only  
have performance improvements if                                
com.ibm.ws.eba.bla.proxies.archiveCacheSize is also set, and    
the EBAs being manipulated are sufficicently large in terms of  
the number of bundles.  Increasing the concurrency does not     
result in linear performance improvement because each thread    
requires its own Archive which is expensive to create.          
Consequently, a concurrency of two often offers the optimum     
performance.                                                    
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix pack 8.5.5.3.  Please refer to the Recommended Updates      
page for delivery information:                                  
                                                                
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  Fix applies to Editions:
Release 8.0
X Application Server (Express or BASE)
X Network Deployment (ND)

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: