Content starts here

Log Management Subsystem Messages

The Log Management1.0 catalog contains messages in the range BEA-170000 - BEA-170999. Messages in this catalog are part of the weblogic.logging Internationalization package and the weblogic.logging Localization package.

BEA-170000(retired)

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(retired)

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(retired)

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(retired)

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(retired)

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(retired)

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 Oracle Customer Support.

BEA-170007(retired)

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 Oracle Customer Support.

BEA-170008(retired)

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(retired)

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 Oracle Customer Support.

BEA-170010(retired)

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 Oracle Customer Support.

BEA-170011

Warning: The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.

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. One of the possible causes could be due to the admin server being shutdown.

Action

To fix this problem, inspect the exception stack trace, correct the problem. If the admin server is shutdown, restart it to resume normal log broadcasting to the domain.

BEA-170012(retired)

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 Oracle Customer Support.

BEA-170013(retired)

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 Oracle if it is a WebLogic Server log message.

BEA-170014(retired)

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(retired)

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(retired)

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(retired)

Info: 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(retired)

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

BEA-170019

Notice: The server log file fileName is opened. All server side log events will be written to this file.

Description

During server startup this message indicates the file name to which the server will log.

Cause

This message is for informational purposes only.

Action

No action is needed.

BEA-170020

Error: The server log file fileName could not be opened successfully.

Description

This error is reported during server startup when opening the log file. It indicates that events will not be written to the log file.

Cause

The filepath configured for the server's log file is not valid.

Action

Please specify a valid filepath for the server's log file.

BEA-170021(retired)

Error: The log handler/appender for publishing log events to the domain log could not be initialized.

Description

This error can happen during the server startup when the Logging system is getting initialized. This indicates that domain logging will not be available for this server session.

Cause

The LogBroadcaster runtime is not available during server startup.

Action

Please take appropriate action based on the stack trace of the error. If the problem persists then contact Oracle for help.

BEA-170022

Error: Log4j failed to initialize for logName. The default JDK Logging implementation will be used.

Description

This is caused at Server startup if Log4j logging is enabled and Log4j classes could not loaded.

Cause

The Log4j libraries may not be in the server CLASSPATH.

Action

Please take correction action based on the stack trace details.

BEA-170023

Info: The Server Logging is initialized with Java Logging API implementation.

Description

This message is emitted on server startup when JDK Logger is initialized with WebLogic handlers for Server Logging.

Cause

This message is only for informational purposes.

Action

No action is needed.

BEA-170024

Info: The Server Logging is initialized with Apache''s Log4j Logging API implementation.

Description

This message is emitted on server startup when Log4j Logger is initialized with WebLogic appenders for Server Logging.

Cause

This message is only for informational purposes.

Action

No action is needed.

BEA-170025

Info: Initialized Domain Logging. Domain log events will be written to fileName.

Description

This message indicates that the domain logger on the Admin server has successfully initialized.

Cause

This message is for informational purpose.

Action

No action is needed.

BEA-170026(retired)

Warning: The servlet context logger could not be initialized for servlet context contextName to write to its own log file.

Description

The messages pertaining to this servlet context will be written to the servers log.

Cause

There is an I/O error opening the file for the servlet context log.

Action

Ensure that the logging configuration for the webapp is valid.

BEA-170027

Notice: The Server has established connection with the Domain level Diagnostic Service successfully.

Description

This initialization happens on Server starup and whenever the Admin server restarts. Log events and SNMP traps if enabled will now be broadcasted to the Admin Server.

Cause

The server has established contact with the Domain Diagnostic Service successfully.

Action

No action is needed from the user.

BEA-170028

Error: The Remote Handler is not available, so the trap notification information can not be sent.

Description

The remote SNMP Trap notification utilizes a remote handler to send information to the Administrative Server SNMP Agent. The non-availability of the remote handler will preclued the SNMP Trap from being generated.

Cause

The managed server might not be able to reach the admin server. One of the possible causes could be due to the admin server being shutdown.

Action

If the admin server is shutdown, restart it to resume normal communication for the domain.

BEA-170029

Warning: The data gathering handler could not be initialized

Description

The data gathering handler could not be initialized

Cause

There was an error initializing the data gathering handler

Action

Review the nested exception details for the cause

  Back to Top