- Top Category > General Questions > DataSpider Servista > [DataSpider Servista] File named jrockit.****.dump was displayed and service has stopped
Search via FAQ No.
[DataSpider Servista] File named jrockit.****.dump was displayed and service has stopped
File named jrockit.****.dump was displayed in $DATASPIDER_HOME/server/bin and DataSpider Servista service has stopped. (Normal width number will be displayed in ****) let us know the cause and its counter measures.
- Category :
Answer
■Assumed Causes
When terminating abnormally due to some problems, Java outputs the situation in the memory of that time to the log. That log is known as "Dump file" in DataSpider Servista. jrockit.<pid>.dump is that dump file.
Just In Time compilation method (Hereafter known as JIT method) is adopted for Java and at the time of execution, the performance is improved by converting from Java intermediate code to OS Native code (compile) and executing it as the conversion details can be optimized depending on the process status in JavaVM of jrockit.
When executing GC (Garbage Collection) while using this optimized compiler, then the service might be stopped.
When the relevant log is not displayed in "■Confirmation Method", refer to "Irrelevant Cases" described at the end of this document.
■Confirmation Method
- Dump File Check
Expand the dump file of the below directory
$DATASPIDER_HOME/server/bin/jrockit.****.dump
- Processing Thread Check
Search the dump file with "OC currently running" or "YC is not running" and check that GC is being executed. For example, the below message will be displayed.
Example:
- In case of OC currently running
GC Status : OC currently running, in phase: marking. This is OC#36088.
: YC is not running. Last finished YC was YC#24744.
- In case of YC is currently running
GC Status : OC is not running. Last finished OC was OC#1844959.
: YC is currently running. This is YC#1671506.
■Handling method
The problem can be avoided by disabling the optimized compiler. Set the below value to "lax.nl.java.option.additional=", of the configuration file and restart the service.
(*Refer to "Property reference" in the help for the details of configuration file)
- Location of configuration file (DataSpiderServer.lax)
$DATASPIDER_HOME/server/bin/DataSpiderServer.lax
- Setting key
-XnoOpt
Example:
lax.nl.java.option.additional=-server -Djava.ext.dirs=..\\system\\boot\\ext;..\\..\\jre\\lib\\ext（Omitted）
-XstrictFP -XnoOpt
■Irrelevant Cases
When the dump file is displayed and when Garbage collection is not executed during compiling, there are chances for the problem to occur in some other location. In this case, send the below information to our company support center.
- Reoccurrence frequency
Let us know the frequency or the number of times the problem has occurred.
- Status during occurrence
During problem occurrence such as the newly added processing being executed for the first time, a large number of cases are set as a synchronous target, when you want to execute the processing different from others, let us know that information.
- Setting changes
Before and after the starting of problem occurrence, let us know whether the settings of the environment or DataSpider Servista have been changed.
When there is a change in the settings, there are chances for event cancellation by restoring. Try that and let us know the result so as to enable us for an earlier solution.
- Various Logs
- Dump File
$DATASPIDER_HOME/server/bin/jrockit.****.dump
- Server Log
$DATASPIDER_HOME/server/logs/server.log
- Server Standard Error Output
$DATASPIDER_HOME/server/logs/server.error.log
- exec Log
$DATASPIDER_HOME/server/logs/<Date Directory (yyyyMMdd)>/exec.log
- XML Log
$DATASPIDER_HOME/server/logs/<Date Directory (yyyyMMdd)>/execution/<Execution ID>.xml
*Send when the script execution which is considered to be the cause, can be specified
(* Refer to "Log Guide" in help for the details of various logs.)
The content similar to this FAQ, is described even in "Trouble Shooting" of product help.
·Trouble shooting
If the information on service stop due to other factors is required, refer to "Qnnn" of FAQ.
Refer to the below for the information of configuration file and the log.
·Property reference
·Log guide