PM44835: CLASSCASTEXCEPTION CONNECTING TO TIBCO GENERIC JMS PROVIDER AFTER MIGRATION FROM VERSION 6

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.
  
  After migrating from WebSphere Application Serve version 6 to
  version 7.0.0.19 and having Feature Pack for OSGi Applications
  and JPA version 1.0.0.5 installed, experiencing
  java.lang.ClassCastException when connecting to TIBCO Generic
  JMS Provider. Depending how the message queue is looked up, this
  java.lang.ClassCastException can be thrown by application, or by
  WebSphere Application Server code, like:
  
  MDBListenerIm W   WMSG0017E: Unable to lookup JMS resources,
  JNDI lookup exception: com.tibco.tibjms.naming.TibjmsQueueName
  incompatible with javax.jms.Destination
  MDBListenerIm W   WMSG0019E: Unable to start MDB Listener
  MyTestMDB, JMSDestination jms/Tibco/MyTestQueueDestination :
  java.lang.ClassCastException:
  com.tibco.tibjms.naming.TibjmsQueueName incompatible with
  javax.jms.Destination
   at
  com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBList
  enerImpl.java:259)
   at
  com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListen
  erImpl.java:730)
   at
  com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.j
  ava:653)
   at
  
  
  or it can also come from Universal Test Client (UTC) if this is
  used, like:
  
  
  java.lang.ClassCastException:
  com.tibco.tibjms.naming.TibjmsQueueName incompatible with
  org.omg.CORBA.portable.ObjectImpl
   at
  com.ibm.rmi.javax.rmi.PortableRemoteObject.getObjectImpl(Portabl
  eRemoteObject.java:620)
   at
  com.ibm.rmi.javax.rmi.PortableRemoteObject.narrow(PortableRemote
  Object.java:341)
   at
  javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:
  148)
   at
  com.ibm.etools.utc.servlet.UtilityServlet.postToQueue(UtilitySer
  vlet.java:140)
   at
  com.ibm.etools.utc.servlet.UtilityServlet.doPost(UtilityServlet.
  java:288)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All IBM WebSphere Application Server        *
  *                  Feature                                     *
  *                  Pack for OSGi Applications and JPA 2.0      *
  *                  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 1.0.0.7. 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:

  PM49447

Fix information

• Fixed component name

  JPA OSGI FEATUR

• Fixed component ID

  5724J0857

Applicable component levels

• R700 PSY

     UP