Fixes are available
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Under certain circumstances the SSLCache may fail with the following set of errors: Please specify a different SSLCachePortFilename, this filename is already in use. Shutting down session ID cache daemon ... [debug] mod_ibm_ssl_sidd.c(121): sidd process 33685769 exited; reason 0 why 1 exit code 3 signal -1 [debug] mod_ibm_ssl_sidd.c(121): sidd process 33685769 exited; reason 3 why 1 exit code -1 signal -1 [error] SSL0603E Session id cache daemon process 33685769 exited with exit code 3; not restarting; check sidd configuration or enable sidd error log with SSLCacheErrorLog
Local fix
Manually delete the file specified by SSLCachePortFilename.
Problem summary
**************************************************************** * USERS AFFECTED: IBM HTTP Server users of the mod_ibm_ssl * * module running on z/OS with * * SSLCacheEnable. * **************************************************************** * PROBLEM DESCRIPTION: SSL Cache fails with following * * messages. * * mod_ibm_ssl_sidd.c(121): sidd process * * 83952045 exited; reason 3 why 0 exit * * code -1 signal -1 * * Please specify a different * * SSLCachePortFilename, this filename * * is already in use. * **************************************************************** * RECOMMENDATION: * **************************************************************** There is a safety check on the specified SSLCachePortFilename file to make sure it is the correct type of file before it is unlinked at initialization time before the new instance is created. On z/OS 1.13 and prior the file was showing as a type character special file and the test was done for that. On z/OS 2.1 the file is showing as type socket which causes the check to fail.
Problem conclusion
The check has been changed to make sure the file is of either type character or socket before the file is unlinked. The fix for this APAR is available in the following IBM HTTP Server fixpacks: * 8.5.5.3 * 8.0.0.10 * 7.0.0.35
Temporary fix
Comments
APAR Information
APAR number
PI17434
Reported component name
WAS IHS ZOS
Reported component ID
5655I3510
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-05-07
Closed date
2014-05-14
Last modified date
2015-02-16
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
WAS IHS ZOS
Fixed component ID
5655I3510
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
28 April 2022