Fixes are available
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
Customer detected that switching to rolling update resulted in interruption of their MDB processing - message J2CA0520W, Root cause was determined to be with the underlying implementation of the PAUSELISTENER and then RESUMELISTENER code - management code is issuing a PAUSE but is not waiting for it to complete before issuing the RESUME and the WAS z/OS native code rejects the RESUME because of that. Fix is to update the code to apply the JVM server stop wait custom property to the pause command. With that, customer can adjust the custom property to wait for the pause command.
Local fix
Manually resume activation specs as needed.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 and 9.0. * **************************************************************** * PROBLEM DESCRIPTION: When resuming an application server * * during an application rollout update * * in a z/OS environment, resume failed * * with error. * **************************************************************** * RECOMMENDATION: * **************************************************************** If application servers are configured to be paused rather than stopped during an application rollout update, the deployment manager waits for 10 seconds for a server to pause. If an application server is resumed before the pause is complete, an error similar to the following will occur in the log: 13.42.45 STC31052 BBOO0298E SERVER RDL3/QR3NODE/QR3LR1 IS CURRENTLY MODIFYING 073 073 COMMUNICATION LISTENERS. THE RESUMELISTENERS MODIFY OPTION IS NOT 073 ALLOWED AT THIS TIME. 13.42.45 STC31052 BBOO0211I MODIFY COMMAND RESUMELISTENERS COMPLETED WITH ERRORS
Problem conclusion
Allow a custom property, com.ibm.websphere.zos.rollout.pause.waitTimeout, in the node agent configuration to specify in seconds how long the deployment manager waits for a server to pause. This property must be added to the settings for all of the node agents on which you want to provide a longer length of time to pause the servers instead of the default 10 seconds. Follow the step below to configure the new custom property: 1.In the administrative console, click System Administration > Node agents > Administrative Services > Custom Properties > New 2.Enter com.ibm.websphere.zos.rollout.pause.waitTimeout in the Name field, and the wait time in seconds in the Value field. 3.Click OK. 4.Click Save to save your changes to the master configuration. 5.Restart the node agent. APAR PI77669 is currently targeted for inclusion in Fix Packs 8.5.5.13 and 9.0.0.5 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI77669
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
2017-03-06
Closed date
2017-05-24
Last modified date
2017-05-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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022