uCosminexus Application Server, Maintenance and Migration Guide
This section describes the settings for acquiring core dumps in UNIX.
The maximum size of core files may be 0 depending on the operation environment of the system. In such cases, core dumps cannot be acquired during abnormal termination of server processes, and therefore, you need to set in advance the maximum size of core files to infinite. To set the maximum size of the core file to infinite, either specify the option in the JavaVM start parameter in the simple setup definition file or execute shell commands.
Note that the core file size increases with the increase in the memory pool size specified in the JavaVM start parameter in the simple setup definition file, secure sufficient free disk space.
<configuration> <logical-server-type>j2ee-server</logical-server-type> <param> <param-name>add.jvm.arg</param-name> <param-value>-XX:+HitachiFullCore</param-value> </param> : </configuration> |
limit coredumpsize unlimit |
ulimit -c unlimited |
Also, in addition to these settings, we recommend that you execute the shell commands to set the maximum file size to unlimited.
limit filesize unlimit |
ulimit -f unlimited |
You can define the upper limit for the number of core files in the ejb.server.corefilenum parameter in the <configuration> tag of a logical J2EE server (j2ee-server) in the Easy Setup definition file. Define the ejb.server.corefilenum parameter in the extension parameter of the J2EE server.
If the total of core dump files output to working-directory/ejb/server-name/ while restarting the cjstartsv process exceeds the specified maximum number, the files are deleted in the order of output date, starting from the oldest file.
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.