IC60661: NOSUCHMETHODEXCEPTION WHEN CONNECTING TO WEBSPHERE MQ FROM LOTUS EXPEDITOR

WebSphere MQ V7.0 Fix Pack 7.0.1.1
WebSphere MQ V7.0 Fix Pack 7.0.1.2

APAR status

• Closed as documentation error.

Error description

• When using Lotus Expeditor Version 6.2, the following error
  occurs when trying to connect to WebSphere MQ:
  
  java.lang.NoSuchMethodException:
  java.util.MissingResourceException.<init>(java.lang.String)
  at java.lang.Class.throwNoSuchMethodException(Unknown Source)
  at java.lang.Class.getConstructor(Unknown Source)
  at com.ibm.msg.client.commonservices.trace.Trace.
  ffstInternal(Unknown Source)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of Lotus Expeditor Version 6.2.
  
  Platforms affected:
  All Distributed (iSeries, all Unix and Windows) +Java
  ****************************************************************
  PROBLEM SUMMARY:
  Lotus Expeditor 6.2 uses the WebSphere MQ (WMQ) V7 OSGi bundles
  when connecting to a WMQ queue manager.
  
  Lotus Expeditor performed its own explicit registration of its
  OSGi bundles during startup. Unfortunately, this led to a clash
  with the WMQ V7 OSGi bundles, and meant that certain classes
  and methods were no longer available to it.
  

Problem conclusion

• Lotus Expeditor has been changed to no longer explicitly
  register its own OSGi bundles during startup.
  
  The JavaDoc for two WMQ V7 methods have also been updated to
  include information about how they work in an OSGi environment.
  Details of these changes are shown below:
  
  
  com.ibm.msg.client.commonservices.componentmanager.
  ComponentManager.registerComponent(Component)
  ----------------------------------------------------------------
  When called in an OSGi environment, this method will explicitly
  force the ComponentManager to use the component passed in
  regardless of what other ones are available.
  
  
  com.ibm.msg.client.commonservices.componentmanager.
  ComponentManager.getInstance()
  ----------------------------------------------------------------
  Calling this method in a BundleActivator will stop the
  ComponentManager from finding components in the OSGi runtime.
  

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

Applicable component levels