Problem | An invalid username was passed into the process creation parameters. The user does not appear to exist on the system. |
User response | A valid user name needs to be entered into the process creation parameters. |
Problem | An invalid group name was passed into the process creation parameters. The group does not appear to exist on the system. |
User response | A valid group name needs to be entered into the process creation parameters. |
Problem | An invalid working directory was passed into the process creation parameters. The working directory does not appear to exist on the system or the user id running the process does not have access to the directory. |
User response | A valid working directory needs to be entered into the process creation parameters. |
Problem | An invalid executable was passed into the process creation parameters. The executable either does not exist or is not executable by the current user. |
User response | A valid executable needs to be entered into the creation parameters. Check the executable and its execution permissions |
Problem | An invalid priority was passed into the process creation parameters. The operating system would not accept it. |
User response | A valid process priority needs to be entered into the creation parameters. |
Problem | An invalid process group was passed into the process creation parameters. The operating system would not accept it. |
User response | A valid process group needs to be entered into the creation parameters. |
Problem | Some files the process needs for execution were not accessible by the process. This is commonly log files (redirects of standard out and error, or directories they reside in) that are not set readable and writable to the use rid that will be running the process that will access them. |
User response | Check the standard out and error redirection files and their directories to make sure they're readable and writable by the user id that will be running the process. |
Problem | The operating system refused to create a new process due to too many file handles already being open. |
User response | Increase the maximum number of allowable file handles, or reduce the number of active processes on the system. |
Problem | The operating system refused to create a new process due to lack of memory to contain the new process. |
User response | Reduce the memory usage on the system. |
Problem | A non-existent PID was passed into the process code to bind to for monitoring. |
User response | A valid PID needs to be passed to the binding call. |
Problem | A failure in termination has occurred. |
User response | Manually kill it through the operating system mechanisms under a user with authority to terminate the process. |
Problem | The parameters used to terminate a process appear invalid or null, therefore termination cannot be done. |
User response | No user action. |
Problem | A failure in termination has occurred. |
User response | Manually kill it through the operating system mechanisms. |
Problem | A failure in termination has occurred. |
User response | Manually kill it through the operating system mechanisms. |
Problem | Some files that the process needs to run are not accessible. These files are commonly log files that are not readable and writeable to the user ID that runs the process. |
User response | Check the standard out and error redirection files and the parent directories to make sure that these files are readable and writeable by the user ID that runs the process. |
Problem | Some files that the process needs to run are not accessible. These files are commonly log files that are not readable and writeable to the user ID that runs the process. |
User response | Check the standard out and error redirection files and the parent directories to make sure that these files are readable and writeable by the user ID that runs the process. |
Problem | The value passed to the process bind call was not a valid PID, it contained non-numeric characters. |
User response | No action. |
Problem | The process represented by the PID could not be opened for monitoring. The current process does not have sufficient authority to open it. |
User response | No action. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class could not be loaded. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class could not be initialized. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class could not be linked into the virtual machine. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class and method to generate the javacore could not be executed. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class and method to generate the javacore could not be executed. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class and method to generate the javacore could not be executed. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class and method to generate the javacore could not be executed. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class dump method could not be initialized. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class and method to generate the javacore could not be executed. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class and method to generate the javacore could not be executed. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class and method to generate the javacore could not be executed. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine. |
Problem | The call to generate a Java thread dump (a javacore) failed. This failed because it is unknown how to cause the Java Virtual Machine to thread dump for the specified version and vendor. |
User response | Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation can be supported on the referenced Java Virtual Machine. |
Problem | This can occur if the system activity is too high for a process to be created within a specific time limit. The general time limit for the process to initialize is two minutes. If the process cannot be initialized during that time, then a CreateProcessTimeoutException is thrown and the creation is canceled. 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. |
User response | 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, CPU usage, and memory size that processes are allowed. |