Problem

-- After a system update, some new kernel and/or glibc security fix prevent vshell process to start. Depending of the Linux system a core file and/or an hs_err_pid{pid}.log files are generated.

-- The hs_err_pid{pid}.log file show a SIGBUS error

-- The core file analysis show either a segmentation fault or a sigabort.

Resolution

- It's possible to make vshell process starts by setting the stack size parameter of the jvm to 1280k

- It can be done by modifying the jvm.xml of the API Gateway instances and node manager by adding:

<VMArg name="-Xss1280k"/>

in the <ConfigurationFragment>. You can refer to this article for more information on the jvm.xml file.

- Another solution is the export the JAVA_TOOL_OPTIONS environment variable before starting vshell process:

export JAVA_TOOL_OPTIONS=-Xss1280k

- When installing API Gateway, you have to export the JAVA_TOOL_OPTIONS envrionment variable before running the installer.