BROKEN PIPE CONDITION CAUSES SSL SERVER SHUTDOWN

 
 APAR Identifier ...... PK80387      Last Changed ........ 09/06/19
 BROKEN PIPE CONDITION CAUSES SSL SERVER SHUTDOWN
 
 Symptom ...... IN INCORROUT         Status ........... CLOSED  PER
 Severity ................... 4      Date Closed ......... 09/05/05
 Component .......... 5735FAL00      Duplicate of ........
 Reported Release ......... 540      Fixed Release ............ 999
 Component Name TCP/IP V2 FOR V      Special Notice
 Current Target Date ..              Flags
 SCP ...................
 Platform ............
 
 Status Detail: SHIPMENT - Packaged solution is available for
                           shipment.
 
 PE PTF List:
 
 PTF List:
 Release 540   : UK46335 available 09/05/07 (0902 )
 
 Parent APAR:
 Child APAR list:
 
 ERROR DESCRIPTION:
 Upon detection of a 'broken pipe' condition, the SSL server
 initiates a shutdown, causing all secure connections to be
 closed.
 
 For example, when the FTP server encounters a disk full
 condition while handling a secure file transfer PUT request, it
 closes the subject data connection.  This action creates a
 broken pipe condition in the SSL server for which a shutdown
 ensues, even though this condition has no adverse impact on
 other secure connections.
 
 Because a broken pipe condition can arise due to conditions that
 pertain to a specific connection only, a shutdown should not
 be initiated unless fully warranted.
 
 LOCAL FIX:
 None.
 
 PROBLEM SUMMARY:
 ****************************************************************
 * USERS AFFECTED: All customers running the z/VM SSL server.   *
 ****************************************************************
 * PROBLEM DESCRIPTION:                                         *
 ****************************************************************
 * RECOMMENDATION: APPLY PTF                                    *
 ****************************************************************
 Existing logic within the SSLSERV module initiates a server
 shutdown whenever a broken pipe condition is detected.
 However, such a condition can be raised in conjunction with
 errors that are not sufficiently severe to warrant this action,
 as in the case of the problem described, for which the broken
 pipe is associated with an incomplete send().
 
 PROBLEM CONCLUSION:
 The routine responsible for initiating a server shutdown upon
 the broken pipe condition has been modified to instead just
 issue a warning of this condition.  Server-initiated shutdown
 actions thus will be controlled by logic elsewhere within the
 SSLSERV module.
 
 With this change, message DTCSSL073 now will be issued as a
 warning message, not as an error message.
 
 ===============================================================
 The revised information that follows will be included in any
 future updates to the following publication(s):
 
 GC24-6124-04 -- z/VM: TCP/IP Level 540 Messages and Codes
 Chapter 18.  SSL Messages
 Page: 380
 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 
 Changed Message and Text:
 -------------------------
 
 DTCSSL073W Broken pipe condition encountered
 
  Explanation:  A connection to the TCP/IP server, or other local
    server or client, has closed unexpectedly or is in an
    unusable state.  This condition might arise due to an error
    encountered by the server or client involved with the secured
    connection.
 
  System Action: SSL Processing continues.
 
  System Programmer Response:  Verify that the subject server is
    still operational.  If it is not, take appropriate action to
    restart that server.  Review pertinent console messages or
    message logs for errors that correspond to this error and
    take corrective action, as warranted.
 
 TEMPORARY FIX:
 
 COMMENTS:
 
 MODULES/MACROS:   SSLSERV  SSLVMAIN SSLVMCOM
 
 SRLS:      GC24612404
 
 RTN CODES:
 
 CIRCUMVENTION:
 
 MESSAGE TO SUBMITTER: