The Log Management 1.0
catalog contains messages in the range
BEA170000 - BEA170999.
Messages in this catalog are part of the
weblogic.management.internal
Internationalization package and the
weblogic.i18n
Localization package.
|
BEA-170000
|
Warning: An invalid search request was received. The search for the domain logfile can only be performed on the admin server.
|
Description
| The domain log file resides only on the file system accessible by the admin server in the WebLogic Server domain. |
|
Cause
| This error message is caused by invoking the search for the domain logfile on one of the managed servers. |
|
Action
| Redirect the request to the admin server in the domain. |
|
|
BEA-170001
|
Error: The end time (endTime) is less than the start time (startTime) in the search request.
|
Description
| The end time specified for the time range should be later than the start time. |
|
Cause
| The time range specified for searching the log is invalid. |
|
Action
| Specify a valid time range with an end time that is later than the start time. |
|
|
BEA-170002
|
Warning: DomainLogfile Handler is unable to obtain the filter information. The system will use the default filter.
|
Description
| If there is no DomainLogFilter targeted to this server, the server will use the default DomainLogFilter to broadcast messages to the domain log. |
|
Cause
| The DomainLogFilter is not specified for the server. |
|
Action
| Configure a DomainLogFilter for the server specifying the granularity messages that will be broadcasted to the domian log file. |
|
|
BEA-170003
|
Critical: The DomainLogfile Handler is unable to open the domain logfile filename. The domain logfile is disabled.
|
Description
| This message is encountered at admin server startup time, when the log file for the WebLogic domain cannot be opened for IO operations. |
|
Cause
| The filepath specified for the domain log is invalid or the server process cannot write to the domain log file. |
|
Action
| Specify an valid filepath for the domain log file. |
|
|
BEA-170004
|
Error: The DomainLogfile Handler is unable to subscribe to broadcaster broadcasterObjectName at - serverURL.
|
Description
| The DomainLog File Handler was unable to subscribe to domain log events from the given server. |
|
Cause
| This might occur due to managed server partitioning from the network, or the admin server might not be able to reach it. |
|
Action
| Correct the network problems. |
|
|
BEA-170005
|
Error: The DomainLogfile Handler cannot log a message to the domain logfile - th.
|
Description
| The domain log message could not be written to the log file. |
|
Cause
| This may happen due to an I/O operation failing during the write to the domain log file. |
|
Action
| Ensure the WebLogic Server process can access and write to the domain log file. |
|
|
BEA-170006
|
Error: There was an error creating the log broadcaster.
|
Description
| The log broadcaster object could not be created. |
|
Cause
| This indicates an internal error in the server. |
|
Action
| Contact BEA support. |
|
|
BEA-170007
|
Warning: An invalid log message was found in fname at line lineNum - ignored during search.
|
Description
| There are some missing fields in the header, or some fields may contain the field delimiters themselves. |
|
Cause
| This might occur due to some error in the formatter for WebLogic messages or due to the presence of third-party messages in the server log. |
|
Action
| Correct the formatter for user applications, or if it is a WebLogic message, report the problem to BEA support. |
|
|
BEA-170008
|
Critical: Unable to contact managed server serverName at url. Domain logfile does not contain messages from this server.
|
Description
| The admin server could not reach the given managed server. |
|
Cause
| The managed server might be getting network partitioned from the admin server, or the server might be running in MSI mode. |
|
Action
| Reestablish the network connection between the admin and managed servers. |
|
|
BEA-170009
|
Critical: Failed to create a default filter for thedomain log. No messages will be sent to the domain log.
|
Description
| An MBeanCreationException is caught while trying to create a default log filter MBean for the server. |
|
Cause
| An internal error might have occurred in the management infrastructure. |
|
Action
| Report this problem to BEA support. |
|
|
BEA-170010
|
Critical: Received a ConfigurationException when trying to set the filename for the domain log. No domain log will be created.
|
Description
| The domain log file name attribute could not be set. |
|
Cause
| An internal error in the management infrastructure may have occurred. |
|
Action
| Report this problem to BEA support. |
|
|
BEA-170011
|
Critical: The LogBroadcaster on this server is unable to obtain the domain log handler.
|
Description
| The LogBroadCaster on the managed server could not find a reference to the DomainLogHandler on the admin server. Messages from this server will not be logged in the domain log. |
|
Cause
| The managed server might not be able to reach the admin server. |
|
Action
| To fix this problem, inspect the exception stack trace, correct the problem, and restart this server. |
|
|
BEA-170012
|
Critical: The LogBroadcaster on this server is unable to obtain server runtime information. Messages from this server will not be logged in the domain log.
|
Description
| The runtime state of this server is not available to the LogBroadcaster. |
|
Cause
| This indicates an internal error in the management infrastructure. |
|
Action
| Report this problem to BEA support. |
|
|
BEA-170013
|
Warning: A field is missing in a message in fname at line lineNum. The message was ignored during the search.
|
Description
| The log record is not properly formatted. |
|
Cause
| The expected fields are not all present in the first line of a log record. |
|
Action
| Report this problem to BEA if it is a WebLogic Server log message. |
|
|
BEA-170014
|
Warning: The date field is probably invalid on fname line lineNum. The message was ignored during the search.
|
Description
| The date and time information in the log entry field is not correctly formatted. |
|
Cause
| A timestamp might not be formatted for the locale setting on the machine. |
|
Action
| Correct the locale setting for the server machine. |
|
|
BEA-170015
|
Info: End of startup logfile. The server will continue logging in the main logfile.
|
Description
| If there are any messages generated in the server before logging initialization is completed, the server logs into this startup file. Once initialization is complete, the server starts logging into the regular logfile as specified in the configuration. |
|
Cause
| This message indicates that the startup is complete and the server logging system is fully initialized. |
|
Action
| Check the main server log for any further log records. |
|
|
BEA-170016
|
Info: FileLogger initialized. There may be some pre-initialization messages in oldFilename.
|
Description
| If there are any messages generated in the server before logging initialization is completed, the server logs into oldFilename. Initialization is now complete, and the server will continue logging in this logfile. |
|
Cause
| This is an information-level message only. |
|
Action
| No action required. |
|
|
BEA-170017
|
Alert: The log file f1 will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.
|
Description
| This message is emitted to indicate that the current log is being scheduled for rotation. |
|
Cause
| This event happens whenever the log file is about to be rotated based on either size or time rotation criterion. |
|
Action
| On certain platforms, if some application is tailing the log, the rotation fails. Stop the application tailing and reopen the tail after the rotation is complete. |
|
|
BEA-170018
|
Alert: The log file has been rotated to f2. Log messages will continue to be logged in f1.
|
Description
| This message is emitted to indicate that the current log file has been rotated. |
|
Cause
| This event happens after the log file is rotated based on either size or time rotation criterion. |
|
Action
| No action required. |
|
