Fix (APAR):  PI07313

Status:  Fix

Release:  8.0.0.7

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

Supersedes Fixes:  PM90923

CMVC Defect:  xxxxxx

Byte size of APAR:  292985

Date: 2013-12-13

Abstract:  not necessary for fixpacks containing pm90923 - pm90923 interim fix invalid, causes noclassdeffounderror

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

ERROR DESCRIPTION:                                              
The fix published for PM90923 is invalid, and causes a          
java.lang.NoClassDefFoundError:                                 
org/apache/aries/jndi/spi/AugmenterInvoker error.               
                                                                
PM90923 fix present in Fix Packs (currently targetted for       
8.0.0.8 and 8.5.5.1) is valid, this APAR is only to allow a     
superceding fix to be published.                                
                                                                
PM90923 Error description:                                      
                                                                
NOINITIALCONTEXTEXCEPTION                                       
CALLING CODE'S BUNDLECONTEXT COULD NOT BE DETERMINED            
                                                                
When using the Apache Aries enterprise bundle application       
(EBA), containing two OSGi Blueprint bundles, the following     
exception is encountered;                                       
                                                                
javax.naming.NoInitialContextException: The calling code's      
 BundleContext could not be determined.                         

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
 All users of IBM WebSphere Application
Server who have applied the interim fix
for PM90923

PROBLEM DESCRIPTION:
The published interim fix for PM90923
is incorrect, and causes a
NoClassDefFoundError

RECOMMENDATION:
None

A manifest file was missing from the interim fix for PM90923,
causing required classes to not be visible to a JNDI bundle.
When an application made an "osgi:" URL scheme JNDI lookup,
the lookup fails as the class is not available.

PROBLEM CONCLUSION:                                             
The interim fix has been re-built, and is being made available  
under this APAR to ensure the updated fix can be applied to     
existing systems that have the PM90923 interim fix applied. No  
new code changes have been made, and therefore if a Fix Pack    
has been applied with PM90923 included, this fix will not be    
necessary.                                                      
                                                                
The fix for this APAR is the same as PM90923, which is          
currently targeted for inclusion in fix pack 8.0.0.8 and        
8.5.5.1. 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)
__ Edge Components
_X_ Developer

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: