IBM Support

IC59986: LOTUS EXPEDITOR VERSION 6.2 FAILS TO RECONNECT TO MICROBROKER AUTOMATICALLY FOLLOWING A FAILURE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using Lotus Expeditor Version 6.2 with the Spring
    template, applications fail to reconnect to MicroBroker
    automatically following a failure. In order to start processing
    messages again, the application needs to be restarted.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of the OGSi bundles shipped as
    part of the WebSphere MQ (WMQ) Version 7 Java client.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    The classloader in the WebSphere MQ Version 7 Java client's
    ComponentManager that scans for instances of
    META-INF/compinfo.properties does not work in OSGi.
    
    Both the WebSphere MQ TT client and the WebSphere MQ Version 7
    client are used by Lotus Expeditor, and explicitly register
    their services in their respective bundle activators. Because
    of this, a simple race condition exists whereby whichever
    bundle is started first will get its services registered first,
    overriding the other.
    
    This has the effect that J2ME common services get applied over
    the top of J2SE common services, which results in the problem
    reported in this APAR.
    

Problem conclusion

  • The Client Activator was modified so that it scans all of the
    bundles and, if it finds the J2SE common services bundle, it
    doesn't register the J2ME one.
    
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.0
    --------           --------------------
    Windows            U200306
    AIX                U823774
    HP-UX (PA-RISC)    U823665
    HP-UX (Itanium)    U823667
    Solaris (SPARC)    U823772
    Solaris (x86-64)   U824344
    iSeries            tbc_p700_0_1_0
    Linux (x86)        U823664
    Linux (x86-64)     U823773
    Linux (zSeries)    U823668
    Linux (Power)      U823666
    
    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

    IC59986

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-12

  • Closed date

    2009-02-24

  • Last modified date

    2009-02-24

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
24 February 2009