ca-wcc-services repeatedly crashes after updating SLES11 SP4 kernel

Document ID : KB000118919
Last Modified Date : 02/11/2018
Show Technical Document Details
Issue:
WCC is running on SLES11 SP4. After updating the kernel to 3.0.101-108.57-default, the ca-wcc-services service will no longer stay running. It crashes within minutes after starting. In the ca-wcc-services.log file, the following error can be seen...

INFO | jvm 1 | 2018/10/10 09:27:07 | 2402 | WrapperManager Debug: Send a packet PING : ping 00005bd9
DEBUG | wrapperp | 2018/10/10 09:27:07 | 2402 | read a packet PING : ping 00005bd9
INFO | jvm 1 | 2018/10/10 09:27:09 | 2404 | CAUAJM_E_10010 Fatal error. Process terminating. [/as/anon/atsysbld/jenkins/build-unix/ws/Autosys/source/native/libmsg/src/msgq.cpp][112]
DEBUG | wrapper | 2018/10/10 09:27:09 | 2404 | Signal trapped. Details:
DEBUG | wrapper | 2018/10/10 09:27:09 | 2404 | signal number=17 (SIGCHLD), source="unknown"
DEBUG | wrapper | 2018/10/10 09:27:09 | 2404 | Received SIGCHLD, checking JVM process status.
STATUS | wrapper | 2018/10/10 09:27:09 | 2404 | JVM received a signal SIGKILL (9).
DEBUG | wrapperp | 2018/10/10 09:27:09 | 2404 | socket read no code (closed?).
DEBUG | wrapperp | 2018/10/10 09:27:09 | 2404 | Closing backend socket.
STATUS | wrapper | 2018/10/10 09:27:09 | 2404 | JVM process is gone.
DEBUG | wrapper | 2018/10/10 09:27:09 | 2404 | JVM process exited with a code of 1, setting the wrapper exit code to 1.
ERROR | wrapper | 2018/10/10 09:27:09 | 2404 | JVM exited unexpectedly.
Environment:
WCC 11.3.6
WCC 11.4
Service Pack: Any
O/S: SLES11 SP4 only
Cause:
This problem is caused by a bug in SLES 11 SP4 after updating the kernel to 3.0.101-108.57-default. The bug causes the 32-bit JRE used by ca-wcc-services to crash. The bug also exists in later kernel versions, but was fixed in 3.0.101-108.74.1.
Resolution:
Update the SLES11 SP4 kernel to version 3.0.101-108.74.1 or higher.