TRAS

TRAS0018I: The trace state has been changed. The new trace state is {0}.

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.

TRAS0031W: Unable to rename file {0} to {1} during log file rollover. Attempting to copy file contents.

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.

TRAS0032W: Runtime injection of detailed method trace is not available.

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.

TRAS0033E: Runtime injection of detailed method trace failed for class {0} with exception {1}

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/ .

TRAS0034W: Trace level {0} for specification {1} is not valid. The trace specification will be ignored.

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'.

TRAS0035W: Trace setting value {0} for specification {1} is not recognized. The trace specification will be ignored.

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'.

TRAS0036E: The system could not create file {0} because of the following exception: {1}

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.

TRAS0037E: The system could not create new file {0}

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.

TRAS0038E: The system could not delete file {0}

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.

TRAS0039E: The system could not delete file {0} because of the following exception: {1}

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.

TRAS0040I: The configured trace state included the following specifications that do not match any loggers currently registered in the server: {0} Ignore this message if the trace specifications {0} are valid.

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.

TRAS0041I: The following messages are hidden from the console.log and messages.log files: {0}

Explanation	Messages that are configured to be hidden are not written to the console.log and messages.log files. However, they are written to the trace.log file.
Action	No action is required

TRAS0042I: The message routing group {0} contains the following messages: {1}

Explanation	The set of message IDs configured for the specified message routing group has changed. The set of message IDs currently associated with this message routing group is listed.
Action	No action is required.

TRAS0080W: Operation {0} took {1} ms to complete, which was longer than the expected duration of {2} ms based on past observations.

Explanation	The specified timed operation is running more slowly than expected.
Action	Investigate the reason this timed operation is running slower than expected.

TRAS0081W: Operation {0} took {1} ms to complete, which was unusual when compared to the expected duration of {2} ms based on past observations.

Explanation	The specified timed operation is running more slowly than expected.
Action	Investigate the reason this timed operation is running slower than expected.

TRAS0082I: The following data was used to make this determination: duration={0} ms, previous most recent durations=[{1} ms, {2} ms, {3} ms, {4} ms, {5} ms, {6} ms, {7} ms] moving average={8} ms, standard deviation={9} ms. This data shows that the most recent duration is above the zone delimited by 3 standard deviations from the moving average.

Explanation	The specified timed operation is running more slowly than expected.
Action	No action is required.

TRAS0083I: The following data was used to make this determination: duration={0} ms, previous most recent durations=[{1} ms, {2} ms, {3} ms, {4} ms, {5} ms, {6} ms, {7} ms] moving average={8} ms, standard deviation={9} ms. This data shows that the most recent duration is below the zone delimited by 3 standard deviations from the moving average.

Explanation	The specified timed operation is running more slowly than expected.
Action	No action is required.

TRAS0084I: The following data was used to make this determination: duration={0} ms, previous most recent durations=[{1} ms, {2} ms, {3} ms, {4} ms, {5} ms, {6} ms, {7} ms] moving average={8} ms, standard deviation={9} ms. This data shows that two out of three consecutive durations fall beyond the zone delimited by 2 standard deviations, above the moving average.

Explanation	The specified timed operation is running more slowly than expected.
Action	No action is required.

TRAS0085I: The following data was used to make this determination: duration={0} ms, previous most recent durations=[{1} ms, {2} ms, {3} ms, {4} ms, {5} ms, {6} ms, {7} ms] moving average={8} ms, standard deviation={9} ms. This data shows that two out of three consecutive durations fall beyond the zone delimited by 2 standard deviations, below the moving average.

Explanation	The specified timed operation is running more slowly than expected.
Action	No action is required.

TRAS0086I: The following data was used to make this determination: duration={0} ms, previous most recent durations=[{1} ms, {2} ms, {3} ms, {4} ms, {5} ms, {6} ms, {7} ms] moving average={8} ms, standard deviation={9} ms. This data shows that four out of five consecutive durations fall beyond the zone delimited by 1 standard deviation, above the moving average.

Explanation	The specified timed operation is running more slowly than expected.
Action	No action is required.

TRAS0087I: The following data was used to make this determination: duration={0} ms, previous most recent durations=[{1} ms, {2} ms, {3} ms, {4} ms, {5} ms, {6} ms, {7} ms] moving average={8} ms, standard deviation={9} ms. This data shows that four out of five consecutive durations fall beyond the zone delimited by 1 standard deviation, below the moving average.

Explanation	The specified timed operation is running more slowly than expected.
Action	No action is required.

TRAS0088I: The following data was used to make this determination: duration={0} ms, previous most recent durations=[{1} ms, {2} ms, {3} ms, {4} ms, {5} ms, {6} ms, {7} ms] moving average={8} ms, standard deviation={9} ms. This data shows that eight consecutive durations are above the moving average.

Explanation	The specified timed operation is running more slowly than expected.
Action	No action is required.

TRAS0089I: The following data was used to make this determination: duration={0} ms, previous most recent durations=[{1} ms, {2} ms, {3} ms, {4} ms, {5} ms, {6} ms, {7} ms] moving average={8} ms, standard deviation={9} ms. This data shows that eight consecutive durations are below the moving average.

Explanation	The specified timed operation is running more slowly than expected.
Action	No action is required.

TRAS0090E: Transformation of class {0} failed due to the following error: {1}

Explanation	Byte code injection for timed operations failed for this class, and the class will not be monitored by the timed operations feature.
Action	See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support.

TRAS0093I: The expected duration for {0} is not available yet.

Explanation	The expected duration is based on a moving average of recent durations which are still being collected.
Action	No action is required.

TRAS0094I: The total number of timed operations is {0}, which exceeds the configured maximum number of {1}. You can also find the number of timed operations in the report that is periodically generated to the logs. If you find that the number of timed operations is excessive, you can disable the timed operations feature.

Explanation	The number of timed operations is monitored and useful to know since each timed operation is allocated memory from the heap.
Action	You can change the maximum number of timed operations that triggers this message via the maxNumberTimedOperations attribute in server.xml file.

TRAS0095I: The total number of timed operations has reached the configured maximum of {0}. As new timed operations are created the least recently used timed operations will be removed to maintain the total number of tracked timed operations at this level.

Explanation

The number of timed operations is limited to the configured maximum shown in this message. This ensures that operation timing does not consume more memory than expected. To maximize the benefit of the operation timing, data related to the least recently used operations are deleted automatically when new operations are run. This ensures that the list of timed operations adapts to your system workload over time.

Action

No action required

TRAS0112W: Request {0} has been running on thread {1} for at least {2}ms. The following stack trace shows what this thread is currently running. {3} The following table shows the events that have run during this request. {4}

Explanation	The request has been running for longer than the configured slow request duration. The information in the table shows what events have already run as part of the request. Events that are still running are indicated with a + next to the duration. The default value for slow request duration is 10 seconds, check the server.xml file for the current value.
Action	Use the information in the table to determine what part of the request is slower than expected. If many warnings are provided for different requests at nearly the same time it may indicate that something slowed down the entire server process, such as another process on the same system consuming a large amount of processing resources.

TRAS0113I: Request {0} on thread {1}, which was previously detected as slow, completed after {2} ms.

Explanation	The request has been running for longer than the configured slow request duration. The request completed in the posted time.
Action	No action required.

TRAS0114W: Request {0} has been running on thread {1} for at least {2}ms. The following table shows the events that have run during this request. {3}

Explanation	The request has been running for longer than the configured hung request duration. The information in the table shows what events have already run as part of the request. Java cores will automatically be triggered to collect further information about what may be causing the request to hang. The default value for hung request duration is 10 minutes, check the server.xml file for the current value.
Action	Use the information in the table to determine what part of the request is hanging or in a loop.

TRAS0115W: Request {0} on thread {1} which was previously detected to be hung, has completed after {2}ms.

Explanation	Hung request task will notify the user when any hung request is completed.
Action	No action required.

TRAS3000E: Runtime injection of detailed method trace failed for class {0} with exception {1}.

Explanation	An error occurred while injecting detailed method trace into the specified class.
Action	See the problem determination information on the product support web page: http://www.ibm.com/software/webservers/appserv/was/support.

TRAS3001I: The following messages are hidden from the console.log and messages.log files: {0}

Explanation	Messages that are configured to be hidden are not written to the console.log and messages.log files. They are written to the trace.log file.
Action	No action is required

TRAS3002I: The messages.log output format has now been updated to '{0}'.

Explanation	The output format for messages.log has now been updated.
Action	No action is required.

TRAS3003I: The console output format has now been updated to '{0}'.

Explanation	The output format for console has now been updated.
Action	No action is required.

TRAS3004I: The following messages are hidden from the console.log file: {0}

Explanation	Messages that are configured to be hidden are not written to the console.log file. They are written to the log and trace data repositories in the binary logging.
Action	No action is required

TRAS3005E: Failed to write messages to the {0} file.

Explanation	An error occurred when trying to write message to the file.
Action	Ensure that the directory exists, is writable, and has sufficient disk space.

TRAS3006I: Logging messages to the {0} file has resumed.

Explanation	Messages can be written to the file.
Action	No action is required.

TRAS3007W: The JSON logging field name mapping is incorrectly formatted.

Explanation	The JSON logging field name mapping is incorrectly formatted.
Action	Ensure the format of the JSON logging field name mapping property is correct. The JSON field name mapping can be specified in a number of ways, specified in the logging configuration documentation.

TRAS3008W: The JSON logging field name mapping property has too many or too few tokens in an entry.

Explanation	The JSON logging field name mapping property must be formatted defaultFieldName:newFieldName or source:defaultFieldName:newFieldName.
Action	The JSON logging field name mapping property must be formatted defaultFieldName:newFieldName or source:defaultFieldName:newFieldName.

TRAS3009W: Provided JSON logging field name does not match one of the known field names for the specified source(s)

Explanation	Provided JSON logging field name does not match one of the known field names
Action	Please provide a JSON logging field name that matches one of the known fields (e.g. message, ibm_datetime, ibm_sequence)

TRAS3010W: The provided JSON logging field mapping source identifier does not match one of the known sources

Explanation	The accepted sources are: message, trace, accessLog, ffdc, audit
Action	The accepted sources are: message, trace, accessLog, ffdc, audit

TRAS3011W: An invalid character was provided in the JSON logging field name mapping property

Explanation	Only letters, numbers, and : are accepted in the JSON logging field name mapping property
Action	Change your JSON logging field name mapping property value to remove invalid characters

TRAS3012W: Header name is missing for one or more accessLogging logFormat fields: {0}.

Explanation	JSON logging uses the logFormat attribute from accessLogging to select which http_access.log message fields to include. A header name must be supplied when using the %i or %o fields in the accessLogging logFormat attribute.
Action	Provide a header name for the field in the accessLogging logFormat attribute.

TRAS3013W: The log rollover interval cannot be less than 1 minute long. If a value that is less than 1 minute is specified, the log rollover interval is set to a default of 1 day.

Explanation	The log rollover interval cannot be less than 1 minute long.
Action	Specify a log rollover interval that is equal to or greater than 1 minute.

TRAS3014I: Deleted {0} FFDC files based on the configured maxFfdcAge value.

Explanation	The number of FFDC files that were deleted during a FFDC cleanup.
Action	No action is required.

TRAS3015W: The log rollover start time property is incorrectly formatted. As a result, the value is set to a default of '00:00', which represents midnight.

Explanation	The rollover start time property must be formatted HH:MM, with 00:00 representing midnight.
Action	Ensure that the rollover start time property value is properly formatted in HH:MM 24-hour notation, where 00:00 represents midnight.

TRAS3100I: Event logging is enabled. One request out of every {0} requests will be sampled. Only events with a duration exceeding {1}ms and type {2} will be logged.

Explanation	Event logging feature is started with the configuration settings indicated in the message.
Action	No action required.

TRAS3300E: The timing configuration associated with PID {0} cannot be read from the configuration.

Explanation	The request timing service attempted to read an embedded timing configuration from the server.xml file. The PID associated with the timing element is in the message.
Action	Look in messages.log for other error messages, such as CWWKG0058E, for details on the configuration problem. Correct the configuration to resolve the error.

TRAS3301W: A timing configuration of type {0} and context info pattern {1} already exists. The timing configuration associated with PID {2} replaces the previous timing configuration.

Explanation	A duplicate timing configuration was found in the server.xml file. The combination of type and context info pattern was already defined.
Action	Inspect the server.xml file and remove any duplicate timing configurations.

TRAS3302W: The timing configuration for the {0} PID supplies a context information pattern, but the request timing configuration sets the includeContextInfo attribute to false. The timing configuration will be ignored.

Explanation	The request timing service read an embedded timing configuration from the server.xml file. The timing configuration specified a context information pattern to match. The request timing service is configured to disable context information for all requests, and cannot match requests to this timing configuration.
Action	Inspect the server.xml file and resolve the configuration conflict by changing the value of includeContextInfo to true in the request timing configuration, or by removing the context information pattern from the timing configuration.

TRAS3303W: The timing configuration associated with the {0} PID supplies a context information pattern that contains a wildcard in an unsupported location. The wildcard will be treated as an asterisk. The context information pattern is {1}.

Explanation	The request timing service read an embedded timing configuration from the server.xml file. In the context information pattern, an asterisk character is treated as a wildcard unless it is escaped with a backslash character. A wildcard is only permitted as the last character of the context information pattern.
Action	To interpret the wildcard character as an asterisk, escape it with a backslash character.