Explanation | A request to change the current trace state was received and processed. |
Action | If the new trace state is not the desired trace state, change it to the desired state. |
Explanation | Failed to rename the file indicated. The most likely cause is that another process or thread is accessing the log file. WebSphere will try to complete the rollover operation by copying the contents of the log file - this process is slower, and all threads making attempting to log will be halted during this process. |
Action | Determine the cause of the rename failure and resolve it - this may involve shutting down other processes that are accessing the same log file. |
Explanation | The class file transformer responsible for adding method-level trace could not be installed, because a suitable java.lang.instrument.Instrumentation reference could not be obtained. |
Action | Start the server with the appropriate -javaagent command line argument. |
Explanation | An error occurred while injecting detailed method trace into the specified class. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The trace level configured for the specified group, class or package name was not recognized, the trace setting for that name will be skipped. |
Action | Examine the trace configuration and correct the level to a recognized value. Valid trace levels are listed in the documentation and include 'all', 'info' and 'debug'. |
Explanation | The trace setting value configured for the specified group, class or package name was not recognized, the trace setting for that name will be skipped. |
Action | No action is required unless the intended trace setting value is 'disabled'. In this case, examine the trace configuration and correct the setting to 'disabled'. |
Explanation | An attempt to open the specified resource failed. The exception indicates the root cause of the failure. |
Action | Examine the exception to determine the root cause. Ensure that the specified file name is a valid file name. Ensure that the Application Server runtime is allowed write access to the directory for the resource, and that the disk is not full. If this does not solve the problem, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An application server component could not perform an operation on a required resource. |
Action | Ensure that the specified file name is a valid file name. Ensure that the Application Server runtime is allowed write access to the directory for the resource, and that the disk is not full. If this does not solve the problem, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An application server component could not perform an operation on a required resource. |
Action | Ensure that the specified file name is a valid file name. Ensure that the Application Server runtime is allowed write access to the directory for the resource, and that the disk is not full. If this does not solve the problem, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An attempt to delete the specified resource failed. The exception indicates the root cause of the failure. |
Action | Examine the exception to determine the root cause. Ensure that the Application Server runtime is allowed write access to the directory for the resource. If this does not solve the problem, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | Loggers are registered in the server when the code that creates them is first used. The system has detected that certain trace specifications refer to loggers that have not been registered in the server. The configured trace specifications may be valid for loggers that are not yet registered, or they could have been typed incorrectly. This check is performed each time the trace specification is updated on a running server. |
Action | Ensure that the trace specification has been configured correctly. If there are no mistakes in the trace specification string, no action is required. |