Problem | An attempt to open the specified service log file failed. The exception indicates the root cause of the failure. |
User response | Examine the exception to determine the root cause. Ensure that the specified file name is a valid file name. Ensure that the Application Server run time is allowed write access to the directory for the log file. If this does not solve the problem, contact IBM. |
Problem | An attempt to write a message to the service log failed. The indicated exception was encountered. |
User response | Examine the exception to determine the root cause of the failure. Ensure that the service log file exists. Ensure that the file system is not full. Ensure that the Application Server run time is allowed write access to the directory for the log file. If this does not solve the problem, contact IBM. |
Problem | An attempt to change the size of the service log failed. The indicated exception was encountered. |
User response | Examine the exception to determine the root cause of the failure. Ensure that the service log file exists. Ensure that the file system is not full. Ensure that the Application Server run time is allowed write access to the directory for the log file. If this does not solve the problem, contact IBM. |
Problem | The configuration option to disable logging messages to the service log has been selected. |
User response | Enable logging to the service log by setting the configuration option to the enabled state. |
Problem | The configuration option to send trace to a standalone file was selected. An attempt to open the indicated file failed with the indicated exception. Trace will be routed to an alternate facility. |
User response | Examine the exception to determine the root cause of the failure. Ensure that the file name is correct and is a valid name. Ensure that the Application Server run time is allowed write access to the directory for the specified file. Ensure that the file system is not full. If this does not solve the problem, contact IBM. |
Problem | An error has been encountered while attempting to route trace to a user-specified file. Trace output will be routed to System.out instead. |
User response | Search the log for other error messages detailing the failure encountered while opening the user-specified file. Correct the error and retry the operation. |
Problem | The service log is maintained in a binary format. When transferred from one machine to another, it must be transferred in binary format. |
User response | Transfer the log in binary format. In some cases it is possible to undo the damage by transferring the log back to the original machine using the original transfer format, then retransferring the log back to the target machine in binary format. |
Problem | Corruption has been found in the service log. The indicated number of messages were not readable. |
User response | Corruption usually occurs when the service log is transferred from one machine to another incorrectly. Any such transfer must be made in binary mode. |
Problem | The name supplied must be a fully-qualified file name. The directory must exist, or ras must be able to created it. Ras must be granted write access to that directory. |
User response | Supply a file name that meets the above parameters in the configuration data for the indicated stream. Restart the server in order for this change to take effect. |
Problem | See the message in the base exception. This should indicate the root cause of the failure. |
User response | Determine the root cause of the base exception and correct it. If an IOException was encountered, ensure the directory exists, Ras has write access to the directory and that the file system is not full. |
Problem | An exception message was logged. |
User response | Determine the cause of the exception and take appropriate action. Other messages related to the exception may have also been logged. |
Problem | The indicated log file has been configured to use a time based rollover algorithm. An attempt to schedule a rollover event has failed. The log will use a size based rollover algorithm. |
User response | Determine from the indicated exception whether the event was due to an internal WebSphere error or an unexpected system state. If the event is due to a WebSphere internal program error, contact IBM support and provide the logged information. |
Problem | The indicated log file has been configured to use a rollover algorithm. The rollover threshold has been reached. An exception occurred while attempting to roll the log file over. |
User response | Determine from the indicated exception whether the event was due to an internal WebSphere error or an unexpected system state. If the event is due to a WebSphere internal program error, contact IBM support and provide the logged information. |
Problem | The trace service has been started. The startup trace state, determined from configuration data, is displayed here. |
User response | If a different trace startup state is desired, change the configuration data appropriately and restart the process. |
Problem | A request to change the current trace state has been received and processed. |
User response | If the new trace state is not the desired trace state, change it to the desired state. |
Problem | An error was detected while attempting to route trace to a file. Trace has been routed to the in-memory ring buffer instead. |
User response | Search the log for a message detailing the error encountered when routing trace to the file. That message should contain an exception indicating the root cause of the failure. Fix the root cause of the failure and retry the operation. |
Problem | Syntax Errors found in Trace String. |
User response | Check the parameter startupTraceSpecification in server.xml for Syntax Errors and make it compliant with trace string grammar. |
Problem | The level name specified for the logging agent handler must be one of the following: DETAIL, CONFIG, INFO, AUDIT, WARNING, SEVERE, FATAL |
User response | Modify the server configuration to use one of the allowable filter levels. |
Problem | None |
User response | None |
Problem | None |
User response | None |
Problem | The log stream record size is too small to accomodate the log entry being logged. |
User response | If problem occurs frequently, increase the size of records in the log stream. |
Problem | The source file specified may not exist, may be a directory rather than a regular file, or may not be accessible. |
User response | Check parameters to make sure that the specified source file exists and is a regular file. Check also to make sure the user executing the convertLog command has sufficient permissions to read the file. |
Problem | The destination file may not be writable because the file name specified is a directory name, or the file name specified is invalid. |
User response | Check parameters to make sure that the specified destination is a valid file name on a file system that the user has sufficient permissions to write to. |
Problem | The source file was too large to process with this tool. |
User response | If the source file is large, try breaking it into parts before processing. |
Problem | The trace is configured to go into circular memory buffer. The size of the buffer is printed as well. The buffer holds references to message objects, the amount of memory these objects use can not be determined. |
User response | Do not use circular memory buffer when enabling full tracing, or configure the buffer to hold less objects, to prevent out of memory condition. Message objects used when tracing is enabled will use more memory than non tracing message objects. |
Problem | WebSphere could not 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. |
User response | Determine the cause of the rename failure and resolve it - this may involve shutting down other processes that are accessing the same log file. |
Problem | Trace String is Empty. |
User response | Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. |
Problem | Trace string with extra colon passed. |
User response | Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. |
Problem | Trace string with component and no type=state value pair(s). |
User response | Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. |
Problem | Trace string without a component name. |
User response | Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. |
Problem | Trace String found with an extra comma. |
User response | Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. An extra comma may need to be removed. |
Problem | Trace string with garbage or incomplete type=state pair. |
User response | Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. |
Problem | Trace string without a state value. |
User response | Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. |
Problem | Trace string without a type value. |
User response | Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. |
Problem | Trace string with a bad type value. |
User response | Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. |
Problem | Trace string with a bad state value. |
User response | =Modify server.xml for this server and make the parameter startupTraceSpecification compliant with trace string grammar. |
Problem | The extension name specified is the same as an internally used extension name and cannot be used. |
User response | Use an extension with a different name. |
Problem | The message IDs have been deprecated, the new message IDs should be used. |
User response | Add system property com.ibm.websphere.logging.messageId.version=6 for your server process to enable new message IDs |
Problem | The TCP/IP subsystem returned a null value when requesting the localhost's hostname. |
User response | Resolved this issue in the TCP/IP configuration. |