Content starts here

Diagnostics Subsystem Messages

The Diagnostics1.0 catalog contains messages in the range BEA-320000 - BEA-320899. Messages in this catalog are part of the weblogic.diagnostics.i18n Internationalization package and the weblogic.diagnostics.l10n Localization package.

BEA-320000

Info: The Diagnostics subsystem is initializing on Server serverName.

Description

This message indicates that the Diagnostics subsystem is initializing during the server startup phase.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320001

Info: The ServerDebug service initialized successfully.

Description

This message indicates that the ServerDebug service has initialized successfully during startup.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320002

Info: The Diagnostics subsystem is stopping on Server serverName.

Description

This message indicates that the Diagnostics subsystem is shutting down during the server shutdown phase.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320003(retired)

Error: The DebugLogger for the ServerDebugMBean attribute attributeName could not be initialized from its configured value.

Description

This happens when the ServerDebugMBean attribute value cannot be read successfully to initialize the corresponding DebugLogger instance.

Cause

This could be due to some error in the OA&M configuration layer.

Action

Take appropriate action based on the exception message.

BEA-320004

Error: The following unexpected exception was thrown: message

Description

This happens when an unexpected exception was caught.

Cause

An exception was thrown unexpectedly.

Action

Take appropriate action based on the unexpected exception message.

BEA-320005

Error: Diagnostic monitor of unknown type monType used in instrumentation scope scopeName.

Description

This happens when a diagnostic monitor of specified type does not exist in the monitor library.

Cause

Diagnostic monitor library is probably out of date.

Action

Update diagnostic monitor library

BEA-320006(retired)

Warning: Error occurred while attempting to access the following MBean: name

Description

This exception occurs when there is a JMXException thrown when attempting to access an MBean.

Cause

MBean was unregistered from MBeanServer before unregistering with Harvester.

Action

Unregister MBean instance from Harvester before unregistering from MBeanServer.

BEA-320007(retired)

Warning: Error occurred while attempting to access the following HarvestableDataSource: name

Description

This exception occurs when there is a checked exception thrown from a HarvestableDataSource.

Cause

Queried harvestable attribute is no longer part of the HarvestableDataSource.

Action

Query the HarvestableDataSource for the latest collection of harvestable attributes.

BEA-320008

Error: Error occurred while collecting diagnostic metrics:

Description

This exception occurs when an exception is thrown internally that affects the harvesting process.

Cause

Error occurred while constructing a Harvester instance.

Action

Make sure that all harvester configuration parameters are set appropriately.

BEA-320009

Warning: The elapsed time of the last snapshot of diagnostic metrics exceeded the configured sample period by the following number of milliseconds: delay.

Description

This event occurs when a sampling cycle completes outside of the specified sample period.

Cause

Harvested MBeans and/or DataSources are taking too long to return sampled attribute values.

Action

Increase sample period window.

BEA-320010

Error: An error occurred while generating a diagnostic image: th

Description

This error message indicates a failure to create any part of a diagnostic image zip file.

Cause

The user has abruptly changed permissions on the zip/directory. The file system doesn't have sufficient disk space to continue writing the image.

Action

The customer must allocate sufficient disk space and provide the proper permissions to create the image zip file.

BEA-320011

Error: The following diagnostic image destination directory could not be created: destination

Description

Upon initialization of the ImageManager, the default destination directory for images will be created. This error message indicates that the directory could not be created.

Cause

The customer has not given write permissions on the absolute path for default directory. The customer hasnt allocated sufficient disk space for the directory to be created.

Action

Customer must give write permissions to absolute path for default directory if no configured destination directory is specified. Customer must also allocate sufficient disk space for the default directory to be created if no destination directory is specified.

BEA-320012

Error: The following destination directory for diagnostic images couldn't be read/written: dir

Description

This error message is logged when a user specifies a destination directory for diagnostic images that isn't readable/writable.

Cause

Customer hasn't created the directory. Customer hasn't given the directory read/write permissions.

Action

Customer should create the destination directory with appropriate read/write permissions.

BEA-320013

Error: Diagnostic image capture attempted during a lockout period.

Description

ImageManager locks out subsequent image capture requests if a lockout period is configured.

Cause

ImageManager has locked image captures for a specified number of minutes.

Action

Lockout period must expire before a new image capture request is accepted.

BEA-320014

Error: Lockout of lockoutMinutes above allowed maximum lockout minutes for image captures.

Description

User can specify a certain amount of minutes to lockout subsequent image captures.

Cause

User specified a number of minutes that exceeds maximum allowed lockout minutes.

Action

User should specify a lockout period between the minimum and maximum.

BEA-320015

Error: Lockout of lockoutMinutes below allowed minimum lockout minutes for image captures.

Description

User can specify a certain amount of minutes to lockout subsequent image captures.

Cause

User specified a number of minutes that falls below minimum allowed lockout minutes.

Action

User should specify a lockout period between the minimum and maximum.

BEA-320016

Alert: Creating diagnostic image in destination with a lockout minute period of minutes.

Description

Either a FirstFailure or customer has initiated a diagnostic image capture request.

Cause

FirstFailure has occurred, customer configured a diagnostic image notification handler, or explicitly invoked a capture image method on ImageManager.

Action

Diagnostic image capture request will be scheduled and executed.

BEA-320017(retired)

Error: Instrumentation engine configuration resourceName can not be located.

Description

Internal error. Instrumentation engine configuration is missing from the build.

Cause

Instrumentation engine configuration is missing from the build.

Action

Contact Oracle support

BEA-320018

Error: Instrumentation engine configuration resourceName could not be parsed due to: cause

Description

Internal error. Could not parse instrumentation engine configuration. It could be malformed.

Cause

Instrumentation engine configuration is possibly malformed.

Action

Contact Oracle support.

BEA-320019

Error: Code generator class className for standard monitor monitorName could not be found.

Description

Internal error. Specified code generator for the standard monitor is not found on the class path.

Cause

Standard monitor code generator is not on the class path.

Action

Contact Oracle support

BEA-320020

Error: Code generator className for standard monitor monitorName could not be instantiated.

Description

Internal error. Code generator for a standard monitor was found, but it could not be instantiated.

Cause

Standard monitor code generator is missing default constructor.

Action

Contact Oracle support

BEA-320021

Error: Code generator className could not be accessed for standard monitor monitorName.

Description

Internal error. Standard monitor code generator could not be accessed.

Cause

Standard monitor code generator implementation has problems

Action

Contact Oracle support

BEA-320022

Error: An error was encountered while creating SerialVersionUID for class className.

Description

Internal error. SerialVersionUID for a class could not be created.

Cause

Internal error

Action

Contact Oracle support

BEA-320023

Error: File classFile does not contain a valid Java class

Description

File does not contain a valid Java class.

Cause

File does not contain a valid Java class

Action

Make sure that the file being instrumented is a valid Java class file.

BEA-320024

Error: Class in file fileName could not be instrumented.

Description

Class could not be instrumented.

Cause

This can happen because the input file or output file can not be read from or written to.

Action

Check file permissions and disk space.

BEA-320025

Error: Input file fileName for instrumentation engine can not be found.

Description

Specified input file could not be found.

Cause

Input class file does not exist.

Action

Provide correct path to input class file.

BEA-320026

Error: Monitor monitorName could not be found in instrumentation engine configuration

Description

Specified monitor is not configured in the instrumentation engine configuration.

Cause

Monitor name may be misspelt.

Action

Specify correct monitor name on the command line.

BEA-320027(retired)

Error: Configured action class className is not on the class path

Description

Configured action class is not on the class path

Cause

Configured action class is not on the class path

Action

Make sure that the action class is on the class path.

BEA-320028(retired)

Error: Configured action of class className could not be instantiated.

Description

Configured action could not be instantiated.

Cause

Action class does not have public default constructor.

Action

Reimplement action class to conform to requirements. If this is an action supplied with the product, contact Oracle support.

BEA-320029(retired)

Error: Configured action class className is not a valid action class

Description

Configured action class is not a valid action class

Cause

Incorrect action implementation

Action

Reimplement action class to conform to requirements. If this is an action supplied with the product, contact Oracle support.

BEA-320030

Error: Delegating monitor monitorName in scope scopeName allows using action of type actionType, which does not exist.

Description

Delegating monitor is configured to use an action of a specified type, but the action does not exist.

Cause

Misconfigured delegating monitor in the instrumentation engine configuration

Action

Contact Oracle support

BEA-320031

Error: An attempt to add a monitor of type monType to instrumentation scope scopeName failed because the monitor already exists in the scope.

Description

Attempt to add duplicate monitor to an instrumentation scope failed. New monitor is ignored.

Cause

Incorrect instrumentation configuration

Action

Remove multiple monitor entries with same types from the instrumentation scope configuration.

BEA-320032

Warning: Attempt to add duplicate action actionName to monitor monType in scope scopeName failed.

Description

Attempt to add duplicate action with same name to a delegating monitor failed. New action entry is ignored.

Cause

Instrumentation scope configuration is incorrect. It has duplicate actions attached to the same monitor.

Action

Remove duplicate actions attached to the same monitor.

BEA-320033

Error: Attempt to attach incompatible action of type actType to a delegating monitor of type monType in scope scopeName.

Description

Attempt to attach incompatible action to a delegating monitor

Cause

Incorrect instrumentation configuration

Action

Make sure that only compatible actions are used with delegating monitors.

BEA-320034

Error: Instrumentation engine configuration configFile could not be parsed. errMsg

Description

Instrumentation engine configuration could not be parsed.

Cause

Instrumentation configuration is malformed

Action

Contact Oracle support

BEA-320035

Error: Instrumentation configuration configFile could not be read.

Description

Instrumentation configuration could not be read due to some i/o error.

Cause

Missing or invalid instrumentation configuration

Action

Contact Oracle support

BEA-320036

Error: Instrumented method methodNamemethodDesc in class className exceeds size limit. Original method is preserved.

Description

After instrumentation, the method size exceeds 64K limit imposed by the VM, which would make the resulting class unloadable. Therefore, the original method is preserved.

Cause

Original method is too large to begin with. The class to which it belongs is probably generated by a generator program.

Action

Split method into multiple methods if possible. Exclude class from instrumentation to speed up instrumentation process.

BEA-320037

Error: Class bytes for className do not conform to class format.

Description

Class bytes do not conform to class format

Cause

Corrupt class file.

Action

Make sure that the class file is not corrupt.

BEA-320038

Error: Could not instrument class className

Description

Could not instrument class

Cause

General instrumentation failure

Action

Contact Oracle support

BEA-320039

Error: Invalid class inclusion pattern(s) for instrumentation engine/scope scope. Disabling instrumentation in scope scope.

Description

Specified inclusion patterns could not be parsed

Cause

Malformed inclusion patterns

Action

Specify inclusion patterns in correct format

BEA-320040

Error: Invalid class exclusion pattern(s) for instrumentation engine/scope scope. Disabling instrumentation in scope scope.

Description

Specified exclusion pattern(s) could not be parsed.

Cause

Malformed exclusion pattern(s)

Action

Specify exclusion patterns in correct format.

BEA-320041

Error: Invalid lockout minutes value specified in image notification. Image capture was not performed.

Description

The value for the lockout minutes for the image capture is invalid.

Cause

The value is invalid.

Action

Recreate the notification with a valid lockout minutes value.

BEA-320042

Error: Invalid diagnostic image location imageLocation specified in notification, exception message is exc. Image capture was not performed.

Description

The value for the image location for the image capture is invalid.

Cause

The value is not a valid directory or file name.

Action

Recreate the notification with a valid image location. Take appropriate action based on the exception message.

BEA-320043

Error: Image notification was not performed because the image capture was attempted before the lockout time expired. The exception message is exc

Description

The notification attempted an image capture before the lockout period had completed.

Cause

An image capture was attempted before the lockout period had expired.

Action

Recreate the image notification with a smaller value for lockout minutes. Optionally, utilize the watch alarm feature to ensure the notification does not reoccur before the lockout period has expired.

BEA-320044

Error: Error occurred while performing a watch notification:

Description

This exception occurs when an exception is thrown internally that affects the notification process.

Cause

Error occurred while performing the operations required for the notification.

Action

Take appropriate action based on the unexpected exception message.

BEA-320045(retired)

Error: Invalid type of Notification passed to Watch Notification Listener. Expected notification of type WatchNotification, received notification of type className.

Description

The notification listener only supports notifications of a specific type. A different type was received.

Cause

Notification was not of type WatchNotification.

Action

Contact Oracle support as this indicates an internal error.

BEA-320046(retired)

Error: An error occurred while parsing the email address address for the SMTP notification.

Description

This exception occurs when an exception is thrown by the javax.mail.internet,InternetAddress.parse method.

Cause

The format of the email address can not be parsed.

Action

Create a new notification with a valid email address.

BEA-320047

Error: Mail notification has not been sent due to an error that occurred while creating or sending a mail message:

Description

A MessagingException was thrown when creating a mail message, setting the recipient, or sending the mail message.

Cause

Error occurred while performing the mail operations required for the notification.

Action

Verify the MailSession properties and email destination. Take appropriate action based on the Messaging exception message.

BEA-320048

Error: JMS notification message has not been sent due to an error that occurred while creating a JMS map message:

Description

A JMSException was thrown when creating and initializing a JMS mail message.

Cause

Error occurred while performing the JMS operation.

Action

Verify the JMS queue and connection factory configuration settings in the JMS notification. Take appropriate action based on the JMS exception message.

BEA-320049

Warning: Exception occurred sending JMS notification message. Reinitializing JMS objects and retrying.

Description

A JMSException was thrown when sending the JMS map message. The JMS notification will attempt to reinitialize the JMS state, looking up the connection factory and destination again, reinitializing the session and message producer, and attempting to send the message again.

Cause

Error occurred while sending the JMS message.

Action

Look for additional error messages in the log from the reinitialization or resend of the message.

BEA-320050(retired)

Error: Exception occurred while retrying the send of a JMS notification message.

Description

A JMSException was thrown when retrying the send the JMS map message. The error either occurred while reinitializing JMS or resending the message.

Cause

Error occurred while reinitializing JMS or resending the JMS message.

Action

Verify that the JMS destination is available. Take appropriate action based on the JMS exception message.

BEA-320051(retired)

Error: Exception occurred while initializing the JMS setup (connection factory, connection, session, destination, or message producer).

Description

A JMSException was thrown when creating the JMS objects used to send the notification to the JMS destination.

Cause

JMS destination is not configured correctly or is not available.

Action

Verify that the JMS destination is available. Take appropriate action based on the JMS exception message.

BEA-320052

Error: Error occurred while initializing a SMTP notification:

Description

This error occurs when an exception is thrown while looking up the mail session via JNDI or initializing the transport.

Cause

The mail session is incorrectly configured or not available.

Action

Ensure that the mail session JNDI name is correct. Ensure that the mail session MBean properties are valid. Take appropriate action based on the exception message.

BEA-320053

Error: The SNMP Agent is not configured so the trap for the SNMP Watch notification can not be sent.

Description

The SNMP Watch Notification utilizes the SNMP Agent to send the trap to the configured trap destinations.

Cause

SNMP Agent is not enabled.

Action

Enable the SNMP Agent using the console.

BEA-320054

Error: Error occurred while sending a SNMP notification:

Description

This error occurs when an exception is thrown while sending the SNMP trap.

Cause

SNMP Agent threw an exception when sending the SNMP trap to the configured trap destinations.

Action

Ensure that the trap destinations are configured correctly. Take appropriate action based on the exception message.

BEA-320055

Error: Could not read or create index on log file file

Description

Could not read or create index on log file

Cause

Disk may be full or directory is not writable

Action

Check if disk is full or directory is unwritable

BEA-320056

Error: Log index file file has invalid magic number

Description

Log index file has incorrect magic number

Cause

Corrupt or invalid index file

Action

Delete the corrupt index file

BEA-320057

Error: Log index file file contents are inconsistent with its header

Description

Log index file header is inconsistent with its contents

Cause

Corrupt or truncated index file

Action

Delete index file

BEA-320058

Error: Could not parse log record: record

Description

Could not parse log record

Cause

Malformed log record

Action

Please contact Oracle Support

BEA-320062(retired)

Error: Watch definition for watch watchName is invalid. Watch create failed with error: error.

Description

An exception was thrown when creating the watch. The attributes defined in the watch are not valid.

Cause

Watch is not defined correctly. Attributes are not valid.

Action

Verify that the watch attributes are valid. Take appropriate action based on error message.

BEA-320063

Warning: An attempt to add watch watchName failed because the watch has already been defined.

Description

Attempt to add duplicate watch failed. New watch is ignored as two watches can not have the same name.

Cause

Two different watch definitions have the same name.

Action

Remove multiple watch entries with the same name.

BEA-320064

Error: Watch watchName could not be created due to the following unexpected exception: error

Description

An unexpected exception was thrown while creating the watch. Notification has been ignored.

Cause

An exception was thrown unexpectedly.

Action

Take appropriate action based on the unexpected exception message.

BEA-320065(retired)

Error: Notification definition for notificationName is invalid. Notification create failed with error: error.

Description

An exception was thrown when creating the notification. The attributes defined in the notification are not valid.

Cause

Notification is not defined correctly. Attributes are not valid.

Action

Verify that the notification attributes are valid. Take appropriate action based on error message.

BEA-320066

Warning: An attempt to add notification notificationName failed because the notification has already been defined.

Description

Attempt to add duplicate notification failed. New notification is ignored as two notifications can not have the same name.

Cause

Two different notification definitions have the same name.

Action

Remove multiple notification entries with the same name.

BEA-320067(retired)

Error: Notification notificationName could not be created due to the following unexpected exception: error

Description

An unexpected exception was thrown while creating the notification.

Cause

An exception was thrown unexpectedly.

Action

Take appropriate action based on the unexpected exception message.

BEA-320068

Notice: Watch 'watchName' with severity 'severity' on server 'server' has triggered at time. Notification details: details

Description

A configured watch has triggered and the associated notifications will be performed.

Cause

Configured watch evaluated to true and triggered.

Action

None required.

BEA-320069

Error: Watch watchName contains an invalid notification notificationName that is not defined.

Description

The definition of the watch contains a notification that has not been defined.

Cause

Notification does not exist.

Action

Define the notification or remove the notification from the watch.

BEA-320070

Error: Error occurred while performing notification notificationName for watch watchName. Notification may not have completed.

Description

An exception was thrown while performing the notification for the watch.

Cause

Exception thrown while performing the notification.

Action

Validate the definition for the specified watch and notification. Take appropriate action based on the error message.

BEA-320071

Error: Error occurred while creating watch notification watchName. Notifications may not have completed for this watch.

Description

An exception was thrown while creating the watch notification.

Cause

Exception thrown while creating the watch notification.

Action

Validate the definition for the specified watch and notification. Take appropriate action based on the error message.

BEA-320072(retired)

Warning: Notification notificationName for watch watchName was not performed since the notification is disabled.

Description

The watch triggered, but the notification was not performed since it has been disabled.

Cause

Notification is disabled.

Action

Enable the notification.

BEA-320073

Error: Error while locating a record for timestamp timestamp in the archive

Description

Error locating a record in the archive

Cause

Misconfigured or missing data archive for harvested data

Action

Check that the harvested data archive exists

BEA-320074

Error: Error while executing query.

Description

Error while executing query.

Cause

Internal error

Action

Contact Oracle Support

BEA-320075

Error: Error while reading a record from the archive

Description

Error while reading a record from the archive

Cause

Harvested data archive may be corrupt due to internal error.

Action

Reconfigure harvested data archive. Contact Oracle support to report this problem.

BEA-320076

Error: Could not initialize index information for harvester data archive.

Description

Could not initialize index information for harvester data archive.

Cause

Harvested data archive may be corrupt due to internal error.

Action

Reconfigure harvested data archive. Contact Oracle support to report this problem.

BEA-320077

Info: Initialized the Diagnostic Accessor Service.

Description

This message indicates that the Diagnostic Accessor Service initialized successfully.

Cause

None.

Action

No action is needed.

BEA-320078

Error: Could not initialize the Diagnostic Accessor Service Runtime during server startup.

Description

This message indicates that Diagnostic data will not be available in the Server session.

Cause

The exception message includes the details about the cause of this problem.

Action

Take corrective action based on the exception stack trace. Contact Oracle support if this problem persists.

BEA-320079

Error: Watch 'watchName' rule expression evaluation failed with an exception. No notifications will be performed for this watch. The exception is:

Description

An exception occurred while evaluating the watch rule expression. This caused the evaluation to stop and no notifications will be performed for this watch.

Cause

Exception was thrown during rule evaluation.

Action

Verify that the rule expression is valid. Take appropriate action based on the exception message.

BEA-320080

Error: The log type logType is unknown. Unable to lookup the DiagnosticDataAccessRuntimeMBean instance.

Description

The supported log types are defined in weblogic.diagnostics.accessor.LogTypes interface.

Cause

This message indicates that the logical name specified to look up the DiagnosticDataAccessRuntimeMBean is not correct.

Action

Verify that the log type is valid. Take appropriate action based on the exception message.

BEA-320081(retired)

Error: Instrumentation configuration for scope scopeName could not be read. The exception is:

Description

An exception occurred while reading the instrumentation configuration for a scope. Classes within the instrumentation scope will not be instrumented.

Cause

Exception was thrown during reading the instrumentation scope.

Action

Verify that the instrumentation scope configuration is valid.

BEA-320082

Error: Configuration for diagnostic monitor monType in instrumentation scope scopeName has errors. The exception is:

Description

An exception occurred while reading the configuration for a diagnostic monitor in an instrumentation scope. The monitor will not be applied to classes in the scope.

Cause

Exception was thrown during reading the configuration of a diagnostic monitor in a scope.

Action

Verify that the configuration for the diagnostic monitor is valid.

BEA-320083

Error: Custom diagnostic monitor monType in instrumentation scope scopeName has missing or invalid location attribute.

Description

Custom diagnostic monitor must specify the location attribute, whose value must be one of 'before' 'after' or 'around'.

Cause

Missing or invalid value of 'location' attribute of a custom diagnostic monitor.

Action

Verify that the 'location' attribute of the custom monitor has correct value.

BEA-320084

Error: The user user does not have authorization to view the logs.

Description

The user is not granted one of the Admin roles.

Cause

A user with insufficient authorization attempted to access the server logs.

Action

Ensure that the right users are granted access to view the logs.

BEA-320085

Error: The diagnostic data is accessible only through https in the Production mode.

Description

The AccessorServlet rejected a request made over a non-secure protocol in the Production mode.

Cause

An attempt to access the diagnostic data was made over a non-secure protocol in the Production mode.

Action

Ensure that the SSL is enabled in production mode and the servlet is accessed only over a secure protocol.

BEA-320086

Error: The monitor type type in scope scopeName contains unacceptable characters.

Description

Monitor type contains unacceptable characters. It must start with an alphabetic character, followed by alphanumeric or underscore characters.

Cause

Monitor type contains unacceptable characters. It must start with an alphabetic character, followed by alphanumeric or underscore characters.

Action

Fix assigned monitor type, which must start with an alphabetic character, optionally followed by alphanumeric or underscore characters.

BEA-320087

Info: The cursor cursor has timed out and is being removed from the registry of open cursors.

Description

After the cursor is removed any further calls to fetch data will result in an exception.

Cause

This message is emitted when a cursor has not been invoked and is being removed to free up the associated resources.

Action

Ensure that fetch is no more called on the closed cursor.

BEA-320088

Error: The cursor with name cursor does not exist.

Description

The cursor with the given name does not exist, hence any fetch operation will fail with the given cursor name.

Cause

The cursor could have timed out, closed by the user explicitly or an invalid name has been provided.

Action

Invoke the fetch method with the name of a valid cursor.

BEA-320089(retired)

Error: The DebugScope name name is not valid.

Description

The DebugScope with the given name is not defined in the ServerDebugMBean interface.

Cause

The DebugScope with the given name is not defined in the ServerDebugMBean interface.

Action

Configure the debug scope with a valid name.

BEA-320090(retired)

Error: There was an error applying the DebugScopes configuration.

Description

This creation or removal of a Debug Scope could not be applied.

Cause

This may be due to I/O error reading the DebugScopes from the disk.

Action

Take action based on the error stack trace.

BEA-320091

Error: Attempt to use unknown action actionType in action group groupName

Description

An action used in the action group is not registered.

Cause

Incorrect or incomplete instrumentation engine configuration

Action

Please contact Oracle Support

BEA-320092

Error: Monitor type used empty or non-existent action group groupName

Description

Delegating monitor uses an action group which does not exist or is empty

Cause

Incorrect or incomplete instrumentation engine configuration

Action

Please contact Oracle Support

BEA-320093

Error: Encountered problem while reading attributes of monitor monitor. Attributes: attributes

Description

Some error was encountered while reading attributes of a diagnostic monitor

Cause

Possibly invalid attribute names specified with the diagnostic monitor

Action

Specify correct attributes for the diagnostic monitor.

BEA-320094

Error: Could not initialize server instrumentation scope.

Description

Weaving instrumentation engine for the server scope could not be configured

Cause

Internal error

Action

Contact Oracle support

BEA-320095(retired)

Warning: The debug scope scope is not configurable, the attributes in this scope will not be enabled or disabled.

Description

The user cannot enable either the root or the default debug scopes. For the default debug scope all the attributes in this scope have to be individually configured.

Cause

The user either specified the root or the default debug scope to be enabled or disabled.

Action

Please set the individual attributes appropriately if configuring the default scope. Configuring the root debug scope is not allowed.

BEA-320096

Error: Can not create custom monitor type in server instrumentation scope.

Description

Custom monitors can not be defined in the server instrumentation scope.

Cause

Custom monitors can not be defined in the server instrumentation scope.

Action

Remove custom monitor definition from the server instrumentation scope.

BEA-320097

Error: Monitor type can be created only in an application instrumentation scope. It can not be created in server instrumentation scope.

Description

Attempt to create a monitor in server scope, which can only be created in application scope.

Cause

Attempt to create a monitor in server scope, which can only be created in application scope.

Action

Remove monitor definition from the server instrumentation scope.

BEA-320098

Error: Monitor type can be created only in server instrumentation scope. It can not be created in application instrumentation scope scopeName.

Description

Attempt to create a monitor in application scope, which can only be created in server scope.

Cause

Attempt to create a monitor in application scope, which can only be created in server scope.

Action

Remove monitor definition from the application instrumentation scope.

BEA-320099(retired)

Error: Monitor monType in instrumentation scope scopeName is configured with an invalid monitor-type: monCategory.

Description

Monitor is configured with invalid monitor-type. Valid values are standard, delegating and custom

Cause

Incorrect instrumentation configuration

Action

Specify valid monitor-type value for the monitor.

BEA-320100

Error: Configuration for JDBC based diagnostic archives is invalid or incomplete. Using file based diagnostic archive.

Description

Configuration for JDBC based diagnostic archives is invalid or incomplete.

Cause

Configuration for JDBC based diagnostic archives is invalid or incomplete.

Action

Fix Configuration for JDBC based diagnostic archives

BEA-320101

Error: Attempt to target more than one WLDFSystemResource to server server.

Description

A server can be targeted only one WLDFSystemResource at a time.

Cause

This error indicates that an invalid targeting was specified for a WLDFSystemResource.

Action

Ensure that only one WLDFSystemResource is targeted to a server.

BEA-320102

Error: There was an error trying to access the diagnostic data while executing the query expression query.

Description

This message describes the failure that occurred while trying to retrieve diagnostic data from the Accessor.

Cause

This message indicates that the query is not properly specified.

Action

Ensure that the query is valid.

BEA-320103

Error: There was an error creating the DiagnosticDataRuntimeMBean instance with the given logical name logicalName.

Description

This message describes the failure to create the Accessor for the specified logical name.

Cause

This message indicates that the logical name is not a valid parameter or an error occurred while reading the diagnostic data.

Action

Ensure that the logical name is valid and take corrective action based on the error reported.

BEA-320104

Error: There was an error invoking the log4j operation while activating/deactivating log watch rules.

Description

The log4j libraries are invoked using reflection to register/deregister for log watch events.

Cause

The log4j libraries may not be in the CLASSPATH.

Action

Ensure that the log4j libraries are available when using Log watch rules with Log4j enabled.

BEA-320105

Error: The watch rule expression msg is not valid.

Description

There was a syntax error in parsing the given watch rule.

Cause

The watch rule expression does not confirm to the correct syntax.

Action

Specify a valid watch rule expression.

BEA-320106

Error: The watch notification configuration already contains a notification with the given name name.

Description

The name must be unique across the different types of notifications defined in the WLDFWatchNotification configuration.

Cause

The name for the WLDFNotification being added is not unique.

Action

Specify a unique name for the notification name.

BEA-320111

Warning: The elapsed time since the last Harvester cycle (millis milliseconds) is unacceptably short. Skipping this cycle in order to smooth out the responses.

Description

The Harvester attempts to insure that its cycles occur at intervals as specified in the samplePeriod. In this case, the time between the last cycle and this one is less than the tolerance allowed for deviation from the sample period.

Cause

The previous Harvesting process consumed a large percentage of the sample period. This can happen for 3 reasons: 1) the user can requested that a very large amount of data be harvested, 2) the system is consistently slow for some reason, 3) a intermittent service cause the process to slow down temporarily (for example garbage collection).

Action

No action is required. The Harvester will compensate by skipping cycles that occur too soon. If this happens consistently, either because the user is harvesting a large amount of data, or the Harvester is running on a slow system, the user may choose to either increase the samplePeriod or increase system resources.

BEA-320113

Warning: The type typeName is no longer being harvested.

Description

Due to some issue the specified type is being removed from the list of types currently being Harvested.

Cause

This is caused by an earlier problem. Sufficient log messages should have been issued at the point of failure to allow the problem to be debugged. Note that the type will remain deleted until the Harvester configuration is reloaded. At that time, if the problem is not yet resolved this message may be issued again.

Action

No action is required. But typically this type of error will cause some of the requested data to not be Harvested, so fixing the issue is advisable.

BEA-320114

Info: Initializing the Diagnostics Harvester.

Description

Communicates that the Harvester configuration is being consumed. This occurs when the server is started. Reinitialization may occur later due to updates made to the configuration.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320115

Info: The Harvester is configured to be disabled.

Description

During the loading of the Harvester configuration, this message communicates that the configuration specifies that the Harvester is disabled. When this is discovered, the Harvester ignores the remainder of its configuration.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320116

Info: Harvester type type is configured to be disabled. No harvesting will occur for this type.

Description

During the loading of the Harvester configuration, this message communicates that the configuration specifies that the specified type is disabled. Therefore no harvesting will occur for this type.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320117

Info: The Harvester is being disabled because there are no Harvestable types configured specified.

Description

During the loading of the Harvester configuration, this message communicates that the Harvester is being disabled because there are no valid types configured.

Cause

This may occur because the user did not provide any type specifications, or, if type specifications were provided, none of the specified types were Harvestable.

Action

No action is required.

BEA-320118

Info: The Harvester timer has been initiated for an interval of millis milliseconds.

Description

This message communicates that the Harvester is now active and indicates the time intervals at which harvesting is expected to occur. This message only occurs when the timer is first initiated, or when the samplePeriod is modified.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320119

Info: The Harvester is now in a state state.

Description

After the Harvester configuration is loaded, this message communicates the new Harvester state (enabled or disabled).

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320120(retired)

Warning: An error occurred attempting to Harvest type typeName.

Description

Some error occurred while Harvesting the specified type.

Cause

The actual problem occurred at a previous point in time. Sufficient messages should have been issued at the point of failure to facilitate debugging the problem.

Action

No action is required. But typically this type of error will cause some of the requested data to not be Harvested, so fixing the issue is advisable.

BEA-320121(retired)

Info: Harvester type typeName was discovered.

Description

The metatdata for the specified type has been located by the Harvester.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320122

Warning: Unable to harvest attribute attributeName on item instanceName due to errors. This attribute will no longer be harvested.

Description

The specified attribute cannot be harvested and will be removed. Note that the attribute remains removed until the configuration is reloaded at which time this message may appear again if the problem is not corrected.

Cause

The actual problem occurred at a previous point in time. Sufficient messages should have been issued at the point of failure to facilitate debugging the problem.

Action

No action is required. But typically this type of error will cause some of the requested data to not be Harvested, so fixing the issue is advisable.

BEA-320123

Error: Could not add MBean instance instanceName to the harvested instance list for type typeName: cause.

Description

The specified instance could not be added to the list of Harvested instanced for the specified type. Therefore the problematic instance cannot be harvested. Note that the instance remains removed until the configuration is reloaded at which time this message may appear again if the problem is not corrected.

Cause

The actual problem occurred at a previous point in time. Sufficient messages should have been issued at the point of failure to facilitate debugging the problem.

Action

No action is required. But typically this type of error will cause some of the requested data to not be Harvested, so fixing the issue is advisable.

BEA-320124

Info: The harvester has discovered a new instance of harvested type typeName named instanceName.

Description

This message is emitted when ever a new instance of a harvested type comes into being and is detected by the Harvester.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320125

Error: Attention: text

Description

This message is emitted when an internal inconsistency (one that should never occur) is detected in the Harvester.

Cause

This indicates a system error, not a user error. Further investigation is required to determine the cause.

Action

The user should contact Oracle support to debug this problem. It is often possible to turn on Harvester debug to obtain additional information.

BEA-320126

Info: Reinitializing the Diagnostics Harvester.

Description

Communicates that the Harvester configuration is being reloaded due to user modifications. Previous user errors detected are reset and may reoccur if they have not yet been reconciled. The Harvest timer is reset if modified. If reset, a harvest cycle occurs immediately.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320127

Error: An error occurred while generating Image Source srcName as part of the diagnostic image zip file:

Description

This error message indicates a failure to create the specified Image Source entry that is a standard portion of a requested diagnostic image zip file.

Cause

An unexpected error occurred while the subsystem was collecting or persisting the diagnostic image source information.

Action

Take appropriate action based on the unexpected exception message.

BEA-320128

Error: The WLDFResourceBean is not found for the WLDFSystemResource name.

Description

This error message indicates a failure to load the WLDFResourceBean from the descriptor file.

Cause

This error is caused due to either a deleted or corrupt WLDF descriptor file.

Action

Ensure that the descriptor file exists for the WLDFSytemResource and it conforms to the expected schema.

BEA-320129

Info: Instrumentation module name created.

Description

This message indicates that the instrumentation module for the server or application is created.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320130

Warning: Instrumentation module name is disabled.

Description

This message indicates that the instrumentation module for the server or application is disabled.

Cause

This instrumentation module for server or application is disabled.

Action

No action is required.

BEA-320131

Warning: Instrumentation module name is configured, but disabled because a WLDF system resource is not targeted to the server, or its instrumentation component is not enabled.

Description

Instrumentation module for application is disabled because the instrumentation manager is disabled.

Cause

There is no WLDF system resource targeted to the server, or its instrumentation component is disabled.

Action

Check if there is a WLDF system resource targeted to the server and its instrumentation component is enabled.

BEA-320132

Info: Updating classes within scope scopeName since its instrumentation configuration has changed.

Description

This message indicates that the classes within the scope will be changed and hot-swapped since instrumentation configuration has changed.

Cause

This message is for informational purposes only.

Action

No action is required.

BEA-320133

Error: Could not instantiate one of the known accessors during server startup.

Description

This message indicates that a known accessor failed to instantiate during server startup.

Cause

The exception message includes the details about the cause of this problem.

Action

Take corrective action based on the exception stack trace. Contact Oracle support if this problem persists.

BEA-320134

Error: An occurred while creating a domain log handler: t.

Description

The admin server encountered an internal error while creating the Domain Log Handler, which is used for propagating the Server Log entries to the Domain-wide log.

Cause

Refer to the embedded exception information for more details as to the probable cause of this error.

Action

Contact Oracle support.

BEA-320135

Error: JDBC based logicalName archive could not be created. Falling back on persistent store based archive.

Description

This happens when the JDBC DataSource to be used with the archive is misconfigured, unavailable or database tables not available.

Cause

This happens when the JDBC DataSource to be used with the archive is misconfigured, unavailable or database tables not available.

Action

Ensure that the JDBC DataSource is correctly configured, available and database tables created prior to use.

BEA-320136

Error: Class className could not be instrumented, due to reason: "msg".

Description

Class could not be instrumented.

Cause

This can happen because the class may contain constructs which are unsafe to transform, eg, custom attributes.

Action

Ensure that class does not have custom attributes, etc.

BEA-320137

Error: Invalid class inclusion pattern(s) for instrumentation monitor type in scope scope. Disabling instrumentation in scope scope.

Description

Specified inclusion patterns in instrumentation monitor could not be parsed

Cause

Malformed inclusion patterns in instrumentation monitor

Action

Specify inclusion patterns in instrumentation monitor in correct format

BEA-320138

Error: Invalid class exclusion pattern(s) for instrumentation monitor type in scope scope. Disabling instrumentation in scope scope.

Description

Specified exclusion patterns in instrumentation monitor could not be parsed

Cause

Malformed exclusion patterns in instrumentation monitor

Action

Specify exclusion patterns in instrumentation monitor in correct format

BEA-320139

Warning: Archive archiveName is not found during a data retirement operation.

Description

Data retirement is configured for an archive, but it does not yet exist.

Cause

Data retirement may be configured for a custom archive which does not yet exist.

Action

Ensure that the custom archive is created, or disable or remove this retirement configuration.

BEA-320140

Info: Scheduling data retirement tasks as per configuration.

Description

Begin scheduled data retirement processing

Cause

Begin scheduled data retirement processing

Action

No action is required.

BEA-320141

Error: An error was encountered while performing age based data retirement on archive archiveName

Description

An error was encountered while performing age based data retirement on archive

Cause

An error was encountered while performing age based data retirement on archive

Action

Contact Oracle Support

BEA-320142

Error: An error was encountered while performing size based data retirement on archive archiveName

Description

An error was encountered while performing size based data retirement on archive

Cause

An error was encountered while performing size based data retirement on archive

Action

Contact Oracle Support

BEA-320143

Info: Scheduled size data retirement tasks as per configuration.

Description

Processed configuration and scheduled data retirement tasks.

Cause

Finished processing data retirement configuration

Action

No action is required.

BEA-320144

Info: type operation started on archive archiveName

Description

Starting data retirement operation on named archive

Cause

Starting data retirement operation on named archive

Action

No action is required.

BEA-320145

Info: type operation completed on archive archiveName. Retired count records in time ms.

Description

Finished data retirement operation on named archive

Cause

Finished data retirement operation on named archive

Action

No action is required.

BEA-320146

Error: Failed to register dye dyeName at index dyeIndex.

Description

Specified dye could not be registered, possibly because a dye with the same name or index already exists.

Cause

Dye with the same name or index already exists

Action

Contact Oracle support.

BEA-320147

Error: Instrumentation system is disabled because the instrumentation library is invalid.

Description

Instrumentation engine configuration is corrupt or required DyeInjection monitor cannot be found.

Cause

Instrumentation engine configuration is corrupt or required DyeInjection monitor cannot be found.

Action

Contact Oracle support.

BEA-320148

Error: Required diagnostic monitor name is missing from the instrumentation library.

Description

A required diagnostic monitor can not be found in the instrumentation library.

Cause

Instrumentation engine configuration is corrupt.

Action

Contact Oracle support.

BEA-320149

Error: The DomainRuntime MBeanServer was not available for harvesting.

Description

The WLDF Harvester attempted to load the DomainRuntime MBeanServer for harvesting of metric data, but the MBeanServer could not be found.

Cause

The DomainRuntime MBeanServer could not be loaded by the Harvester.

Action

Contact Oracle support.

BEA-320150(retired)

Error: An error occurred adding an instance name for harvesting: msg

Description

The WLDF Harvester could not recognize the specifed harvested type instance name as a valid ObjectName or supported instance-name pattern.

Cause

The instance name or instance name pattern was not a valid JMX ObjectName or instance name pattern supported by the WLDF Harvester.

Action

Check that the instance name is a valid ObjectName, or an instance name pattern as specified in the WLDF Harvester documentation.

BEA-320151

Error: The instance name instanceName in the Watch configuration watchName is invalid.

Description

The WLDF Harvester could not recognize the specifed watch variable instance name as a valid ObjectName or supported instance-name pattern.

Cause

The instance name or instance name pattern was not a valid JMX ObjectName or instance name pattern supported by the WLDF Watch and Notifications framework.

Action

Check that the instance name is a valid ObjectName, or an instance name pattern as specified in the WLDF Watch and Notifications framework documentation.

BEA-320152

Error: An unexpected exception occurred removing the set of watched metrics "wvName" from the harvester: t

Description

An unexpected exception occurred removing a set of watched metrics from the harvester; this can occur during the deactivation of a WLDF Harvester configuration.

Cause

Deleting a set of watched metrics from the harvester that has already been removed, or one that was never activated within the harvester.

Action

Contact Oracle support.

BEA-320153

Warning: Instrumentation configuration for application "scope" has changed. However, it will take effect only after redeploying the application, since hot-swap is not enabled.

Description

Diagnostic monitors are added or removed from the instrumentation scope configuration. The classes need to be re-woven for them to take effect. However, hot-swap is not enabled, so they will not take effect until application is redeployed.

Cause

Hotswap is not enabled.

Action

Redeploy application, or restart server with diagnostic agent on command line to enable hot-swap.

BEA-320154

Error: Class redefinition failed after instrumentation configuration was changed for application "scope" : t

Description

An unexpected exception occurred while redefining classes after instrumentation configuration was updated.

Cause

An unexpected exception occurred while redefining classes after instrumentation configuration was updated.

Action

Contact Oracle support.

BEA-320155

Error: Inconsistent instrumentation handling information was specified in the same Pointcut definition for className : methodName : methodDesc

Description

Inconsistent instrumentation handling information was specified in the same Pointcut definition for className : methodName : methodDesc

Cause

The instrumentation configuration contains a Pointcut definition that specifies conflicting information for the method

Action

Review the pointcuts that specify the method listed in the error, and verify that there are not multiple definitions for that method which conflict. For example, one indicating an argument is not-sensitive while another indicates it is.

BEA-320156

Error: The renderer class className could not be loaded due to th, the following renderer will be used instead: rendererUsed

Description

The renderer class className could not be loaded due to th, the following renderer will be used instead: rendererUsed

Cause

The instrumentation configuration specified a renderer class that either was not found, is not accessible, or is not a renderer

Action

Verify the renderer class is correctly specified in the instrumentation configuration and that it is available to the server classloader

BEA-320157

Error: There was an error registering the log4j for data gathering operations

Description

The log4j libraries are invoked using reflection to register/deregister for log base data gathering.

Cause

The log4j libraries may not be in the CLASSPATH.

Action

Ensure that the log4j libraries are available when using Log watch rules with Log4j enabled.

BEA-320158

Error: There was an error detected while capturing the flight recorder image

Description

There was an error detected while capturing the flight recorder image

Cause

The exception specified provides details on the error encountered

Action

Review the exception information provided to determine the cause and action to take.

BEA-320159

Error: There was an error detected while initializing the Flight recording

Description

There was an error detected while initializing the Flight recording

Cause

The exception specified provides details on the error encountered

Action

Review the exception information provided to determine the cause and action to take.

BEA-320160

Error: The type based renderer class className for type typeClassName could not be loaded due to typeClassName, that type based renderer will not be used

Description

The type based renderer class className for type typeClassName could not be loaded due to typeClassName, that type based renderer will not be used

Cause

The instrumentation configuration specified a type based renderer class that either was not found, is not accessible, is not a renderer, or the type itself is not found or loadable

Action

Verify the type based renderer class and type class are correctly specified in the instrumentation configuration and they are available to the server classloader

BEA-320161

Error: Legacy Spring instrumentation API was called for an unknown method method

Description

Legacy Spring instrumentation API was called for an unknown method method

Cause

Legacy Spring instrumentation API was called for an unknown method method

Action

Instrument Spring using the tools in the current release

BEA-320162

Warning: Legacy Spring instrumentation API was called

Description

Legacy Spring instrumentation API was called

Cause

Legacy Spring instrumentation API was called

Action

Legacy Spring features should function normally but you should instrument Spring using the tools in the current release

BEA-320163

Error: Wildcarded types are not allowed to be marked as being insensitive with %

Description

Wildcarded types are not allowed to be marked as being insensitive with %

Cause

A % character was specified for a wildcarded type such as * or ..., this is not allowed as it could lead to inadvertantly exposing a type that should be treated as being sensitive

Action

Review the pointcuts that specify the % character to ensure that is not supplied for any types that are wildcarded using * or ...

BEA-320164

Error: Circular class load detected during stackmap frame computation for className

Description

Circular class load was detected during stackmap frame computation

Cause

An attempt was made to class load the class currently being instrumented, this is not supported.

Action

Do not instrument the class that encountered the cycle

  Back to Top