Changing the Server-Side JVM Restart Threshold

DirX Access uses the Java Wrapper1 to run the Java-based DirX Access Services container as a service on Windows and as daemon processes on Linux. This Java Wrapper monitors the corresponding Java Virtual Machine (JVM) process and automatically restarts it if necessary.

Because the Java Wrapper uses a ping mechanism to determine the status of the JVM, it is possible that the Java Wrapper will mistakenly assume that the JVM is not able to respond if another process takes 100% of the CPU resources for longer than the Java Wrapper timeout value (configurable, with a default value of 30 seconds). This will result in an entry like the following in your wrapper.log file and a restart of the JVM:

jvm 1 | 2001/12/01 12:23:23 | start()
wrapper | 2001/12/01 12:23:44 | Startup failed: Timed out waiting for signal from JVM.
wrapper | 2001/12/01 12:23:44 | Java Virtual Machine did not exit on request, terminated
wrapper | 2001/12/01 12:23:49 | Launching a JVM...
jvm 2 | 2001/12/01 12:23:50 | Initializing...

You can change the threshold for this timeout value by adding the following line to the DirX Access Server configuration file DirXAccessInstallPath/services/instances/TenantId/etc/wrapper.conf:

wrapper.ping.timeout=new value

Note that this setting will also increase the amount of time an application will remain unresponsive if there is a real problem.