WA Agent does not start fatal error and sigbus

Document ID : KB000103374
Last Modified Date : 26/06/2018
Show Technical Document Details
Issue:
After the installation of WAAE AutoSys 11.3.6 SP7 on Linux, the local Agent does not start with the following error messages:

# A fatal error has been detected by the Java Runtime Environment: 

# SIGBUS (0x7) at pc=0x00007f0248be8ebc, pid=32132, tid=0x00007f0263d8b720 

# JRE version: Java(TM) SE Runtime Environment (8.0_152-b16) (build 1.8.0_152-b16) 
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.152-b16 mixed mode linux-amd64 compressed oops) 
# Problematic frame: 
# j java.lang.Thread.<init>(Ljava/lang/ThreadGroup;Ljava/lang/Runnable;)V+0 

# Core dump written. Default location: /opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/core or core.32132 

# An error report file with more information is saved as: 
# /opt/CA/WorkloadAutomationAE/SystemAgent/WA_AGENT/hs_err_pid32132.log 

# If you would like to submit a bug report, please visit: 
# http://bugreport.java.com/bugreport/crash.jsp 
#
Environment:
WAAE 11.3.6 SP7 on Linux + Oracle

# uname -a 
Linux ... 2.6.32-696.3.2.el6.x86_64 #1 SMP .... x86_64 x86_64 x86_64 GNU/Linux 
Resolution:
The encountered problem was related to a known problem in Linux Kernel.
 
The same flaw that was introduced to the RHEL 7 kernel 3.10.0-514.26.1.el7.x86_64 was also ported to the RHEL 6 kernel 2.6.32-696.3.2.
 
The solution documented by RedHat is to upgrade the RHEL 6 kernel to version 2.6.32-673 or higher.
 
The workaround documented by RedHat is to increase the Java stack size by setting "-Xss2m" in the Java startup parameters.
 
For the System Agent, that means adding the following parameter in “agentparm.txt” file:
 
oscomponent.jvm.x.options=-Xss2m
 
You can consult the following pages for more information: 
 
https://access.redhat.com/solutions/3091371
 
https://bugzilla.redhat.com/show_bug.cgi?id=1464185
 
https://www.cloudlinux.com/cloudlinux-os-blog/entry/jvm-crashes-occurring-after-upgrading-to-a-kernel-with-the-fix-for-stack-clash
 
https://issues.apache.org/jira/browse/DAEMON-363

Problem resolved by applying the solution.