Variable Information
{0}: Database name
{1}: Server instance (Java VM) name
{2}: Process ID
Explanation
The processing to stop the container did not complete within the process monitoring time.
System Action
The server instance (Java VM) was stopped by force.
User Action
There is no response from the Java application, or processing may have been delayed. Refer to "No Response from Java Functions" in the Operation Guide, and take the required action.
Variable Information
{0}: Database name
Explanation
The container failed to restart automatically, and all active server instances (Java VM) were stopped.
System Action
The container is stopped.
User Action
If any messages have been output to the event log (Windows(R)) or the system log (Linux) before or after this message, take the required action and investigate the cause of instance startup failure.
Variable Information
{0}: Database name
{1}: Server instance (Java VM) name
{2}: Process ID
Explanation
Automatic restart processing for a server instance (Java VM) failed after the server instance (Java VM) terminated abnormally.
System Action
The container is stopped.
However, if one or more server instances (Java VM) of a container remain, processing is continued.
User Action
If any messages have been output to the event log (Windows(R)) or the system log (Linux) before or after this message, take the required action and investigate the cause of abnormal termination of the server instance (Java VM).
Variable Information
{0}: Database name
{1}: Server instance (Java VM) name
{2}: Process ID
Explanation
An error occurred during the start processing of the server instance (Java VM).
System Action
Container processing is interrupted.
User Action
If any messages have been output to the event log (Windows(R)) or the system log (Linux) before or after this message, take the required action and investigate the cause of instance startup failure.
Variable Information
{0}: Database name
Explanation
The container has stopped.
System Action
Container processing is interrupted.
User Action
If any messages have been output to the event log (Windows(R)) or the system log (Linux) before or after this message, take the required action and investigate the cause of instance stopping failure.
Variable Information
{0}:Database name
{1}: Server instance (Java VM) name
{2}: Process ID
Explanation
The server instance (Java VM) has terminated abnormally.
System Action
Processing is interrupted.
User Action
If any messages have been output to the event log (Windows(R)) or the system log (Linux) before or after this message, take the required action and investigate the cause of abnormal termination of the server instance (Java VM).
Variable Information
{0}: Error code
Explanation
A system error occurred.
System Action
Processing is interrupted.
User Action
Recover PL/extJava.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}:Database name
{1}: Server instance (Java VM) name
{2}: Process ID
Explanation
There is no response from the server instance (Java VM). There may be a high load on the system, or insufficient memory.
System Action
Processing is continued.
User Action
Check if there is sufficient available memory.
Stop other applications, and reduce the load on the machine.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}:Database name
Explanation
The container has stopped because the server instance (Java VM) terminated abnormally.
System Action
The container is stopped.
User Action
If any messages have been output to the event log (Windows(R)) or the system log (Linux) before or after this message, take the required action and investigate the cause of abnormal termination of the server instance (Java VM). Restart the instance after removing the cause.
Variable Information
{0}:Database name
Explanation
The container has started.
Variable Information
{0}:Database name
Explanation
The container has stopped.
Variable Information
{0}:Database name
Explanation
The container was stopped by force.
Variable Information
{0}:Database name
{1}:Memory type code
{1}: Server instance (Java VM) name
{2}: Process ID
Explanation
There is insufficient Java VM heap area, therefore the container process stopped.
When Process ID {3} is "none", the process ID cannot be obtained because of one of the following causes:
An incorrect Java VM option is used during the process startup
The port used for debugging of the container is duplicated with the port of another server instance (Java VM)
Debugging is performed for a container with 2 or more server instances (Java VM)
The process is stopped using System.exit
System Action
The container process for which there is insufficient Java VM heap area is stopped.
User Action
If this message is output frequently, change the heap area specified in the Java VM option as follows.
Reestimate the memory required to use the container, and check if sufficient memory is secured.
If it is, there may be insufficient memory to use other applications.
Reestimate the memory required to run other applications on the same machine, and investigate if there is sufficient memory.
If, as a result of the reestimation, it is confirmed that there is insufficient memory, contact the system administrator.
Ask the system administrator to add the main memory or extend the swap area.
Also, if the Java heap size is excessively large, use the modify-jvm-options subcommand of the pgx_jadmin command to reduce the specified size.
Refer to "Java Function Errors" in the Operation Guide for details.
Check if the maximum number of threads that can be executed by the instance administrator has been exceeded. If the maximum number has been exceeded, edit the /etc/security/limits.conf file, and take the required action.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Use the modify-jvm-options subcommand of the pgx_jadmin command to extend the Java heap area, and then restart the instance.
Refer to " Java Function Errors" in the Operation Guide for details.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Use the modify-jvm-options subcommand of the pgx_jadmin command to extend the Java Perm area, and then restart the instance.
Refer to "Java Function Errors" in the Operation Guide for details.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Take the required action described above for the Java heap area, Java Perm area, or C heap area.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}:Database name
Explanation
The process failed to restart, therefore, the container operates with some server instances (Java VM) stopped.
System Action
Container operation is continued.
User Action
Remove the cause of the application process restart failure, and then restart the instance.
Explanation
One of the following occurred:
Some of the server instances (Java VM) failed to start.
All of the server instances (Java VM) failed to start.
System Action
Processing is continued.
User Action
If any messages have been output to the event log (Windows(R)) or the system log (Linux) before or after this message, take the required action and investigate the cause of instance startup failure.
Variable Information
{0}: Java VM log file
Explanation
Failed to output to the Java VM log file.
System Action
If this error occurs on startup, the container start processing is interrupted.
If the container has already started up, container operation is continued.
User Action
Take the following actions:
Check if write privileges were assigned for the file.
Check if write privileges were assigned for the log output directory or parent directory.
Check if the log output directory settings are valid. If the log settings are not valid, change them.
Ensure that the length of the log file's absolute path has not exceeded the maximum path length configured in the operating system. If it has, configure the length of the log file's absolute path so that it does not exceed the maximum path length configured in the operating system.
The disk has become corrupted, therefore, access to the file or directory has failed. Check the disk.
Due to a conflict with other processing, access to the disk is temporarily unavailable. Reexecute processing.
If there is insufficient free disk space, secure more.
Variable Information
{0}:Java VM log file
Explanation
Rotation of the Java VM log file was successful.
Variable Information
{0}:Java VM log file
Explanation
Rotation of the Java VM log file failed.
System Action
If this error occurs on startup, the container start processing is interrupted.
If the container has already started, container operation continues. Rotation will be attempted the next time the log is output (when the rotation type is the log size) or the next time the log rotation time is reached (when the rotation type is the log collection time).
User Action
Take the following actions:
Check if write privileges were assigned for the file.
Check if write privileges were assigned for the log output directory or parent directory.
The disk has become corrupted, therefore, access to the file or directory has failed. Check the disk.
Due to a conflict with other processing, access to the disk is temporarily unavailable. The action is unnecessary.
Variable Information
{0}: Tag name
{1}: Attribute name
{2}: Value
Explanation
There are errors in the definition information of the container.
User Action
Ensure the correct values are specified in the definition information of the container, and reexecute the operation.
Variable Information
{0}: Path
Explanation
Failed to delete the directory.
System Action
Processing is interrupted.
User Action
Take the following actions:
Check if write privileges were assigned for the log output directory or parent directory.
The disk has become corrupted, therefore, access to the file or directory has failed. Check the disk.
Due to a conflict with other processing, access to the disk is temporarily unavailable. Reexecute processing.
Variable Information
{0}:Path
Explanation
Rotation of the current directory failed.
System Action
Processing is interrupted.
User Action
Take the following actions:
Check if write privileges were assigned for the log output directory or parent directory.
The disk has become corrupted, therefore, access to the file or directory has failed. Check the disk.
Due to a conflict with other processing, access to the disk is temporarily unavailable. Reexecute processing.
Variable Information
{0}:Path
Explanation
Failed to create the directory.
System Action
Processing is interrupted.
User Action
Take the following actions:
Check if write privileges were assigned for the log output directory or parent directory.
The disk has become corrupted, therefore, access to the file or directory has failed. Check the disk.
Due to a conflict with other processing, access to the disk is temporarily unavailable. Reexecute processing.
Variable Information
{0}: Java VM log file
{1}: Error information
Explanation
Failed to output the Java VM log file.
System Action
If this error occurs on startup, the container start processing is interrupted.
If the container has already started up, container operation is continued.
User Action
Take the following actions:
Check if write privileges were assigned for the file.
Check if write privileges were assigned for the log output directory or parent directory.
Check if the log output directory settings are valid. If the log settings are not valid, change them.
Ensure that the length of the log file's absolute path has not exceeded the maximum path length configured in the operating system. If it has, configure the length of the log file's absolute path so that it does not exceed the maximum path length configured in the operating system.
The disk has become corrupted, therefore, access to the file or directory has failed. Check the disk.
Due to a conflict with other processing, access to the disk is temporarily unavailable. Reexecute processing.
If there is insufficient free disk space, secure more.
Variable Information
{0}: Message ID
Explanation
Attempted to output a message that has not been defined.
User Action
Recover PL/extJava.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Error information
Explanation
One of the following occurred:
A request was accepted during start processing, and therefore could not be processed.
An error occurred in internal processing.
User action
If this message is output during startup of an instance, ignore it.
Requests accepted during start processing will not be processed.
Refer to any other messages that were output at the same time, and take the required action.
If no other messages were output, contact Fujitsu technical support.
Explanation
The Java EE DAS service failed to start due to the definition file being in an abnormal state.
System Action
Processing is interrupted.
User Action
There may be insufficient Java EE DAS service heap area, or the address space upper limit may have been exceeded.
Recover PL/extJava.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Explanation
The backed up definition file has been restored and the Java EE DAS service has started due to the definition file being in an abnormal state.
System Action
Java EE DAS service startup processing is continued.
User Action
Recover PL/extJava.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Server instance (Java VM) name
{1}:Database name
{2}:Container status
Explanation
The server instance (Java VM) has started.
Variable Information
{0}: Server instance (Java VM) name
{1}:Database name
{2}:Container status
Explanation
The server instance (Java VM) was stopped by force.
Explanation
The definition file of the Java EE DAS service may be in an abnormal state due to insufficient free disk space.
System Action
Processing is interrupted.
User Action
The definition file is recovered when you restart the following service:
Java EE DAS service
After restarting the above service, reexecute processing.
If there is insufficient free disk space, delete unnecessary files and then take the action shown above.
Note that the operation performed before this message is output may cause loss of information, therefore check the content of the operation.
If the definition file fails to recover even after restarting the service, recover PL/extJava.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Error information
Explanation
Initialization of the service failed for the following reason:
Failed to load the library.
System Action
Processing is interrupted.
User Action
Check the detail message displayed in the error information and take the required action.
Variable Information
{0}: Server instance (Java VM) name
Explanation
An error occurred while retrieving the server instance (Java VM) status, therefore the status could not be obtained. The server instance (Java VM) may have hung. Or, the server instance (Java VM) may have already started up.
System Action
Processing is interrupted.
User Action
Recover PL/extJava.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Server instance (Java VM) name
Explanation
Synchronization of the repository failed.
System Action
Processing continues.
User Action
Synchronization of the repository failed, therefore it was not possible to update with the latest information. To update with the latest information, restart the instance.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0} : Database name
Explanation
The container has been created.
Variable Information
{0} : Database name
Explanation
The container has been deleted.
Variable Information
{0}: Server instance (Java VM) name
Explanation
The server instance has not been stopped, therefore the operation failed.
System Action
Processing is interrupted.
User Action
Stop the server instance, and then reexecute the operation.
Variable Information
{0}:Database name
Explanation
Not all server instances (Java VM) have started.
System Action
Processing is interrupted.
User Action
Refer to any other messages that were output at the same time, and take the required action.
Variable Information
{0}:Database name
Explanation
The container has already been stopped.
System Action
Processing is interrupted.
Variable Information
{0} : Server instance (Java VM) name
Explanation
The server instance (Java VM) has been created.
Variable Information
{0} : Server instance (Java VM) name
Explanation
The server instance (Java VM) has been deleted.
Variable Information
{0}: Container name
Explanation
An error occurred while retrieving the container status, therefore the status could not be obtained.
System Action
Processing is interrupted.
User Action
If this message is output, wait for a while then check the status of the domain or server instance (Java VM) using the pgx_jadmin list-domain subcommand or pgx_jadmin list-container subcommand.
If this does not resolve the problem, restart the instance.
Variable Information
{0}: Server instance (Java VM) name
Explanation
The specified server instance has not been started.
System Action
Processing is interrupted.
User Action
Start the instance, and reexecute processing.
Variable Information
{0}: Command
{1}: Detail information
Explanation
The command could not be executed.
System Action
Processing is interrupted.
User Action
Take one of the following actions:
If a message with a message number is output to Detail information, take the action indicated by the message.
Check if the command exists.
If the command does not exist, it is possible that the command may have been deleted or the product may have been installed incorrectly. Install the product again.
If the command exists, check the command's execution privileges and configure the settings as a user with administrator privileges.
If the problem is still not resolved, contact Fujitsu technical support.
Variable Information
{0}: Server instance (Java VM)
{1}: Port number
Explanation
The port number for server instance (Java VM) management is already in use.
System Action
Processing is interrupted.
User Action
Change the port number for server instance (Java VM) management to one that is not in use.
Variable Information
{0}: Server instance (Java VM)
{1}: Port number (system property)
Explanation
The specified port number for server instance (Java VM) management is an invalid value.
System Action
Processing is interrupted.
User Action
Ensure a valid port number is specified for server instance (Java VM) management.
Variable Information
{0}: Detail information
Explanation
An error occurred while setting the container.
System Action
Processing is interrupted.
User Action
Refer to the message displayed in Detail information, and then take the required action.
Variable Information
{0}: Host name
{1}: Port number
Explanation
Failed to connect to the Java EE DAS service.
System Action
Processing is interrupted.
User Action
Refer to any messages that were output before or after this message, and take the required action. After taking action, restart the instance. If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Detail error message
Explanation
An error occurred in the Java EE DAS service.
System Action
Processing is interrupted.
User Action
Refer to the detail error message and remove the cause of the error. After taking action, restart the instance. If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Explanation
Container stop processing is delayed because a Java application is still processing.
Explanation
Container stop processing has started because all Java applications have finished processing.
Explanation
The server instance (Java VM) timer functionality has started.
Explanation
The server instance (Java VM) timer functionality has stopped.
Variable Information
{0}: Java Application processing start time
{1}: Processing thread information
{2}: Target Java application
Explanation
There is no response from the application.
System Action
Processing is continued.
User Action
Refer to the thread dump output to the Java VM log of PL/extJava, to check if there are any occurrences of deadlocks, loops or processing delays.
Explanation
Java application timeout has been notified to the PCMI service.
Variable Information
{0}: Internal information
Explanation
Java application timeout could not be notified to the PCMI service.
System Action
Processing is continued.
User Action
Check the PL/extJava server log, and refer to any messages that have been output at the same time to remove the cause of the error.
Refer to any messages that have been output to the event log (Windows(R)) or the system log (Linux) to remove the cause of the error.
Explanation
A keep alive notification has been sent to the PCMI service.
Variable Information
{0}: Internal information
Explanation
A keep alive notification could not be sent to the PCMI service.
System Action
Processing is continued.
User Action
Refer to any messages that have been output to the PL/extJava server log, as well as the event log (Windows(R)) or system log (Linux), and check if an error has occurred.
If the above does not apply, refer to the Java VM log of PL/extJava and check if an error has occurred.
Variable Information
{0}: Error information
Explanation
Communication with the PCMI service failed.
System Action
Processing is continued.
The server application timer function is not operating correctly.
User Action
Take the following actions:
Take the action indicated in the messages output before and after this message.
Follow the action advised in messages output to the event log (Windows (R)) or the system log (Linux), and investigate the cause of the failure.
If the problem is still not resolved despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Log file name
Explanation
Rotation of the log file ({0}) was successful.
Variable Information
{0}: Log file name
Explanation
Failed to rotation the log file ({0}).
User Action
Possible causes are as follows: After taking action, reexecute the process.
Access authority is not granted to the file.
Access authority of the file may have been changed. Restore the access authority for the file, and reexecute processing.
The file or directory is referenced by another application.
Stop other applications, and reexecute processing.
The disk is defective.
A defect on the disk may be preventing files and directories from being accessed. Run a disk check.
Conflict with another process.
Conflict with another process may make the disk temporarily inaccessible. Reexecute processing.
There is insufficient disk space.
There may not be enough free disk space, therefore manually delete any old log files that exceed the allowable number of generations. Refer to "PL/extJava Log Information" in the Operation Guide for information on the log file output directory.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Log file name
Explanation
Failed to delete the log file.
User Action
Possible causes are as follows: After taking action, reexecute the process.
Access authority is not granted to the file.
Access authority of the file may have been changed. Restore the access authority for the file, and reexecute processing.
The file or directory is referenced by another application.
Stop other applications, and reexecute processing.
The disk is defective.
A defect on the disk may be preventing files and directories from being accessed. Run a disk check.
Conflict with another process.
Conflict with another process may make the disk temporarily inaccessible. Reexecute processing.
There is insufficient disk space.
There may not be enough free disk space, therefore manually delete any old log files that exceed the allowable number of generations. Refer to "PL/extJava Log Information" in the Operation Guide for information on the log file output directory.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Log file name
Explanation
Failed to open the log file ({0}).
User Action
Possible causes are as follows: After taking action, reexecute the process.
Access authority is not granted to the file.
Access authority of the file may have been changed. Restore the access authority for the file, and reexecute processing.
The file or directory is referenced by another application.
Stop other applications, and reexecute processing.
The disk is defective.
A defect on the disk may be preventing files and directories from being accessed. Run a disk check.
Conflict with another process.
Conflict with another process may make the disk temporarily inaccessible. Reexecute processing.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Log file name
Explanation
Failed to open the log file ({0}).
User Action
Possible causes are as follows: After taking action, reexecute the process.
Access authority is not granted to the file.
Access authority of the file may have been changed. Restore the access authority for the file, and reexecute processing.
The file or directory is referenced by another application.
Stop other applications, and reexecute processing.
The disk is defective.
A defect on the disk may be preventing files and directories from being accessed. Run a disk check.
Conflict with another process.
Conflict with another process may make the disk temporarily inaccessible. Reexecute processing.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Error detail
Explanation
Failed to initialize the log file.
User Action
Possible causes are as follows: After taking action, reexecute the process.
Access authority is not granted to the file.
Access authority of the file may have been changed. Restore the access authority for the file, and reexecute processing.
The file or directory is referenced by another application.
Stop other applications, and reexecute processing.
The disk is defective.
A defect on the disk may be preventing files and directories from being accessed. Run a disk check.
Conflict with another process.
Conflict with another process may make the disk temporarily inaccessible. Reexecute processing.
There is insufficient disk space.
There may not be enough free disk space, therefore manually delete any old log files that exceed the allowable number of generations. Refer to "PL/extJava Log Information" in the Operation Guide for information on the log file output directory.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Log file name
Explanation
Failed to output to the log file ({0}).
User Action
Possible causes are as follows: After taking action, reexecute the process.
Access authority is not granted to the file.
Access authority of the file may have been changed. Restore the access authority for the file, and reexecute processing.
The file or directory is referenced by another application.
Stop other applications, and reexecute processing.
The disk is defective.
A defect on the disk may be preventing files and directories from being accessed. Run a disk check.
Conflict with another process.
Conflict with another process may make the disk temporarily inaccessible. Reexecute processing.
There is insufficient disk space.
There may not be enough free disk space, therefore manually delete any old log files that exceed the allowable number of generations. Refer to "PL/extJava Log Information" in the Operation Guide for information on the log file output directory.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Log file name
Explanation
The output to the log file ({0}) was stopped.
User Action
Possible causes are as follows: After taking action, reexecute the process.
Access authority is not granted to the file.
Access authority of the file may have been changed. Restore the access authority for the file, and reexecute processing.
The file or directory is referenced by another application.
Stop other applications, and reexecute processing.
The disk is defective.
A defect on the disk may be preventing files and directories from being accessed. Run a disk check.
Conflict with another process.
Conflict with another process may make the disk temporarily inaccessible. Reexecute processing.
There is insufficient disk space.
There may not be enough free disk space, therefore manually delete any old log files that exceed the allowable number of generations. Refer to "PL/extJava Log Information" in the Operation Guide for information on the log file output directory.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Alert monitoring function operation mode
Explanation
The alert monitoring function operation mode was set.
Variable Information
{0}: Error information
Explanation
The variable information is one of the following:
"Failed to get monitor from fmoni"
"Failed to get warning from fmoni (Java VM may be shutting down)"
The system is overloaded, and predictive monitoring cannot continue.
System Action
Java application processing is continued.
User Action
The variable information is one of the following:
"Failed to get monitor from fmoni"
"Failed to get warning from fmoni (Java VM may be shutting down)"
Ensure that there is no processing in the Java application that causes the system to become overloaded. After taking action, reregister the Java application and restart the instance.
If this message continues to be output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: Container name
{1}: Server instance (Java VM) name
{2}: Detailed message
Explanation
An event was detected in which the alert monitoring function exceeds the alert for the alarm value.
Detailed message
The following detailed messages are output by the alert detected by the alert monitoring function.
The format of the time information contained in the detailed message is "year/month/day hours:minutes:seconds.milliseconds".
Detailed message | Meaning of the warning | Conditions of occurrence |
|---|---|---|
There are possibilities of OutOfMemoryError because of the lack of the memory: TIME={0} SIZE={1} TIME: Time of occurrence SIZE: Rough estimate of amount added to Heap area (Unit: Bytes) (*1) | The Heap area is insufficient, therefore there is a danger that OutOfMemoryError will occur. | When the Heap usage rate immediately after Full GC is greater than 95%. Alternatively, when the Heap usage rate immediately after Full GC is greater than 90%, AND the Heap size used since the occurrence of the previous Full GC has increased continuously for at least 3 times. |
There are possibilities of OutOfMemoryError because of the lack of the Perm region: TIME={0} SIZE={1} TIME: Time of occurrence SIZE: Rough estimate of amount added to Perm area (Unit: Bytes) (*1) | The Perm area is insufficient, therefore there is a danger that OutOfMemoryError will occur. | When the Perm area usage amount is greater than 90%. |
OutOfMemoryError warning is occurred because the Perm region is exhausted: TIME={0} SIZE={1} TIME: Time of occurrence SIZE: Perm area increased amount (Unit: Bytes) | The Perm area usage amount is exhausted, therefore there is a danger that OutOfMemoryError will occur. | When the increase in the Perm area usage amount since the previous measurement is greater than 10 per cent of the overall Perm area, AND the Perm area usage rate that is assumed for the next increase of the same percentage is greater than 90%. Note that the value which is notified for "SIZE" is the size (increased amount) which will be assumed for increases of the same rate. |
It takes long time to do the garbage collections many times: TIME={0} AVERAGE={1} TIME: Time of occurrence AVERAGE: Average time for Full GC for the previous three times (in milliseconds) | Full GC continuously takes a long time. | When the average value for Full GC time for the previous three times is longer than 5 seconds. |
Inefficient garbage collections are run with the short intervals: TIME={0} WEIGHT={1} TIME: Time of occurrence WEIGHT: Usage rate of the old generation immediately before Full GC (in %) | Inefficient Full GC occurs in short intervals. | When the Full GC interval time for the previous three times is shorter than 20 seconds, AND the usage rate of the Old generation area immediately before Full GC is less than 65%. |
The garbage collections are run with the short intervals because of the lack of the memory: TIME={0} SIZE={1} TIME: Time of occurrence SIZE: Rough estimate of amount added to Heap area (Unit: Bytes) (*1) | The Heap area is insufficient, therefore Full GC occurs in short intervals. | When the Full GC interval time for the previous three times is shorter than 20 seconds, AND the Heap usage rate immediately after Full GC is greater than 65%. |
System.gc() are run with the short intervals: TIME={0} INTERVAL={1} TIME: Time of occurrence INTERVAL: Interval time for the java.lang.System.gc() method and the java.lang.Runtime.gc() method (in milliseconds) | The java.lang.System.gc() method and the java.lang.Runtime.gc() method occur in short intervals. | When the Full GC interval time for the previous three times is shorter than 20 seconds, AND the frequency of Full GC that occurs because of the java.lang.System.gc() method and the java.lang.Runtime.gc() method is high. |
The garbage collections are run with the short intervals: TIME={0} INTERVAL={1} TIME: Time of occurrence INTERVAL: Full GC interval time (in milliseconds) | Full GC occurs in short intervals. | When the Full GC interval time for the previous three times is shorter than 20 seconds. |
*1 To avoid warnings, it will be necessary to increase the Heap or Perm area size when the warning occurs. The value which is notified for "SIZE" is the rough estimate increased amount for this.
System Action
Application processing is continued.
User Action
Refer to " Java Function Errors" in the Operation Guide and change the heap area size and Perm area size for the server instance (Java VM) in the container. After taking action, restart the instance.
Variable Information
{0}: Error information 1
{1}: Error information 2
Explanation
An unexpected error occurred, therefore alert monitoring function is stopped.
System Action
Java application processing is continued.
Alert monitoring function is stopped. After this warning is output, alert monitoring function is disabled.
User Action
Refer to the error information and establish the cause of the failure.
If the problem is still not resolved, contact a Systems Engineer.
Variable Information
{0}: Error information
Explanation
A system error occurred.
System Action
Processing is interrupted.
User Action
Contact Fujitsu technical support.
Variable Information
{0}: Server instance (Java VM) name
{1}: Error information
Explanation
Failed to communicate with the PCMI service.
System Action
Processing is interrupted.
User Action
Take the following actions:
Take the action indicated by the message output before and after this message.
Take the action indicated by the message output to the event log (Windows(R)) or the system log (Linux), and investigate the cause of the failure.
If the problem persists, contact Fujitsu technical support.
Explanation
Java management agent started.
