IBM Support

PH31692: NOT ALL MESSAGE LISTENERS STARTED IN THE CONTROL REGION AFTER STARTUP

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Message Driven Beans bound using Listener Ports use a message
    listener in the control region (unless using a non-durable
    subscription), with the MDB processing the message in the
    servant region.
    
    In an environment with multiple Listener Ports configured, an
    issue occurred where the startup of message listeners in the
    control region was not performed for some Listener Ports.  The
    issue occurred during server startup.
    There were no error issued for the non-started listeners.  The
    non-started listeners could be started successfully after
    listener stop/start. This problem occurred intermittently.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of       *
    *                  Listener Ports                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Not all message listeners started in    *
    *                      the control region after Listener       *
    *                      Port startup.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A concurrency issue in the WS390ConnectionBrowserManager
    resulted in omissions in the set of listeners that were
    started.
    

Problem conclusion

  • The concurrency issue was resolved so that the complete set
    of listener ports were started.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.20 and 9.0.5.8. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH31692

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-11-15

  • Closed date

    2021-05-26

  • Last modified date

    2021-05-26

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
27 May 2021