- Top Category > General Questions > DataSpider Servista > [DataSpider Servista] Checklist when service of DataSpiderServer stops
Search via FAQ No.
[DataSpider Servista] Checklist when service of DataSpiderServer stops
When service of DataSpiderServer stops, the information necessary for check is consolidated.
Service has stopped due to multiple factors such as issues in javaVM or low memory.
For details, please refer to below.
- Category :
Answer
Table of Contents
・For confirming the points used to check for isolation
・For knowing the reason why checking is necessary
・The situation – even after checjubg everything in accordance with this document, if reason behind the phenomenon could not be specified or restoration could not be done
Also, for referring to the information related to this FAQ, please check "Reference Information".
Because of this, please check the DataSpiderServer.lax after the dump log.
3. Server log, server standard error output
There will be outbreak of memory shortage errors (java.lang.OutOfMemoryError) when memory more than the capacity specified in DataSpiderServer.lax and this is due to the fact that there are many data numbers in the scope of process or no. of script creations, project.
In this case, as it is difficult to secure the memory necessary for the process, it enters into the state where the service can be easily stopped.
Hence, please check sever log, server standard error output.
・For confirming the points used to check for isolation
・For knowing the reason why checking is necessary
・The situation – even after checjubg everything in accordance with this document, if reason behind the phenomenon could not be specified or restoration could not be done
Also, for referring to the information related to this FAQ, please check "Reference Information".
Check Points
1. Dump log
Check whether any of the below logs could be displayed.
Check whether any of the below logs could be displayed.
・When version from 3.0 onwards or x86 version prior to 2.4x is used.
$DATASPIDER_HOME\server\bin\hs_err_pid<pid>.log
・When x64 version prior to 2.4.x is used
$DATASPIDER_HOME\server\bin\jrockit.<pid>.dump
Counter Measures:
In case of output, refer to any of the below FAQs.
2. DataSpiderServer.lax
Please check the setting value of initial heap size, maximum heap size from the following setting files, and check whether there is no difference in settings values.
$DATASPIDER_HOME/server/bin/DataSpiderServer.lax
The initial heap size is specified based on any of the below mentioned.
・When more than 2GB is set from version 3.0 onwards or version prior to 2.4.x.
lax.nl.java.option.additional=-Xms
・When version x86 prior to version 2.4.x? is used
lax.nl.java.option.java.heap.size.initial
The maximum heap size is specified based on any of the below mentioned.
・When more than 2GB is set from version 3.0 onwards or version prior to 2.4.x.
lax.nl.java.option.additional=-Xmx
・When version x86 prior to version 2.4.x? is used
lax.nl.java.option.java.heap.size.max
Counter Measures:
If there is a difference in 2 setting values, please refer to below FAQ.
3. Server log and server standard error output
Please use the log that was an output in the below directory, and check the details of the output done during service termination.
$DATASPIDER_HOME/server/logs/server.log
$DATASPIDER_HOME/server/logs/server.error.log
Counter Measures:
Search the below error messages and if you find errors corresponding to the time where the service has been stopped then please check the below FAQ.
・java.lang.OutOfMemoryError: Java heap space
・java.lang.OutOfMemoryError: nativeGetNewTLA
・java.lang.OutOfMemoryError: unable to create new native thread
・java.lang.OutOfMemoryError: mmAllocObject
The memory of the heap area cannot be secured.
What would be the handling method for this?
・java.lang.OutOfMemoryError: PermGen space
The memory of the permanent area, which is a part of the heap area cannot be secured.
For the handling method of this case, please refer to the below FAQ.
$DATASPIDER_HOME\server\bin\hs_err_pid<pid>.log
・When x64 version prior to 2.4.x is used
$DATASPIDER_HOME\server\bin\jrockit.<pid>.dump
Counter Measures:
In case of output, refer to any of the below FAQs.
・FAQ No.24300
The file named jrockit.****.dump is displayed in $DATASPIDER_HOME/server/bin, and DataSpider Servista service has stopped. Explain the cause and the handling method.
(Normal width number will be displayed in ****)
・FAQ No.24301
File named hs_err_pid****.log is displayed in $DATASPIDER_HOME/server/bin and DataSpider Servista service has stopped. Explain the cause and the handling method.
(Normal width number will be displayed in ****)
2. DataSpiderServer.lax
Please check the setting value of initial heap size, maximum heap size from the following setting files, and check whether there is no difference in settings values.
$DATASPIDER_HOME/server/bin/DataSpiderServer.lax
The initial heap size is specified based on any of the below mentioned.
・When more than 2GB is set from version 3.0 onwards or version prior to 2.4.x.
lax.nl.java.option.additional=-Xms
・When version x86 prior to version 2.4.x? is used
lax.nl.java.option.java.heap.size.initial
The maximum heap size is specified based on any of the below mentioned.
・When more than 2GB is set from version 3.0 onwards or version prior to 2.4.x.
lax.nl.java.option.additional=-Xmx
・When version x86 prior to version 2.4.x? is used
lax.nl.java.option.java.heap.size.max
Counter Measures:
If there is a difference in 2 setting values, please refer to below FAQ.
・FAQ No.24299
The process of DataSpider Servista has stopped. Even if you go through the log, the error which is supposed to be the cause is not displayed in particular. Explain the cause and the handling method.
3. Server log and server standard error output
Please use the log that was an output in the below directory, and check the details of the output done during service termination.
$DATASPIDER_HOME/server/logs/server.log
$DATASPIDER_HOME/server/logs/server.error.log
Counter Measures:
Search the below error messages and if you find errors corresponding to the time where the service has been stopped then please check the below FAQ.
・java.lang.OutOfMemoryError: Java heap space
・java.lang.OutOfMemoryError: nativeGetNewTLA
・java.lang.OutOfMemoryError: unable to create new native thread
・java.lang.OutOfMemoryError: mmAllocObject
The memory of the heap area cannot be secured.
What would be the handling method for this?
・FAQ No.24257
The below error occurs and script execution fails when the data count targeted for process is increased in the script that had ended normally till then. Explain the cause and the handling method.
java.lang.OutOfMemoryError: Java heap space
・java.lang.OutOfMemoryError: PermGen space
The memory of the permanent area, which is a part of the heap area cannot be secured.
For the handling method of this case, please refer to the below FAQ.
・FAQ No.21334
Error (ScriptNotFoundException) occurs during script execution and sometimes it is not possible to connect with DataSpider Studio. When the server log and the server standard error output were confirmed, the following errors were output. Explain the cause and the handling method.
java.lang.OutOfMemoryError: PermGen space
Reason for checking
1. Dump log
Java adopts the Just In Time compilation method(Hereafter called as JIT method) and performance has been improved by converting(compiling) the Java intermediate code into the Native code of OS and then executing it.
JIT method is adopted even in the internal process of the DataSpiderServer, and when Compiler Thread in the JIT method is called, the service might stop.
When the above issues gets generated in the state where memory is adequately allocated, and due to the fact that processing status during service termination is output in the dump log, it is possible to proceed with examination on this information.
On the contrary, when the memory is not adequately allocated, dump log is not displayed (Because the memory to output the dump log cannot be allocated). Hence, it is possible to isolate the cause to know whether it is due to low memory.
Therefore, please confirm the dump log first of all.
2. DataSpiderServer.lax
When the setting value of initial heap size and maximum heap size differs, JavaVM secures the memory of the capacity specified by the initial heap size when service is started. Later, if memory is not sufficient then the secured memory capacity is enhanced up to the maximum heap size.
During such cases, if memory could not be secured then service is stopped.
Service might stop before detecting memory shortage on the javaVM side, and in such situation,
the log that shows memory shortage in the server log etc. is not displayed.Java adopts the Just In Time compilation method(Hereafter called as JIT method) and performance has been improved by converting(compiling) the Java intermediate code into the Native code of OS and then executing it.
JIT method is adopted even in the internal process of the DataSpiderServer, and when Compiler Thread in the JIT method is called, the service might stop.
When the above issues gets generated in the state where memory is adequately allocated, and due to the fact that processing status during service termination is output in the dump log, it is possible to proceed with examination on this information.
On the contrary, when the memory is not adequately allocated, dump log is not displayed (Because the memory to output the dump log cannot be allocated). Hence, it is possible to isolate the cause to know whether it is due to low memory.
Therefore, please confirm the dump log first of all.
2. DataSpiderServer.lax
When the setting value of initial heap size and maximum heap size differs, JavaVM secures the memory of the capacity specified by the initial heap size when service is started. Later, if memory is not sufficient then the secured memory capacity is enhanced up to the maximum heap size.
During such cases, if memory could not be secured then service is stopped.
Service might stop before detecting memory shortage on the javaVM side, and in such situation,
Because of this, please check the DataSpiderServer.lax after the dump log.
3. Server log, server standard error output
There will be outbreak of memory shortage errors (java.lang.OutOfMemoryError) when memory more than the capacity specified in DataSpiderServer.lax and this is due to the fact that there are many data numbers in the scope of process or no. of script creations, project.
In this case, as it is difficult to secure the memory necessary for the process, it enters into the state where the service can be easily stopped.
Hence, please check sever log, server standard error output.
Information necessary for examination
When issues could not be fixed even if the entire content described in "Check points and
the counter measures" are executed, then the errors that were not generated in the past will be
generated and service might get stopped.
To confirm the status, check the below information and then contact the support center.
(1) Trigger for event generation
Please check the period in which the termination of DataSpiderServer has started to generate.
Also, please confirm the settings changed before and after that or check the executed work.
(2) Existence of generation frequency or avoidance
To check the impact on the operation, please confirm the existence of avoidance(such as restart with service "restore") or generation frequency(daily, monthly etc.,) of the problem.
(3) Conditions to generate the problem
Please check the conditions(when a specific script is executed, and specific data is read) to generate the problem.
(4) Log file
Please send the below log files that are being displayed during the period where problem is generated.
$DATASPIDER_HOME/server/logs/server.log
$DATASPIDER_HOME/server/logs/server.log.N (* N is normal-width characters)
$DATASPIDER_HOME/server/logs/server.error.log
$DATASPIDER_HOME/server/logs/<Run date>/exec.log
(5) Dump file
Please check for the existence of the output of the below dump log.
For displaying, please send it during inquiry.
・When version from 3.0 onwards or x86 version prior to 2.4x is used
$DATASPIDER_HOME\server\bin\hs_err_pid<pid>.log
To confirm the status, check the below information and then contact the support center.
(1) Trigger for event generation
Please check the period in which the termination of DataSpiderServer has started to generate.
Also, please confirm the settings changed before and after that or check the executed work.
(2) Existence of generation frequency or avoidance
To check the impact on the operation, please confirm the existence of avoidance(such as restart with service "restore") or generation frequency(daily, monthly etc.,) of the problem.
(3) Conditions to generate the problem
Please check the conditions(when a specific script is executed, and specific data is read) to generate the problem.
(4) Log file
Please send the below log files that are being displayed during the period where problem is generated.
$DATASPIDER_HOME/server/logs/server.log
$DATASPIDER_HOME/server/logs/server.log.N (* N is normal-width characters)
$DATASPIDER_HOME/server/logs/server.error.log
$DATASPIDER_HOME/server/logs/<Run date>/exec.log
(5) Dump file
Please check for the existence of the output of the below dump log.
For displaying, please send it during inquiry.
・When version from 3.0 onwards or x86 version prior to 2.4x is used
$DATASPIDER_HOME\server\bin\hs_err_pid<pid>.log
・When version x86 prior to version 2.4.x? is used
$DATASPIDER_HOME\server\bin\jrockit.<pid>.dump
$DATASPIDER_HOME\server\bin\jrockit.<pid>.dump
[Reference Information]
・FAQ No.24257
The below error occurs and script execution fails when the data count targeted for process is increased in the script that had ended normally till then. Explain the cause and its counter measures.
java.lang.OutOfMemoryError: Java heap space
・FAQ No.24513
Error (ScriptNotFoundException) occurs during script execution and sometimes it is not possible to connect with DataSpider Studio. When the server log and the server standard error output were confirmed, the following errors were output. Explain the cause and the handling method.
java.lang.OutOfMemoryError: PermGen space
・FAQ No.24300
A file jrockit.****.dump is displayed in $DATASPIDER_HOME/server/bin and DataSpider Servista service is stopped. What would be the reason and handling method?
(half-width characters are used in ****)
・FAQ No.24301
A file hs_err_pid****.log is displayed in $DATASPIDER_HOME/server/bin and DataSpider Servista
service is stopped. What would be the reason and handling method?
(half-width characters are used in ****)
・FAQ No.24299
The process of DataSpider Servista has stopped. Even if you go through the log, the error which is supposed to be the cause is not displayed in particular. Explain the cause and the handling method.