EXCEPTION_RESERVED_EXTENSION=TRAS0110E: The extension name ''{0}'' is reserved The extension name that is specified is the same as an internally used extension name and cannot be used. Use an extension with a different name. MSG_EXCEPTION_LOGGED=TRAS0014I: The following exception was logged {0}. An exception message was logged. Determine the cause of the exception and take appropriate action. Other messages related to the exception might have also been logged. MSG_TRACE_STATE_CHANGED=TRAS0018I: The trace state has changed. The new trace state is {0}. A request to change the current trace state was received and processed. If the new trace state is not the desired trace state, change it to the desired state. EXCEPTION_MISSING_TYPE=TRAS0107E: Missing type value at ''{0}'' A trace string does not have a type value. Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. MSG_RING_BUFFER_STATUS=TRAS0028I: The trace output is stored in the circular memory buffer, holding {0} message objects. 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 and the amount of memory these message objects use cannot be determined. 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 that are used when tracing is enabled will use more memory than non-tracing message objects. RAS_LOG_MBEAN_SHADOW_NOOP=TRAS0113I: This MBean Operation should not be used when High Performance Logging is enabled. Function will be forwarded to proper MBean High performance logging has its own MBean. Use of the MBeans for legacy logging should not be used Updating user scripts or JMX code is recommended EXCEPTION_MISSING_VALUE_PAIR=TRAS0104E: Missing type=state value pair at ''{0}'' A trace string has an extra comma. Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. An extra comma may need to be removed. MSG_TRACE_TO_RING_BUFFER=TRAS0019I: Defaulting trace output to the circular memory buffer. An error was detected while attempting to route trace to a file. Trace was routed to the in-memory ring buffer instead. Search the log file 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. MSG_ROLLOVER_RENAME_FAILED=TRAS0031W: Unable to rename file {0} to {1} during log file rollover. Attempting to copy file contents. 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. Determine the cause of the rename failure and resolve it - this may involve shutting down other processes that are accessing the same log file. MSG_HPEL_OWNERFILE_IS_DIRECTORY=TRAS0292W: The HPEL repository ownership indicator file {0} is a directory but should be a file. The application server uses the ownership indicator file to track which server is allowed to write to the HPEL repository; the configured HPEL repository location precedes the .owner suffix in the ownership indicator file name. There is a directory at the location where the ownership indicator file should be. If a valid directory is already present with the same name as the ownership indicator file, reconfigure the path for the HPEL repository destination. Otherwise, remove the directory with that same name if it is safe to do so. DEPRECATED_MESSAGE_IDS=TRAS0111I: The message IDs that are in use are deprecated The message IDs are deprecated. Use the new message IDs. Add the com.ibm.websphere.logging.messageId.version=6 system property for your server process to enable new message IDs MSG_TRACE_STATE_OPTIMIZED=TRAS0033W: The new trace specification supplied for node {0}, server {1} has been changed from {2} to {3} to eliminate redundancy. A request to change the current trace state was received and processed. If the new trace state is not the desired trace state, change it to the desired state. MSG_OPEN_TRACE_FILE_FAILED=TRAS0008E: Failed to open trace log file {0} {1} The configuration option to send trace to a stand-alone file was selected. An attempt to open the indicated file failed with the indicated exception. Trace will be routed to an alternate facility. 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, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. TRAS0250W=TRAS0250W: The {0} on logstream {1} returned a warning - return code {2}, reason code {3} A warning message was returned from this run Consider reRunning MSG_DUMPED_TO_DEFAULT_LOCATION=TRAS0029I: Could not dump ring buffer to specified directory, {0}. Dumped to default file, {1}. Failed to write the in-memory trace buffer to the specified file. This is mostly likely because the file specified is not valid or does not allow write-access. The trace contents were successfully written to the default dump file. To prevent this message in the future, specify a valid filename in a directory that allows write access. TRAS0270E=TRAS0270E: Failed to connect to logstream {1} - return code {2}, reason code {3} Could not connect to the logstream Have a system logger administrator review the configuration and verify the health of the component and the logstream MSG_STREAM_REPLACEMENT_FAILED=TRAS0013E: An attempt to redirect the {0} stream failed. The following exception was encountered. {1} See the message in the base exception. This should indicate the root cause of the failure. 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. TRAS0230I=TRAS0230I: The message time stamp exceeded end time. Issue with a message read that had a timeStamp outside of the specified range. Consider reRunning TRAS0210I=TRAS0210I: The JNI call could not go thru. Could not access error log file via JNI ReInvoke the reader MSG_OWNERFILE_DIFFERENT_SERVER=TRAS0291W: The log/trace file {0} is already configured for use by server {1}, but server {2} is also configured to write log/trace content to that file. Only one server is allowed to write log/trace content to any one location. Reconfigure the log/trace settings of one or both of the named servers so that they do not use the same location. EXCEPTION_INVALID_STATE=TRAS0109E: Invalid state value - ''{0}'' at ''{1}'' A trace string has a bad state value. =Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. MSG_OWNERFILE_IS_DIRECTORY=TRAS0290W: The log/trace ownership indicator file {0} is a directory but should be a file. The application server uses the ownership indicator file to track which server is allowed to write to the log/trace file; the configured log/trace file name precedes the .owner suffix in the ownership indicator file name. There is a directory at the location where the ownership indicator file should be. If a valid directory is already present with the same name as the ownership indicator file, reconfigure the file name or path for the log/trace destination. Otherwise, remove the directory with that same name if it is safe to do so. MSG_INVALID_FILENAME=TRAS0012W: {0} was specified in the configuration information as the name of the file to use for the {1} stream. This is not a legal name. {2} will be used instead The name that is supplied must be a fully-qualified file name. The directory must exist or RAS must be able to create it. RAS must be granted write access to that directory. 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. MSG_INVALID_LOGGING_AGENT_HANDLER_LEVEL=TRAS0021W: An invalid level name {0} was used as the filter level for the logging agent handler configuration. The level name specified for the logging agent handler must be one of the following: DETAIL, CONFIG, INFO, AUDIT, WARNING, SEVERE, FATAL Modify the server configuration to use one of the allowable filter levels. EXCEPTION_NO_VALUE_PAIRS=TRAS0102E: No type=state value pair(s) found at ''{0}'' A trace string was found with component and no type=state value pair(s). Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. UNKNOWN_TRACE_SPEC=TRAS0040I: The configured trace state included the following specifications that do not match any loggers currently registered in the server: {0} Loggers are registered in the server when 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. Ensure that the trace specifications has been configured correctly. If there are no mistakes in the trace specification string, no action is required. EXCEPTION_NULL_HOSTNAME=TRAS0112E: Null value returned on call to InetAddress.getLocalHost().getHostName(). The TCP/IP subsystem returned a null value when requesting the host name of the local host. Resolve this issue in the TCP/IP configuration. MSG_SHARED_LOG_DISABLED=TRAS0007I: Logging to the service log is disabled The configuration option to disable logging messages to the service log was selected. Enable logging to the service log file by setting the configuration option to the enabled state. MSG_HPEL_OWNERFILE_DIFFERENT_SERVER=TRAS0293W: The HPEL repository {0} is already configured for use by server {1}, but server {2} is also configured to write HPEL repository content to that location. Only one server is allowed to write HPEL repository content to any one location. Reconfigure the HPEL repository settings of one or both of the named servers so that they do not use the same location. MSG_INITIAL_TRACE_STATE=TRAS0017I: The startup trace state is {0}. The trace service is started. The startup trace state that is determined from configuration data is displayed here. If a different trace startup state is desired, change the configuration data appropriately and restart the process. EXCEPTION_INVALID_TYPE=TRAS0108E: Invalid type value - ''{0}'' at ''{1}'' A trace string has a bad type value. Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. MSG_LOGGING_AGENT_HANDLER_DISABLED=TRAS0022I: The logging agent handler is disabled. This mesage is for informational purposes only. No user action is required. EXCEPTION_MISSING_STATE=TRAS0106E: Missing state value at ''{0}'' A trace string does not have a state value. Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. CONVERTLOG_INPUTFILENOTFOUND=TRAS0025E: Unable to load source file {0}. The source file specified might not exist, might be a directory rather than a regular file, or might not be accessible. 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. EXCEPTION_NO_COMPONENT_NAME=TRAS0103E: No component name found at ''{0}'' A trace string does not have a component name. Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. MSG_ROLLOVER_FAILED_EXCEPTION=TRAS0016E: An unexpected exception while trying to archive log file {0} Exception is {1}. The indicated log file was configured to use a rollover algorithm. The rollover threshold was reached. An exception occurred while attempting to roll the log file over. Determine from the indicated exception whether the event was due to an internal error or an unexpected system state. If the event was due to an internal program error, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. RAS_LOG_MBEAN_PROXY_JmxInfo=TRAS0116W: JMX Error Info: ObjectName: {0} Other1: {1} Other2: {2} Other3: {3} This exception is unexpected. The cause is not immediately known. 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/ . MSG_TRACE_SYNTAXERR_WARNING=TRAS0020W: Trace might not be enabled properly due to syntax errors found in the trace string, {0}. Syntax errors were found in the trace string. Check the parameter startupTraceSpecification parameter in the server.xml file for syntax errors and make it compliant with trace string grammar. MSG_SCHEDULE_TIME_ROLLOVER_FAILED=TRAS0015E: Unable to schedule time-based rollover for log file {0}. Size-based rollover will be used instead {1}. The indicated log file was configured to use a time-based rollover algorithm. An attempt to schedule a rollover event has failed. The log file will use a size-based rollover algorithm. Determine from the indicated exception whether the event was due to an internal error or an unexpected system state. If the event was due to an internal program error, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. TRAS0280E=TRAS0280E: Failed to open logstream {1} with return code {2}, reason code {3} Could not open the LogStream Have a System Logger Administer review the configuration and verify the health of the subSystem and the logger CONVERTLOG_OUTOFMEMORY=TRAS0027E: Insufficient memory to process source file {0}. The source file was too large to process with this tool. If the source file is large, try breaking it into parts before processing. TRAS0260I=TRAS0260I: The {0} on logstream {1} returned more than 500 messages in the buffer. Excess messages were discarded. Only 500 messages can be returned in the buffer and this would have retrieved > 500 messages Consider rerunning with more restrictive filtering MSG_UNABLE_TO_DUMP_RING_BUFFER=TRAS0030W: Failed to dump ring buffer to specified file, {0}, or the default dump file location, {1}. Exceptions: {2} {3} Failed to write the in-memory trace buffer to the file system. This is most likely due to a file permission issue - the directories containing the files either do not exist or do not allow write access. Ensure that the application server process has write permission to the specified directory. MSG_LOGGING_AGENT_HANDLER_ENABLED=TRAS0023I: The logging agent handler is enabled. Filter level is set to {0}. This mesage is for informational purposes only. No user action is required. EXCEPTION_INVALID_VALUE_PAIR=TRAS0105E: Invalid type=state value pair - ''{0}'' at ''{1}'' A trace string has garbage or incomplete type=state pair. Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. MSG_SHARED_LOG_WRITE_FAILED=TRAS0005E: Unable to write to the service log. The following exception was encountered {0} An attempt to write a message to the service log failed. 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, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. MSG_TOO_LARGE_FOR_LOGSTREAM=TRAS0024I: Log entry is of size {0} bytes which is too large to be added to log stream which is configured for {1} byte records. Log entry will not be logged to the log stream. The log stream record size is too small to accomodate the log entry that is being logged. If problem occurs frequently, increase the size of records in the log stream. TRAS0240I=TRAS0240I: Logstream {0} does not contain any records beyond start time {1}. The logStream has no records beyond the specified start time Modify the specified start time MSG_CORRUPT_MESSAGE_COUNT=TRAS0011I: {0} messages could not be read from the service log Corruption was found in the service log file. The indicated number of messages were not readable. Corruption usually occurs when the service log file is transferred from one machine to another incorrectly. Any such transfer must be made in binary mode. TRAS0220I=TRAS0220I: The number of dropped messages: {0} Some messages were dropped in processing Consider reRunning EXCEPTION_EMPTY_STRING_SUBTRACESTRING=TRAS0101E: Empty string encountered - remove extra colon Trace string with an extra colon was specified Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. MSG_TRACE_TO_SYSOUT=TRAS0009I: Defaulting trace output to SystemOut.log An error was encountered while attempting to route trace to a user-specified file. Trace output will be routed to the SystemOut.log file instead. Search the log file for other error messages detailing the failure encountered while opening the user-specified file. Correct the error and retry the operation. RAS_LOG_MBEAN_PROXY_ZJmxInvoke=TRAS0115W: Exception resulted from z/OS Servant MBean JMX call This exception is unexpected. The cause is not immediately known. 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/ . RAS_LOG_MBEAN_PROXY_NullParm=TRAS0117W: Method called with a null parameter. This is invalid {0}. This exception is unexpected. The cause is not immediately known. 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/ . CONVERTLOG_OUTPUTFILENOTFOUND=TRAS0026E: Unable to open destination file {0}. The destination file might not be writable because the file name that is specified is a directory name, or the file name that is specified is not valid. 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. EXCEPTION_EMPTY_STRING_TRACESTRING=TRAS0100E: Empty string is not part of trace string grammar The trace string is empty. Modify the server.xml file for this server and make the startupTraceSpecification parameter compliant with trace string grammar. RAS_REMOTE_BadLoggerRegExp=TRAS0150W: Invalid Logger Regular Expression {0}, no Logger Checking Enabled The regular expression passed to filter log records by logger is invalid. Logger filtering disabled Check the regular expression and reSubmit query MSG_SHARED_LOG_CHANGE_SIZE_FAILED=TRAS0006E: Unable to change the size of the service log. The following exception was encountered {0} An attempt to change the size of the service log failed. 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, see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. MSG_SHARED_LOG_CTOR_FAILED=TRAS0004E: Unable to create or open the service log file {0}. The following exception was encountered {1} An attempt to open the specified service log file failed. The exception indicates the root cause of the failure. 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 service log file. 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. MSG_ACTIVITY_LOG_CORRUPTED=TRAS0010I: The size of the service log indicates that some corruption has occurred. This could be due to not transferring the file in binary mode The service log is maintained in a binary format. When transferred from one machine to another, it must be transferred in binary format. Transfer the log file in binary format. In some cases it is possible to undo the damage by transferring the log file back to the original machine using the original transfer format, then retransferring the log file back to the target machine in binary format. RAS_LOG_MBEAN_PROXY_RegFail=TRAS0118W: Diagnostic Provider Registry Propagation failed because {0} This exception is unexpected. The cause is not immediately known. 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/ .