Fix (APAR):  PI38266

Status:  Fix

Release:  8.5.0.2

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  5456372

Date: 2015-04-06

Abstract:  Common shared library classes may define twice when using persistence

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

ERROR DESCRIPTION:                                              
When a server deployment declares applications that share a     
common library, and at least one of the applications uses       
the JPA-1.0 feature, it is possible that classes within the     
shared library will define more than once.                      
                                                                
This is generally not a problem unless a class in the shared    
library loads a native library during its static                
initialization.  A native library may load exactly once over    
the life cycle of the server JVM.  If such a common library     
class defines more than once, the second time will result in    
a failure when the class attempts to reload the native          
library during static initialization.                           

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
 All users of IBM WebSphere Application
Server version 8.5.0 Liberty Profile that
use feature jpa-1.0, shared libraries, and
native libraries.

PROBLEM DESCRIPTION:
A class in a common shared library may
define more than once.

RECOMMENDATION:
None

When deploying two or more applications that reference a common
shared library, classes in the library may define more than once
whenever one of the applications uses feature jpa-1.0 and
another does not.  If a shared library class loads a native
library within a static block, and said class defines more than
once, then the application will fail with an
UnsatisfiedLinkError when the class attempts to reload native
library during its subquent static initialization.

PROBLEM CONCLUSION:                                             
APAR PI38266 resolves this problem by changing the application  
class loaders to define classes of common libraries referenced  
by more than one application, including applications that use   
JPA-1.0, exactly once over the life time of the Application     
Server JVM.                                                     
                                                                
The fix for this APAR is not currently targeted for inclusion in
any fix pack.  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.5.0.2
X_ Application Server (BASE)
X_ Network Deployment (ND)

Install Fix to all WebSphere Virtual Enterprise 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: