A fix is available
APAR status
Closed as program error.
Error description
In some cases, for a connection, two teardown related events may be delivered (e.g. DISCONNECT & UNREACHABLE). If the application can't handle those scenarios (as the CF usually frees resources after the first event) there could be a problem. Hence we eliminate the double delivery.
Local fix
Problem summary
In some cases, for a connection, two teardown related events may be delivered (e.g. DISCONNECT & UNREACHABLE). If the application can't handle those scenarios (as the CF usually frees resources after the first event) there could be a problem. Hence we eliminate the double delivery.
Problem conclusion
In the notification delivery paths (server side and client side) for BROKEN/UNREACHABLE/DISCONNECT etc. we ensure that if the connection is already disconnected (i.e. a prior disconnect type of event has been delivered), we don't generate an event for the second time.
Temporary fix
Comments
APAR Information
APAR number
IV56693
Reported component name
UDAPL
Reported component ID
5765G6240
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Submitted date
2014-03-14
Closed date
2014-03-14
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