Flash : IBMProxy is down by SIGSEGV

Content

Version affected:

• WebSphere Application Server Traditional 8.5.5.12 , 9.0.0.4 and 9.0.0.5

With APAR PI76339 Caching Proxy changed to a different module loading system. The new module loading system was unable to load the archive module which is used by the default Caching Proxy
configuration to perform log rotation at midnight. This results in Caching Proxy on AIX crashing due to a segmentation fault each day at midnight.

This issue does not exist on WebSphere Application Server Traditional 9.0.0.3 or earlier releases.

Remediation:

For WebSphere Application Server Traditional V8.5.5.12:
· Apply Interim Fix PI86249
--OR--
· Apply Fix Pack 8.5.5.13 or later (targeted availability 05 February 2018).
--OR--
· Follow any one of the temporary fix documented in the workaround

For WebSphere Application Server Traditional V9.0.0.4 :
· Apply Interim Fix PI86249
--OR--
· Apply Fix Pack 9.0.0.6 or later (targeted availability March 2018).
--OR--
· Follow any one of the temporary fix documented in the workaround

For WebSphere Application Server Traditional V9.0.0.5 :
· Apply Interim Fix PI86249
--OR--
· Apply Fix Pack 9.0.0.6 or later (targeted availability March 2018).
--OR--
· Follow any one of the temporary fix documented in the workaround

Workaround :

1. Use the old CP module loader system. The old module loading system can
be used by setting the following environment variable before starting Caching Proxy:
CP_USE_LOADANDINIT="true"
export CP_USE_LOADANDINIT

--OR--

2. Disable the log rotation Log rotation can be disabled by commenting out the Midnight directive in
the Caching Proxy config.
The directive should look like this (after it is commented out):
#Midnight /usr/lib/archive.so:begin