APAR status
Closed as program error.
Error description
A servant region ABEND occurred while executing PAUSELISTENERS. When a new servant region started, the Message Listener Port was restarted and the MDB in the new servant region processed messages. The other servant regions did not process messages and a subsequent RESUMELISTENERS did not restart message processing in these servant regions.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users of * * Message Listener Ports * **************************************************************** * PROBLEM DESCRIPTION: Message Listener Port state * * inconsistent across multiple servant * * regions if a servant region dies * * during PAUSELISTENERS * **************************************************************** * RECOMMENDATION: * **************************************************************** A servant region ABEND occurred while executing PAUSELISTENERS. When a new servant region started, the Message Listener Port was restarted and the MDB in the new servant region processed messages. The other servant regions did not process messages and a subsequent RESUMELISTENERS did not restart message processing in these servant regions. There are multiple issues with this behaviour: 1) The restarted servant should not have started processing messages since the listeners were paused. 2) The subsequent RESUMELISTENERS did not resume message processing across all servant regions. 3) Message processing was inconsistent across servant regions with the restarted servant region processing messages and the other servant regions not doing so.
Problem conclusion
The Messaging component was modified so that the failure of the servant region during PAUSELISTENERS is detected and the state of the Message Listener Port successfully changed to paused. This also prevents the the restarted servant region from processing messages while the listeners are paused. Should a mixed servant listener status occur for any other reason then the changes also allow a subsequent RESUMELISTENERS to restore message processing across all servant regions and also prevent premature message processing by the restarted servant region while the listeners are paused. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.10. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
If this condition should occur, an additional PAUSELISTENERS can be performed that will complete pausing of the message listener port and prevent message processing across all of the servant regions.
Comments
APAR Information
APAR number
PH37666
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-05-27
Closed date
2021-10-11
Last modified date
2021-10-11
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":"LOB45","label":"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":"900"}]
Document Information
Modified date:
13 October 2021