Explanation | The process was not created because the specified user name is not defined for this system. |
Action | Specify a user name that is defined for this system. |
Explanation | The process was not created because the specified group name is not defined for this system. |
Action | Specify a group name that is defined for this system. |
Explanation | The process was not created because the specified working directory does not exist on the system or the user ID that is being used to run the process does not have access to the specified directory. |
Action | Specify the name of a working directory that exists on the system, and make sure that the user ID that is being used to run the process has permission to access that directory. |
Explanation | The process has not been created because either the specified file does not exist, or the current user does not have permission to run this file. |
Action | Check the name of the specified file and its permissions. Verify that the current user has permission to run this file. |
Explanation | The process was not created because a priority was specified that is not valid. |
Action | Specify a valid process priority. |
Explanation | The process was not created because the specified process is not valid. |
Action | Specify a valid process group. |
Explanation | The process cannot access some of the files that it requires. These files might be standard out or error redirection files, and the user ID being used to run the process might not have read or write access to the files or the directories in which these log files reside. |
Action | Check the standard out and error redirection log files and their directories. Make sure that the user ID being used to run the process has read and write access to the log files, and the directories in which these log files reside. If the profile containing the server is maintained for use by a non-root user, or the server is configured to run as a non-root user, then ensure the user ID being used to run the process owns the entire profile directory. |
Explanation | The process was not created because the maximum number of file handles that the operating system allows are already open. |
Action | Increase the maximum number of file handles that the operating system allows, or reduce the number of processes that are currently active. |
Explanation | The process was not created because there is not enough memory available on this system to contain the new process. |
Action | Reduce the current memory usage on this system. |
Explanation | The binding request could not be completed because the specified process ID (PID) is not valid for this system. Therefore, the process cannot be monitored. |
Action | Make sure that the PID value being passed to the binding request is a valid PID for this system. |
Explanation | The specified process was not terminated because the user ID that was used to issue the termination request does not have the authority to terminate this process. |
Action | Log onto the system using an ID that has the authority to terminate this process, and manually stop the process. |
Explanation | The process was not terminated because the parameters specified in the termination request are either not valid, or null. |
Action | No action is required. |
Explanation | The specified process was not terminated. See the description of the error code for more information. |
Action | Use the operating system mechanisms to manually stop the process. |
Explanation | The specified process was not terminated. See the description of the error code for more information. |
Action | Use the operating system mechanisms to manually stop the process. |
Explanation | The process was not able to access some of the files that it expected. The files that cannot be accessed are probably log files. These files might be standard out or error redirection files, and the user ID being used to run the process might not have read or write access to the files or the directories in which these log files reside. |
Action | Check the standard out and error redirection files and their directories. Ensure that the user ID being used to run the process has read and write access to the log files, and the directories in which these log files reside. If the profile containing the server is maintained for use by a non-root user, or the server is configured to run as a non-root user, then ensure the user ID being used to run the process owns the entire profile directory. |
Explanation | The process was not able to access some of the files that it expected. The files that cannot be accessed are probably log files. These files might be standard out or error redirection files, and the user ID being used to run the process might not have read or write access to the files or the directories in which these log files reside. |
Action | Check the standard out and error redirection files and their directories. Ensure that the user ID being used to run the process has read and write access to the log files, and the directories in which these log files reside. If the profile containing the server is maintained for use by a non-root user, or the server is configured to run as a non-root user, then ensure the user ID being used to run the process owns the entire profile directory. |
Explanation | The binding request could not be completed because the specified process ID (PID) contained non-numeric characters. A PID must contain all numberic characters. |
Action | No action required. |
Explanation | The process represented by the PID cannot be monitored because the current process does not have the authority needed to complete the binding request. |
Action | No action required. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because the internal diagnostic class could not be loaded. |
Action | Check the documentation for the Java Virtual Machine (JVM) that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because the internal diagnostic class could not be initialized. |
Action | Check the documentation for the Java Virtual Machine (JVM) that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because the internal diagnostic class could not be linked into the Java Virtual Machine (JVM). |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because an IllegalAccessException exception occurred, and the internal diagnostic class and method to generate the Java thread dump could not be executed. |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because a NoSuchMethodException exception occurred, and the internal diagnostic class and method to generate the Java thread dump could not be executed. |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because a NullPointerException exception occurred, and the internal diagnostic class and method to generate the Java thread dump could not be executed. |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because a SecurityException exception occurred, and the internal diagnostic class and method to generate the Java thread dump could not be executed. |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because the internal diagnostic class dump method could not be initialized. |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because an IllegalAccessException exception occurred, and the internal diagnostic class and method to generate the Java thread dump could not be executed. |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because an IllegalArgumentException exception occurred, and the internal diagnostic class and method to generate the Java thread dump could not be executed. |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because an InvokationTargetException exception occurred, and the internal diagnostic class and method to generate the Java thread dump could not be executed. |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | A request to create a Java thread dump, also referred to as a Java core dump, was not processed because it is unknown how to create the Java thread dump on the installed Java Virtual Machine (JVM). |
Action | Check the documentation for the JVM that is running on this system to make sure that the creation of a Java thread dump is supported on that JVM version. |
Explanation | This situation might occur if high system activity prevents the creation of process within within the specified time limit. The general time limit for the process to initialize is two minutes. This is because generally if a process cannot initialize within the time limit then there is not enough system resources to adequately run the new process. When the time limit is exceeded, a CreateProcessTimeoutException is issued and the process creation is canceled. |
Action | Check the CPU, memory, and overall system load characteristics for processes which are monopolizing machine resources. Also check the system limit settings for values that may be affecting the number of processes that can be running at the same time, limits on CPU usage, and memory being allocated to each process. |