IBM Support

IC64572: RESTART OF LOTUS EXPEDITOR INTEGRATOR IN A WMQ V7.0.1.0 ENVIRONMENT RESULTS IN A JAVA.LANG.CLASSCIRCULARITYERROR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The micro broker component of Lotus Expeditor uses WebSphere MQ
    (WMQ) Java Message Service (JMS) to connect to the WMQ server.
    Upon restart of the Lotus Expeditor Integrator, an exception is
    generated:
    java.lang.ClassCircularityError
    .
    The generated stack trace is:
    <extendedDataElements
    name="CommonBaseEventLogRecord:Exception"type="string">
    <values>org.osgi.framework.BundleException: Exception in
    com.ibm.msg.client.osgi.jms.Activator.start() of bundle
    com.ibm.msg.client.osgi.jms.
    at
    org.eclipse.osgi.framework.internal.core.BundleContextImpl.
    startActivator(Unknown Source)
    at
    org.eclipse.osgi.framework.internal.core.BundleContextImpl.
    start(Unknown Source)
    at
    ...
    ...
    org.eclipse.osgi.framework.eventmgr.EventManager$Event
    Thread.run(Unknown Source)
    Caused by:
    java.lang.ClassCircularityError
    at
    org.eclipse.osgi.baseadaptor.loader.ClasspathManager.
    defineClass(Unknown Source)
    at
    org.eclipse.osgi.baseadaptor.loader.ClasspathManager.
    findClassImpl(Unknown Source)
    at
    ...
    ...
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Lotus Expeditor micro broker with WebSphere MQ 7.0.1.0
    JMS bundles
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    The WMQ JMS Client Activator preloaded bundles to ensure that
    the J2SE commonservices bundle was registered in case of a race
    condition.
    This preloading of classes could lead to a class being loaded
    as its own superclass and hence leading to the
    java.lang.ClassCircularityError.
    

Problem conclusion

  • The preloading of classes in the WMQ JMS Client Activator has
    been removed to alleviate the ClassCircularityError.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.2
    --------           --------------------
    Windows            U200316
    AIX                U829807
    HP-UX (PA-RISC)    U829678
    HP-UX (Itanium)    U829681
    Solaris (SPARC)    U829806
    Solaris (x86-64)   U829680
    iSeries            tbc_p700_0_1_2
    Linux (x86)        U829677
    Linux (x86-64)     U829676
    Linux (zSeries)    U829682
    Linux (Power)      U829679
    
    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 number

    IC64572

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-11-16

  • Closed date

    2009-11-30

  • Last modified date

    2009-11-30

  • 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

  • R701 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023