Fixes are available
APAR status
Closed as program error.
Error description
When attempting to stop a application server on WPS for z/OS the servant shuts down, but not completely as there is a remaining hanging thread. The reason for this is that a JMS connection is trying to be closed on a finalize block while the messaging engine is already stopped. So the close call never returns.
Local fix
n/a
Problem summary
When attempting to stop an application server on WebSphere Process Server for z/OS the servant shuts down, but not completely as there is a remaining hanging thread. The reason for this is that a JMS connection is trying to be closed in a finalize() method. This happens when the messaging engine is already stopped and as a result the close call never returns. The JMS connection is designed to stay open as long as the BPEL engine is alive, because the connection is used in system failure scenarios.
Problem conclusion
When running on z/OS the JMS connection is no longer closed in the finalize() method. FIX AVAILABILITY: Fix is targetted for inclusion in next fixpack for BPM V7.5.1, BPM 8.0.1, BPM 8.5.0
Temporary fix
Comments
APAR Information
APAR number
JR47636
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-29
Closed date
2013-11-14
Last modified date
2013-11-14
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
BPM STANDARD
Fixed component ID
5725C9500
Applicable component levels
R751 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
07 January 2022