PM49447: WMSG0017E and WMSG0019E due to ClassCastException connecting to Tibco Generic JMS Provider after migration from v6.x

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

• JAVA.NAMING.FACTORY.OBJECT is not honoured with the OSGi
  Applications and JPA 2.0 feature pack installed.
  
  When migrating from WebSphere Application Server v6.x to v8.0,
  the following problem can occur when using a 3rd party JMS
  provider configured as a Generic JMS Provider in the WebSphere
  Application Server v8.0 configuration.
  
  This exception occurs when using a Tibco JMS Provider:
  
  [1/2/12 11:23:48:455 CST] 00000019 MDBListenerIm W   WMSG0019E:
  Unable to start MDB Listener MyMDBListener, JMSDestination
  jms/MyJMSDestination : java.lang.ClassCastException:
  com.tibco.tibjms.naming.TibjmsQueueName incompatible with
  javax.jms.Destination
          at
  com.ibm.ejs.jms.listener.MDBListenerImpl.createResources
  (MDBListenerImpl.java:263)
          at
  com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart
  (MDBListenerImpl.java:734)
          at com.ibm.ejs.jms.listener.MDBListenerImpl.start
  (MDBListenerImpl.java:657)
          at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start
  (MDBListenerManagerImpl.java:827)
          at
  com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.
  java:235)
  ...
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM WebSphere Application Server users  *
  ****************************************************************
  * PROBLEM DESCRIPTION: JAVA.NAMING.FACTORY.OBJECT JVM          *
  *                      property is not honoured.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the Apache Aries code was attempting to return an object
  instance due to a JNDI lookup, it was not attempting to use
  the user specified object factories in the
  JAVA.NAMING.FACTORY.OBJECT JVM property.
  

Problem conclusion

• The code has been modified to ensure that it will attempt to
  use JAVA.NAMING.FACTORY.OBJECT factories when specified.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.2. 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:

  PM44835

• 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

• R800 PSY

     UP