WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS


PROC

PROC0001E: User: [{0}] does not appear to be valid on this system. Process could not be created.
Explanation An invalid username was passed into the process creation parameters. The user does not appear to exist on the system.
Action A valid user name needs to be entered into the process creation parameters.
PROC0002E: Group: [{0}] does not appear to be valid on this system. Process could not be created.
Explanation An invalid group name was passed into the process creation parameters. The group does not appear to exist on the system.
Action A valid group name needs to be entered into the process creation parameters.
PROC0003E: Working Directory: [{0}] does not appear to be valid, or accessible by the process. Process could not be created.
Explanation 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.
Action A valid working directory needs to be entered into the process creation parameters.
PROC0004E: Executable: [{0}] does not appear to be a valid executable. Process could not be created.
Explanation An invalid executable was passed into the process creation parameters. The executable either does not exist or is not executable by the current user.
Action A valid executable needs to be entered into the creation parameters. Check the executable and its execution permissions
PROC0005E: Priority: [{0}] does not appear to be a valid value for this system or could not be set. Process could not be created.
Explanation An invalid priority was passed into the process creation parameters. The operating system would not accept it.
Action A valid process priority needs to be entered into the creation parameters.
PROC0006E: Process Group: [{0}] is not valid. Process could not be created.
Explanation An invalid process group was passed into the process creation parameters. The operating system would not accept it.
Action A valid process group needs to be entered into the creation parameters.
PROC0007E: Some files required by the process or the process definition were inaccessible. Please check the standard in, out, and error file redirects and directories. Process could not be created.
Explanation 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.
Action 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.
PROC0008E: The operating system reported too many file handles are already open. Process could not be created.
Explanation The operating system refused to create a new process due to too many file handles already being open.
Action Increase the maximum number of allowable file handles, or reduce the number of active processes on the system.
PROC0009E: The operating system reported not enough free memory to create the process.
Explanation The operating system refused to create a new process due to lack of memory to contain the new process.
Action Reduce the memory usage on the system.
PROC0010E: Process: [{0}] is not on the system. It could not be bound to.
Explanation A non-existent PID was passed into the process code to bind to for monitoring.
Action A valid PID needs to be passed to the binding call.
PROC0011E: Process termination failed. The current effective UID attempting to terminate the process [{0}] does not have authority to terminate it.
Explanation A failure in termination has occurred.
Action Manually kill it through the operating system mechanisms under a user with authority to terminate the process.
PROC0012E: The parameters passed in to terminate appear to be invalid or null.
Explanation The parameters used to terminate a process appear invalid or null, therefore termination cannot be done.
Action No user action.
PROC0013E: Process termination failed. The error returned from native was: {0}.
Explanation A failure in termination has occurred.
Action Manually kill it through the operating system mechanisms.
PROC0014E: Process termination failed. The process identified by [{0}] did not terminate in a timely manner. It still appears to be active on the system.
Explanation A failure in termination has occurred.
Action Manually kill it through the operating system mechanisms.
PROC0015E: The process creation failed. Some files that are required by the process or the process definition are inaccessible, such as standard in, out, and error redirects. Verify that user [{0}] has read and write access to the following items: Working directory: [{1}]. Standard input: [{2}]. Standard output: [{3}]. Standard error: [{4}]. Empty [] indicates the value is not set and the operating system defaults are used.
Explanation 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.
Action 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.
PROC0016E: The process creation failed. Some files that are required by the process or the process definition are inaccessible, such as standard in, out, and error redirects. Verify that the current user has read and write access to the following items: Working directory: [{1}]. Standard input: [{2}]. Standard output: [{3}]. Standard error: [{4}]. Empty [] indicates that the value is not set and the operating system defaults are used.
Explanation 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.
Action 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.
PROC0017E: The process bind failed. The PID [{0}] is invalid. It contains non-numeric charcaters.
Explanation The value passed to the process bind call was not a valid PID, it contained non-numeric characters.
Action No action.
PROC0018E: The process bind failed. The PID [{0}] could not be bound to. The operating system reported the binding process does not have sufficient authority.
Explanation The process represented by the PID could not be opened for monitoring. The current process does not have sufficient authority to open it.
Action No action.
PROC0019E: Java thread dump has failed. Failure reason was the virtual machine was unable to load Java dump class: [{0}]. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class could not be loaded.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0020E: Java thread dump has failed. Failure reason was the virtual machine was unable to initialize the Java dump class: [{0}]. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class could not be initialized.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0021E: Java thread dump has failed. Failure reason was the virtual machine was unable to link the Java dump class: [{0}] into the virtual machine. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation 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.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0022E: Java thread dump has failed. Failure reason was the virtual machine was unable to call the method [{3}] on the Java dump class: [{0}]. The error was an IllegalAccessException. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation 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.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0023E: Java thread dump has failed. Failure reason was the virtual machine was unable to call the method [{3}] on the Java dump class: [{0}]. The error was a NoSuchMethodException. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation 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.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0024E: Java thread dump has failed. Failure reason was the virtual machine was unable to call the method [{3}] on the Java dump class: [{0}]. The error was a NullPointerException. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation 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.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0025E: Java thread dump has failed. Failure reason was the virtual machine was unable to call the method [{3}] on the Java dump class: [{0}]. The error was a SecurityException. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation 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.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0026E: Java thread dump has failed. Failure reason was the virtual machine was unable to initialize the Java dump class method: [{0}]. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation The call to generate a Java thread dump (a javacore) failed. This happened because the internal diagnostic class dump method could not be initialized.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0027E: Java thread dump has failed. Failure reason was the virtual machine was unable to call the method [{3}] on the Java dump class: [{0}]. The error was an IllegalAccessException. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation 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.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0028E: Java thread dump has failed. Failure reason was the virtual machine was unable to call the method [{3}] on the Java dump class: [{0}]. The error was an IllegalArgumentException. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation 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.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0029E: Java thread dump has failed. Failure reason was the virtual machine was unable to call the method [{3}] on the Java dump class: [{0}]. The error was an InvokationTargetException. Java Virtual Machine version is: [{1}]. Java Virtual Machine Vendor is: [{2}].
Explanation 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.
Action Contact IBM support and report the Java Virtual Machine Version and Vendor to see if this operation is supported on that virtual machine.
PROC0030E: Java thread dump has failed. Method for generating java thread dumps for Java Virtual Machine version: [{0}] from vendor: [{1}] is unknown.
Explanation 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.
Action 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.
PROC0031E: The process creation failed. The process creation for program [{0}] with priority [{1}] timed out. This can occur if the system activity is too high for a process to be created within a specific time limit of two minutes.
Explanation 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.
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, CPU usage, and memory size that processes are allowed.
Reference topic    

Terms of Use | Feedback

Last updated: Jul 22, 2008 7:04:22 AM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.process.processmessages.html

© Copyright IBM Corporation 2006, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)