If execution of a Java application fails, the Java function will return the error SQLSTATE 39000. Check the server log of Symfoware Server and then if required, check if any errors from IJServer12000 to IJServer12999 have been output to the logs below:
Event log
Container server log
Container Java VM log
Domain server log
Web server trace log
Web server internal log
Some examples are provided below.
Abnormal termination of the Java EE DAS service
Even if the Java EE DAS service ends in an error, it will be restarted automatically, enabling jobs to continue. However, if the error occurs repeatedly, investigate its cause by referring to "Messages Output by PL/extJava" in Messages, using the messages with "IJServer" in the message number that are output to the log file below. Identify the cause and prevent the error from recurring.
Event log
Domain server log
Abnormal termination of the PCMI service
The server instance(Java VM) monitored by the PCMI service and the Java EE DAS service will remain unduly. You must forcibly terminate these processes (refer to "8.10.3 Errors Caused by Failure to Start PL/extJava" for details), remove the cause of the error, and then restart the instance.
Java heap insufficiency
If an error message is output to the log below indicating that memory is insufficient and the Java application cannot be executed, then the heap area size and Perm area size of the server instance(Java VM) in the container must be modified.
Container server log
Container server instance(Java VM) log
Point
The following default values are set for the heap area and Perm area of the server instance(Java VM) in the container.
Type | Setting value |
|---|---|
Server instance(Java VM) heap area size | 512MB |
Server instance(Java VM) Perm area size | 192MB |
Perform the following procedure to change the server instance(Java VM) heap area size and Perm area size in the container:
Use the pgx_jadmin command with the list-jvm-options subcommand to check the size of the heap area and Perm area in the current server instance(Java VM).
Example
> pgx_jadmin list-jvm-options --dbname db01
Refer to the output results of the corresponding item to be checked below for the heap area size and the Perm area size.
Option | Item to be checked |
|---|---|
heap area size | -Xmx |
Perm area size | -XX:MaxPermSize |
See
Refer to "pgx_jadmin" in the Reference for information on the list-jvm-options subcommand.
Stop the instance
Stop the instance . Refer to 2.1 Starting and Stopping an Instance" for information on how to stop an instance.
If the instance fails to stop, refer to "8.11 Actions in Response to Failure to Stop an Instance".
Use the pgx_jadmin command with the modify-jvm-options subcommand to modify the configured size of the heap area and Perm area in the server instance(Java VM).
Example
To change the heap area size and the Perm area size of the server instance(Java VM) to "1024 (megabytes)" and "384 (megabytes)", respectively.
> pgx_jadmin modify-jvm-options --dbname db01 --heapsize 1024 --permsize 384
See
Refer to "pgx_jadmin" in the Reference for information on the modify-jvm-options subcommand.
Start the instance
Start the instance. Refer to 2.1 Starting and Stopping an Instance" for information on how to start an instance.
If the instance fails to start, refer to "8.10 Actions in Response to Instance Startup Failure"
Domain root disk failure
Refer to "8.10.3 Errors Caused by Failure to Start PL/extJava" for information on the corrective action to take when the disk on which the domain root is placed fails, or when domain root resources become corrupted due to incorrect operation.
