- Top Category > General Questions > DataSpider Servista > [DataSpider Servista] File named hs_err_pid****.log is output and service has stopped
Search via FAQ No.
[DataSpider Servista] File named hs_err_pid****.log is output and service has stopped
File named hs_err_pid****.log is displayed in $DATASPIDER_HOME/server/bin and DataSpider Servista service is stopped. Explain the cause and the handling method.
(Normal width number will be displayed in ****)- 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. hs_err_pid****.log 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.
Though JIT method is adopted even in the internal processing of DataSpiderServer, when the Compiler thread is invoked in the JIT method, the service might stop. Check the below for the confirmation or handling method.
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 that is displayed in the below path.
$DATASPIDER_HOME/server/bin/hs_err_pid****.log
- Processing Thread Check
Search the dump file with "CompilerThread" and check whether there is any information stating
that failure has occurred in "CompilerThread". For example, the below log will be displayed.
Current thread (0x52d70cf8): JavaThread "CompilerThread1" daemon
- Compiled Module Check
Search the dump file with "Current CompileTask" and check the module compiled at the time of failure occurrence. For instance, the log is displayed as given below.
Example:
Current CompileTask:
C2:2519? !??
jp.co.headsol.salesforce.adapter.executer.AbstractUpdateByMultiKeyExecuter.exec()V (994 bytes)
■Handling method
By removing the module compiled at the time of problem occurrence from the target of JIT method, the event can be avoided. Set the below value in "lax.nl.java.option.additional=" of the configuration file and restart the service.
(* Refer to "Property Reference" in help for more details on configuration file)
- Location of configuration file (DataSpiderServer.lax)
$DATASPIDER_HOME/server/bin/DataSpiderServer.lax
- Configuration key
-XX:CompileCommand=exclude,full/class/name,method
In case of the example provided in "■Confirmation Method", below values should be set.
Example:
-
XX:CompileCommand=exclude,jp/co/headsol/salesforce/adapter/executer/AbstractUpdateByMultiKeyExecuter,exec
■Irrelevant Cases
Dump file is displayed and there is no damage with "CompilerThread", there are chances for the problem to occur in some other location. In such cases, send the below information to our company support center.
- Reoccurrence frequency
Let us know the frequency or the number of times the event has occurred.
- Status during occurrence
During the problem such as the newly added process being executed for the first time, especially, a large number of cases are set as synchronous target, and when you want to execute the process different from others, let us know that information.
- Setting changes
Before and after the starting of event 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 the 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/hs_err_pid****.log
- 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 the help for the details of various logs)
The content similar to this FAQ, is described in "Trouble Shooting" of product help
·Trouble shooting
When the information on service stop due to other factors is necessary, refer to "Qnnn" of FAQ
Refer to the following for the information of configuration file and the log.
·Property Reference
·Log guide