Troubleshooting
- A server shuts down abnormally.
- An application stops due to memory shortage
- Fail to start a server
- It takes time to start a server
- Garble when converting it from Windows-31J(CP932)
- Connection test succeeds even if setting of global resource is invalid
Event
A server may output a dump file and shut down abnormally.
- A server process stops.
- A dump file (hs_err_pidxxxx.log) is output under "$DATASPIDER_HOME/server/bin".
- You see information in a dump file saying a failure occurred at "Compiler Thread".
e.g.) Current thread (0x52d70cf8): JavaThread "CompilerThread1" daemon
Cause
Java has adopted the Just In Time Compiling Method (below as JIT method). Before executing a program, Java middle codes are compiled into Native codes of OS, which contribute to a better performance.
The JIT method is adopted in the internal processing of the server.When running the method, this may occur when a Compiler Thread is called.
For more details of the cause, refer to the technical information by Oracle (https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/crashes001.html#CIHDDHCI).
Solution
You can avoid the abnormal event by making the process not applicable to the JIT method.
Set the below value in "lax.nl.java.option.additional=" of a lax file and start the server.
"-XX:CompileCommand=exclude,com/appresso/ds/common/kernel/ModuleName,equals"
For information regarding a lax file of the server, refer to "Property Reference".
Event
Applications such as a server and a client may stop due to memory shortage.
Cause
This is because maximizing the memory used in applications is failed due to the shortage of the memory in the OS.
Solution
When starting an application, set the initial heap size equal to the maximum heap size.
By assuring the maximum memory size when starting an application, you can avoid system suspension caused by a failure of memory expansion.
For information regarding how to change the heap size of applications, refer to "Property Reference".
Event
If you start a server while a file under "$DATASPIDER_HOME/server/tmp" is open, booting may be failed.
Cause
This is because the process to delete unnecessary files under "$DATASPIDER_HOME/server/tmp" is failed.
Solution
Please start a server after files are all closed.
Event
If there are enormous amount of folders/files under "$DATASPIDER_HOME/server/tmp", it may take a while to start a server.
Cause
This is because the system is deleting unnecessary files under "$DATASPIDER_HOME/server/tmp" when starting a server.
Solution
Please make sure to delete unnecessary files in advance.
In Windows-31J(Microsoft Code Page 932), the character encoded more than once exists.
When these characters are converted into another encode with DataSpider (Internally maintain it with Unicode), the garble might be generated.
The garble of a specific character can be evaded by using character converter "Convert CP932 to SJIS" and "Convert SJIS to CP932" in the place where it is between Windows-31J and Shift_JIS.
"Convert SJIS to CP932" And, the specific character that can be converted by "Convert CP932 to SJIS" is as follows.
| Character |
Code position of Shift_JIS |
Mapping from Shift_JIS to Unicode |
Mapping from Windows31-J to Unicode |
| ― |
0x815C |
0x2014 |
0x2015 |
| ～ |
0x8160 |
0x301c |
0xff5e |
| ∥ |
0x8161 |
0x2016 |
0x2225 |
| － |
0x817C |
0x2212 |
0xff0d |
| ¢ |
0x8191 |
0x00a2 |
0xffe0 |
| £ |
0x8192 |
0x00a3 |
0xffe1 |
| ¬ |
0x81ca |
0x00ac |
0xffe2 |
Refer to page (http://support.microsoft.com/kb/170559/EN-US/) of the technical intelligence of Microsoft for details of the overlapping code.
Event
[Connection test] succeeds even if the setting of a global resource is invalid in the adapter that passes networks such as the mail adapters and Web adapters.
Cause
It is generated because the virus checker installed in the case that DataSpiderServer operates connects it with the port where the virus checker is open for the connection destination to which the connection of the adapter is set by a global resource.
Coping process
Remove the port connected with the adapter from the watch object of the virus check software.
Event
If you log off from an OS upon ScriptRunner execution, the return value of ScriptRunner becomes "143".
Cause
Due to JVM specifications, if you log off from an OS while executing ScriptRunner processes, the processes of ScriptRunner will be forced to shut down.
In this case, "143" is returned.
Solution
Add "-Xrs" to "lax.nl.java.option.additional" in ScriptRunner.lax.
If you specify "-Xrs", JVM does not supervise and process CTRL_C_EVENT, CTRL_CLOSE_EVENT, CTRL_LOGOFF_EVENT and CTRL_SHUTDOWN_EVENT.
Therefore, since JVM does not detect your log off, you can avoid this event from happening.