Menu
▾
▴
#214 wrapper | There may be a configuration problem: please check
I'm running a Java application with the Java Service Wrapper
I am getting this error
STATUS | wrapper | JVM requested a restart.
FATAL | wrapper | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
FATAL | wrapper | There may be a configuration problem: please check the logs.
This usually happens when CPU usage is high and the system is heavily loadaed. wrapper tries to ping the JVM. it is possible that the Wrapper will think that the JVM is hung when it isn't if another process is taking 100% of the CPU.
There are some conf for this in the wrapper.conf --
I’ve tried these –
wrapper.ping.interval=30
wrapper.ping.timeout=45
wrapper.cpu.timeout=10
but no joy …any clue how to get rid of this??
Many Thanks.
Is this happening when the JVM launches for the first time? Or is it happening after the JVM has been running for a while?
If it is the later, then the JVM is being restarted the first time for some reason. That may be due to a ping timeout. You can control that timeout using the wrapper.ping.timeout property.
The successive invocations appear to be failing to start within the configured time. That is controlled by a different timeout: wrapper.startup.timeout
http://wrapper.tanukisoftware.org/doc/english/prop-startup-timeout.html
Usually if the system is that loaded however then the Wrapper will also wait to launch the JVM.
Enabling debug output and then reproducing this would give me the log output needed to be able to properly diagnose this for you.
wrapper.debug=true
The log file can be uploaded at the bottom of this issue.
Cheers,
Leif