Table of Contents

 

 

1. Dump log

• When using version 3.0 or later, or x86 version prior to version 2.4.x

• If you are using an x 64 version of 2.4 .x or earlier

2. DataSpiderServer.lax

• If the initial heap memory size is set to 2 GB or larger in versions 3.0 and later, or in versions 2.4.x and earlier.

• If you are using an x86 version earlier than 2.4.x

• If the maximum heap memory size is set to 2 GB or larger in versions 3.0 and later, or in versions 2.4.x and earlier.

• If you are using an x86 version earlier than 2.4.x

3. Server log and server standard error output

• java.lang.OutOfMemoryError: Java heap space
• java.lang.OutOfMemoryError: nativeGetNewTLA
• java.lang.OutOfMemoryError: unable to create new native thread
• java.lang.OutOfMemoryError: mmAllocObject

• java.lang.OutOfMemoryError: PermGen space

 

Java uses the Just In Time compilation (hereinafter referred to as the JIT method.) to improve the performance by converting a Java intermediate code to an OS Native code (compile) upon execution and executing it.

 

The internal processing of the DataSpiderServer also uses the JIT method, which can cause the service to stop when the Compiler Thread is called.

 

If the above error occurs when sufficient memory is available, the process status upon the service termination is output to the dump log. Therefore, it is possible to investigate based on this information.

 

On the other hand, if there is not enough memory, the dump logs will not be output so you can isolate the cause of (no memory available to output dump logs.) from the lack of memory.

 

For this reason, please check the dump log first.

If the initial heap size and maximum heap size settings are different, the javaVM reserves memory at service startup for the amount specified by the initial heap size. If it runs out of memory after that, it will increase the amount of memory it reserves up to the maximum heap size.

 

If memory cannot be secured at this time, the service will stop.

 

The service may stop before the javaVM detects that it is out of memory. In this case, no log indicating insufficient memory is output to the server log.

 

Please check DataSpiderServer.lax after the dump log.

An Out of Memory error (java.lang.OutOfMemoryError) occurs when the number of projects, scripts, or data being processed requires more memory than is specified in DataSpiderServer.lax.

 

In this case, it is difficult to allocate the memory required for processing, and the service is likely to stop.

 

For this reason, please check the server log and server standard error output.

 

If the problem persists after you have completed the instructions in "Checkpoint and Workaround", the service may be stopped with an error that has not occurred in the past.

 

For confirmation of the situation, please contact the support center with the following information.

Please check when the DataSpiderServer outage began. Also, you need to confirm the settings that were changed and the work that was done before and after that

In order to confirm the impact on the operation, please confirm the frequency of occurrence of the event (Daily, Monthly, etc.) and whether there is a workaround (such as restarting with "Recovery of service").

Please check the conditions under which the event occurs (When running certain scripts, when reading certain data, etc.).

Please send the following log file that is outputted at the time of the event.

 

$ DATASPIDER_HOME / server / logs / server.log

$ DATASPIDER_HOME / server / logs / server.log.N (* N is single-byte numbers)

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

$ DATASPIDER_HOME / server / logs / <execution date> /exec.log

Please check the following dumb log output. If so, please send it at the time of inquiry.

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

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

 

Reference Information