IC72511: USEJNDI PROPERTY DOES NOT WORK ON APACHE GERONIMO WHEN USING THE V7.0 WEBSPHERE MQ RESOURCE ADAPTER

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

APAR status

• Closed as program error.

Error description

• JCA: useJNDI property doesn't work on Apache Geronimo
  
  Define a destination and set useJNDI to true:
  
  <activation-config-property>
  <activation-config-property-name>destination
  </activation-config-property-name>
  <activation-config-property-value>java:comp/env/TestQueue
  </activation-config-property-value>
  </activation-config-property>
  <activation-config-property>
  <activation-config-property-name>useJNDI
  </activation-config-property-name>
  <activation-config-property-value>true
  </activation-config-property-value>
  </activation-config-property>
  
  with a corresponding plan entry
  
  <conn:adminobject-interface>javax.jms.Queue
  </conn:adminobject-interface>
  <conn:adminobject-class>com.ibm.mq.connector.outbound.
  MQQueueProxy</conn:adminobject-class>
  <conn:adminobject-instance>
  <conn:message-destination-name>TestQueue
  </conn:message-destination-name>
  <conn:config-property-setting name="baseQueueName">
  TEST.QUEUE</conn:config-property-setting>
  </conn:adminobject-instance>
  
  Then a message driven bean (MDB) deployment fails with
  
  Caused by:
  com.ibm.mq.connector.DetailedResourceException: MQJCA0003: A
  JNDI naming exception was thrown. See the linked exception for
  details. An attempt to look up a JMS destination in the JNDI
  namespace failed. Either the namespace cannot be accessed, or
  a destination with the supplied name is not bound in the
  namespace.  See the linked exception for details of the
  failure.
  
  Check that the JNDI namespace is available, that a destination
  with the correct name is bound in the JNDI namespace, and that
  the value of the property called destination is correctly
  defined.
  at com.ibm.mq.connector.services.JCAExceptionBuilder.
  buildException(JCAExceptionBuilder.java:124)
  at com.ibm.mq.connector.services.JCAExceptionBuilder.
  buildException(JCAExceptionBuilder.java:100)
  at com.ibm.mq.connector.DestinationBuilder.
  createDestination(DestinationBuilder.java:113)
  at com.ibm.mq.connector.inbound.MessageEndpointDeployment.
  start(MessageEndpointDeployment.java:328)
  at com.ibm.mq.connector.inbound.MessageEndpointDeployment.<init>
  (MessageEndpointDeployment.java:301)
  at com.ibm.mq.connector.ResourceAdapterImpl.
  endpointActivation(ResourceAdapterImpl.java:463)
  at org.apache.openejb.core.mdb.MdbContainer.
  deploy(MdbContainer.java:137)
  ... 30 more
  Caused by:
  javax.naming.NameNotFoundException: TestQueue
  at java.lang.Throwable.<init>(Throwable.java:67)
  at javax.naming.NamingException.<init>(NamingException.java:98)
  at org.apache.xbean.naming.context.AbstractContext.
  lookup(AbstractContext.java:108)
  at org.apache.xbean.naming.context.AbstractContext.
  lookup(AbstractContext.java:619)
  at org.apache.xbean.naming.context.AbstractContext.
  lookup(AbstractContext.java:156)
  at org.apache.xbean.naming.context.AbstractContext.
  lookup(AbstractContext.java:619)
  at org.apache.xbean.naming.context.AbstractContext.
  lookup(AbstractContext.java:156)
  at org.apache.xbean.naming.context.AbstractContext.
  lookup(AbstractContext.java:605)
  at javax.naming.InitialContext.lookup(InitialContext.java:455)
  at com.ibm.mq.connector.DestinationBuilder.
  createDestination(DestinationBuilder.java:100)
  ... 34 more
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the WebSphere MQ v7.0 Resource
  Adapter (RA).  It has been observed when using the Apache
  Geronimo Application Server.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java
  ****************************************************************
  PROBLEM SUMMARY:
  When using the Apache Geronimo application server, the WebSphere
  MQ v7.0 JMS implementation was given an internal ("wrapper")
  version of the com.ibm.mq.MQDestination object rather than the
  com.ibm.mq.MQDestination itself.
  
  The WebSphere MQ classes for JMS code expected a native
  WebSphere MQ object rather than the wrapper class, which
  resulted in an exception being thrown.
  

Problem conclusion

• The code has been altered to use the underlying
  com.ibm.mq.MQDestination object as necessary.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
                     v7.0
  Platform           Fix Pack 7.0.1.5
  --------           --------------------
  Windows            U200324
  AIX                U839183
  HP-UX (PA-RISC)    U839621
  HP-UX (Itanium)    U839626
  Solaris (SPARC)    U839622
  Solaris (x86-64)   U839628
  iSeries            tbc_p700_0_1_5
  Linux (x86)        U839623
  Linux (x86-64)     U839627
  Linux (zSeries)    U839624
  Linux (Power)      U839625
  
  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