A fix is available
APAR status
Closed as program error.
Error description
The current instance of dapli_thread may be hung because some other instance of dapli_thread from the past (which hasn't been cleaned properly) may reap its event. As a result the cyrrent dapli_thread may be stuck in a sleep waiting for an (async) event for which it was woken up (but which has since been processed by the other instance).
Local fix
Problem summary
The current instance of dapli_thread may be hung because some other instance of dapli_thread from the past (which hasn't been cleaned properly) may reap its event. As a result the cyrrent dapli_thread may be stuck in a sleep waiting for an (async) event for which it was woken up (but which has since been processed by the other instance).
Problem conclusion
The uDAPL thread (dapli_thread) wasn't being cleaned up properly The solution makes sure that, upon close, the dapli_thread falls through and is done... that will ensure that these threads won't hang around and the current events are received only by the current threads.
Temporary fix
Comments
APAR Information
APAR number
IV52990
Reported component name
UDAPL
Reported component ID
5765G6240
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Submitted date
2013-12-09
Closed date
2013-12-09
Last modified date
2015-11-22
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
UDAPL
Fixed component ID
5765G6240
Applicable component levels
R610 PSY U861472
UP15/11/22 I 1000
PTF to Fileset Mapping
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG11Q","label":"AIX 6.1 HIPERS, APARs and Fixes"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 November 2015