IC85731: SSPCM CRASHES AFTER SIGN-ON

APAR status

• Closed as program error.

Error description

• Error Description￘
  CM will start and stay up until it is used.  It will normally
  crash as soon as the user logs in but a few times has stay
  running for as long as an hour or more.  We have attempted to
  create java dump files but these are not being produced.
  strace shows that the CM throws a SIGPIPE error and then fails
  immediately.
  
  customer can reproduce at will.
  
  IBM Sterling Secure Proxy Configuration Manager Version
  3.4.1.0, Patch 2, Build 74
  
  
  System Information:
  Node Name: nahas00028.am.boehringer.com
  Operation System: Linux
  Version: 2.6.18-194.11.1.el5
  Hardware: x86_64
  Machine Type: x86_64
  Processor Information:
  processor    : 0
  vendor_id    : GenuineIntel
  model name    : Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz
  cpu MHz        : 2933.437
  processor    : 1
  vendor_id    : GenuineIntel
  model name    : Intel(R) Xeon(R) CPU           X5670  @ 2.93GHz
  cpu MHz        : 2933.437
  
  Number of Processors: 2
  
  MemTotal:      3913468 kB
  MemFree:        147748 kB
  
  IP Address:
  inet addr:10.128.60.162  Bcast:10.128.61.255  Mask:255.255.254.0
  inet addr:127.0.0.1  Mask:255.0.0.0
  

Local fix

• Local Fix￘
  New Fix Needed
  

Problem summary

• SSPCM crashes after signon on RedHat Linux.
  Customer installed SSP 3.4.1.0 on RedHat Linux and attempted to
  signon to the SSPCM GUI interface.  Within minutes of logging
  in, the GUI became unresponsive because the SSPCM process was
  gone.  Nothing in the logs showed what had happened.  By turning
  on a truss trace for the SSPCM process, it was determined that
  the last thing that happened was a SIGPIPE interruption and the
  process died.  Further investigation revealed that this was a
  problem with the IBM JRE that is shipped with the product, and
  is discussed in IBM APAR IV02379: "JAVA EXITS SILENTLY AND
  UNEXPECTEDLY ON LINUX DUE TO SIGPIPE".  The Customer was running
  on RedHat Linux at the 2.6.18-194.11.1.el5 level.
  

Problem conclusion

• Updated the JRE that is shipped on the Linux platform to the IBM
  SR10 FP1 level, which contains the fix for the SIGPIPE problem
  on Linux.
  

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

  STR SECURE PROX

• Fixed component ID

  5725D0300

Applicable component levels

• R341 PSY

     UP