Variable Information
{0}: Command name
{1}: PCMI directory path
Explanation
The command {0} terminated normally.
Variable Information
{0}: Command name
{1}: PCMI directory path
{2}: Error information
{3}: System error number
Explanation
The command {0} failed.
System Action
Processing is interrupted.
User Action
If a message displaying the cause has been output before this message, take the action indicated by that message.
If a message displaying the cause has not been output before this message, take the action indicated by the message output to the event log (Windows(R)) or the system log (Linux) before this message and investigate the cause of command execution failure.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service is not registered in the specified directory {0}.
The structure of the PCMI directory {0} may be corrupted.
System Action
Processing is interrupted.
User Action
If this message is output during installation, perform the installation again.
In all other cases, or if the problem is still not resolved despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: PCMI directory path
Explanation
The registration of the PCMI service is being processed.
System Action
Processing is interrupted.
User Action
Install or uninstall, again.
If this error message continues to occur, contact Fujitsu technical support.
Variable Information
{0}: PCMI directory path
{1}: Error information
{2}: System error number
Explanation
An internal error occurred.
System Action
Processing is interrupted.
User Action
Take one of the following actions:
If a message displaying the cause has been output before this message, take the action indicated by that message.
Make a note of System error number {2} that is output, and then notify the system administrator.
If this error message continues to occur, contact Fujitsu technical support.
Variable Information
{0}: PCMI directory path
{1}: Error information
{2}: System error number
Explanation
A system error occurred.
System Action
Processing is interrupted.
User Action
Take one of the following actions:
If a message displaying the cause has been output before this message, take the action indicated by that message.
Check Error information {1} and System error number {2} that are output, refer to the following table, and then take the action indicated by Error information {1} and System error number {2}.
Error information {1} | System error number {2} | Explanation/Action |
|---|---|---|
- | [8,12,14] | There may be insufficient memory. Close unnecessary Java applications, and then reexecute the command. |
[102,105,201] | - | There may not be enough free space for the device. Secure free space for the device, and then reexecute the command. |
- | [4,28] | |
All other cases | Make a note of Error information {1} and System error number {2}, and then notify the system administrator. | |
If this error message continues to occur, contact Fujitsu technical support.
Variable Information
{0}: PCMI directory path
Explanation
The command cannot be executed. A process that cannot be executed at the same time may have been executed.
System Action
Processing is interrupted.
User Action
Wait for a while, and then reexecute the command.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service has started.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service has stopped.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service cannot be started.
System Action
Processing is interrupted.
User Action
If a message displaying the cause has been output before this message, take the action indicated by that message.
If a message displaying the cause has not been output before this message, take the action indicated by the message output to the event log (Windows(R)) or the system log (Linux) before this message and investigate the cause of command execution failure.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service cannot be stopped.
System Action
Processing is interrupted.
User Action
If a message displaying the cause has been output before this message, take the action indicated by that message.
If a message displaying the cause has not been output before this message, take the action indicated by the message output to the event log (Windows(R)) or the system log (Linux) before this message and investigate the cause of command execution failure.
Variable Information
{0}: PCMI directory path
{1}: System error number
Explanation
An error occurred while retrieving the PCMI status, therefore the status could not be obtained successfully. The PCMI service may have stopped responding.
System Action
Processing is interrupted.
User Action
If a message displaying the cause has been output before this message, take the action indicated by that message.
If a message displaying the cause has not been output before this message, take the action indicated by the message output to the event log (Windows(R)) or the system log (Linux) before this message and investigate the cause of command execution failure.
Variable Information
{0}: PCMI directory path
Explanation
The specified PCMI directory {0} is not empty.
System Action
Processing is interrupted.
User Action
If this message is output during installation, empty the applicable directory {0} and perform the installation again.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service has started.
System Action
Processing is interrupted.
User Action
If this message is output during uninstallation, stop the instance and perform the uninstallation again.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service name is already being used.
If the uninstallation was performed before this operation, unnecessary resources may still exist.
System Action
Processing is interrupted.
User Action
Delete unnecessary resources using the following procedure, and then install again.
If "FUJITSU PCMI(isje6-<componentId>)" remains in services, execute the sc command as shown below to delete the "FUJITSU PCMI(isje6-<componentId>)" service.
sc delete "FUJITSU PCMI(isje6-<componentId>)"
If the following files exist, remove them using the rm command:
/etc/rc.d/init.d/FJSVpcmiisje6-componentId /etc/rc.d/rc2.d/S99FJSVpcmiisje6-componentId /etc/rc.d/rc3.d/S99FJSVpcmiisje6-componentId /etc/rc.d/rc4.d/S99FJSVpcmiisje6-componentId /etc/rc.d/rc5.d/S99FJSVpcmiisje6-componentId /etc/rc.d/rc0.d/K00FJSVpcmiisje6-componentId /etc/rc.d/rc1.d/K00FJSVpcmiisje6-componentId /etc/rc.d/rc6.d/K00FJSVpcmiisje6-componentId
Example
Configure componentId using the following format:
"STFSYMOIDB" + "VL" + "firstDigitOfArchitecture"VL: Version/level of Symfoware Server
firstDigitOfArchitecture: Product architecture ("3" for the 32-bit version; "6" for the 64-bit version)
For Symfoware Server version "1210" with 64-bit product architecture, componentId will be configured as shown below:
STFSYMOIDB12106
Variable Information
{0}: PCMI directory path
Explanation
Automatic startup has not been configured for the PCMI service. Unnecessary resources may still exist.
System Action
Processing is continued.
User Action
Delete unnecessary resources using the following procedure, and then install again.
If "FUJITSU PCMI(isje6-<componentId>)" remains in services, execute the sc command as shown below to delete the "FUJITSU PCMI(isje6-<componentId>)" service.
sc delete "FUJITSU PCMI(isje6-<componentId>)"If the following files exist, remove them using the rm command:
/etc/rc.d/init.d/FJSVpcmiisje6-componentId /etc/rc.d/rc2.d/S99FJSVpcmiisje6-componentId /etc/rc.d/rc3.d/S99FJSVpcmiisje6-componentId /etc/rc.d/rc4.d/S99FJSVpcmiisje6-componentId /etc/rc.d/rc5.d/S99FJSVpcmiisje6-componentId /etc/rc.d/rc0.d/K00FJSVpcmiisje6-componentId /etc/rc.d/rc1.d/K00FJSVpcmiisje6-componentId /etc/rc.d/rc6.d/K00FJSVpcmiisje6-componentId
Example
Configure componentId using the following format:
"STFSYMOIDB" + "VL" + "firstDigitOfArchitecture"VL: Version/level of Symfoware Server
firstDigitOfArchitecture: Product architecture ("3" for the 32-bit version; "6" for the 64-bit version)
For Symfoware Server version "1210" with 64-bit product architecture, componentId will be configured as shown below:
STFSYMOIDB12106
Variable Information
{0}: PCMI directory path
Explanation
A command was executed without an appropriate permission.
System Action
Processing is interrupted.
User Action
Reexecute the command as a user with privileges to execute the command.
Explanation
Failed to obtain the common Java information.
System Action
Processing is interrupted.
User Action
Contact Fujitsu technical support.
Explanation
The PCMI service has already stopped.
System Action
Processing is interrupted.
User Action
Check if the instance has started.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service has started.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service has stopped.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
Explanation
The server instance (Java VM) {1} has started.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
Explanation
Failed to start the server instance (Java VM) {1}.
System Action
Processing is interrupted.
User Action
Take one of the following actions:
If another message has been output at the same time as this message, take the action indicated by that message.
If a message has been output to the event log (Windows(R)) or the system log (Linux) before this message, take the action indicated by that message and investigate the cause of instance startup failure.
If the issue is not resolved by the above actions, make a note of internal information {2}, and contact Fujitsu technical support.
Variable Information
{0}: PCMI directory path
{1}: Detail information
Explanation
The PCMI service cannot be started.
System Action
Processing is interrupted.
User Action
Take one of the following actions:
Check Detail information {1} that is output, remove the cause of the error, and then reexecute the command.
If a message has been output to the event log (Windows(R)) or the system log (Linux) before this message, take the action indicated by that message and investigate the cause of instance startup failure.
If this error message continues to occur, make a note of Detail information {1}, contact Fujitsu technical support.
Variable Information
{0}: PCMI directory path
Explanation
The PCMI service cannot be started.
System Action
Processing is interrupted.
User Action
Take one of the following actions:
If another message has been output at the same time as this message, take the action indicated by that message.
If a message has been output to the event log (Windows(R)) or the system log (Linux) before this message, take the action indicated by that message and investigate the cause of instance startup failure.
If this error message continues to occur, contact Fujitsu technical support.
Explanation
The PCMI service cannot be started.
System Action
Processing is interrupted.
User Action
Take one of the following actions:
If another message has been output at the same time as this message, take the action indicated by that message.
If a message has been output to the event log (Windows(R)) or the system log (Linux) before this message, take the action indicated by that message and investigate the cause of instance startup failure.
If this error message continues to occur, contact Fujitsu technical support.
Variable Information
{0}: PCMI directory path
{1}: Detail information
Explanation
The processing of the startup script executed using the exit function when the PCMI service starts has terminated abnormally.
System Action
Processing is interrupted.
User Action
Check Detail information {1} that is output, refer to the following table, and then and take the action indicated.
Detail information {1} | Variable Information in Detail information {1} | Explanation/Action |
|---|---|---|
Failed to execute command. [%s] [%d] | [%s]: Startup script path [%d]: Startup script return value | Ensure the host information for building PL/extJava has been added to the hosts file. If the problem still exists, contact Fujitsu technical support. |
All other cases | Recover PL/extJava. If the problem still exists, contact Fujitsu technical support. | |
Variable Information
{0}: PCMI directory path
Explanation
Internal error occurred while stopping the PCMI service.
System Action
Processing is continued.
User Action
Contact Fujitsu technical support.
Explanation
The PCMI service has already stopped.
System Action
Processing is interrupted.
User Action
Check if the port number for domain management is correct. Or, check if the port number is not being used by another application.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
Explanation
The server instance (Java VM) {1} has stopped.
Explanation
An internal error occurred in the PCMI service.
System Action
Processing is interrupted.
User Action
Check the message output to the event log (Windows(R)) or the system log (Linux) before this message, and take the action indicated by that message.
If this error message continues to occur, contact Fujitsu technical support.
Variable Information
{0}: Internal information
{1}: Reason
Explanation
Communication error occurred.
System Action
The communication processing that failed is discarded. If this error occurs on startup, the processing is interrupted.
User Action
Check Internal information {0} and Reason {1} that are output, and remove the cause of the failure.
Variable Information
{0}: Communication environment definition file path
Explanation
Failed to read the communication environment definition file {0}.
System Action
Processing is interrupted.
User Action
Contact Fujitsu technical support.
Variable Information
{0}: Internal information
{1}: Reason
Explanation
The communication environment definition file is incorrect.
System Action
The PCMI service is stopped.
User Action
Contact Fujitsu technical support.
Variable Information
{0}: File path
Explanation
An I/O error occurred.
System Action
Processing is interrupted.
User Action
Take one of the following actions:
Check if the disk device where the file {0} is saved is working correctly.
Check if the file {0} has been opened by another program. If it has, close the file {0}.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
{3}: Process ID
Explanation
The processing to stop the process did not complete within the process monitoring time.
System Action
The application process is stopped by force.
User Action
Take one of the following actions:
Check the log file, and investigate the cause of the long time required to stop the Java application process.
Check the thread dump output to the Java VM log (console.log) of PL/extJava, and investigate if there is a problem in the Java application.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
{3}: Process ID
Note
When Process ID {3} is "unknown", the process ID cannot be obtained because of one of the following causes:
The port used for debugging of the server instance (Java VM) is duplicated with the port of another server instance (Java VM) or application.
The process was forcibly stopped by the user or another application.
Explanation
The processing to start the process did not complete within the process monitoring time.
System Action
The Java application process is stopped by force.
User Action
Take one of the following actions, and then reexecute processing:
Check the thread dump output to the Java VM log (console.log) of PL/extJava, and investigate if there is a problem in the Java application.
Variable Information
{0}: Server instance (Java VM) name
{1}: Process ID
Explanation
The instance process has terminated abnormally.
System Action
Processing is interrupted.
User Action
Take one of the following actions:
If a message has been output to the event log (Windows(R)) or the system log (Linux) before this message, take the action indicated by that message and investigate the cause of abnormal termination of the process.
If a message has not been output to the event log (Windows(R)) or the system log (Linux) before this message, check the log file and investigate if there is a problem in the Java application.
If the instance has terminated abnormally, check the information output to the server log and Java VM log of PL/extJava, and investigate if there is any problem in the Java application.
Check the thread dump output to the Java VM log of PL/extJava, and investigate if there is a problem in the Java application.
Variable Information
{0}: Server instance (Java VM) name
{1}: Process ID
{2}: Memory type code
Explanation
There is insufficient Java VM heap area, therefore the process stopped.
System Action
The process for which there is insufficient Java VM heap area is stopped.
User Action
If this message is output frequently, refer to the following table and change the heap area specified in the Java VM option according to the memory type code {2} that is output. Refer to " Java Function Errors" in the Operation Guide for information on tuning.
Memory type code {2} | Action |
|---|---|
0 (C heap area) | Reestimate the memory required to run thePL/extJava, 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. If the Java heap area is excessively large, reduce the Java VM heap area size and Perm area size. Refer to " Java Function Errors" in the Operation Guide for details. |
1 (Java VM heap area size) | Extend the Java VM heap area size, and restart the instance. Check "heap_size" in the Java VM log of PL/extJava for the Java heap area when an OutOfMemoryError occurs. Refer to Java Function Errors" in the Operation Guide for details. Note Even if "heap_size" in the Java VM log provides sufficient space for "max_heap_size", the heap area may be insufficient if the generated object is extremely large, or if there is no contiguous heap area. Extend the heap area in this case as well. |
2 (Java VM Perm area size) | Extend the Java VM Perm area size, and restart the instance. Check "perm_size" in the Java VM log of PL/extJava for the Java permanent area when an OutOfMemoryError occurs. Refer to " Java Function Errors" in the Operation Guide for details. |
-1 (Failed to obtain the JavaVM information) | Check the setting value for "heap_type" in the Java VM log of PL/extJava to determine the memory type code, and take action for the C heap area, Java VM heap area size and Perm area size described above. Also, check the information output to the Java VM log of the instance for details of the insufficient Java VM heap area, and tune accordingly. |
Example
Java VM log output example
:
--------------------------------------------------------------------------------
OutOfMemory Log
--------------------------------------------------------------------------------
pid=4696
heap_type=1
heap_size=136800
max_heap_size=6291456
perm_size=2052320
max_perm_size=67108864
requested_size=40000016
--------------------------------------------------------------------------------
VM is terminated by occurred OutOfMemoryError on Java heap.
"main" prio=6 tid=0x00307000 nid=0x12a8 [0x0092f000]
java.lang.Thread.State: RUNNABLE
at test.<init>(test.java:10)
at test.main(test.java:5)Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
{3}: Process ID
Explanation
The Java application processing time has exceeded the monitoring time.
System Action
Application processing is continued.
User Action
If a message has been output to the event log (Windows(R)) or the system log (Linux) immediately before this message, take the action indicated by that message and investigate the cause of time-consuming Java application processing.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
{3}: Process ID
Explanation
The Java application processing time exceeded the monitoring time, therefore the Java application terminated abnormally.
System Action
The application is stopped.
User Action
If a message has been output to the event log (Windows(R)) or the system log (Linux) immediately before this message, take the action indicated by that message and investigate the cause of time-consuming Java application processing.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Process ID
Explanation
This is the notification, which indicates that the active state monitoring time was exceeded.
System Action
Processing is continued.
User Action
If a message has been output to the event log (Windows(R)) or the system log (Linux) immediately before this message, take the action indicated by that message and investigate the cause of response deterioration.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Process ID
Explanation
The notification of active state monitoring time was exceeded, therefore the server instance (Java VM) was stopped by force.
System Action
The server instance (Java VM) is stopped.
User Action
If a message has been output to the event log (Windows(R)) or the system log (Linux) immediately before this message, take the action indicated by that message and investigate the cause of response deterioration.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
{3}: Detail information
Explanation
An error occurred during restart processing after the process stopped.
System Action
The restart processing for the process is canceled.
User Action
Check Detail information {3} that is output, and remove the cause of the failure.
If this error message continues to occur, make a note of the error information in this message and contact Fujitsu technical support.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
Explanation
The process monitoring has failed.
System Action
The process monitoring is continued after the process monitoring for the server instance (Java VM) {1} is skipped.
User Action
If another message has been output immediately before this message, take the action indicated by that message.
If a message has not been output immediately before this message, or this message is still output despite taking the above action, contact Fujitsu technical support.
Variable Information
{0}: PCMI directory path
{1}: Server instance (Java VM) name
{2}: Internal information
{3}: Detail information
Explanation
An error occurred during the processing to stop the process.
System Action
Processing is continued.
User Action
Not required.
Variable Information
{0}: Path
Explanation
Failed to delete the directory {0}.
Possible causes are as follows:
Write privileges have not been configured for the directory or the parent directory.
The disk has become corrupted, therefore access to the file or directory has failed.
Due to a conflict with other processing, access to the disk is temporarily unavailable.
System Action
Processing is interrupted.
User Action
Check if write privileges have been configured for the directory or the parent directory.
Check if the disk has become corrupted.
If access to the disk is temporarily unavailable, wait for a while and then reexecute processing.
Variable Information
{0}: Current directory path
{1}: Current directory backup destination path
Explanation
Failed to rotate the current directory {0}.
Possible causes are as follows:
Write privileges have not been configured for the directory or the parent directory.
The disk has become corrupted, therefore access to the file or directory has failed.
Due to a conflict with other processing, access to the disk is temporarily unavailable.
System Action
Processing is interrupted.
User Action
Check if write privileges have been configured for the directory or the parent directory.
Check if the disk has become corrupted.
If access to the disk is temporarily unavailable, wait for a while and then reexecute processing.
Variable Information
{0}: Path
Explanation
Failed to create the directory {0}.
Possible causes are as follows:
Write privileges have not been configured for the directory or the parent directory.
The disk has become corrupted, therefore access to the file or directory has failed.
Due to a conflict with other processing, access to the disk is temporarily unavailable.
System Action
Processing is interrupted.
User Action
Check if write privileges have been configured for the directory or the parent directory.
Check if the disk has become corrupted.
If access to the disk is temporarily unavailable, wait for a while and then reexecute processing.
Variable Information
{0}: Log file path
Explanation
Rotation of the log file {0} was successful.
Variable Information
{0}: Log file path
{1}: Reason
Explanation
Rotation of the log file {0} failed for the reason in {1}.
System Action
The rotation processing is canceled, and the server instance processing is continued.
User Action
If there is insufficient free disk space, secure more.
If access privileges have not been configured correctly for the log file to be rotated, configure these privileges.
If an I/O error occurred, check if the disk device where the log file is saved is running normally.
Check if a file with the same name as the log file name after rotation exists. If a file with the same name exists, delete or back up the file.
If another program has opened the log file, close the log file.
Check if an old generation log file has been locked.
Variable Information
{0}: Log file path
{1}: Reason
Explanation
Initialization of the log file {0} failed for the reason in {1}.
System Action
Log file initialization is interrupted, and server instance (Java VM) processing is continued.
User Action
If there is insufficient free disk space, secure more.
If access privileges have not been configured correctly for the log file, configure these privileges.
If an I/O error occurred, check if the disk device where the log file is saved is running normally.
If another program has opened the log file, close the log file.
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.
Variable Information
{0}: Log file path
Explanation
A pending message was output to the log file {0}.
Explanation
An error has occurred in the log collection thread. The log collection feature will be stopped.
System Action
The server instance (Java VM) processing is continued.
User Action
To continue Java VM log collection for PL/extJava, restart the instance.
Variable Information
{0}: Log file path
{1}: Reason
Explanation
Output to the log file {0} failed for the reason in {1}.
System Action
The server instance (Java VM) processing is continued.
User Action
If there is insufficient free disk space, secure more.
If an I/O error occurred, check if the disk device where the log file is saved is running normally.
Explanation
Failed to initialize the trace log file.
System Action
The processing to start the PCMI service is canceled.
User Action
Restart the instance.