UVMS stops with "Exit code:5099"

Products

• CA Automic Dollar Universe

Issue/Introduction

The following errors appear in UVMS log without having manually stopped the UVMS via the command unistopms :

 |ERROR| Thread-X | com.orsyp.central.server.ShutdownHook | Signal trapped! Try to stop the application... 
 |ERROR| Thread-X | com.orsyp.central.server.ShutdownHook | A signal was trapped. Exit code:5099 
 

 

Environment

UVMS on Windows or Linux

Cause

Third-party: the UVMS Java process was brutally shutdown because of an unexpected system shutdown or lack of memory on the system where it was running (Linux only).

Resolution

Dollar Universe products ( Application Servers, UVMS, Reporter ) should properly be stopped before shutdown the servers hosting them.
For example, ask the System admins in charge of System Patches to launch the /etc/init.d script to stop the Application properly before launching the command shutdown or reboot.

Additional Information

Recent case occurred on a Linux server Virtual Machine where there was a Reporter client doing many (more than 30) extractions at the same time exhausting the Virtual Machine memory and the oom-killer that Linux has enabled by default would kill the UVMS process as being the one using most memory, the traces of this kill could only be found in the /var/log/messages as seen below:

kernel: C1 CompilerThre invoked oom-killer: xxx
...
kernel: Out of memory: Killed process PID_UVMS (java) total-vm:15404244kB, anon-rss:4251228kB...

In such circumnstances, please ask your System Administrator to increase the memory of the server hosting the UVMS and reduce the amount of parallel extractions (uxrepadd processes) that run on the same server or other potential third-party processes that may use a big amount of memory during a short period of time.