PM45000: URL JNDI LOOKUPS WITH THE RMI SCHEME ARE FAILING.

8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• URL JNDI lookups with the RMI scheme are failing on
  WebSphere Application Server v8 due to not finding the
  URLContextFactory for RMI scheme. This problem can be hidden
  underneath other layers like JMX that fail
  when using RMI JNDI lookups internally. For example code like
  the below example would fail:
  
  JMXConnector connector = JMXConnectorFactory.connect(new
  JMXServiceURL("service:jmx:rmi:///jndi/rmi://somehost:4455/somem
  bean"));connector.getMBeanServerConnection()
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server v8                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: URL lookups are failing when            *
  *                      attempting to use built-in              *
  *                      com.sun.url schemes.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The OSGi Applications code that is intercepting the URL lookup
  was not searching for ObjectFactories that belong in the
  com.sun.jndi.url package.
  

Problem conclusion

• This APAR solves the problem by looking for ObjectFactories
  following the com.sun.jndi.url package structure.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.2 of WebSphere Application Server. Please
  refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM49466

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP