APAR status
Closed as program error.
Error description
JNDI operation may fail due to an Exception while attempting to obtain an object instance from an ObjectFactory. In previous releases such an Exception was caught and alternative methods of retreiving the object instance were performed successfully. An example callstack is show below: javax.naming.NoInitialContextException: Unable to determine caller's BundleContext; remaining name '' at com.ibm.osgi.jndi.fep.bridge.ServiceReaperImpl.addBundleCon text(ServiceReaperImpl.java:359) at com.ibm.osgi.jndi.fep.bridge.ServiceReaperImpl$BundleContex tAddingObjectFactoryProxy.getObjectInstance(ServiceReaperImpl.j ava:265) at org.apache.aries.jndi.ObjectFactoryHelper.getObjectInstance UsingObjectFactories(ObjectFactoryHelper.java:134) at org.apache.aries.jndi.ObjectFactoryHelper.access$300(Object FactoryHelper.java:39) at org.apache.aries.jndi.ObjectFactoryHelper$1.run(ObjectFacto ryHelper.java:100) at java.security.AccessController.doPrivileged(AccessControlle r.java:734) at org.apache.aries.jndi.ObjectFactoryHelper.getObjectInstance (ObjectFactoryHelper.java:67) at org.apache.aries.jndi.OSGiObjectFactoryBuilder.getObjectIns tance(OSGiObjectFactoryBuilder.java:66) at javax.naming.spi.DirectoryManager.getObjectInstance(Directo ryManager.java:177)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: JNDI operations fail if an * * ObjectFactory throws an Exception. * **************************************************************** * RECOMMENDATION: * **************************************************************** The fix for APAR PH02744 backported, into WebSphere Application Server, the fix for an issue in the open source Apache Aries project identified in JIRA ARIES-1068. When obtaining an object instance, the OSGi JNDI implementation's InitialContextFactoryBuilder must try several different methods to obtain the instance. The fix modified the Exception handling such that an Exception from one such method was no longer handled causing a premature failure of the attempt.
Problem conclusion
The defect in Apache Aries JIRA ARIES-1068 was identified and fixed in Apache Aries JIRA ARIES-2000. The fix for this APAR backports the open source fix for the ARIES-2000 JIRA into the version of Apache Aries shipped in WebSphere Application Server. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.11. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
Comments
APAR Information
APAR number
PH43816
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-02-02
Closed date
2022-02-10
Last modified date
2022-02-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
04 May 2022