com.ibm.ws.logging.hpel.resources.HpelMessages

Explanation

The buffer size specified was invalid, a default size is being used instead

Action

If the default size is not optimal, specify a valid buffer size

Explanation

The flush period specified is invalid, a default period is being used instead

Action

If the default flush period is not optimal, specify a valid flush period

Explanation

An exception occurred while flushing the buffered log stream. Details are included with the message

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

Explanation

There is information missing in the header

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

Explanation

Log header was not valid as the code processing it was not able to parse and convert it

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

Explanation

A process order issue occurred and records are being written before the logging system is ready

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

Explanation

The log information was not serialized properly. Exception information is included in the error

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

Explanation

Location specified for the log directory does not contain any files with records

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

Explanation

Repository information specified is incorrect

Action

ReAssess the specified location information and modify the calls

Explanation

File is not a legitimate file in the repository

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

Explanation

Expected file has been removed either by the location manager or by manual intervention

Action

If information from the file is desired and it has been archived, consider restoring the information.

Explanation

Header information in file indicatest that the file is not a properly formed file in this repository

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

Explanation

The hour of the day specified is invalid, a default hour is being used instead

Action

If the default hour is not optimal, specify a valid hour of the day

Explanation

Either the file does not have valid header information or when buffering is enabled, the repository is creating a new binary file that is simultaneously being accessed.

Action

This could be a timing issue, consider reRunning the query. 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.

Explanation

This file is currently empty. This is generally indicative of some sort of error as files are created because records exist to be stored or the repository is creating a new binary file that is simultaneously being accessed.

Action

This could be a timing issue, consider reRunning the query. 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.

Explanation

Log file internal information indicates that a problem may have occurred.

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

Explanation

Log file internal information indicates that a problem may have occurred.

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

Explanation

Somehow an offset into a file is invalid (beyond the end of the file)

Action

If this is a locally written client, review the logic on calculation of the offset. 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.

Explanation

There appears to be an issue in positioning into the appropriate location in the file.

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

Explanation

There appears to be an issue in positioning into the appropriate location in the file.

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

Explanation

Unable to read a record from the file

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

Explanation

Error occurred on attempting to reposition within the file

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

Explanation

Error occurred while closing a stream. Exception should include more information

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

Explanation

Specified repository pointer does not belong to any repository. Most probably the file it points to was deleted already.

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

Explanation

Unable to read a record from the file while file may contain some other good records.

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

Explanation

A new entry in the restricted list was of the wrong format

Action

Determine if this entry is from the properties file, or someone using the API to add entries, then fix the file or caller of the API

Explanation

String to be parsed into loggerName and level could not be parsed

Action

Determine if this entry is from the properties file, or someone using the API to add entries, then fix the file or caller of the API

Explanation

Logging and Tracing configurations require more space than this file system currently contains

Action

Clear space from the file system or modify log and trace configurations to point elsewhere or consume less space