PK39018: PERFORMANCE DEGRADATION AFTER SIDD EXITS UNEXPECTEDLY

PK53584; 2.0.47.1: IBM HTTP Server 2.0.47 Cumulative Interim Fix
PK65782; 2.0.47.1: IBM HTTP Server V2.0.47 Cumulative Interim Fix
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris

APAR status

• Closed as program error.

Error description

• The sidd program is critical to SSL performance in most
  configurations.
  If it exits unexpectedly for any reason, it is not restarted
  automatically, and a performance degradation may result.  While
  the sidd termination point can be determined by the start of
  SSL0600S messages, no specific message indicates when and how
  sidd terminated.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM HTTP Server customers on all platforms   *
  *                 but Windows, with excessive SSL0600S         *
  *                 messages caused by the sidd process (session *
  *                 id cache daemon) exiting unexpectedly.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: No facility was provided for restarting *
  *                      sidd if it exited unexpectedly.  Thus,  *
  *                      if a customer action caused sidd to     *
  *                      terminate or if sidd exited due to a    *
  *                      defect, session ID caching would no     *
  *                      longer work and a severe performance    *
  *                      degradation could occur.                *
  ****************************************************************
  

Problem conclusion

• mod_ibm_ssl has been modified to catch premature termination
  of sidd and restart it in most cases.
  sidd will not be restarted if it reports a configuration or
  basic setup problem.
  This fix is targeted for the following service packs:
  6.0.2.19
  6.1.0.9
  Cumulative e-fix PK53584 for 2.0.47.1
  

Temporary fix

Comments

APAR Information

• 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

  IBM HTTP SERVER

• Fixed component ID

  5724J0801

Applicable component levels

• R60A PSN

     UP

• R60H PSN

     UP

• R60P PSN

     UP

• R60I PSN

     UP

• R60S PSN

     UP

• R60Z PSN

     UP

• R61A PSN

     UP

• R61H PSN

     UP

• R61P PSN

     UP

• R61I PSN

     UP

• R61S PSN

     UP

• R61Z PSN

     UP