IV33377: SSM 4.0 FP13 SSMCONSOLE LOGGING MAY HANG WHEN IT WRITES WARNING / ERROR MESSAGES

IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001

APAR status

• Closed as program error.

Error description

• SSMConsole locks the console when it executes configuration
  lines.
  If whilst executing that line, an error or warning log message
  is logged to the ssmagent.log (by a different thread) it may
  deadlock as it tries to log to write to the console. This causes
  the agent to hang and be unresponsive.
  

Local fix

• Fix the issue that was causing the warning or error message to
  occur. For instance if it was due to invalid names in a control
  row, making the names valid will work around the possible
  deadlock.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All SSM 4.0 Users across all platforms.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The SSM agent locks the console when it executes             *
  * configuration lines. If whilst executing that line, an error *
  * or warning log message is logged to ssmagent.log by a        *
  * different thread it may deadlock as it tries to log the      *
  * message. This causes the agent to hang and be unresponsive.  *
  *                                                              *
  * This is incorrect and is rectified in the next release. The  *
  * fix logs a debug message similar to the following where      *
  * previously it used to hang:                                  *
  *                                                              *
  * [Console Print] Failed to lock and print: <message>          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to the next release of SSM. The work around is to    *
  * fix the cause of the warning/error message. For instance if  *
  * it was due to invalid name in a control row, making the name *
  * valid avoids the possible deadlock.                          *
  ****************************************************************
  

Problem conclusion

• The possible deadlock has been fixed.
  
  
  The fix for this APAR is contained in the following packages:
  System Service Monitors V4.0.1
  The fix for this APAR is contained in the following maintenance
  packages:
      | fix pack | 4.0.0-TIV-SSM-FP0014
  

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

  NETCOOL SYS SVC

• Fixed component ID

  5724P4300

Applicable component levels

• R400 PSY

     UP