IC66103: JAVA.LANG.NOCLASSDEFFOUNDERROR EXCEPTION SEEN IN OSGI ENVIRONMENT RUNNING WMQ 7.0.1 CLIENT

WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.3
WebSphere MQ V7.0 Fix Pack 7.0.1.3

APAR status

• Closed as program error.

Error description

• Exception seen when running WebSphere MQ client (WMQ) v7.0.1
  in an Equinox OSGi environment. The stack shows:
  
  java.lang.NoClassDefFoundError:
  javax.transaction.TransactionManager
  at java.lang.J9VMInternals.verifyImpl(Native Method)
  at java.lang.J9VMInternals.verifyImpl(Native Method)
  at java.lang.J9VMInternals.verify(J9VMInternals.java:69)
  at java.lang.J9VMInternals.verify(J9VMInternals.java:69)
  at java.lang.J9VMInternals.initialize(J9VMInternals.java:131)
  at java.lang.J9VMInternals.initialize(J9VMInternals.java:236)
  at
  com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.<init>
  (MQMessag eConsumer.java:489)
  at
  com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.<init>
  (MQMessag eConsumer.java:489)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the WebSphere MQ V7 OSGi bundles
  that run in an Equinox environment.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java
  ****************************************************************
  PROBLEM SUMMARY:
  The problem here was that there were two versions of the
  packages:
  
  javax.transaction
  javax.transaction.xa
  
  being loaded into the OSGi environment.
  
  The WebSphere MQ bundle:
  
  com.ibm.msg.client.osgi.wmq
  
  was expecting to use the versions of these packages provided in:
  
  com.ibm.msg.client.osgi.wmq.prereq
  
  However, due to the order in which the different versions of
  the packages were being loaded by the OSGi framework, it
  actually picked up a version of javax.transaction that didn't
  contain the class:
  
  javax.transaction.TransactionManager
  

Problem conclusion

• The OSGi bundle:
  
  com.ibm.msg.client.osgi.wmq.prereq
  
  has been changed to export a specific version of the packages:
  
  javax.transaction
  javax.transaction.xa
  
  These versions are now imported by the bundle:
  
  com.ibm.msg.client.osgi.wmq
  
  which ensures that it will always load and use the versions it
  expects.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.3
  --------           --------------------
  Windows            tbc_p700_0_1_3
  AIX                tbc_p700_0_1_3
  HP-UX (PA-RISC)    tbc_p700_0_1_3
  HP-UX (Itanium)    tbc_p700_0_1_3
  Solaris (SPARC)    tbc_p700_0_1_3
  Solaris (x86-64)   tbc_p700_0_1_3
  iSeries            tbc_p700_0_1_3
  Linux (x86)        tbc_p700_0_1_3
  Linux (x86-64)     tbc_p700_0_1_3
  Linux (zSeries)    tbc_p700_0_1_3
  Linux (Power)      tbc_p700_0_1_3
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available, information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

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:

Fix information

• Fixed component name

  WMQ WINDOWS V7

• Fixed component ID

  5724H7220

Applicable component levels

• R700 PSY

     UP