A fix is available
APAR status
Closed as unreproducible in next release.
Error description
WebSphere Application Server (WAS) hangs on shutdown because the STIMER was waiting on WMQ module CSQ3SSI. It seems that WMQ module CSQ3SSI1 has detected that there was a thread associated with the WAS Servant Region (SR), which has been scheduled for deferred end-of-task processing in the queue-manager, and is waiting for it to complete. In the queue-manager, the deferred end-of-task processing is suspended waiting for an SRB scheduled into the Servant Region to complete. Eventually the Servant Region received an ABENDS878, and it looks as though the SRB never had a chance to run before the address space started terminating. . Additional Symptom(s) Search Keyword(s): ABN=30D-00000000 ABEND30D ABENDS30D 30D S30D S030D CSQVSRX CSQVSRRX CSQV086E REASON 00E50054
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: An address space connected to MQ does * * not terminate after going through end * * of memory processing without completing * * end of task processing. * * The queue manager does not respond to * * shutdown commands and needs to be * * cancelled. * **************************************************************** * RECOMMENDATION: * **************************************************************** The connected address space has one or more tasks going through end of task processing in the queue manager when it encounters an error causing it to go through end of memory processing. CSQ3SSI1 detects that there is at least one thread associated with address space which has been scheduled for deferred end-of-task processing in the queue-manager, and waits for it to complete. In the queue-manager, the deferred end-of-task processing is taking place and CSQ3TM00 has called CSQMDISC to clean up MQ related storage in the connected address space. CSQMDISC is suspended, waiting for an SRB scheduled into the connected address space. Given that the connected address space is going through end of memory processing, the SRB will never run and the hang occurs.
Problem conclusion
Temporary fix
********* * HIPER * *********
Comments
The code was changed to prevent deadlock between the tasks from occurring.
APAR Information
APAR number
PI25678
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
100
Status
CLOSED UR1
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-09-12
Closed date
2014-12-10
Last modified date
2015-02-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI23754
Modules/Macros
CSQ3TM00
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI23754
UP15/01/16 P F501
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 February 2015