Menu
▾
▴
2 Attachments
#293 Heap dump file creation problem
Hi Team,
Problem while generating the heap dump file and getting the following exception in wrapper logs. (Hprof file is not created in this situation)
Version details:
Java Service Wrapper Professional Edition 32-bit 3.5.15
Copyright (C) 1999-2012 Tanuki Software, Ltd. All Rights Reserved.
http://wrapper.tanukisoftware.com
wrapper.logs
INFO | jvm 2 | 2015/01/12 02:47:35 | Connect to: [ http://localhost:8022 ]
INFO | jvm 2 | 2015/01/12 19:53:33 | java.lang.OutOfMemoryError: Java heap space
STATUS | wrapper | 2015/01/12 19:53:33 | Filter trigger matched. Restarting JVM.
INFO | jvm 2 | 2015/01/12 19:53:33 | Dumping heap to java_pid6088.hprof ...
ERROR | wrapper | 2015/01/12 19:54:10 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2015/01/12 19:54:10 | JVM did not exit on request, terminated
STATUS | wrapper | 2015/01/12 19:54:16 | Launching a JVM...
INFO | jvm 3 | 2015/01/12 19:54:18 | WrapperManager: Initializing...
=============================================================================================
In the above wrapper logs, JVM restarted after waiting 30 second after heap dump creation but
I set the wrapper.ping.timeout =120 in wrapper.conf. Please let me know why the JVM restarted after 30 second instead of waiting 120 second.
Please give suggestion to resolve the problem.
Please find the attached wrapper.conf and wrapper.log for more information.
I am awaiting for your reply.
Thanks in advance.
Balaji P J
Balaji,
It looks like it requires more than 30 sec to create the dump.
The property wrapper.ping.timeout is not the correct property to look at in this case. Instead, please have a look at wrapper.shutdown.timeout:
http://wrapper.tanukisoftware.com/doc/english/prop-shutdown-timeout.html
The default value is 30, you can try and set a higher value.
Please let me know the result.
I was not able to download wrapper.log. If you still have a problem, please send it to support@tanukisoftware.com.
Regards,
Alexandre Klein
Thanks for your input. I will increase shutdown timeout value and update the status shortly.
Hi ,
Thanks for your quick response.
I attached the same for your reference.
Awaiting for your valuable input.
On Thu, Feb 5, 2015 at 2:59 PM, Alexandre alex-tanuki@users.sf.net wrote:
--
Balaji P J
Zoho Development Centre,
Chennai.
Related
Bugs: #293
Balaji,
You can also try this property: wrapper.jvm_exit.timeout
http://wrapper.tanukisoftware.com/doc/english/prop-jvm-exit-timeout.html
For example:
wrapper.jvm_exit.timeout=300
Please let me know the result.
Regards,
Alexandre Klein
Hi,
I want to appear JVM hang for some time to ensure the "wrapper.shutdown.timeout=120" flag.
changed default time out (30) value by using the above flag, so I want to test the same in my environment.
Please give some idea to ensure the same.
Thanks.
Balaji P J
Balaji,
The wrapper.shutdown.timeout is the time for the WrapperManager.stop method to complete. In order to test this, you would need to write some code to cause this method to take some time. This is normally not possible with the WrapperSimpleApp helper class unless you extend it or something.
If you want to test the wrapper.jvm_exit.timeout, you can simply register a new shutdown hook with the JVM and make loop or do something that takes longer that the timeout. The JVM will wait for all shutdown hooks to complete before exiting, and this timeout lets you control how long to wait before forcibly killing the JVM.
Cheers,
Leif