There are many reasons such as javaVM problem, insufficient memory for stopping the service.

Considering the emergency support, we are describing only the check points for isolation as given below. When the reasons to be checked are necessary, refer to "■Reasons for Checking" at the end of this document and when you want to check the details of all the problems, refer to each FAQ that is provided below.

 

Is any one of the below logs being displayed? Check for it.

$DATASPIDER_HOME\server\bin\hs_err_pid<pid>.log

 

$DATASPIDER_HOME\server\bin\jrockit.<pid>.dump

 

Refer to FAQ 24300 or 24301 when it is being output.

 

Check the setting value of initial heap size and maximum heap size from the below setting file and check whether there is any difference in the setting value.

 

$DATASPIDER_HOME/server/bin/DataSpiderServer.lax

 

The initial heap size is specified with any of the following keys.

lax.nl.java.option.additional= - Xms

lax.nl.java.option.java.heap.size.initial

 

The maximum heap size is specified with any of the following keys.

 lax.nl.java.option.additional= - Xmx

lax.nl.java.option.java.heap.size.max

 

　Refer to FAQ 24299 when there is a difference in two setting values.

 

In the log displayed in the below directories, check the contents displayed in the time zone where the service has stopped.

$DATASPIDER_HOME/server/logs/server.log
$DATASPIDER_HOME/server/logs/server.error.log

Perform search with the below error messages and when there is an error relevant to the time zone where the service has been stopped, check the below FAQs.

The heap area memory is in a state where it cannot be allocated. Refer to FAQ 24257 for the handling method.

The permanent area memory which is a part of the heap area memory is in a state where it cannot be allocated. Refer to FAQ 24513 for the handling method.

 

 

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.

 

JIT method is adopted even in the internal processing of DataSpiderServer, but when the compiler thread is called in JIT method, the service might stop.

 

When the above-mentioned problem occurs even after allocating sufficient memory, then the processing status that is at the time of service stop can be output to the dump log and thus the investigation can be proceeded from this information.

 

On the contrary, if sufficient memory is not allocated and the dump log is not displayed (the memory to output the dump log cannot be allocated), then it is possible to isolate whether the reason is due to insufficient memory or not.

 

Hence check the dump log first.

When the setting value of initial and maximum heap size are different, JavaVM allocates the memory capacity specified in the initial heap size during service startup and after that if the memory is insufficient, then it extends the memory capacity until it reaches the maximum heap size. If the memory cannot be allocated at this point, then the service is stopped.

 

Service might stop even before detecting the memory shortage on the javaVM side and in this case, the log denoting the insufficient shortage is not output in the server log etc. Therefore, next to dump log, check the DataSpiderServer.lax.

As there are more number of projects and scripts created or the number of data cases targeted for processing and when the memory capacity more than specified in DataSpiderServer.lax is needed, insufficient memory error (java.lang.OutOfMemoryError) occurs.

 

In this case, it would be difficult to allocate the memory required for processing and it would be in the state where the service is stopped easily. Therefore, check the server log and server standard error output.

 

The related FAQs are provided below.

 

・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 its counter measures.

 

java.lang.OutOfMemoryError: PermGen space
 

・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

The file hs_err_pid****.log is displayed in $DATASPIDER_HOME/server/bin and DataSpider Servista service had stopped. Explain the cause and the handling method.

(Normal width number will be displayed 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.