A fix is available
APAR status
Closed as program error.
Error description
In Rational Developer for System z (RDz) v8.5.1.4, when a user kills his RDz client, the RDz server will see it and terminate his session on the server. In some circumstances, it can happen that some user threads will remain in the threadpool due to a deadlock situation. Operator command DISPLAY PROCESS may the show the user as still connected. A javacore file will show the following information: 1LKDEADLOCK Deadlock detected !!! NULL --------------------- NULL 2LKDEADLOCKTHR Thread "DStore ReceiverThread-650" (0x3713FB00) 3LKDEADLOCKWTR is waiting for: 4LKDEADLOCKMON sys_mon_t:0x375C1F00 infl_mon_t: 0x375C1F38: 4LKDEADLOCKOBJ java/util/ArrayList@0x12BFB638/0x12BFB644: 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "DStore UpdateHandlerThread-647" (0x3712F700) 3LKDEADLOCKWTR which is waiting for: 4LKDEADLOCKMON sys_mon_t:0x375C1EC0 infl_mon_t: 0x375C1EF8: 4LKDEADLOCKOBJ java/util/ArrayList@0x12BFB6B0/0x12BFB6BC: 3LKDEADLOCKOWN which is owned by: 2LKDEADLOCKTHR Thread "DStore ReceiverThread-650" (0x3713FB00)
Local fix
Threads can be terminated manually using command f bpxoinit, term=<PID>.<thread id> Or the threadpool needs to be terminated
Problem summary
**************************************************************** * USERS AFFECTED: 01.RDz 8* users * **************************************************************** * PROBLEM DESCRIPTION: 01.During a disconnect, it's possible * * for a deadlock to occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** 01.When an RDz user disconnects from the server, it is possible (although rare) for the timing to be such that a deadlock can occur. In such scenarios, this can also result in locked datasets.
Problem conclusion
01.In order to avoid the deadlock, a synchronized block in the server code was removed. This is a change that had already gone into the RDz 9* versions.
Temporary fix
Comments
APAR Information
APAR number
PI22155
Reported component name
RD/Z HOST
Reported component ID
5724T0723
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-07-16
Closed date
2015-01-20
Last modified date
2015-02-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FEKFDST0
Fix information
Fixed component name
RD/Z HOST
Fixed component ID
5724T0723
Applicable component levels
R850 PSY UI24911
UP15/02/05 I 1000
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSJK49","label":"IBM Developer for z Systems"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"8.5","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
27 October 2020