IBM Support

PM31552: MESSAGING ENGINE IS AUTOMATICALLY STOPPED WHEN AN APPLICATION IS DEPLOYED OR UPDATED ON THE APPLICATION SERVER.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • An application is deployed in a cluster that is a member
    of Websphere Application Server v7.0.x Service Integration
    Bus. The deploying of the application causes the messaging
    engine to stop which then results in the following errors
    written to the SystemOut.log and the application fails
    to connect to the messaging engine:
    
    javax.jms.JMSException: CWSIA0241E: An exception was received
    during the call to the method JmsManagedConnectionFactoryImpl.
    createConnection: com.ibm.websphere.sib.exception.SIResource
    Exception CWSIT0088E: There are currently no messaging engines
    in bus XXXBus running.Additional failure information:
    CWSIT0103E: No messaging engine was found that matched the
    following parameters: bus=XXXBus, targetGroup=null,
    targetType=BusMember, targetSignificance=Preferred,
    transportChain=InboundBasicMessaging, proximity=Bus.
    

Local fix

  • Restart the jvm hosting the messaging engine
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server            *
    ****************************************************************
    * PROBLEM DESCRIPTION: The deployment of an application to a   *
    *                      server or cluster that contains a       *
    *                      space in its name results in the        *
    *                      messaging engine being automatically    *
    *                      stopped.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an application is deployed or updated this will cause a
    Bus configuration reload. Due to the space in either the
    cluster name or server name, the messaging engine incorrectly
    parses the name of the cluster/server and assumes that the
    messaging engine has been deleted as it can no longer find the
    configuration files. This results in the messaging engine
    being stopped and the application failing to connect.
    

Problem conclusion

  • This APAR fixes the problem and allows Bus configuration
    reload to work with a cluster or server name that contains a
    space.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.17.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM31552

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-01-31

  • Closed date

    2011-02-21

  • Last modified date

    2011-02-21

  • 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

    PLAT MSG COM

  • Fixed component ID

    620800101

Applicable component levels

  • R300 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM31552

Modified date: 21 February 2011