Skip Headers
Oracle® WebLogic Server Error Messages Reference
12c Release 1 (12.1.1)

Part Number E26117-01
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

1 BEA-000001 to BEA-2160002

BEA-000001: Server must be started by Node Manager when consensus leasing is enabled.
Cause: The server was not started by Node Manager.
Action: Start the server using Node Manager.

Level: 1

Type: INTERNAL_ERROR

Impact: ConsensusLeasing

BEA-000101: Cannot resolve ClusterAddress: {0}
Cause: The cluster address {0} could not be resolved. ClusterAddress should be a DNS name that maps to multiple IP addresses.
Action: Set the correct ClusterAddress property for the cluster.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000102: Joining cluster {0} on {1}:{2}
Cause: The server has joined cluster {0}.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000103: Disconnecting from cluster {0}
Cause: When a server is suspended, it is no longer a member of cluster {0}.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000104: Cluster members are running incompatible versions. Local version: {0}. Remote version ({1}): {2}
Cause: This server is a different version than other servers in this cluster.
Action: Ensure that all members of this cluster are running the same version.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000105: The server is leaving the cluster because it is an incompatible version.
Cause: This server is running a different version of WebLogic Server.
Action: Set a different multicast address for this cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000107: Failed to install {0} in place of those currently installed due to {1}.
Cause: An error occurred while resolving non-local conflicting offers for a node in the JNDI tree.
Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000108: Attempt to retract offer {0}, which is neither installed nor pending.
Cause: An attempt was made to retract an offer, which was neither previously installed nor is in the conflict resolution stage.
Action: No action is required.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000109: An error occurred while sending multicast message: {0}.
Cause: An error occurred while trying to send a message over multicast.
Action: WebLogic Server will try to recover from this error. If the problem continues to persist, make sure that the network infrastructure and NIC are functioning properly. If you believe no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000110: Multicast socket receive error: {0}.
Cause: An error occurred while trying to receive a message over the multicast.
Action: Ensure that the NIC is functioning properly. If it appears that no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000111: Adding {0} with ID {2} to cluster: {1} view.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000112: Removing {0} from cluster view due to timeout.
Cause: Removing {0} from cluster as it failed to send heartbeats over the multicast in the past 30 seconds.
Action: If a server has been shut down or suspended, no action is required. If the remote server {0} appears to be hung, take thread dumps and send them to My Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000113: Removing {0} from cluster view due to PeerGone.
Cause: The TCP/IP connection to server {0} was lost.
Action: If a server has been shut down or suspended, no action is required. If the remote server {0} appears to be hung, take thread dumps and send them to My Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000114: Failed to find cluster license: {0}
Cause: A valid license file is required to run clusters.
Action: Contact an Oracle sales representative for a valid license.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000115: Lost {0} multicast message(s).
Cause: This is an informational message. When a server joins a stable cluster, this message will appear since multicast messages sent out by servers in the cluster were not received.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000116: Failed to join cluster {0} at address {1} due to: {2}.
Cause: This happens if you specify an incorrect multicast address for the cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.
Action: Set a valid multicast address and try again.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000117: Received a stale replication request for object {0}.
Cause: This happens when a network problem exists, or one of the servers is taking a long time to collect garbage, causing the virtual machine to freeze.
Action: Tune garbage collection so that it does not pause. If the problem still persists, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000118: Lost {0} replication updates of object {1}.
Cause: If the secondary failed to receive some of the updates, it indicates this to the primary server by causing a NotFoundException to the primary so that the primary server can recreate the session state.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000119: Missing multicast address for cluster: {0}. Set the MulticastAddress="a.b.c.d" property for the cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.
Cause: The cluster does not have a defined multicast address.
Action: Specify a valid multicast address.

Level: 1

Type: INTERNAL_ERROR

Impact: Cluster

BEA-000120: Received error while creating ClusterRuntimeMBean.
Cause: The JMX framework failed to initialize the ClusterRuntimeMBean.
Action: Check the cluster configuration. If it appears that there are no configuration problems, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000121: Two domains in the same LAN should not use the same multicast address. Domains in conflict are {0} and {1}.
Cause: Two clusters on the local area network are using the same multicast address.
Action: Change the multicast address of either domain {0} or {1}.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000122: Clusters {0} and {1} cannot use the same multicast address.
Cause: Multiple clusters in the same domain are using the same multicast address.
Action: For efficiency purposes, use two different multicast addresses.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000123: Conflict start: You tried to bind an object under the name {0} in the JNDI tree. The object {1} is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.
Cause: The cluster is not homogeneous. Two servers in the cluster are providing different services under the same name {0}. If the object is non-clusterable, only one server in the cluster can provide this service.
Action: There are various options. 1. Make the object clusterable. 2. Change the JNDI name of the object under which it is bound. 3. Make sure the object gets deployed only on one server. 4. Deploy the service on all the servers. However, binding it into the JNDI tree, set the replicate bindings property to false.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000124: Conflict start: The object {1} you tried to bind under the name {0} in the JNDI tree is clusterable but is incompatible. Ensure that all the servers in the cluster use an identical copy of the object.
Cause: The object {1} is clusterable. However, it implements different or incompatible interfaces on different servers.
Action: Ensure that all the servers in the cluster use an identical copy of the object.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000125: Conflict resolved: {0} for the object {1} under the bind name {0} in the JNDI tree.
Cause: Corrective action was taken to resolve the conflict.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000126: All session objects should be serializable to replicate. Check the objects in the session. Failed to replicate a non-serializable object.
Cause: Objects in the session are not serializable or externalizable.
Action: Ensure that all user-defined objects in the HTTP session are serializable.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000127: Adding {0} to the cluster.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000128: Updating {0} in the cluster.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000129: Removing {0} from the cluster.
Cause: This is an informational message.
Action: No action is required unless you did not shut down a server.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000133: Waiting to synchronize with other running members of {0}.
Cause: The cluster member is waiting to synchronize cluster information with other cluster members before completing startup and entering running mode.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000137: Error sending multicast message: {0}.
Cause: The multicast message failed to send due to an IOException.
Action: Enable cluster debugging to see a detailed message.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000138: Listening for announcements from cluster {0} on {1}:{2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000139: There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name {0} and they are using the same address {1} and port {2}.
Cause: There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name {0} and they are using the same address {1} and port {2}.
Action: Change either the multicast address or the multicast port.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000140: Failed to deserialize statedump from server {0} with {1}.
Cause: The server failed to deserialize an object since it does not have the class definition. This usually happens if the application classes are not deployed on all the nodes in the cluster. It is preferable to deploy beans to all the nodes of the cluster.
Action: Ensure that all the classes are available on all the nodes of the cluster.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000141: TCP/IP socket failure occurred while fetching state dump over HTTP from {0}.
Cause: An IOException occurred in the operating system.
Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support with the stack trace for further analysis.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000142: Trying to download cluster JNDI tree from server {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000143: Trying to download JNDI tree from a server listening on {0}.
Cause: This is an informational message.
Action: If this message continues to appear, ensure that the network is stable. Contact My Oracle Support for further assistance.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000144: Managed Server {0} has been suspended or shut down.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000145: Managed Server {0} is tagged as a migratable server. A cluster that has migratable servers should configure a JDBC data source to ensure that the migratable server is highly available.
Cause: The cluster is misconfigured.
Action: Configure the DataSourceForAutomaticMigration property.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000147: Server "{0}" failed to renew lease in the {1}.
Cause: The server failed to renew the lease on time.
Action: No action is required.

Level: 1

Type: WARNING

Impact: Cluster

BEA-000148: Migratable server "{0}" is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should have at least a couple of machines assigned to it for automatic migration.
Cause: The migratable server is misconfigured.
Action: Ensure that the server is targeted to a machine and restart the migratable server.

Level: 1

Type: WARNING

Impact: Cluster

BEA-000149: Server failed to get a connection to the {1} during {0}.
Cause: The database or the consensus leasing basis appears to be down.
Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis the server is in the minority partition and the leasing basis is in some other partition that is not reachable.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000150: Server failed to get a connection to the {1} in the past {0} seconds for lease renewal. Server will shut itself down.
Cause: The database or consensus leasing basis appears to be down.
Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis, the server is in the minority partition and the leasing basis is in some other partition that is not reachable.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000151: Server "{0}" has taken over the role of Cluster Master.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000152: Server "{0}" lost the privileges to be the Cluster Master.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000153: Cluster is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should at least have a couple of machines assigned to it for automatic migration.
Cause: The cluster is misconfigured.
Action: Assign a pool of machines for automatic migration and refer to WebLogic Server documentation for more details.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000154: Cluster is misconfigured. The remote cluster address {0} is not a valid URL.
Cause: The server is misconfigured.
Action: Set the correct remote cluster address and restart the servers. If it is not clear on how to set remote ClusterAddress, refer to WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000155: Configured cluster address is invalid : {0}. Constructing cluster address dynamically.
Cause: The cluster configuration is invalid.
Action: Ensure that the cluster address contains either a DNS name or a comma-separated host list (or IP list) or a comma-separated host:port list (or IP:port list).

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000156: Could not send out new attributes for cluster member {0}: {1}.
Cause: There was a problem sending out changed member attributes.
Action: Examine the server logs.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000158: Server has stopped sending cluster heartbeats and announcements. It is still receiving heartbeats and announcements from other cluster members.
Cause: The server is going out of the cluster as a result of the suspend or shutdown operation.
Action: No action is required

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000159: The clocks of the machines hosting local server and remote server "{0}" are off by {1} seconds
Cause: The clocks of the machines hosting servers in the cluster are not synchronized.
Action: Ensure that all the machines are synchronized to the same time.

Level: 1

Type: WARNING

Impact: Cluster

BEA-000160: A request to synchronize the JNDI tree has been made over an insecure channel. Configure a secure HTTP channel for all of the servers in the cluster.
Cause: The cluster was configured to encrypt multicast data but the request to synchronize the JNDI tree was done on a non-secure channel (HTTP). To secure the cluster completely, configure a secure HTTP channel for all of the servers in the cluster.
Action: Configure a secure HTTP channel on all of the servers in the cluster.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000161: Multicast message from server {0} appears to have been tampered with.
Cause: The authenticity of the message could not be verified.
Action: Ensure that the network is not being hijacked.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000162: Starting "{0}" replication service with remote cluster address "{1}"
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000163: Stopping "{0}" replication service
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000164: Synchronized cluster JNDI tree from server {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000165: Some other domain has a cluster that is configured to use the same multicast address and port as a cluster in {0}. Two domains in the same LAN should not use the same multicast address.
Cause: Two clusters on the local area network are using the same multicast address.
Action: Change the multicast address of either domain.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000166: Some other cluster in this domain is configured to use the same multicast address as {0}. Clusters cannot use the same multicast address.
Cause: Multiple clusters in the same domain are using the same multicast address.
Action: For efficiency purposes, use two different multicast addresses.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000167: Some services failed to roll back successfully when trying to abort the migration: {0}.
Cause: An exception caused the rollback to fail: {0}.
Action: It would be safest to shut down this server so that any lingering services will stop. They will not be automatically restarted upon reboot. Once the cause of the rollback has been fixed, attempts to migrate to this server should be successful.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000168: Failed to restart/migrate server "{0}" because of {1}
Cause: There was an error while restarting migratable server: {1}
Action: Examine the server logs.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000170: The server {0} did not receive the multicast packets that it sent.
Cause: Each WebLogic Server instanec is expected to receive the messages it multicast to its multicast group. Since the server does not receive its own messages, the multicast address configuration in the cluster configuration or the interface address specification may be wrong.
Action: Ensure that the cluster configuration and server interface configuration are valid

Level: 1

Type: ERROR

Impact: Cluster

BEA-000171: Failed to load the custom Singleton Services SQL Query Helper: {0}, because of {1}.
Cause: The most likely cause for failing to load the named class is either a typo in the name of the class or that the class is missing from the server classpath.
Action: Ensure that the provided classname is valid and that the class exists in the classpath of the server.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000172: TCP/IP socket failure occurred while fetching state dump over HTTP from {0}. Error message received: {2}. The request was generated by {3}. {1}
Cause: An IOException occurred in the operating system.
Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support with the stack trace for further analysis.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000176: {0} does not specify a machine.
Cause: {0}'s configuration does not specify the machine on which it is running. Machines must be specified if scripts are to be executed when migrations happen.
Action: Specify the machine on which {0} is running in the server's console page.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000178: Failed to execute {0} because of {1}.
Cause: While trying to run {0}, an exception occurred: {1}.
Action: Check that the script, {0}, is fully debugged. It may help to run the script by hand to see if any errors are raised.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000179: {0} failed while altering its lease.
Cause: An exception occurred: {1}.
Action: Ensure that, if a database is being used for leasing, it is available.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000180: Unable to retrieve Job {0} from the database. The retrieval failed with {1}
Cause: An error occurred while reading a job from the database.
Action: ENsure that the classes corresponding to the job are present in the server classpath and are of the correct version.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000182: Job Scheduler created a job with ID {0} for TimerListener with description {1}
Cause: Job Scheduler created an entry in the database for a submitted job.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000183: Successfully cancelled job with ID {0}
Cause: Job Scheduler removed a job entry from the database based on application request
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000184: This server did not attempt to renew its lease for {0} seconds. The server may need to be restarted or migrated.
Cause: The thread that is supposed to regularly renew the lease has become blocked for some reason.
Action: Ensure that the server is not overloaded with work and that there are enough system resources available on the machine.

Level: 1

Type: WARNING

Impact: Cluster

BEA-000185: Despite the delay in the lease-renewing thread, the server has successfully renewed its lease. It is no longer in imminent risk of being migrated or restarted.
Cause: The thread that is supposed to regularly renew the lease became blocked, but is running properly again and has successfully renewed the lease.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000186: An error was encountered while migrating {0}: {1}
Cause: See the error in the message body.
Action: Ensure that there are enough candidate servers running in the cluster.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000187: The Singleton Service {0} is now registered on this server. This server may be chosen to host this service.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000188: The Singleton Service {0} is no longer registered on this server.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000189: The Singleton Service {0} is now active on this server.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000190: The Singleton Service {0} has been deactivated on this server.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000191: Now monitoring the Migratable Server {0}
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000192: A running server was not found to host {0}. The server will retry in a few seconds.
Cause: All running servers failed when asked to activate {0}.
Action: Ensure that there is at least one active candidate server for this service and that there is no bug in the activate() method. The service will be tried on all running servers in another few seconds.

Level: 1

Type: WARNING

Impact: Cluster

BEA-000193: The JTA service for {0} has failed, but {0} is still running. JTA cannot be migrated from a running server.
Cause: The JTA service failed.
Action: Check the logs of {0}; {0} should be restarted once the cause of the error has been determined and fixed. Upon restart, the JTA service will be migrated and running transactions recovered.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000194: An error was encountered while trying to report a migration event: {0}.
Cause: The most likely cause is the Administration Server being unavailable. If this is intended, this message can be ignored.
Action: If monitoring information is desired, the Administration Server should be running and reachable.

Level: 1

Type: WARNING

Impact: Cluster

BEA-000195: An error was encountered while trying to save a migration event. The error was: {0}.
Cause: An internal error occurred while trying to create a runtime MBean to encapsulate this data.
Action: Contact My Oracle Support and provide the stack trace for further analysis.

Level: 1

Type: WARNING

Impact: Cluster

BEA-000196: Received data about a migration of type {0}, but no such type is recognized by the Administration Server.
Cause: If the Managed Servers have been upgraded to a newer version of WebLogic Server, they may be reporting data that the Administration Server does not know how to handle.
Action: Upgrade the Administration Server to the same version as the cluster members.

Level: 1

Type: WARNING

Impact: Cluster

BEA-000197: Listening for announcements from cluster using unicast cluster messaging
Cause: Unicast cluster messaging mode is enabled.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-000198: All replication calls for cluster {0} must be made over channel {1}
Cause: All replication calls for cluster {0} must be made over channel {1}
Action: Check the configured channel for replication calls.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000199: Replication calls can only be made by {0} over {1} channel
Cause: Replication calls can only be made by {0} over {1} channel
Action: Check the roles of the users for whom the replication calls are being made.

Level: 1

Type: ERROR

Impact: Cluster

BEA-000214: WebLogic Server "{1}" version: {0} Copyright (c) 1995, 2011, Oracle and/or its affiliates. All rights reserved.
Cause: The startup banner used when a server starts.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000215: Loaded license: {0}.
Cause: This prints from the location from which the license file was loaded.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000220: Cannot shut down the server because the request was from a null user (Principal).
Cause: The server refused to shut down since the command came from an unauthorized user.
Action: Only users within the Administrators group can shut down the server. Retry the command with a user who has administrator credentials.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000221: Cannot shut down the server because the request was from a nameless user (Principal).
Cause: The server refused to shut down since the command came from an unauthorized user.
Action: Only users within the Administrators group can shut down the server. Retry the command with a user who has administrator credentials.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000222: Cannot disable server logins because the request was from a null user (Principal).
Cause: The server refused to lock itself since the command came from an unauthorized user.
Action: Retry the command with a user who has the privileges necessary to perform this operation.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000223: Cannot disable server logins because the request was from a nameless user (Principal).
Cause: The server refused to lock itself since the command came from an unauthorized user.
Action: Retry the command with a user who has the privileges necessary to perform this operation.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000224: Cannot enable server logins because the request was from a null user (Principal).
Cause: The server refused to unlock itself since the command came from an unauthorized user.
Action: Retry the command with a user who has the privileges necessary to perform this operation.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000225: Cannot enable server logins because the request was from a nameless user (Principal).
Cause: The server refused to unlock itself since the command came from an unauthorized user.
Action: Retry the command with a user who has the privileges necessary to perform this operation.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000226: The enabling of server logins has been requested by {0}.
Cause: The server has been requested to unlock itself and enable server logins again.
Action: No action is needed.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000227: Server logins have been enabled.
Cause: Server logins have been enabled.
Action: No action is needed.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000228: The disabling of server logins has been requested by {0}.
Cause: A LOCK command was issued by an administrator.
Action: No action is needed.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000229: Server logins have been disabled.
Cause: A LOCK command was issued by an administrator.
Action: No action is needed.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000231: Waiting {0} seconds for server shutdown.
Cause: A shutdown command was issued with a wait time. The server will wait the specified number of seconds before starting shutdown.
Action: A cancel shutdown command can be issued during the wait time to cancel the shutdown process. Otherwise no action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000232: Server shutdown is commencing now and is irreversible.
Cause: A shutdown command was issued by an administrator.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000236: Stopping execute threads.
Cause: An administrator issued a shutdown command.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000238: Shutdown has completed.
Cause: Shutdown has completed.
Action: No action needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000240: Cannot cancel the server shutdown because the request was from a null user (Principal).
Cause: Server shutdown could not be canceled because the user account that was used to issue the cancel command does not have the appropriate privileges.
Action: The command can only be executed by a user from the administrator group. Retry the command with a user account that has administrator privilieges.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000241: Cannot cancel the server shutdown because the request was from a nameless user (Principal).
Cause: Server shutdown could not be canceled because the user account that was used to issue the cancel command does not have the appropriate privileges.
Action: The command can only be executed by a user from the administrator group. Retry the command with a user account that has administrator privilieges.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000242: Cannot cancel server shutdown because there is no shutdown in progress.
Cause: The server shutdown cannot be canceled as the server is not in the state 'Shutdown in Progress'.
Action: No action is needed. Check the Administration Console for the state of the server.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000243: It is too late to cancel the server shutdown because the shutdown is already in progress.
Cause: The server has already started to shut down. It is too late to cancel shutdown at this point.
Action: No action is needed.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000244: Canceling server shutdown.
Cause: An administrator has issued a cancel shutdown operation.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000246: Server shutdown has been canceled and logins are enabled.
Cause: The cancel shutdown operation was successful.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000248: An exception occurred while trying to find a localized T3Srvr message, message ID {0}, {1}
Cause: The localized version of the message could not be found.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000249: Because the weblogic.ConsoleInputEnabled property is set to true, the server can only be shut down from the command line. Type the command "shut" in the window in which the server was started.
Cause: The weblogic.ConsoleInputEnabled property was set true on the server startup command line.
Action: To shut down the server, type the command "shut" in the window in which the server was started.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000251: The server switched to the group "{0}".
Cause: A non-privileged group was specifed. The server switched to the specified group after starting.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000252: Cannot switch to the group "{0}". {1}
Cause: The server was unable to switch to the specified group.
Action: Ensure that the specified group exists.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000253: Switched to the user "{0}".
Cause: A non-privileged user was specified. The server switched to the specified user after starting.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000254: Cannot switch to the user "{0}". {1}
Cause: The server could not switch to the specified non-privileged user.
Action: Ensure that the specified user exists.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000256: Invoking {0}.main({1})
Cause: The server configuration specifies startup and shutdown classes to run.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000257: Exception reading command: {0}
Cause: An exception occurred while reading commands from the shell window.
Action: Disable the shell command input property weblogic.ConsoleInputEnabled.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000258: Command [{0}]
Cause: The Administration Console received the specified command and is about to execute it.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000259: Administration Console: profiling enabled.
Cause: Profiling has been enabled in the Administration Console.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000260: Administration Console: profiling disabled.
Cause: Profiling has been disabled in the Administration Console.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000261: The system user is not permitted to shut down, {0}.
Cause: The server was not shut down because the user is not authorized to shut down the server.
Action: See the exception text in {0} for more information on diagnosing the problem. See the previous log messages for more information on authorization failure. If the user does not have permission to shut down the server, but should, use the Administration Console to define a policy for this server that allows the user to shut down.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000262: No such command: {0}.
Cause: The unknown command was entered.
Action: Refer to the list of known commands.

Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000263: GC: before free/total={0}/{1} ({2}%).
Cause: The GS statistics are shown before forcing GC.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000264: GC: after free/total={0}/{1} ({2}%).
Cause: The GS statistics are shown after forcing GC.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000265: Attempt to unbind ClientContext "{0}" that is not bound.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000266: {0} has {1,choice,1#one pending ExecuteRequest|2#{1,number} pending ExecuteRequests}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000267: {0} had a negative workQueueDepth of {1}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000268: Failed to send unsolicted message "{0}" to client, {1}
Cause: Deprecated functionality
Action: Deprecated functionality

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000269: The connection to the client using "{0}" has been unexpectedly lost due to {1}. The server is initiating a hard disconnect.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000270: Timing out "{0}" because it was idle.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000271: Ignoring a repeated request to schedule the death of "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000272: Scheduling the death of "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000273: Removing "{0}" because of hard disconnect timeout.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000274: Removing "{0}" because of soft disconnect timeout.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000275: Soft disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000276: Hard disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000277: Idle disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000283: Failed to marshal response, {0}
Cause: Deprecated functionality
Action: Deprecated functionality

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000284: Unexpected failure to marshal response, {0}
Cause: Deprecated functionality
Action: Deprecated functionality

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000286: Failed to invoke startup class "{0}", {1}.
Cause: An exception occurred in a startup class.
Action: Determine the error in the startup class code and restart the server. To work around the problem, set the "abort on startup failure" property to false.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000287: Invoking startup class: {0}.startup({1}).
Cause: The startup class was invoked with the specified arguments.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000288: {0} reports: {1}.
Cause: The return value of the startup class was logged.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000289: Failed to invoke shutdown class "{0}", {1}.
Cause: An exception occurred in a shutdown class.
Action: Determine the error in the shutdown class code and restart the server.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000290: Invoking shutdown class: {0}.shutdown({1}).
Cause: The server is invoking shutdown classes as a part of shutdown.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000291: {0} reports: {1}.
Cause: The server logs the return value of the shutdown class.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000297: Inconsistent security configuration, {0}
Cause: An exception occurred in SSL initialization.
Action: Look at the exception in {0} for more information on diagnosing the problem.

Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000298: Certificate expires in {0} days: {1}
Cause: The certificate is about to expire.
Action: Obtain a new server certificate or trusted CA certificate before it expires.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000306: Cannot use SSL because no certificates have been specified in the WebLogic Server configuration.
Cause: No certificates can be found for use by SSL.
Action: If using a keystore for the server certificate, set the ServerPrivateKeyAlias in the SSL MBean. If using the Server Certificate File, ensure that valid certificates are contained within the file.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000307: Exportable key maximum lifespan set to {0} uses.
Cause: The server logs the exportable key maximum lifespan so it is clear what lifespan is being used.
Action: Verify that the lifespan is the desired value.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000314: The execution class "{0}" did not retrieve a T3Executable or T3ExecutableLazy.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000315: Unexpected failure of T3ExecutableLazy, {0}
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000316: enableWatchDog() is not permitted from within a server.
Cause: Deprecated functionality
Action: Deprecated functionality

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000317: disableWatchDog() is not permitted from within a server.
Cause: Deprecated functionality
Action: Deprecated functionality

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000320: Error creating runtime MBean for execute queue {0}.
Cause: An internal system error occurred.
Action: Contact My Oracle Support with the server logs.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000329: Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in production mode.
Cause: The production mode of the server is enabled.
Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000330: Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in production mode.
Cause: The production mode of the server is enabled.
Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script file to change the server mode.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000331: Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in development mode.
Cause: The production mode of the server is disabled (default).
Action: Set the weblogic.ProductionModeEnabled property of the domain in the configuration script to change the server mode.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000332: Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in development mode.
Cause: The production mode of the server is disabled (default).
Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000333: Queue usage is greater than QueueLengthThresholdPercent "{0}%" of the maximum queue size. An attempt will be made to allocate ThreadsIncrease "{1}" thread(s) to help.
Cause: The server is under high load.
Action: Review the execute queue settings.

Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-000337: {0} has been busy for "{1}" seconds working on the request "{2}", which is more than the configured time (StuckThreadMaxTime) of "{3}" seconds. Stack trace: {4}
Cause: The server is extremely busy or the thread is hung.
Action: Monitor the method that the hung thread is running. Use the Administration Console monitor execute request feature or take a thread dump (weblogic.Admin THREAD_DUMP).

Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000339: {0} has become "unstuck".
Cause: A thread previously stuck is now available.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000342: Unable to initialize the server: {0}.
Cause: An exception occurred during the server initialization.
Action: Analyze the weblogic.log file to determine why the server did not initialize completely.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000343: The health monitor for "{0}" failed to register because of exception "{1}".
Cause: Refer to the exception printed in the log message.
Action: Refer to the exception printed in the log message.

Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-000344: The health monitor for "{0}" failed to unregister because of exception "{1}".
Cause: Refer to the exception printed in the log message.
Action: Refer to the exception printed in the log message.

Level: 1

Type: WARNING

Impact: WebLogicServer

BEA-000357: Started WebLogic Server independent Managed Server "{0}" for domain "{1}" running in development mode.
Cause: The server started with the Managed Server independence mode enabled.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000358: Started WebLogic Server independent Managed Server "{0}" for the domain "{1}" running in production mode.
Cause: The production mode of the server is enabled.
Action: Set the ProductionModeEnabled property of the domain in the configuration file to change the server mode.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000360: The server started in {0} mode.
Cause: The startup mode was set to SUSPENDED.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000362: Server failed. Reason: {0}
Cause: Inspect the log file for indications of the root cause of the failure.
Action: Inspect the log file for indications of the root cause of the failure.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000365: Server state changed to {0}.
Cause: The server progressed through the startup or shutdown sequence.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000366: The server failed to shut down. Exception: {0}
Cause: Inspect the log file for indications of the root cause of the failure.
Action: Inspect the log file for indications of the root cause of the failure.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000371: An error occurred during server shutdown: {0}.
Cause: Inspect the log file for indications of the root cause of the failure.
Action: Inspect the log file for indications of the root cause of the failure.

Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000374: Waiting for ExecuteQueue {0} to finish {1} pending requests.
Cause: The server found pending requests in one of the execute queues while suspending. The server will wait for the requests to complete.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000377: Starting WebLogic Server with {0} Version {1} from {2}.
Cause: The server is starting.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000378: The server failed to shut down within the configured timeout of {0} seconds. The server process will now exit.
Cause: Forced shutdown is taking too long to complete.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000381: ServerLifeCycle operation failed. Message: {0} {1}
Cause: A server operation, such as shutdown, failed.
Action: If the error is not application related, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000382: A critical service failed. The server will automatically transition to the ADMIN state.
Cause: A server lifecycle operation or a critical service failed.
Action: The server logs contain information about the failure. If the error is not application related, contact My Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000383: A critical service failed. The server will shut itself down.
Cause: A critical service failed.
Action: The server logs contain information about the failure. If the error is not application related, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: WebLogicServer

BEA-000384: A fatal configuration failure occurred during startup. Check if the config.xml file contains invalid entries. Reason: {0}
Cause: The server failed to start due to invalid configuration.
Action: Check if the config.xml file contains invalid entries. Contact My Oracle Support for more information.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000385: Server health failed. Reason: {0}
Cause: Inspect the log file for indications of the root cause of the failure.
Action: Inspect the log file for indications of the root cause of the failure.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000386: Server subsystem failed. Reason: {0}
Cause: Inspect the log file for indications of the root cause of the failure.
Action: Inspect the log file for indications of the root cause of the failure.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000388: JVM called the WebLogic Server shutdown hook. The server will force shutdown now.
Cause: The JVM called the WebLogic Server shutdown hook. The server will force shutdown now.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000394: Deadlock detected: {0}.
Cause: There are threads deadlocked in the server.
Action: Report this error to My Oracle Support if the deadlock involves WebLogic Server internal code.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000395: The following extensions directory contents added to the end of the classpath: {0}.
Cause: Extensions directory contents were added to the classpath.
Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: WebLogicServer

BEA-000396: Server {0} has been requested by {1}.
Cause: A request was made to perform the specified server operation.
Action: No action is needed.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000398: WebLogic Server "{0}" for domain "{1}" is running with class caching enabled in production mode. Class caching is not supported in production mode. Disable class caching by setting CLASS_CACHE to "false" in the startWeblogic script and then restarting the server.
Cause: Class caching is turned on by default when server production mode is enabled.
Action: Set the CLASS_CACHE to false in the startWeblogic script and then restart the server.

Level: 1

Type: INTERNAL_ERROR

Impact: WebLogicServer

BEA-000401: Socket queue full, dropping socket {0}.
Cause: This is an internal error.
Action: Capture the errors and send the server log files to My Oracle Support.

Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000402: There are: {0} active sockets, but the maximum number of socket reader threads allowed by the configuration is: {1}. The configuration may need altered.
Cause: When non-native I/O is used, I/O is performed in a blocking manner. Therefore, if the number of socket reader threads is less than the number of active sockets, performance may degrade significantly.
Action: Optimally, increase the ThreadPoolPercentSocketReaders, or the ThreadPoolSize, or both. Optimally, decrease the SocketReaderTimeoutMinMillis, or the SocketReaderTimeoutMaxMillis, or both.

Level: 1

Type: WARNING

Impact: Socket

BEA-000403: IOException occurred on socket: {0} {1}.
Cause: An unexpected IOException occurred while performing I/O for the socket.
Action: Check network connectivity. If the situation persists after environmental issues are resolved, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: Socket

BEA-000404: ThreadDeath in processSockets {0}.
Cause: This is an internal error.
Action: Capture the errors and send the server log files to My Oracle Support.

Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000405: Uncaught Throwable in processSockets {0}.
Cause: This is an internal error.
Action: Capture the errors and send the server log files to My Oracle Support.

Level: 1

Type: ERROR

Impact: Socket

BEA-000406: {0}
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000409: Problem on socket: {0} {1}
Cause: An exception occurred while registering the socket with the muxer. It is possible that the file descriptor cannot be obtained from the socket.
Action: Capture the errors and send the server log files to My Oracle Support.

Level: 1

Type: ERROR

Impact: Socket

BEA-000414: Could not initialize the POSIX performance pack.
Cause: The shared library for the POSIX performance pack could not be loaded.
Action: Ensure that the muxer shared library (libmuxer.so) exists in a directory that is in the LD_LIBRARY_PATH. If the situation persists, contact My Oracle Support.

Level: 1

Type: INTERNAL_ERROR

Impact: Socket

BEA-000415: System has file descriptor limits of soft: {0}, hard: {1}
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000416: Using effective file descriptor limit of: {0} open sockets and files.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000421: Uncaught Throwable in processSockets {0}.
Cause: This is an internal error.
Action: Capture the errors and send the server log files to My Oracle Support.

Level: 1

Type: ERROR

Impact: Socket

BEA-000429: Muxer received error: {0} {1}.
Cause: An unexpected error occurred while processing socket I/O requests.
Action: Capture the errors and send the server log files to My Oracle Support.

Level: 1

Type: ERROR

Impact: Socket

BEA-000431: Accepted connection: filtering is set to: "{0}", remote address: "{1}", remote port: "{2,number,0}", local address: "{3}", local port: "{4,number,0}", protocol: "{5}"
Cause: This is an informational message for the administrator.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000432: Unable to load performance pack. Using Java I/O instead. {0}
Cause: The native library for the performance pack was unable to be loaded.
Action: Ensure that the classpath and the environment is set up properly. If the situation persists, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: Socket

BEA-000435: Unable to initiate read for the socket. The maximum allowed number of pending I/O requests ({0}) has been exceeded.
Cause: This is an internal error.
Action: Capture the errors and send the server log files to My Oracle Support.

Level: 1

Type: ERROR

Impact: Socket

BEA-000436: Allocating {0} reader threads.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000438: Unable to load performance pack. Using Java I/O instead. {0}
Cause: The native performance pack was unable to be loaded.
Action: Ensure that the appropriate path for the native libraries is set properly in the environment.

Level: 1

Type: ERROR

Impact: Socket

BEA-000439: Unable to create the Java socket muxer.
Cause: This is an internal error.
Action: Ensure that the classpath is set properly. If the situation persists, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: Socket

BEA-000440: Unable to initiate I/O for {0} {1}.
Cause: The initiation of the I/O operation failed, which could have been caused by the network, I/O or other problems. It could also have been an internal error.
Action: Correct any conditions as suggested by the error message, if applicable. If the situation persists, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: Socket

BEA-000441: Unable to find internal data record for the socket {0}, with I/O completion result {1}
Cause: This is an internal error.
Action: If the situation persists, contact My Oracle Support.

Level: 1

Type: WARNING

Impact: Socket

BEA-000442: The connection attempt was rejected because the incoming protocol is not enabled on channel "{0}".
Cause: The connection attempt was rejected because a protocol was not enabled for this server, as determined by the ServerMBean, or was not enabled on this particular channel.
Action: Enable the protocol on the channel.

Level: 1

Type: WARNING

Impact: Socket

BEA-000443: The connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.
Cause: The connection attempt was rejected because the {1} protocol was not enabled for this server, as determined by the ServerMBean, or was not enabled on this particular channel.
Action: Enable the {1} protocol on the channel.

Level: 1

Type: WARNING

Impact: Socket

BEA-000444: Could not load the performance pack that can take advantage of the /dev/(e)poll device due to: {0}. Will attempt to use the performance pack that does not depend on the /dev/(e)poll device.
Cause: The operating system does not support the /dev/(e)poll or the device is not initialized.
Action: Ensure that the operating system supports the /dev/(e)poll device.

Level: 1

Type: WARNING

Impact: Socket

BEA-000445: Connection rejected, filter blocked {0}, {1}
Cause: The incoming message was not recognized as one of the supported protocols.
Action: Ensure that the server is configured for the relevant protocol.

Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000446: Native I/O enabled.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000447: Native I/O disabled. Using Java I/O.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Socket

BEA-000448: Socket channel support has been enabled for a JVM on which the feature is unsupported.
Cause: This error is caused by turning on a feature that is not supported on the underlying JVM.
Action: Either disable socket channel support or use a JVM version on which this feature is supported.

Level: 1

Type: ERROR

Impact: Socket

BEA-000449: Closing the socket, as no data read from it on {1}:{2} during the configured idle timeout of {0} seconds.
Cause: The WebLogic Server instance or the network may be overloaded, which is causing the socket to idle timeout.
Action: Capacity tuning of the server is required.

Level: 1

Type: WARNING

Impact: Socket

BEA-000451: Closing the socket, as end of file is encountered while reading from the socket to the ONS server at {0}.
Cause: The connection to the remote Oracle Notification Server (ONS) process might have been disconnected.
Action: Check the status of the remote ONS process.

Level: 1

Type: WARNING

Impact: Socket

BEA-000452: An exception occurred on the socket to the ONS server at {0}: {1}.
Cause: An exception occurred while reading from the socket. The connection to the remote Oracle Notification Server (ONS) process might have been disconnected.
Action: Check the network connectivity to the remote ONS process. If the situation persists after environmental issues are resolved, contact My Oracle Support.

Level: 1

Type: WARNING

Impact: Socket

BEA-000453: An exception occurred while processing the message sent from the ONS at {0}: {1}
Cause: An error occurred while parsing the message received from the remote ONS.
Action: Check the ONS log file for additional details.

Level: 1

Type: ERROR

Impact: Socket

BEA-000454: Unable to establish connection to the remote ONS process at {0}:{1}. Exception occurred while doing handshake: {2}
Cause: An exception occurred while doing handshake with the remote ONS process.
Action: Check the exception and ONS log file for additional details.

Level: 1

Type: ERROR

Impact: Socket

BEA-000455: Attempting to remove unregistered HandshakeCompletedListener: class={0}, instance={1}.
Cause: The unregistered HandshakeCompletedListener: class={0}, instance={1}, is attempting to be removed.
Action: The unregistered HandshakeCompletedListener: class={0}, instance={1}, is attempting to be removed.

Level: 1

Type: ERROR

Impact: Socket

BEA-000501: Peergone send failed - target unreachable.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000502: Peergone send failed - target already gone.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000503: Incoming message header or abbreviation processing failed. {0}
Cause: While processing an incoming message an error was encountered. It is likely that the message was corrupted.
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.

Level: 1

Type: ERROR

Impact: RJVM

BEA-000504: Unmarshal exception: received illegal command code: {0}
Cause: A message containing an invalid command code was received. This message cannot be processed. One of the possible reasons is that the message was corrupted in transit.
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.

Level: 1

Type: ERROR

Impact: RJVM

BEA-000505: Peer did not send us a valid heartbeat interval; using the default heartbeat specified as a property.
Cause: The incoming message has an invalid heartbeat interval. This is either due to message corruption in transit or to an invalid choice for the heartbeat interval on the peer that is attempting to establish communication with this JVM.
Action: If the peer that is attempting to establish communication is overriding the default heartbeat interval, ensure that a valid interval is used. If not, contact My Oracle Support with the server logs and configuration.

Level: 1

Type: ERROR

Impact: RJVM

BEA-000506: Closing: {0} because of {1}
Cause: This JVM has received an incoming message that is incompatible with the way the protocols are supposed to work.
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.

Level: 1

Type: ERROR

Impact: RJVM

BEA-000507: Could not create/send request to close duplicate connection message. {0}
Cause: Creation or sending of the message to request closing a connection caused an I/O error.
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.

Level: 1

Type: WARNING

Impact: RJVM

BEA-000508: ID: {0} in use by: {1}, can not install {2}
Cause: The ID {0} is already associated with and in use by {1} and hence cannot be used in association with {2}.
Action: Ensure that unique IDs are used in registration.

Level: 1

Type: ERROR

Impact: RJVM

BEA-000509: Finder not initialized.
Cause: This JVM was created without a valid finder.
Action: Ensure that a valid finder is used when creating this JVM.

Level: 1

Type: ERROR

Impact: RJVM

BEA-000510: Unsolicited response: {0}
Cause: A duplicate response has been received for a request that has already received its response.
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.

Level: 1

Type: WARNING

Impact: RJVM

BEA-000511: Unsolicited error response for: {0}
Cause: A duplicate error response was received for a request that has already received its response or its error response.
Action: This is most likely a temporary situation. No action is necessary. If this situation continues, contact My Oracle Support with the server logs and configuration.

Level: 1

Type: WARNING

Impact: RJVM

BEA-000512: New heartbeat period: {0} is different from established heartbeat period: {1}; using established heartbeat period
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000513: Failure in heartbeat trigger for RJVM: {0}. {1}
Cause: This error indicates a temporary failure in the heartbeat trigger mechanism.
Action: No action is required. This is usually a temporary failure.

Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000514: openConnection() failed. {0}
Cause: Possible causes are an invalid target address or the target not being active or reachable.
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.

Level: 1

Type: ERROR

Impact: RJVM

BEA-000515: execute failed {0}
Cause: A failure was encountered when handling the incoming HTTP message.
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.

Level: 1

Type: ERROR

Impact: RJVM

BEA-000519: Unable to connect to a remote server on address {1} and port {2,number,0} with protocol {0}. The exception is {3}
Cause: The target is either not reachable or is not active.
Action: Ensure that the target is active.

Level: 1

Type: WARNING

Impact: RJVM

BEA-000570: Network Configuration for Channel "{0}" Listen Address {1} Public Address {2} Http Enabled {3} Tunneling Enabled {4} Outbound Enabled {5} Admin Traffic Enabled {6}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: RJVM

BEA-000572: The server rejected a connection attempt {0} probably due to an incorrect firewall configuration or administrative command.
Cause: The incoming connection attempt was probably made through an address translating firewall. WebLogic Server needs to be correctly configured for this to work. This message can also occur if an administration connection attempt, requiring administrator level security, is made on a non-administrative port.
Action: Configure the public and private addresses for this WebLogic Server instance to reflect the configuration of the firewall. The private address is the actual address the server is running. The public address is the address that external clients use to connect.

Level: 1

Type: ERROR

Impact: RJVM

BEA-000600: Callback {0} failed: {1}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: Common

BEA-000601: AdminProxyWatchDog: Enabled. Interval = {0} secs.
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000602: AdminProxyWatchDog: Enable failed.
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: Common

BEA-000603: AdminProxyWatchDog: Disabled.
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000604: AdminProxyWatchDog: Disable failed.
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: Common

BEA-000605: Connectivity lost to WatchDog Client. Shutting down.
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: Common

BEA-000606: AdminProxyWatchDog: No echo received in last {0} minutes. Shutting down.
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: Common

BEA-000607: AdminProxyWatchDog: Echo Received.
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000608: AdminProxyWatchDog: Tick. diff = {0}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000609: An error occurred during server shutdown: {0}.
Cause: This is an internal error.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: Common

BEA-000611: No resources in the pool {0} will be tested, as the specified MaxUnavailable {1} has been reached.
Cause: The application MaxUnavailable attribute for this pool has been configured. Since the number of unavailable resources in the pool has reached or exceeded the configured limit, no more resources will be tested. Resources become unavailable to the application during the testing.
Action: Tune the MaxUnavailable attribute for the pool if so desired.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000612: All {1} resource instances currently available in the pool {0} are being tested.
Cause: This is a warning indicating that all currently available resources in the pool are being tested, and therefore some or all of them may become unavailable to the application for a short time.
Action: Reduce the current setting of the MaxUnavailable attribute for the pool.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000613: Testing of resources upon creation has been dynamically enabled for pool "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000614: Testing of resources upon creation has been dynamically disabled for pool "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000615: Testing of resources when being reserved has been dynamically disabled for pool "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000616: Testing of resources when being reserved has been dynamically enabled for pool "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000617: Testing of resources when being released has been dynamically enabled for pool "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000618: Testing of resources when being released has been dynamically disabled for pool "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000619: Unable to forcibly release resource "{1}" back into the pool "{0}". Received exception: {2}.
Cause: As part of the InactiveResourceTimeout feature, resources that are found to be inactive for the configured period of time are forcibly released back into the pool. The operation could not be performed for the indicated reason.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: Common

BEA-000620: Forcibly releasing inactive resource "{1}" back into the pool "{0}".
Cause: The resource was found to be unused by the application for the specified duration and is being forcibly released back into pool.
Action: Check application code for leakages of resource objects or tune the configured value of the relevant pool attribute.

Level: 1

Type: WARNING

Impact: Common

BEA-000621: Expected RemoteException, RuntimeException, or Error {0}
Cause: An unexpected low-level message was sent to the server.
Action: This is likely due to an internal client/server error that should be reported to My Oracle Support.

Level: 1

Type: ERROR

Impact: Common

BEA-000622: Ignoring an attempt to release resource "{1}" to pool "{0}" after the pool has been shut down.
Cause: Application is trying to release a resource to a pool after the pool has been shut down.
Action: Check application behavior. All resources should be closed before the application is shut down.

Level: 1

Type: WARNING

Impact: Common

BEA-000623: Setting CapacityIncrement for pool "{0}" to 1. The specified value of "{1}" is not valid.
Cause: The application had specified an invalid value for CapacityIncrement.
Action: Check and correct the specified value for CapacityIncrement for the indicated pool.

Level: 1

Type: WARNING

Impact: Common

BEA-000624: Setting frequency of testing of free resources in pool "{0}" to five seconds since the specified value of "{1}" is not valid.
Cause: The application had specified an invalid value for the test frequency.
Action: Check and correct the specified value for TestFrequencySeconds for the indicated pool.

Level: 1

Type: WARNING

Impact: Common

BEA-000625: The application has disabled periodic testing of free resources in pool "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000626: Free resources in pool "{0}" will be tested every "{1}" seconds.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000627: Reached maximum capacity of pool "{0}", making "{2}" new resource instances instead of "{1}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000628: Created "{1}" resources for pool "{0}", out of which "{2}" are available and "{3}" are unavailable.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000629: Recreated "{2}" out of "{1}" resources for pool "{0}".
Cause: As part of forcibly suspending a pool, all resources currently in use are destroyed and recreated. This message indicates that not all required resources were recreated.
Action: Contact My Oracle Support.

Level: 1

Type: WARNING

Impact: Common

BEA-000630: Unable to create "{1}" resources for pool "{0}".
Cause: As part of the ConnectionCreationRetry feature, pools periodically attempt to create unavailable resources. This message indicates that, in the current attempt, the indicated number of resources could not be created.
Action: Check if the failure condition that prevents the resources from being created (for example, database server or downed network connectivity to it) is still persisting.

Level: 1

Type: WARNING

Impact: Common

BEA-000631: Unknown resource "{1}" being released to pool "{0}": {2}
Cause: The application is trying to release a resource to a pool that is no longer part of the pool. This could happen if the pool was forcibly suspended (which results in all borrowed resources being closed and replaced with new ones) while the resource was borrowed by the application.
Action: Check the application behavior.

Level: 1

Type: WARNING

Impact: Common

BEA-000632: Resource Pool "{0}" shutting down, ignoring {1} resources still in use by applications.
Cause: The administrator is shutting down the pool while applications are still using resources they have obtained from the pool. It is possible that these resources may have been leaked by the applications.
Action: Check the application behavior.

Level: 1

Type: WARNING

Impact: Common

BEA-000633: Resource Pool "{0}" suspending due to number of resource creation or test failures exceeding threshold of {1}
Cause: Resource creation or resource tests have repeatedly failed.
Action: Determine cause of resource failures and correct.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000634: Resource hang detected for pool "{0}", group "{1}". Waited {2} milliseconds where a typical test has been taking {3}
Cause: Resource tests have been taking longer than expected.
Action: Correct condition that causes the resource tests to block for extended periods of time.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000635: Resource Pool "{0}", group "{1}" disabled due to number of resource creation or test failures exceeding threshold of {2}
Cause: Resource creation or resource tests have repeatedly failed.
Action: Determine cause of resource failures and correct.

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000636: Resource Pool "{0}", group "{1}" enabled
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000637: Resource Pool "{0}" resuming due to successful resource creation or test
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Common

BEA-000701: Unable to mount the fileSystem named {0} {1}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000702: Unable to unmount the fileSystem named {0} {1}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000703: Unable to get fileSystem context from Root {0}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000704: Cannot create file system at {0} {1}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000705: Created file system at {0}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: NOTIFICATION

Impact: T3Misc

BEA-000706: Unable to find remote file {0} {1}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000707: Unable to open remote file {0} {1}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000708: T3RemoteOutputStreamProxy: write timed out or interrupted - {0}, {1}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000709: T3RemoteOutputStreamProxy: flush timed out or interrupted - {0}, {1}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000710: TimeRepeat trigger scheduled to run at a date in the past : {0}, trigger will not repeat
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000711: Uncaught throwable in run {0}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000712: Exception invoking {0} {1}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000713: Exception closing stream {0}
Cause: Deprecated functionality.
Action: Deprecated functionality.

Level: 1

Type: ERROR

Impact: T3Misc

BEA-000800: {0} stopped.
Cause: A ThreadDeath exception caused a shutdown.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: Kernel

BEA-000801: ExecuteRequest: {0} cancelled.
Cause: This only happens when WebLogic Server is used in conjunction with an IDE, which uses JVMDI to cancel in-flight requests. If this occurs in normal operation, contact My Oracle Support.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000802: ExecuteRequest failed {0}.
Cause: An execute request generated an exception that was not handled.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: Kernel

BEA-000803: The Class {0} has a setter {1} for attribute {2} which does not have a constructor that could be initialized from a String value of {3}.
Cause: No constructor that takes a String argument was found for the declared attribute type.
Action: Provide a constructor with a String argument.

Level: 1

Type: ERROR

Impact: Kernel

BEA-000804: The Class {0} attribute {1} could not be initialized with value {2}. The exception message is {3}.
Cause: See the exception stack trace for details.
Action: Take the appropriate action based on the error message.

Level: 1

Type: ERROR

Impact: Kernel

BEA-000805: The self-tuning thread pool is disabled. An execute queue will be created for each Work Manager definition.
Cause: The server is starting.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000807: Work Manager {0} has reached its capacity. It is rejecting from thread {1}. The message is {2}. Throwable is {3}.
Cause: This is a Work Manager bug.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Kernel

BEA-000808: The executing thread is a non-WebLogic Server thread. Modify the application to use the Commonj Work Manager API.
Cause: The use of an application spawned a Java thread instead of the Commonj Work Manager API.
Action: Modify the application to use the Commonj Work Manager APIs.

Level: 1

Type: WARNING

Impact: Kernel

BEA-000902: A duplicate expression was found in the system property {0}.nonProxyHosts: {1}.
Cause: The system property {0}.nonProxyHosts contains a pipe character delimited list of hosts, which should be connected to directly and not through the proxy server.
Action: Check the system property {0}.nonProxyHosts. The value can be a list of hosts, each separated by a |. In addition, a wildcard character (*) can be used for matching. For example: -D{0}.nonProxyHosts="*.foo.com|localhost".

Level: 1

Type: ERROR

Impact: Net

BEA-000903: Failed to communicate with proxy: {0}/{1}. Will try connection {2}/{3} now.
Cause: An IOException was received while communicating with the proxy server.
Action: Check the exception for more information. Check if the proxy is running by pinging the proxy: {0}/{1} from the same machine.

Level: 1

Type: ERROR

Impact: Net

BEA-000904: {0} initializing the URL stream handler with custom factory: {1}.
Cause: The factory class that was specified against the system property weblogic.net.http.URLStreamHandlerFactory failed to load or invoke.
Action: Check the system property weblogic.net.http.URLStreamHandlerFactory. This property is used to set a custom URLStreamHandlerFactory.

Level: 1

Type: ERROR

Impact: Net

BEA-000905: Could not open connection with host: {0} and port: {1}.
Cause: The connection attempt failed.
Action: Ensure that the server is running on the specified host and port.

Level: 1

Type: WARNING

Impact: Net

BEA-001035: The following error has occurred: {0}.
Cause: The embedded message should contain an explanation of the failure.
Action: Take appropriate action based on the reported error.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001058: Could not get JNDI context: {0}
Cause: Look at the printed exception to see why the call failed.
Action: Correct the problem and re-run the operation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001064: Ignoring the property "enableTwoPhaseCommit" for JDBCTxDataSource "{0}". This property is used only for those drivers that do not natively support XA.
Cause: The property EnableTwoPhaseCommit was configured to "true" for an XADataSource and will be ignored.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001066: Delaying {0,number} seconds before making a {1} pool connection.
Cause: Some databases cannot handle a tight loop of making multiple connections from one application. If this is the case and the delay is more than 2 seconds, this message will be printed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001067: Connection for pool "{0}" refreshed.
Cause: A connection for the specified pool has been refreshed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001068: Connection for pool "{0}" created.
Cause: A connection for the specified pool has been created.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001072: Connection for XA pool "{0}" created.
Cause: A connection for the specified XA pool has been created.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001073: Connection for XA pool "{0}" refreshed.
Cause: A connection for the specified XA pool has been refreshed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001074: A JDBC pool connection leak has been detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the data source connection pool. The following stack trace at create shows where the leaked connection was created. {0}
Cause: A JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the data source connection pool. A stack trace is printed indicating where the leaked connection was created.
Action: Close the connection appropriately.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001076: An attempt has been made to release a connection that belongs to a non-existing pool. Ensure that the pool "{0}" has been destroyed by intent.
Cause: An attempt was made to release a connection that belongs to a non-existing pool.
Action: Correct the destroy operation to specify a valid pool name.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001083: Multi data source "{0}" was created with {1,number} connection pools for {2}.
Cause: A multi data source was created with the specified number of connection pools.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001084: Multi data source "{0}" will be shutdown
Cause: The specified multi data source is being shut down.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001086: Data source "{0}" with JNDI name "{1}" will be shut down.
Cause: The specified data source is being shut down.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001089: Data source connection pool {0} has been started for application {1}, module {2}.
Cause: The specified data source connection pool is being started.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001099: Data source connection pool "{0}" reset by "{1}".
Cause: The specified connection pool has been reset.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001100: Data source connection pool "{0}" shut down by "{1}".
Cause: The specified data source connection pool has been shut down, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001101: Data source connection pool "{0}" disabled by "{1}".
Cause: The specified data source connection pool has been disabled.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001102: Data source connection pool "{0}" enabled by "{1}".
Cause: The specified data source connection pool has been enabled.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001104: A globally scoped data source connection pool named ({0}) already exists.
Cause: When adding or referencing a JDBC data source connection pool that is an application-scoped pool, a globally scoped data source connection pool with the same name already exists. The locally scoped pool has precedence over the global pool.
Action: If you want to reference the global pool in your application, the name of the global pool or the application-scoped pool must be changed to be unique.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001105: Referenced global pool ({0}) has the same name as a locally defined data source connection pool or data source ({1}).
Cause: When deploying a JDBC data source connection pool (not application-scoped) an application (locally) scoped data source connection pool with the same name already exists. The locally scoped pool has precedence over the global pool.
Action: If you want to reference the global pool in your application, the name of the global pool or the application-scoped pool must be changed to be unique.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001107: There is a globally defined data source ({0}) with the same JNDI name ({1}) as a locally defined data source.
Cause: It is possible to use a resource descriptor with application-scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name that is specified in the resource descriptor, it is assumed that this is a pool that the application meant to use and it is bound into comp/env. However, a check in the global namespace indicates that there is also a global pool with the same JNDI name.
Action: If you want to reference the global pool in your application, the JNDI name of the global pool or the application-scoped pool must be changed to be unique.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001108: A locally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).
Cause: It is possible to use a resource descriptor with application-scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is the pool that the application meant to use and it is bound into comp/env.
Action: No action is required. If this association is not desired, specify a unique JNDI name in the resource descriptor.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001109: A globally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).
Cause: It is possible to use a resource descriptor with global data source connection pools. If the JNDI lookup reveals that there is a pool with the JNDI name that is specified in the resource descriptor, it is assumed that this is the pool that the application was meant to use and it is bound into comp/env.
Action: No action is required. If this association is not desired, specify a unique JNDI name in the resource descriptor.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001110: No test table set up for pool "{0}". Connections will not be tested.
Cause: TestConnectionsOnReserve, TestConnectionsOnRelease, TestConnectionsOnCreate, TestFrequencySeconds were configured but TestTableName was not configured.
Action: Configure a valid TestTableName for the data source connection pool.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001111: Unable to verify the test "{1}" set up for pool "{0}". Connections will not be tested. The test will not be used by isValid either.
Cause: While creating a data source connection pool with the attributes specified to test the pool connections, a test is run during the pool initialization. This test failed with the printed error.
Action: Check the SQL error that occurred and correct the problem. The specified TestTableName might not exist.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001112: Test "{1}" set up for pool "{0}" failed with exception: "{2}".
Cause: The specified data source connection pool has been configured with one or more attributes to test the pool connections. One of those test attempts failed. The associated error is printed.
Action: Check the associated error to see what the problem is and correct it. Normally, this indicates that a connection was lost to the database (the database is down). This needs to be corrected by the database administrator.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001113: Data source connection pool "{0}" shrunk by "{1}".
Cause: The data source connection pool has been shrunk by the specified amount as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001114: Soft shutdown called on data source connection pool "{0}" by "{1}".
Cause: A soft shutdown operation on the specified data source connection pool has been started, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001115: Hard shutdown called on data source connection pool "{0}" by "{1}".
Cause: A hard shutdown operation on the specified data source connection pool has been started, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001116: Disable and freeze users called on data source connection pool "{0}" by "{1}".
Cause: An operation to disable and freeze users on the specified data source connection pool has been started, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001117: Disable and drop users called on data source connection pool "{0}" by "{1}".
Cause: An operation to disable and drop users on the specified data source connection pool has been started, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001118: Unable to register for receiving MBean notifications of dynamic configurations changes for data source connection pool "{0}": "{1}". Pool will not be dynamically reconfigured.
Cause: The server was unable to register for receiving MBean notifications of dynamic configurations changes for the specified data source connection pool. The connection pool will not be dynamically reconfigured.
Action: Check the exception that is printed along with this message to see what the cause of the failure was.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001119: Unable to delete configuration MBean for pool "{0}": "{1}"
Cause: While doing a forced shutdown, the data source connection pool was removed but the associated MBean for the connection pool was not removed.
Action: Check the exception that is printed along with this message to see what the cause of the failure was.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001120: Created data source named {0} for Pool {1}.
Cause: There was a user request to create a data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001121: Created TX data source named {0} for Pool {1}.
Cause: The user requested that the TX data source be created, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001122: Destroyed TX data source named {0} for Pool {1}.
Cause: There was a user request to destroy the TX data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001123: Destroyed data source named {0} for Pool {1}.
Cause: There was a user request to destroy the data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001124: Created Connection Pool named {0}.
Cause: There was a user request to create the data source connection pool, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001125: Created multi data source named {0}.
Cause: There was a user request to create the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001126: Destroyed Connection Pool named {0}.
Cause: There was a user request to destroy the data source connection pool, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001127: Destroyed multi data source named {0}.
Cause: There was a user request to destroy the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001128: Connection for pool "{0}" has been closed.
Cause: A connection for the specified data source connection pool has been closed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001129: Received exception while creating connection for pool "{1}": {0}.
Cause: The exception message should indicate the probable cause of the error.
Action: Check the error to see why the connection creation failed and correct the problem.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001130: Disabled statement caching for connection in pool "{0}" as it is using the WebLogic Type-2 XA driver.
Cause: Statement caching was disabled for the specified data source connection pool because it is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when the XAResource.end is called, causing all prepared statements to be no longer valid.
Action: No action is required. Use a different driver if you want to use the prepared statement cache with the driver.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001131: Received an exception when closing a cached statement for the pool "{0}": {1}.
Cause: When closing a prepared statement in the prepared statement cache for the specified data source connection pool, an error occurred.
Action: Check the associated error that is printed and, if possible, correct the problem.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001132: Initialized statement cache of size "{1}" for connection in pool "{0}".
Cause: A prepared statement cache has been enabled for a connection in the specified data source connection pool.
Action: No action is required. If you do not want statement caching turned on for the pool, do not configure or disable it.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001133: Statement caching is not enabled for connection in specified data source connection pool "{0}".
Cause: A configured data source connection pool has been started without statement caching being enabled.
Action: No action is required. If you want statement caching turned on for the pool, configure and enable it.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001134: Statement caches of connections in the data source connection pool "{0}" have been cleared by "{1}".
Cause: The statement caches for connections in the specified data source connection pool have been cleared, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001135: Initializing the JDBC service.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001136: Initialization failed.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001137: Initialization complete.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001138: Resuming the JDBC service.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001139: Resume failed.
Cause: Check earlier messages that are printed in the log.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001140: Resume complete.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001141: Suspending the JDBC service.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001142: Suspend of JDBC service failed.
Cause: Check earlier messages that are printed in the log.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001143: Suspend completed.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001144: Force Suspending the JDBC service.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001145: Force suspend of the JDBC service failed.
Cause: Check earlier messages that are printed in the log.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001146: Force suspend of the JDBC service completed.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001147: Shutting down the JDBC service.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001148: Shutdown of the JDBC service failed.
Cause: Check earlier messages that are printed in the log.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001149: Shutdown of the JDBC service has completed.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001150: Connection pool "{0}" deployment failed with the following error: {1}.
Cause: The cause should be indicated in the exception message.
Action: Correct the problem described in the exception message.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001151: Data source "{0}" deployment failed with the following error: {1}.
Cause: The cause should be indicated in the exception message.
Action: Correct the problem described in the exception message.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001152: Cannot enable statement caching for connection in pool "{0}", because it is using the WebLogic Type-2 XA driver.
Cause: Statement caching has been disabled for the specified data source connection pool because the connection pool is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when XAResource.end is called, causing all prepared statements to no longer be valid.
Action: No action is required. Use a different driver if you want to use the prepared statement cache with the driver.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001153: Forcibly releasing inactive/harvested connection "{1}" back into the data source connection pool "{0}", currently reserved by: {2}.
Cause: The connection was found to be unused by the application for the specified duration (configured using InactiveConnectionTimeoutSeconds attribute of the pool MBean), and therefore is being forcibly released back into pool. Alternatively, the connection was harvested and the application callback did not close the connection.
Action: Check the application code for leakages of connection objects, or tune the configured value of the specifed connection pool attribute.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001154: Disabling statement caching for connection in pool "{0}" because it is using the WebLogic Type-2 XA driver or the Pointbase DBMS.
Cause: Statement caching has been disabled for the specified data source connection pool because it is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when XAResource.end is called, causing all prepared statements to be no longer valid. Pointbase DBMS does not allow the reuse of cached statements across table drop and create operations. Therefore statement caching has been disabled.
Action: Use a different driver if you want to use the prepared statement cache with the driver. If you are using Pointbase DBMS and are NOT dropping and creating tables in your application, you can enable statement caching at runtime by setting the attribute StatementCacheSize for the connection pool JDBCConnectionPoolMBean.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001155: The following exception has occurred:
Cause: An error condition has occurred.
Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001156: Stack trace associated with message {0} follows:
Cause: An error condition was reported.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001157: Data source connection pool "{0}" being suspended by user "{1}".
Cause: The specified data source connection pool is being suspended, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001158: Data source connection pool "{0}" being forcibly suspended by user "{1}".
Cause: The specified data source connection pool is being forcibly suspended, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001159: Data source connection pool "{0}" is being resumed by user "{1}".
Cause: The specified data source connection pool is being resumed, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001160: Data source connection pool "{0}" being forcibly destroyed by user "{1}"
Cause: The specified data source connection pool is being forcibly destroyed, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001161: Data source connection pool "{0}" being destroyed by user "{1}".
Cause: The specified data source connection pool is being destroyed, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001162: Data source connection pool "{0}" being forcibly shutdown by user "{1}".
Cause: The specified data source connection pool is being forcibly shutdown, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001163: Data source connection pool "{0}" being shut down by user "{1}".
Cause: The specified data source connection pool is being shut down, as requested by the application.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001164: Unable to initialize connection in pool "{0}". Initialization SQL = "{1}". Received exception: "{2}".
Cause: The exception message should contain a reason for the failure.
Action: Take appropriate corrective action.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001165: Invalid statment cache size "{1}" specified for connection in pool "{0}".
Cause: An invalid value has been specified for statement cache size for connections in the indicated data source connection pool.
Action: Check the allowed limits for statement cache size for this data source connection pool and fix the specified value.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001166: Activation of application-scoped data source connection pool "{1}":"{2}":"{0}" failed. Received exception: "{3}".
Cause: The error message should contain the reason for the failure.
Action: Take appropriate corrective action.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001167: Deactivation of application-scoped pool "{1}":"{2}":"{0}" failed. Received exception: "{3}".
Cause: The error message should contain the reason for the failure.
Action: Take appropriate corrective action.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001168: Attempt to resume JDBCService when it is already running...Ignoring.
Cause: The application attempted to resume JDBCService, although the service is already running.
Action: Take appropriate corrective action.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001169: Error occured during shutdown of pool "{0}". Received exception: "{1}".
Cause: The exception should contain the reason for the failure.
Action: Take appropriate corrective action.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001170: Unable to initialize JDBC Log. Received exception: "{0}".
Cause: The message should contain the reason for the failure.
Action: Take appropriate corrective action.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001171: Unable to close connection "{0}". Received exception: "{1}".
Cause: The message should contain the reason for the failure.
Action: Take suitable action if possible. Otherwise, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001172: Error occurred during shutdown of data source "{0}". Received exception: "{1}".
Cause: The message should contain the reason for the failure.
Action: Take appropriate corrective action.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001173: "TestTableName" attribute for pool "{0}" being dynamically changed to "{1}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001174: Creating data source named {0}, JNDI Name = {1}.
Cause: The user requested that the data source be created, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001175: Creating transactional data source named {0} for Pool {1}.
Cause: The user requested that the transactional data source be created, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001176: Creating multi data source named {0}.
Cause: The user requested that the multi data source be created, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001177: Creating data source connection pool named {0}, URL = {1}, Properties = {2}.
Cause: A request was issued to create the data source connection pool, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001178: Attempt to set query timeout on a statement failed : {0}.
Cause: The reported message should contain a description of the failure.
Action: Contact My Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001250: Unable to load application configured callback {1} for multi data source {0}, got error: {2}. Application control of multi data source failover behaviour will not work.
Cause: This is most likely because the application-defined class location has not been added to the CLASSPATH environment varible.
Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001251: Application configured callback {1} for multi data source {0} does not implement required interface {2}. Application control of multi data source failover behaviour will not work.
Cause: The configured callback {1} does not implement the required interface {2}.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001252: Unable to add notification listener for Config MBean for multi data source {0} failed, got exception: {1}.
Cause: The reported exception should indicate the cause of the failure.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001254: Multi data source {0} unable to disable connection pool {1}, got exception: {2}.
Cause: The reported exception should indicate the cause of the failure.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001255: Multi data source {0} unable to disable connection pool {1}, got exception: {2}.
Cause: The reported exception should indicate the cause of the failure.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001256: Dynamically changing the value of attribute FailoverRequestIfBusy for multi data source {0} from {1} to {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001257: Dynamically changing value of attribute HealthCheckFrequencySeconds for multi data source {0} from {1} to {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001258: Unable to setup timer for multi data source {0}, got exception: {1}.
Cause: The reported exception should indicate the cause of the failure.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001259: Application has disallowed multi data source {0} from re-enabling data source connection pool {1}, which had previously been found dead and was disabled.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001260: Multi data source {0} unable to enable connection pool {1}, got exception: {2}.
Cause: The reported exception should indicate the cause of the failure.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001261: Multi data source {0} unable to enable connection pool {1}, got exception: {2}.
Cause: The reported exception should indicate the cause of the failure.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001262: Registered application callback {1} for multi data source {0} to control multi data source failover behavior.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001500: Creating application-coped multi data source {0}, algorithm type {3} for Application {1}, Module {2}.
Cause: The user requested that the multi data source be created, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001501: Creating multi data source {0}, algorithm type {1}.
Cause: A request was made to create the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001503: Creating application-scoped data source connection pool {0} for Application {1}, Module {2}, URL = {3}, Properties = {4}.
Cause: A request was made to create the data source connection pool, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001504: Destroying multi data source {0}, created for Application {1}, Module {2}.
Cause: A request was made to destroy the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001505: Destroying multi data source Pool {0}.
Cause: A request was made to destroy the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001507: Destroying data source connection pool {0}, created for Application {1}, Module {2}.
Cause: A request was made to destroy the data source connection pool, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001508: Destroying data source connection pool {0}.
Cause: A request was made to destroy the data source connection pool, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001510: Creating application-scoped data source {0} for Application {1}, Module {2}, Application Context Name = {3}.
Cause: A request was made to create the data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001512: Data source {0} has been successfully created.
Cause: A request was made to create the data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001513: Destroying application-scoped data source {0}, created for Application {1}, Module {2}.
Cause: A request was made to destroy the data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001514: Destroying data source {0}.
Cause: A request was made to destroy the data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001515: Data source {0} has been successfully destroyed.
Cause: A request was made to destroy the data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001516: Data source connection pool "{0}" connected to Database: "{1}", Version: "{2}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001517: Data source connection pool "{0}" using Driver: "{1}", Version: "{2}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001518: Data source connection pool "{0}" Connection Usage Data:
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001519: Id : "{0}"
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001520: Timestamp : "{0}"
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001521: User : "{0}"
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001522: Data source connection pool "{0}" Connection Wait Data:
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001523: Data source connection pool "{0}" Connection Leak Data:
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001524: Data source connection pool "{0}" Connection Reserve Fail Data:
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001525: Data source connection pool "{0}" Statement Cache Entry Data:
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001526: Unable to load class "{0}", got exception : {1}. Driver Interception feature disabled.
Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.
Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001527: Application configured class {0} does not implement required interface {1}. Driver Interception feature disabled.
Cause: The configured class {0} does not implement the required interface {1}.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001528: Driver Interceptor class {0} loaded.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001529: JDBC loggging last resource (LLR) connection pool {0} did not find its table and is creating a new one using the following SQL: {1}
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001530: JDBC loggging last resource (LLR) connection pool {0} retrieved {1} record(s) from the database table {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001531: Received updated event for unexpected type of bean: {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001532: Data source connection pool "{0}" Statement Usage Data:
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001533: Pool Name : "{0}"
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001534: Data source connection pool "{0}" Connection Last Usage Data:
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001535: Data source connection pool "{0}" Connection Multi-threaded Usage Data:
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001536: Creating multi data source named {0}, JNDI Name = {1}.
Cause: A request was made to create the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001537: Creating application-scoped multi data source {0} for Application {1}, Module {2}, Application Context Name = {3}.
Cause: A request was made to create the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001538: Created multi data source named {0}.
Cause: A request was made to create the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001539: Destroying multi data source {0}.
Cause: A request was made to destroy the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001540: Destroying application-scoped multi data source {0}, created for Application {1}, Module {2}.
Cause: A request was made to destroy the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001541: Destroyed multi data source named {0}.
Cause: A request was made to destroy the multi data source, either implicitly or explicitly.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001542: JVM DriverManager Login Timeout value set to {0}.
Cause: The application has specified this behavior to be enabled, via the corresponding configuration setting.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001543: Received change event: {1} for unexpected type of bean: {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001544: Received add event: {1} for unexpected type of bean: {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001545: Received unexpected event: {1} for unexpected type of bean: {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001546: Data source connection pool "{0}" is being started by user "{1}".
Cause: The specified data source connection pool is being started, as requested by the administrator.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001547: The "{0}" field value "{1}" in table reference "{2}" format [[[catalog.]schema.]table) is too long. The database supports a maximum length of "{3}" for this field.
Cause: This is a configuration error.
Action: When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001548: Empty field value in table reference "{0}" (format [[[catalog.]schema.]table).
Cause: This is a configuration error.
Action: Ensure that the entire table reference is blank, or that the table field is not blank. If there is no schema, ensure that there are no periods "." in the table reference. Do not start the table reference with a period ".". Note that JDBC stores automatically append "WLStore" to table references.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001549: An old style WebLogic driver URL {0} is used. Because the WebLogic driver URL auto-convert switch is turned on, it is converted to {1}.
Cause: An old style WebLogic driver URL is used and the WebLogic driver URL auto-convert switch is turned on.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001550: WebLogic Oracle driver is being used. The driver URL is {0}. WebLogic Server no longer supports the WebLogic Oracle driver.
Cause: The WebLogic Oracle driver has been deprecated and removed.
Action: Stop using the WebLogic Oracle driver, use the Oracle Thin driver instead.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001551: Application context for member data source {1} not found for standalone multi data source module {0}. Ensure that multi data source standalone modules have a higher deployment order than member data source standalone modules.
Cause: The deployment order of the multi data source is the same or lower than one of its member datasources.
Action: Change the deployment order of the standalone multi data source to be greater than each member data source's deployment order.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001552: The logging last resource (LLR) data source {0} will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.
Cause: Remote JDBC access over RMI is disabled.
Action: Either configure the data source to use an XA-capable driver, or enable remote JDBC on all servers.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001553: Unable to deploy JDBC data source {0}. No credential mapper entry found for password indirection user {1}
Cause: No credential mapper entry was found for user {1} on data source {0}
Action: Ensure that a credential mapper entry is defined for the data source {0} that maps the specified user name {1} to a password. The WebLogic Server administration console provides support for managing data source credential mapper entries.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001554: Data source connection pool "{0}" Connection Unwrap Data:
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001555: Invalid member data source {1} specified for multi data source {0}. GridLink data source may not be used in multi data source configurations.
Cause: A GridLink data source was specified as a multi data source member.
Action: Either use a single GridLink data source or define generic data sources for use in a multi data source configuration.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001556: Data source {0} for service {1} registering with ONS daemons using configuration string {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001557: Data source {0} for service {1} unregistering with ONS daemons {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001558: Data source {0} for service {1} received a service down event for instance {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001559: Data source {0} for service {1} received a node down event for node {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001560: Data source {0} for service {1} received a service up event for instance {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001561: Data source {0} for service {1} received a node up event for node {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001562: Data source {0} for service {1} not registering for Fast Application Notification (FAN) events.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001563: ADM_DDL LLR (logging last resource) connection pool {0} did not find its table {1}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001564: JTSLoggableResourceTable.existsForADMDDL about to return: return value = {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001565: Logging last resource (LLR) data source {0} using LLR table {1} defined by system property weblogic.llr.table.{0}
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001566: JTSLoggableResourceTable.init for ADMDDL is generating SQL statement(createSQL): {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001567: SQLRuntimeException caught at existsForADMDDL for poolName: {0} ddlName: {1} by: {2}.
Cause: Look at the printed exception to see why the call failed.
Action: Correct the problem and run the operation again.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001568: Data source {0} for service {1} received a service up event
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001569: Data source {0} failed to create runtime MBean for RAC instance {1}. Exception={2}
Cause: Refer to the exception error message for the cause of the failure.
Action: Try redeploying the data source or restart the WebLogic Server instance.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001570: Attempt to enable Fast Application Notification (FAN) support for a non-GridLink data source {0}, which is not supported.
Cause: Subscribing to FAN events is only supported by GridLink data sources.
Action: Either set the FAN enabled attribute to false or configure a GridLink data source.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001571: Unable to load the connection labeling callback class "{0}", got exception : {1}.
Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.
Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001572: Application-configured connection labeling callback class {0} does not implement required interface {1}.
Cause: The configured class {0} does not implement the required interface {1}.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001573: Connection labeling callback class {0} loaded.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001574: Unable to load the connection Initialization callback class "{0}", got exception : {1}.
Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.
Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001575: Application configured connection initialization callback class {0} does not implement required interface {1}.
Cause: The configured class {0} does not implement the required interface {1}.
Action: Refer to the WebLogic Server documentation.

Level: 1

Type: ERROR

Impact: JDBC

BEA-001576: Connection Initialization callback class {0} loaded.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JDBC

BEA-001580: An exception was thrown from the ConnectionHarvestingCallback: {0}.
Cause: The application callback threw an exception when the callback was called.
Action: Look at the associated message. If more information is desired, turn on connection debuggging.

Level: 1

Type: WARNING

Impact: JDBC

BEA-001581: An invalid scope of Application instead of Global is specified for data source {0}, URI = {1}.
Cause: The configuration is invalid. The specified datasource must have a Global scope.
Action: Correct the configuration for the specified datasource.

Level: 1

Type: ERROR

Impact: JDBC

BEA-002001: Received an unknown message type.
Cause: This should not occur. This indicates that the client is sending garbaged messages. It might also indicate that malicious third parties are trying to access the server using IIOP.
Action: Contact My Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002002: Failed to parse method name {0}.
Cause: This can happen for a variety of reasons. Normally, it is because the caller made a request for a non-existent method. Alternatively, the IDL mangling of the method name may be ambiguous, so WebLogic Server cannot decide which method to call.
Action: If the IDL mangling is causing a problem, try changing the name of the method. In particular, names such as getSomedata() (where somedata is also the name of an attribute or method) can cause problems. Also, some bugs with name mangling exist in JDK 1.3.1. Try using a JDK 1.4 client.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002003: Unable to send the message: {0}.
Cause: Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.
Action: Verify that the client-server network connection is working.

Level: 1

Type: ERROR

Impact: IIOP

BEA-002005: OutOfMemoryError in adapter: {0}.
Cause: This is often caused by marshalling mismatches between the client and the server and is generally a bug in either the client or the server or both.
Action: Restart the server and contact My Oracle Support.

Level: 1

Type: INTERNAL_ERROR

Impact: IIOP

BEA-002006: Cannot scavenge idle connections, {0}
Cause: The server was unable to schedule a trigger to watch for idle IIOP connections. The fact that it was unable to do so indicates some core failure in the server.
Action: Restart the server. If this occurs again, contact Oracle Customer Support.

Level: 1

Type: ERROR

Impact: IIOP

BEA-002008: Failed to export {0}. The following exception occurred: {1}.
Cause: This is most often caused by the server being unable to find or generate an IIOP stub for the remote object. Ensure that the Common Object Request Broker API (CORBA) objects have corresponding _Stub classes in the server classpath. RMI-IIOP object stubs should be generated automatically.
Action: For CORBA objects, ensure that the idlj was run on the server class. For RMI-IIOP objects, contact My Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002011: Failed to marshal exception {0}: {1}.
Cause: The server could not find the appropriate exception definitions in its classpath. For Common Object Request Broker API (CORBA) exceptions, the application must contain the exception helper classes as well as the exception classes.
Action: Add missing exception classes to the application.

Level: 1

Type: ERROR

Impact: IIOP

BEA-002012: Failed to send exception {0}: {1}.
Cause: This only happens if the connection between the client and server was very unreliable.
Action: Verify that the client-server network connection is working. Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: IIOP

BEA-002013: Complete failure to send exception {0}: {1}.
Cause: Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.
Action: Verify the client-server network connection.

Level: 1

Type: ERROR

Impact: IIOP

BEA-002014: IIOP subsystem enabled.
Cause: The IIOP subsystem is operational and is listening for incoming IIOP requests.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002015: Using javax.rmi.CORBA.UtilClass {0}; The IIOP subsystem requires a WebLogic Server-compatible UtilClass.
Cause: Some application code, or a foreign object request broker (ORB), set the system property javax.rmi.CORBA.UtilClass or tried accessing javax.rmi.CORBA.Util functions before the IIOP subsystem had initialized.
Action: The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.

Level: 1

Type: ERROR

Impact: IIOP

BEA-002016: Using javax.rmi.CORBA.PortableRemoteObjectClass {0}, the IIOP subsystem requires a WebLogic Server-compatible PortableRemoteObjectClass.
Cause: Some application code, or a foreign object request broker (ORB), set the system property javax.rmi.CORBA.PortableRemoteObjectClass or tried accessing javax.rmi.PortableRemoteObject functions before the IIOP subsystem had initialized.
Action: The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.

Level: 1

Type: ERROR

Impact: IIOP

BEA-002017: LocateRequest is {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002018: Default GIOP version is 1.{0}
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002019: LocationForward policy is {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002021: SecurityService registered under {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002022: Could not bind SecurityService {0}.
Cause: This is an internal JNDI problem.
Action: Contact My Oracle Support.

Level: 1

Type: WARNING

Impact: IIOP

BEA-002023: Could not resolve SendingContext RunTime: {0}.
Cause: An invalid object reference for SendingContext RunTime was provided by the client.
Action: Contact My Oracle Support.

Level: 1

Type: WARNING

Impact: IIOP

BEA-002026: Transaction mechanism is {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002027: Complete failure to rewrite exception from {0}: {1}.
Cause: This error should not occur.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: IIOP

BEA-002028: An OTS error occurred: {0}, {1}.
Cause: OTS errors are generally not bugs but always result in exception information being lost when propagated to the caller. Thus, the root cause is always logged, so that system administrators can determine the real cause. OTS errors are generally caused by some transaction subsystem operation (for instance, a transaction being rolled back).
Action: Ensure that this is an expected error.

Level: 1

Type: WARNING

Impact: IIOP

BEA-002033: Codeset for {0} data set to {1}, OSF registry entry {2}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002037: CosNaming Service registered under {0}.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: IIOP

BEA-002038: Could not bind the CosNaming Service {0}.
Cause: This is an internal JNDI problem.
Action: Contact My Oracle Support.

Level: 1

Type: WARNING

Impact: IIOP

BEA-002039: Replacer: {0}
Cause: The replacer did not have enough information to do a proper replacement.
Action: Contact My Oracle Support.

Level: 1

Type: WARNING

Impact: IIOP

BEA-002041: Connection attempt was rejected because IIOP is not enabled on this channel.
Cause: The connection attempt was rejected because IIOP is not enabled at all for this server, as determined by the ServerMBean, or is not enabled on this particular channel.
Action: Enable IIOP.

Level: 1

Type: WARNING

Impact: IIOP

BEA-002043: Naming exception: {0}
Cause: A standard exception was generated by the naming implementation.
Action: No action is required.

Level: 1

Type: WARNING

Impact: IIOP

BEA-002605: Adding address: {0} to the licensed client list.
Cause: The server accepted a connection from the specified client.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002606: The server is unable to create a server socket for listening on channel "{3}". The address {0} might be incorrect or another process is using port {1,number,0}: {2}
Cause: The address was incorrect or another process was using the port.
Action: Use ipconfig or ifconfig to check if the listen address is valid, and use netstat to check that the specified port is not in use by another process.

Level: 1

Type: ERROR

Impact: Server

BEA-002607: Channel "{2}", listening on {0}:{1,number,0}, was shut down.
Cause: The server or channel was shut down.
Action: No action is required. If this was an unexpected error, contact My Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002608: The ListenThread failed because of an error: {0}
Cause: An exception occurred when the server socket was unable to accept client connections.
Action: Check the file descriptor limit. Tune the operating system parameters that handle socket creation using ServerSocket.

Level: 1

Type: ERROR

Impact: Server

BEA-002609: Channel Service initialized.
Cause: The Channel subsystem is operational.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002610: Dynamic Listener Service initialized.
Cause: The dynamic listener subsystem is operational.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002611: The hostname "{0}", maps to multiple IP addresses: {1}.
Cause: The host name of the server resolved to multiple IP addresses, which can cause problems for the Administration Server.
Action: Check if this was done on purpose.

Level: 1

Type: WARNING

Impact: Server

BEA-002612: Channel "{2}", listening on {0}:{1,number,0}, did not start did not start properly.
Cause: Some of the listen ports did not open or failed within the configured grace period.
Action: Ensure that none of the configured listen ports are in use by other processes.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002613: Channel "{2}" is now listening on {0}:{1,number,0} for protocols {3}.
Cause: The server successfully started the listen thread and server socket.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002614: Reopening channel "{2}" on {0}:{1,number,0}.
Cause: The server backed off because a socket exception occurred while accepting client connections. The server is now ready to accept connections.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002615: After having failed to listen, the server is now listening on channel "{2}" on {0}:{1,number,0}.
Cause: The server backed off because a socket exception occurred while accepting client connections. The server is now ready to accept connections.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002616: Failed to listen on channel "{2}" on {0}:{1,number,0}, failure count: {3}, failing for {4} seconds, {5}
Cause: An exception occurred while trying to accept client connections. The server will try to back off to aid recovery.
Action: The operating system (OS) limit for the number of open file descriptors (FD limit) needs to be increased. Tune the OS parameters that might help the server to accept more client connections (for example, TCP accept back log).

Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002617: Attempting to close and reopen the server socket on channel "{2}" on {0}:{1,number,0}.
Cause: The server listener could not accept a socket connection and failed after several simple retries. It has closed and reopened the server socket.
Action: Check if the file decriptor limit needs to be increased. Tune the operating system parameters that might help the server accept more client connections.

Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002618: An invalid attempt was made to configure a channel for unconfigured protocol "{0}".
Cause: The server configuration specified a channel that uses a protocol that is not enabled.
Action: Enable the protocol in the server configuration.

Level: 1

Type: ERROR

Impact: Server

BEA-002619: One or more listen ports did not start properly.
Cause: One or more listen ports failed to open during server startup.
Action: Ensure that none of the configured listen ports are in use by other processes.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002620: An invalid attempt was made to configure a channel for server "{0}" on an unknown listen address "{1}".
Cause: The server configuration specified a channel that uses a listen address that does not exist.
Action: Correct the server configuration.

Level: 1

Type: ERROR

Impact: Server

BEA-002621: The connection was rejected because the server license only allows connections from {0} unique IP addresses.
Cause: Clients tried to connect from more distinct addresses than the license allows.
Action: Use a server license that allows for more clients to connect.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002622: The protocol "{0}" is now configured.
Cause: The server has loaded a protocol making it available for outbound traffic and configurable for inbound traffic.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002623: Connection rejected, the server is in the {0} state. Starting service {1}, {2} of {3}. Last service {4} took {5} milliseconds.
Cause: Clients tried to connect to the server before it was in the RUNNING state.
Action: Connect to the server after it has started.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002624: The administration protocol is "{0}" and is now configured.
Cause: The server has loaded the administration protocol making it available for outbound traffic and configurable for inbound traffic.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002625: An attempt to configure channel "{0}" failed because of {1}.
Cause: The cause is detailed in the accompanying exception.
Action: Review the exception.

Level: 1

Type: ERROR

Impact: Server

BEA-002626: The protocol "{0}" could not be loaded: {1}
Cause: Consult the exception for why the protocol could not be loaded.
Action: Consult the exception for why the protocol could not be loaded.

Level: 1

Type: WARNING

Impact: Server

BEA-002627: The domain configuration must have at least one administration channel on every server or no administration channels at all.
Cause: The server was contacted by a server that did not reflect the same administration state as itself.
Action: Modify the domain configuration so that all servers have administration channels, or enable the domain-wide administration port.

Level: 1

Type: ERROR

Impact: Server

BEA-002628: Unable to export RemoteLifeCycleOperations RMI object due to {0}.
Cause: The RMI export failed.
Action: Contact My Oracle Support and provide the logs.

Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002630: Accepting connections again.
Cause: The server is accepting client connections again after refusing connections as part of server throttling.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002631: Max threshold reached for open sockets [total open sockets: {0}, allowed max: {1}]. No more connections allowed.
Cause: The MaxOpenSocketCount attribute of the server configuration defines the upper bound of the number of open sockets.
Action: Increase the MaxOpenSocketCount attribute of the server configuration. Use the server tuning tab in the Administration Console.

Level: 1

Type: WARNING

Impact: Server

BEA-002632: Found jrmp.jar in {0} directory. JRMP service is now enabled.
Cause: JRMP is enabled.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002633: A port conflict was detected in the server configuration. The server is configured to listen on two ports that have the same port number and IP address. Channel "{0}" address "{1}" conflicts with channel "{2}" address "{3}".
Cause: The server is configured to listen on two ports that have the same port number and IP address.
Action: Ensure that the address identities [ListenAddress and ListenPort combinations] are distinct and unique.

Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002634: The server "{0}" disconnected from this server.
Cause: The remote server may have crashed, been shut down normally or been partitioned from the network.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002635: The server "{0}" connected to this server.
Cause: The remote server may have been booted or a network partition may have been resolved.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002636: Unable to update server "{0}" with local channel information.
Cause: The remote server may have crashed, been shut down normally or been partitioned from the network.
Action: No action is required.

Level: 1

Type: ERROR

Impact: Server

BEA-002637: Failed to register a disconnect listener because of {0}
Cause: This can happen during server startup when the incoming network connection is not suitable for callbacks and the booting server does not yet have a listen port open.
Action: No action is required. The server should eventually be connected properly.

Level: 1

Type: WARNING

Impact: Server

BEA-002638: {0} was issued remotely from {1}.
Cause: Log the host address of the machine that issued the SLC operation.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002639: ServerRuntime:{0}
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002640: A request has been received to force a shutdown of the server.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002641: -DserverType is set to an unrecognized value: {0}. The server will start with all services enabled.
Cause: An undefined server type was specified or a typographical error was made.
Action: See the WebLogic Server documentation for valid values for -DserverType.

Level: 1

Type: WARNING

Impact: Server

BEA-002642: {0} not found. The server will start with all services enabled.
Cause: The file was deleted or moved.
Action: Replace the file from the WebLogic Server installation.

Level: 1

Type: WARNING

Impact: Server

BEA-002643: Attempt to read {0}, failed: {1}
Cause: The file has been corrupted or had its permissions changed.
Action: Replace the file with one from the WebLogic Server installation.

Level: 1

Type: WARNING

Impact: Server

BEA-002644: The JAR file {0} being processed as a potential service plug-in could not be read: {1}
Cause: The file may be damaged.
Action: Check the file, replace & and try again.

Level: 1

Type: ERROR

Impact: Server

BEA-002645: The manifest of the JAR file {0} being processed as a potential service plug-in, could not be read: {1}
Cause: The manifest may be corrupted.
Action: Replace the file and retry.

Level: 1

Type: ERROR

Impact: Server

BEA-002646: Unable to load the service plug-in activator class from {0}: {1}
Cause: The plug-in JAR file does not meet the service plug-in requirements.
Action: Check the contents of the JAR file and retry.

Level: 1

Type: ERROR

Impact: Server

BEA-002647: The service plug-in, {1}, was added from {0}.
Cause: The plugin was placed in the domain lib directory.
Action: No action is required. To remove the plug-in, remove it from the domain lib directory.

Level: 1

Type: NOTIFICATION

Impact: Server

BEA-002648: Could not obtain the relevant ServerRuntimeMBean for server {0}.
Cause: The remote server runtime object for server {0} could not be obtained. This can happen if the server has already been shut down or is otherwise unavailable.
Action: If the server is active when this error occurs, contact My Oracle Support.

Level: 1

Type: WARNING

Impact: Server

BEA-002649: A port conflict was detected in the server configuration. Both TCP and SDP channels are configured to listen on the same port number and IP address. Channels "{0}" and "{1}" on address "{2}".
Cause: Both TCP and SDP channels are configured to listen on the same port number and IP address.
Action: Ensure that the channels with the same [ListenAddress and ListenPort combinations] either all support SDP or do not support SDP.

Level: 1

Type: INTERNAL_ERROR

Impact: Server

BEA-002900: Initializing self-tuning thread pool.
Cause: The server is starting.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002901: Creating Work Manager "{2}" for module "{0}" and application "{1}"
Cause: The application is being initialized.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002902: Creating execute queue "{0}".
Cause: The server is starting.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002903: Creating Work Manager from "{1}" WorkManagerMBean for application "{0}"
Cause: The application is being initialized.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002905: Removing {0} threads from the thread pool.
Cause: The server has realized that some threads are not needed to handle the present load.
Action: No action is required as the server auto tunes.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002908: Unable to create runtime MBean for Work Manager {0}. {1}
Cause: A fatal error occurred while creating the runtime MBeans.
Action: Contact My Oracle Support with the server logs.

Level: 1

Type: INTERNAL_ERROR

Impact: WorkManager

BEA-002911: Work Manager {0} failed to schedule a request due to {1}
Cause: Work Manager did not schedule a request due to a fatal failure.
Action: This is a critical failure. Report to My Oracle Support with the logs.

Level: 1

Type: INTERNAL_ERROR

Impact: WorkManager

BEA-002912: Overload Manager {0} rejected request as current length {1} exceeds max capacity of {2}
Cause: A request was rejected as the overload capacity was reached or exceeded.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002913: Work Manager {0} rejected request as the server is low on memory
Cause: A request was rejected as the server was low on memory.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002914: Shutdown callback invocation failed with: {0}
Cause: There was an internal error in the application shutdown.
Action: Report to My Oracle Support with the logs.

Level: 1

Type: ERROR

Impact: WorkManager

BEA-002916: Request belonging to Work Manager {0}, application {1} is rejected as the WorkManager is shutdown.
Cause: The request was refused entry because the Work Manager was shutdown.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002917: Enqueued request belonging to Work Manager {0}, application {1} is cancelled as the Work Manager is shutdown.
Cause: The request was refused because the Work Manager was shutdown.
Action: No action was required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002918: Server detected execute queue(s) in self-tuning mode. Execute queues will not be self-tuned. They retain their behavior from earlier releases. Consider using Work Managers to take advantage of self-tuning.
Cause: The execute queues were detected in the self-tuning server.
Action: Consider removing the execute queues. The server automatically adjusts the thread pool size for optimal performance. Work Managers can be used to change the default behavior where needed.

Level: 1

Type: WARNING

Impact: WorkManager

BEA-002919: Unable to find a Work Manager with name {0}. Dispatch policy {0} will map to the default Work Manager for the application {1}
Cause: There is no Work Manager with the given name.
Action: This could indicate a configuration error. Check the dispatch-policy and ensure that it matches the name of a Work Manager defined either within the same application or globally.

Level: 1

Type: WARNING

Impact: WorkManager

BEA-002920: An instance of the mSA Work Manager
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002921: The name of the Work Manager
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002922: The number of waiting requests in the queue
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002923: The number of requests that have been processed
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002924: An instance of the MinThreadsConstraint for a particular Work Manager
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002925: Completed request count
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002926: Pending requests that are waiting for an available thread
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002927: Number of requests that are currently executing
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002928: Number of requests executed out of turn to satisfy this constraint
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002929: Number of requests that must be executed to satisfy the constraint
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002930: The maximum time a request had to wait for a thread. Only requests whose execution is needed to satisfy the constraint are considered.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002931: Number of requests that must be executed to satisfy the constraint
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002932: An instance of the MaxThreadsConstraint for a particular Work Manager
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002933: Number of requests that are currently executing
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002934: Number of requests that are denied a thread for execution because the constraint is exceeded
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002935: request-class-name reference within ContextCase element for entry {0} with value: {1} ;cannot be resolved for Work Manager.
Cause:
Action:

Level: 1

Type: WARNING

Impact: WorkManager

BEA-002936: maximum thread constraint {0} is reached
Cause: The number of threads assigned to this work manager has reached the configured value in the maximum threads constraint
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002937: The maximum thread constraint {0} is no longer reached.
Cause: The number of threads assigned to this Work Manager has dropped below the configured value in the maximum threads constraint.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-002938: Global work manager "{0}" created with customized configuration
Cause: The default configuration for a global work manager has been overriden and the work manager is created with a customized configuration
Action: no action needed

Level: 1

Type: NOTIFICATION

Impact: WorkManager

BEA-003000: Could not send cache multicast message for key "{0}", {1}.
Cause: UThis error is usually caused by some communication failure.
Action: Check the exception message for details.

Level: 1

Type: WARNING

Impact: Cache

BEA-003001: Leasing failure: {0}
Cause: This error is usually caused by some communication failure.
Action: Check the exception message for details.

Level: 1

Type: WARNING

Impact: Cache

BEA-003002: Replication failure: {0}
Cause: This error is usually caused by some communication failure.
Action: Check the exception message for details.

Level: 1

Type: WARNING

Impact: Cache

BEA-003004: Unexpected failure {0}
Cause: This is a general purpose warning message.
Action: No action is required. The cache will try to adjust to the failure.

Level: 1

Type: WARNING

Impact: Cache

BEA-003005: CacheFilter not caching the response for uri: {0} reason: {1}
Cause: CacheFilter does not cache responses unless the status is 200.
Action: Check the message for information on how to fix the problem.

Level: 1

Type: WARNING

Impact: Cache

BEA-003090: Could not send cache multicast message for key "{0}", {1}.
Cause: This error is usually caused by some communication failure.
Action: Check the exception message for details.

Level: 1

Type: WARNING

Impact: LLD

BEA-003101: Modified non-dynamic {0} property on the Administration Server.
Cause: The non-dynamic {0} property was updated while the server was in a running state.
Action: Reboot the Administration Server so that the {0} property takes effect.

Level: 1

Type: WARNING

Impact: Cluster

BEA-003102: There was a failure in the execution of the post script {0} while deactivating MigratableTarget {1}. Since post script failure is marked as fatal, the MigratableTarget will not be automatically migrated. To enable automigration, fix the post script failure and manually migrate the failed migratable target or disable the post script failure fatal flag.
Cause: The execution ofthe post deactivation script failed.
Action: Fix the post deactivation script and migrate the MigratableTarget manually.

Level: 1

Type: ERROR

Impact: Cluster

BEA-003103: {0} failed to release its lease because of {1}. This may affect its automatic migration behavior.
Cause: An exception occurred: {1}.
Action: If a database is being used for leasing, ensure that it is available.

Level: 1

Type: ERROR

Impact: Cluster

BEA-003104: Failed to notify the execution failure of the post script {1} for {0} to the SingletonServiceStateManager because of {2}. This may affect its automatic migration behavior.
Cause: An exception occurred: {2}.
Action: Ensure that the network is working properly.

Level: 1

Type: ERROR

Impact: Cluster

BEA-003105: The asynchronous replication request timed out while attempting to add object {0} to the replication queue. This session has not been replicated to any backup at this point.
Cause: The asynchronous replication request timed out while attempting to add object {0} to the replication queue. Once full, the queue waits until it has space for the object. This wait took longer than the ClusterMBean specified AsyncSessionQueueTimeout, thus the session object was not put into the queue and will not be replicated at this time.
Action: This could be due to the secondary server or persistent store slowing down the replication process. To better handle this, the SessionFlushInterval and the SessionFlushThreshold can be reduced to replicate less at a time and to replicate more often. Checking the performance of the secondary server or persistent store is advised.

Level: 1

Type: WARNING

Impact: Cluster

BEA-003106: An unexpected exception occured during replication: {0}. Future session updates should replicate as expected.
Cause: An unexpected runtime exception occured during replication probably from the Remote Management Interface (RMI) stub. Future session updates should replicate as expected.
Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support. with the stack trace for further analysis.

Level: 1

Type: WARNING

Impact: Cluster

BEA-003107: Lost {0} unicast message(s).
Cause: This is an informational message. When a server joins a stable cluster, this message will appear since the server did not receive unicast messages sent out by other servers in the cluster.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003108: Unicast receive error : {0}
Cause: An error occurred while trying to receive a message over the cluster broadcast.
Action: Ensure that the NIC is functioning properly. If it appears that no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.

Level: 1

Type: ERROR

Impact: Cluster

BEA-003109: Cluster {0} uses a database as the migration basis but no data source for migration has been configured.
Cause: Cluster {0} uses a database as the migration basis but no data source for migration has been configured.
Action: Ensure that the data source is created and set for database migration basis.

Level: 1

Type: ERROR

Impact: Cluster

BEA-003110: Connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.
Cause: The connection attempt was rejected because the {1} protocol is not enabled at all for this server, as determined by the ServerMBean, or is not enabled on this particular channel.
Action: Enable the {1} protocol on the channel.

Level: 1

Type: WARNING

Impact: Cluster

BEA-003111: No channel exists for replication calls for cluster {0}
Cause: No channel exists for replication calls for cluster {0}
Action: Configure the channels for replication calls.

Level: 1

Type: ERROR

Impact: Cluster

BEA-003112: Channels "{0}" configured for replication traffic.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003113: Using one-way RMI for replication
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003114: Ignoring one-way RMI calls for replication because multiple replication channels are not present.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003115: Failed to synchronize a secondary session due to missing updates.
Cause: The Work Manager queue might be full and as a result update messages were dropped.
Action: Either increase the number of servers in the cluster (preferred) or add more replication channels (requires server re-start).

Level: 1

Type: ERROR

Impact: Cluster

BEA-003116: Starting Member Death Detector.
Cause: None.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003117: Starting Member Death Detector Heartbeat Receiver.
Cause: None.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003118: WLS Server "{0}" does not have an associated machine configured. Member Death Detector will not be enabled for this server.
Cause: No associated machine configured with the server.
Action: Please associate a machine with this server.

Level: 1

Type: WARNING

Impact: Cluster

BEA-003501: The migration of server {0} from machine {1} has failed. No suitable candidate machines could be found.
Cause: No candidate machines are available, or the server {0} has encountered an error on booting independent of its location.
Action: Further migration of server {0} has been disabled. When the cause of the problem has been determined and fixed, the server {0} should be started by the user, at which point it will resume standard automatic migration behavior.

Level: 1

Type: ERROR

Impact: Cluster

BEA-003502: Beginning the migration of server {0} from machine {1} to machine {2}
Cause: The failure of server {0} has provoked a migration attempt to a new machine, machine {2}.
Action: No action is required, but the logs of server {0} should be examined to determine why it crashed and could not successfully restart on machine {1}.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003503: The migration of server {0} from machine {1} to machine {2} has succeeded.
Cause: The failure of server {0} provoked a migration attempt to a new machine, machine {2}. The migration is now complete.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-003504: The migration of server {0} from machine {1} to machine {2} has failed, because machine {2} is not reachable.
Cause: Machine {2} was not reachable. A new machine for server {0} will be chosen.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: Cluster

BEA-010000: Exception occurred during ejbActivate: {0}
Cause: An error occurred while calling ejbActivate() on the bean.
Action: Check your implementation of the ejbActivate method.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010001: While deploying EJB "{0}", class {1} was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.
Cause: The specified class is located in the server classpath.
Action: Remove this class from the server classpath. It should only be located in the packaged application.

Level: 1

Type: WARNING

Impact: EJB

BEA-010002: An error occurred while undeploying: {0}.
Cause: An error occurred while undeploying.
Action: Please check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010003: Exception occurred while loading _WL_TIMESTAMP FILE.
Cause: The container generates the _WL_GENERATED file, which stores the server version of the appc compiler. If the current server version is different from the version specified in the _WL_GENERATED file, appc recompiles the beans. There was an error reading this file.
Action: The container will automatically recompile the beans.

Level: 1

Type: ERROR

Impact: EJB

BEA-010006: Error occurred while saving ejb deployment timestamps. {0}
Cause: The container generates the _WL_GENERATED file, which stores the server version of the appc compiler. if the current server version is different from the version specified in the _WL_GENERATED file, appc recompiles the beans. There was an error writing this file.
Action: Please check the exception for the exact error message. The container will recompile the beans if this file is not found.

Level: 1

Type: ERROR

Impact: EJB

BEA-010007: License validation passed for {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010008: EJB Deploying file: {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010009: EJB deployed EJB with JNDI name {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010011: Exception looking up current transaction: {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010012: Exception looking up current transaction: {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010014: Error occurred while attempting to rollback transaction: {0}
Cause: There was an error when rolling back the transaction.
Action: Please check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010015: Error occurred while marking transaction for rollback: {0}.
Cause: The container was unable to mark the transaction for rollback.
Action: Please check the exception for exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010016: Exception occurred while marking transaction for rollback: {0}.
Cause: The container was unable to mark the transaction for rollback.
Action: Please check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010017: Exception occurred during rollback of transaction {0}: {1}.
Cause: The container was unable to rollback the transaction.
Action: Please check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010018: Error occurred while resuming caller transaction: {0}
Cause: The container was unable to resume the transaction.
Action: Please check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010019: Running in a cluster, but DNS name of cluster is not set. This may prevent EJB handles from operating properly.
Cause: The DNS name of the cluster is not set.
Action: Set the DNS cluster name.

Level: 1

Type: WARNING

Impact: EJB

BEA-010020: EJB-20 - MessageDriven - Could not start the JMS connection: {0}
Cause: The JMS provider may not be available, or the Message-Driven Bean deployment descriptors or annotation or both may not be correct.
Action: Verify that the JMS provider is running and accessible through the network. Verify that the deployment descriptors or annotation or both specify the correct configuration information for the JMS provider.

Level: 1

Type: ERROR

Impact: EJB

BEA-010021: Clusters must be homogeneous for EJB replication. Ensure that you have deployed the bean named {0} on all members of your WebLogic cluster.
Cause: Clusters must be homogeneous for EJB replication.
Action: Ensure that you have deployed the bean named {0} on all members of your WebLogic cluster.

Level: 1

Type: ERROR

Impact: EJB

BEA-010022: Error occurred in ejbPassivate: {0}.
Cause: There was an error passivating the bean.
Action: Please check the exception for the exact error message. Verify the implementation of the ejbPassivate method in the bean.

Level: 1

Type: ERROR

Impact: EJB

BEA-010024: Error occurred during passivation: {0}
Cause: The container was unable to passivate the bean.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010025: Exception occurred during rollback of transaction {0}: {1}
Cause: An error occurred when rolling back the transaction.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010026: Exception occurred during commit of transaction {0}: {1}.
Cause: An error occurred when committing the transaction.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010029: Exception occurred during commit of transaction {0}: {1}.
Cause: An error occurred while committing the transaction.
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010030: Ignoring exception that occurred when rolling back a transaction during undeployment of {0}.
Cause: An error occurred while undeploying the bean.
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010031: EJB exception in method: {0}: {1}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010032: Exception during ejbActivate(): {0}
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010033: Exception from ejbLoad: {0}
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010034: Exception from ejbStore: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010036: Exception from ejbStore: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010038: Exception from __WL_superEjbLoad: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010039: Exception in ejbStore: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010040: Exception in ejbStore: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010043: Exception in ejbActivate: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010044: Exception trying to resume transaction: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010045: Exception in afterBegin: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010046: Exception in beforeCompletion: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010047: Exception during setRollbackOnly: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010048: Exception in afterCompletion: {0}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010049: EJB exception in method: {0}: {1}.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010050: A stateless session bean with bean-managed transactions must commit or roll back a transaction before the business method completes.
Cause:
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010051: EJB exception occurred during invocation from home: {0} generated exception: {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010052: An exception occurred while creating the free pool for EJB {0}. Since this occurred during server startup, when a dependent resource may be unavailable, the error will be ignored and deployment will proceed. The EJB container will instead attempt to create the bean instances on demand. The exception was: {1}
Cause: An exception occurred while the EJB container was initializing the free pool of bean instances. The root exception should be printed as part of the warning message issued by the EJB container. Check the server log for further details.
Action: If you believe the root exception is due to a temporary condition that will automatically be resolved, no action is required. If this exception was not due to a temporary condition, fix the cause of the root exception. If changes to your application are required to fix this issue, redeploy the updated application.

Level: 1

Type: WARNING

Impact: EJB

BEA-010054: EJB deployment: {0} has a class {1} that is in the classpath. This class should only be located in the ejb-jar file.
Cause: {1} is in the classpath.
Action: Remove this class from the classpath. It should only be in the ejb-jar.

Level: 1

Type: WARNING

Impact: EJB

BEA-010055: Could not load the RDBMS deployment descriptor for EJB {0} from the file {1}. The file was not found in the JAR file {2}.
Cause: {1} is missing from the JAR file.
Action: Please add the missing file to the JAR file.

Level: 1

Type: ERROR

Impact: EJB

BEA-010057: Could not find a license for EJB 3.0. Please contact Oracle to get a license.
Cause: Unable to get license for EJB 3.0.
Action: Contact Oracle to get a license.

Level: 1

Type: ERROR

Impact: EJB

BEA-010058: The EJB deployment named {0} is being recompiled within the WebLogic Server instance. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a standalone tool to generate the required classes.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010059: An error occurred while attempting to invalidate the target Read-Only Entity EJB: {0}. The error was: {1}
Cause: The invalidation of read-only beans failed.
Action: Check the message for the cause.

Level: 1

Type: ERROR

Impact: EJB

BEA-010060: The Message-Driven EJB {0} has connected or reconnected to the JMS destination {1}.
Cause: The JMS connection has been re-established.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010061: The Message-Driven EJB {0} is unable to connect to the JMS destination {1}. The Error was: {2}
Cause: The JMS destination is not available due to a network problem or a problem with the JMS provider, or the configuration information in the MDB deployment descriptor or annotation or both is incorrect. This warning may also occur during WebLogic cluster startup if the JMS destination is located on another server.
Action: Check that the JMS provider is running and that network connectivity is available. Also check that the configuration information in the MDB deployment descriptor and/or annotation is correct.

Level: 1

Type: WARNING

Impact: EJB

BEA-010065: MessageDrivenBean threw an Exception in onMessage(). The exception is: {0}.
Cause: The onMessage method of the MDB may have generated an exception for a legitimate reason, such as the loss of a database connection. If that is not the case, then the MDB may have a programming error that causes it to generate an unchecked Java exception, such as a NullPointerException.
Action: Unless you are sure that the MDB has generated the exception on purpose, check the source code to ensure that it does not contain any programming errors that might cause it to generate an unchecked Java exception such as a NullPointerException or IndexOutOfBoundsException.

Level: 1

Type: WARNING

Impact: EJB

BEA-010066: The Entity EJB {0} generated an exception when its unsetEntityContext was called. This error is ignored by the EJB container. The error is: {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010067: Exception during ejbRemove: {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010071: Error occurred while performing Pop of Caller Principal: {0}
Cause: This is a possible internal container error.
Action: Check the security settings related to the run-as roles and principals setting.

Level: 1

Type: ERROR

Impact: EJB

BEA-010072: Error occurred while starting EJB module {0}. Exception is: {1}
Cause: The container was unable to start the EJB module.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010073: Unable to add the {0} interface "{1}" and any dependent classes to the client-jar since it was loaded from the classpath.
Cause: EJB interface and other dependent classes exist in the system classpath.
Action: Please remove the classes from the system classpath.

Level: 1

Type: WARNING

Impact: EJB

BEA-010074: Unable to create the client-jar file due to classes being loaded from the classpath rather than the input JAR. Please modify your classpath so that it does not contain these classes and try again.
Cause: EJB interface and other dependent classes exist in the system classpath.
Action: Please modify your classpath so it does not contain these classes and try again.

Level: 1

Type: WARNING

Impact: EJB

BEA-010075: Skipping creation of the client-jar since no EJBs with a remote client view are contained in the JAR file.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010076: Client-jar {0} created.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010079: An error occurred while attempting to receive a message from JMS for processing by a Message-Driven Bean: {0} The exception is : {1}
Cause: The JMS provider for the MDB may have been shut down or has crashed, or network connectivity may have been lost.
Action: Check that the JMS provider is available and accessible through the network.

Level: 1

Type: ERROR

Impact: EJB

BEA-010080: An error occurred while attempting to process a message inside a Message-Driven Bean: {0} Exception is : {1}
Cause: This error usually occurs if the onMessage method of the MDB throws an exception.
Action: Check that the MDB is able to process messages by ensuring that any resources it uses (such as database connections) are available. Check the MDB source code to ensure that it does not have any bugs that cause an exception (such as a NullPointerException) to be generated.

Level: 1

Type: ERROR

Impact: EJB

BEA-010081: The Message-Driven Bean {0} was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.
Cause: The nature of the JMS API does not permit this in a standard way.
Action: No action is required. However, if you require better performance for a foreign JMS provider and do not need exactly-once transactional semantics, redeploy the MDB so that it has a transaction mode of NotSupported.

Level: 1

Type: WARNING

Impact: EJB

BEA-010082: Failed to undeploy security role for resource {0}, while undeploying EJB.
Cause: Unable to remove the role from the security layer.
Action: Check the exception for the exact error message.

Level: 1

Type: WARNING

Impact: EJB

BEA-010083: Failed to undeploy security policy for resource {0}, while undeploying EJB.
Cause: The policy could not be removed from the security layer.
Action: Check the exception for the exact error message.

Level: 1

Type: WARNING

Impact: EJB

BEA-010084: The Message-Driven Beans are being suspended. This may take a minute or two.
Cause: The server is being suspended or shut down.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010085: The Message-Driven Beans have all been suspended.
Cause: The server is being suspended or shut down.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010086: The deployment unit {0} that contains Message-Driven Beans is undeployed already. The server cannot start the Message-Driven Beans that are part of undeployed unit.
Cause: The beans were started after having been undeployed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010087: The EJB deployment named {0} is being recompiled within the WebLogic Server instance. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a standalone tool to generate the required classes. The generated source files will be placed in {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010088: Could not find a license for in-memory replication of the EJB. This feature is disabled;
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010089: Failed to create copy of bean {0} with error: {1}.
Cause: The server was unable to create the secondary server.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010090: Failed to update secondary copy with: {0}
Cause: The server was unable to update the secondary.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010091: Failure during stateful session bean replication: {0}
Cause: The container was unable to replicate the stateful session bean.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010092: Failure while updating secondary server during replication of {0}. The error was: {1}
Cause: The server was unable to update the secondary server.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010094: Failed to update the secondary copy of a stateful session bean from home {0}.
Cause: The server was unable to update the secondary server.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010096: The Message-Driven EJB {0} is unable to connect to the JMS destination or bind to JCA resource adapter {1}. The onnection failed after {2} attempts. The MDB will attempt to reconnect/rebind every {3} seconds. This log message will repeat every {4} seconds until the condition clears.
Cause: The JMS provider or JCA resource adapter is not available, or the configuration is incorrect and WebLogic Server is not able to connect.
Action: Ensure that the JMS provider is running and is reachable using the network, or the JCA resource adapter is deployed. Also ensure that the configuration information in the MDB deployment descriptor or the annotation or both are correct.

Level: 1

Type: WARNING

Impact: EJB

BEA-010097: Exception occurred during the invocation of EJB {0} with primary key {1}.
Cause: The bean generated a system exception.
Action: Check the exception for the exact error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010098: The database type {0} mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver {1}.
Cause: The database type {0} mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver {1}.
Action: Check the database-type tag inside weblogic-cmp-rdbms-jar.xml.

Level: 1

Type: WARNING

Impact: EJB

BEA-010099: WARNING(S) from EJB QL Compiler. {0}
Cause: The compilation of EJB-QL succeeded. These are some non-fatal warnings.
Action: Check the message for the exact warnings.

Level: 1

Type: WARNING

Impact: EJB

BEA-010100: This server is not part of a cluster. Therefore the InMemory replication feature for StatefulSession EJB {0} will have no effect on this server.
Cause: The bean has been deployed on a server, which is not a part of cluster. Hence the InMemory replication feature will be ignored.
Action: No action is required.

Level: 1

Type: WARNING

Impact: EJB

BEA-010102: Error encountered while attempting to create default DBMS table {0}. Error text: {1}
Cause: An error was encountered while attempting to create the default DBMS table.
Action: Take appropriate action based on the logged error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010124: Method SecurityHelper.{0} returned a NULL principal. The CallerPrincipal stack has been corrupted.
Cause: One cause of corruption might be that a bean has created its own threads. Note that this would be in violation of EJB2.0 Final Spec Chapter: Runtime Management 24.1.2.
Action: Review your code about thread safety. If a bean does not create its own thread, this is likely a bug in the EJB subsystem and you should probably contact My Oracle Support.

Level: 1

Type: ERROR

Impact: EJB

BEA-010127: Incorrect data source type detected. The data source with JNDI name {0}, specified in the RDBMS deployment descriptor for the EJB {1}, does not support global transactions.
Cause: The EJB container requires that a data source which supports global transactions be specified for transactions to be managed correctly.
Action: Specify the correct data source for the EJB.

Level: 1

Type: ERROR

Impact: EJB

BEA-010128: Error during deployment of EJB {0}. The EJB references an application-level cache, {1}, that is not defined in the weblogic-application.xml descriptor.
Cause: The weblogic-ejb-jar.xml descriptor for the EJB refers to an unknown application-level cache.
Action: Ensure that the application-level cache is defined in the weblogic-application.xml descriptor and ensure the cache name defined in the weblogic-ejb-jar.xml is correct.

Level: 1

Type: ERROR

Impact: EJB

BEA-010129: Error during deployment of EJB {0}. The EJB references a MultiVersion application-level cache {1}, but it must use an Exclusive cache instead. EJBs with a concurrency-strategy of Exclusive must use an Exclusive cache.
Cause: An incorrect concurrency strategy is specified. The concurrency-strategy you specify for the bean must be compatible with the caching-strategy specified in weblogic-application.xml.
Action: Specify the correct concurrency strategy.

Level: 1

Type: ERROR

Impact: EJB

BEA-010130: An error occurred during deployment of EJB {0}. The EJB references an Exclusive application level cache {1}, but it must use a MultiVersion cache instead. EJBs with a concurrency-strategy of Database, ReadOnly, or Optimistic must use a MultiVersion cache.
Cause: An incorrect concurrency strategy is specified. The concurrency-strategy you specify for the bean must be compatible with the caching-strategy specified in weblogic-application.xml.
Action: Specify the correct concurrency strategy.

Level: 1

Type: ERROR

Impact: EJB

BEA-010132: Error during deployment of EJB {0}. The EJB has been deployed with use-select-for-update set to true. The database indicates it does not support SELECT ... FOR UPDATE.
Cause: The database indicates it does not support SELECT ... FOR UPDATE.
Action: Modify use-select-for-update to false, or use a different database that supports SELECT ... FOR UPDATE.

Level: 1

Type: ERROR

Impact: EJB

BEA-010139: Bean with primary key {0} already exists.
Cause: A bean with the indicated primary key value already exists.
Action: Do not use a non-unique value as a primary key.

Level: 1

Type: ERROR

Impact: EJB

BEA-010141: Creation of Many-To-Many relationship for primary key: {0} and {1} effected {2} rows in {3}, instead of just 1.
Cause: JoinTable contains a non-unique row for specified primary keys, indicating a Many-To-Many relationship.
Action: Check the JoinTable to remove the duplicate row.

Level: 1

Type: ERROR

Impact: EJB

BEA-010144: The setXXX method for a primary key field may only be called during ejbCreate.
Cause: The setXXX method for a primary key field may only be called during ejbCreate.
Action: Remove the setXXX method call (for a primary key field) from places other than ejbCreate.

Level: 1

Type: ERROR

Impact: EJB

BEA-010145: When a cmp-field and a cmr-field (relationship) are mapped to the same column, the setXXX method for the cmp-field may not be called.
Cause: The cmp-field is read-only.
Action: Remove the setXXX method call if cmp-filed is also used as cmr-field.

Level: 1

Type: ERROR

Impact: EJB

BEA-010146: The setXXX method for a cmr-field that is mapped to a primary key may not be called.
Cause: The cmr-field is read-only.
Action: Remove the setXXX method call if it is cmr-field mapped to a primary key.

Level: 1

Type: ERROR

Impact: EJB

BEA-010147: The setXXX method for a cmr-field may not be called during ejbCreate. The setXXX method should be called during ejbPostCreate instead.
Cause: The setXXX method should be called during ejbPostCreate instead.
Action: Move the setXXX method call for a cmr-field to ejbPostCreate.

Level: 1

Type: ERROR

Impact: EJB

BEA-010148: In EJB {0}, the primary key field {1} was not set during ejbCreate.
Cause: All primary key fields must be initialized during ejbCreate.
Action: Be sure to initialize the primary key field during ejbCreate.

Level: 1

Type: ERROR

Impact: EJB

BEA-010149: According to the EJB 2.0 specification, a value of "null" may not be assigned to a collection valued cmr-field.
Cause: This violates the EJB 2.0 specification.
Action: Avoid using a null argument for a collection valued cmr-field.

Level: 1

Type: ERROR

Impact: EJB

BEA-010152: Illegal value for concurrency-strategy. Value was {0}, but must be one of ReadOnly, Exclusive, Database, or Optimistic.
Cause: An illegal value was used for concurrency-strategy.
Action: Specify a correct value for concurrency-strategy. It must be one of ReadOnly, Exclusive, Database, or Optimistic

Level: 1

Type: ERROR

Impact: EJB

BEA-010153: Only instances of beans with a remote client view can invoke getEJBObject().
Cause: See the error message body.
Action: Remove the getEJBObject() method call from the local client.

Level: 1

Type: ERROR

Impact: EJB

BEA-010154: Only instances of beans with a local client view can invoke getEJBLocalObject().
Cause: See the error message body.
Action: Remove the getEJBLocalObject() method call from remote client.

Level: 1

Type: ERROR

Impact: EJB

BEA-010155: Only instances of beans with container-managed transaction demarcation can use getRollbackOnly().
Cause: See the error message body.
Action: Remove the getRollbackOnly() method call if container-managed transaction is not used, or enable container-managed transaction for EJB.

Level: 1

Type: ERROR

Impact: EJB

BEA-010156: Illegal attempt to call EJBContext.getRollbackOnly() from an EJB that was not participating in a transaction
Cause: See the error message body.
Action: Make sure to begin the transaction before calling the getRollbackOnly() method.

Level: 1

Type: ERROR

Impact: EJB

BEA-010157: Only instances of beans with container-managed transaction demarcation can use setRollbackOnly().
Cause: See the error message body.
Action: Remove the setRollbackOnly() method call if container-managed transaction is not used, or enable container-managed transaction for EJB.

Level: 1

Type: ERROR

Impact: EJB

BEA-010158: Illegal attempt to call EJBContext.setRollbackOnly() from an EJB that was not participating in a transaction
Cause: See the error message body.
Action: Begin the transaction before calling the setRollbackOnly() method.

Level: 1

Type: ERROR

Impact: EJB

BEA-010159: To support the use of Handles and HomeHandles, an EJB must be deployed with a JNDI name. This EJB, {0}, was deployed without specifying a JNDI name. To specify a JNDI name for this EJB, add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.
Cause: This EJB, {0}, was deployed without specifying a JNDI name.
Action: To specify a JNDI name for this EJB, add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.

Level: 1

Type: ERROR

Impact: EJB

BEA-010160: Security violation: User {0} has insufficient permission to access EJB {1}.
Cause: The specified user has insufficient permission to access the EJB.
Action: Grant sufficient permissions to the user to enable to access the EJBResource.

Level: 1

Type: ERROR

Impact: EJB

BEA-010166: Error occurred while starting transaction: {0}.
Cause: An exception occurred while starting the Message-Drive Bean transaction.
Action: Take appropriate action based on the text of the exception message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010167: Message-Driven Beans are not allowed to call {0}.
Cause: The method is unavailable for MDBs.
Action: Remove the method call from the MDBs.

Level: 1

Type: ERROR

Impact: EJB

BEA-010168: Method {0} has been declared in an assembly-descriptor exclude-list and cannot be executed.
Cause: The specified method is declared in the exclude-list.
Action: Remove the method name from the exclude-list or remove the method call.

Level: 1

Type: ERROR

Impact: EJB

BEA-010173: env-entry for type java.lang.Character had length = 0.
Cause: If there is env-entry for type java.lang.Character, the parameter value should not be length = 0.
Action: Use a non-zero length value for java.lang.Character env-entry.

Level: 1

Type: ERROR

Impact: EJB

BEA-010188: Error encountered while attempting to drop Default DBMS Table {0}.
Cause: See the exception stack trace included in the logged message.
Action: Take appropriate action based on the exception stack trace in the logged message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010189: Error encountered while attempting to alter Default DBMS Table: {0}.
Cause: See the exception stack trace included in the logged message.
Action: Take appropriate action based on the exception stack trace in the logged message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010191: The alter table option is not supported in {0}. Use the DropAndCreate option.
Cause: The alter table option is not supported in the given database.
Action: Use the DropAndCreate option.

Level: 1

Type: ERROR

Impact: EJB

BEA-010194: Only instances of beans with bean-managed transaction demarcation can use getUserTransaction().
Cause: An illegal invocation was made to the getUserTransaction() method on a Container Managed Bean.
Action: Remove the getUserTransaction() method call from EJBs that are using container-managed transaction.

Level: 1

Type: ERROR

Impact: EJB

BEA-010195: Security violation: User {0} has insufficient permission to access method {1}.
Cause: The specified user has insufficient permission to access the specified method.
Action: Grant sufficient permissions to the user to enable access to the method.

Level: 1

Type: ERROR

Impact: EJB

BEA-010197: The entity bean {0} uses optimistic concurrency with read-verification enabled. The database indicates that exclusive row locks are not supported. Read-verification will not guarantee data integrity if the isolation level of the transaction is lower than repeatable read.
Cause: This is a mismatch problem between the concurrency strategy and the transaction isolation level.
Action: If data integrity should be guaranteed under a read-verification enabled configuration, use the appropriate transaction isolation level.

Level: 1

Type: WARNING

Impact: EJB

BEA-010198: An exception occurred while uninitializing the EJB module {0}.
Cause: Check the exception for the exact cause.
Action: Check the exception for the exact error message, and take appropriate action.

Level: 1

Type: WARNING

Impact: EJB

BEA-010199: EJB {0} with run as role {1} has no run-as-principal-name specified in its deployment descriptor or annotation. The EJB container has chosen principal-name {2} from the security-role-assignment list for role {1} to be the run as principal name.
Cause: The specified EJB with the specified run as role has no run-as-principal-name specified in its deployment descriptor or annotation.
Action: Specify run-as-principal-name explicitly if the chosen principal-name is not the appropriate one.

Level: 1

Type: WARNING

Impact: EJB

BEA-010201: The Message-Driven Bean {0} encountered an error while recovering a JMS session. This is a secondary error. The original error occurred while the Message-Driven Bean was processing a message. The recover action was taken in an attempt to recover from the original error, which will be logged separately.
Cause: The Message-Driven Bean may have generated an exception, or there may be a problem with the JMS provider.
Action: Check that the JMS provider is running and accessible through the network. In addition, check that the Message-Driven Bean onMessage method does not generate any unchecked Java exceptions such as NullPointerException or IndexOutOfBoundsException.

Level: 1

Type: ERROR

Impact: EJB

BEA-010202: Call-by-reference is not enabled for EJB {0}. The server will have better performance if it is enabled. To enable call-by-reference, set the enable-call-by-reference element to True in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.
Cause: Call-by-reference is not enabled.
Action: If appropriate, enable call-by-reference in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for the EJB.

Level: 1

Type: WARNING

Impact: EJB

BEA-010204: The EJB component, {0}, will be rolled back and redeployed to update class {1}. This class is not a bean implementation class. Only bean implementation classes can be updated without redeploying the entire module, and only when enable-bean-class-redeploy is set to True in weblogic-ejb.jar.xml.
Cause: A command was issued to update the specified class.
Action: No action is necessary. This is just an informative message indicating why the EJB module is being redeployed, since this can cause disruption to clients using an EJB in this EJB module.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010205: The EJB module, {0}, will be rolled back and redeployed to update the class {1}. Bean implementation classes, such as this, can be updated without redeploying the entire EJB module. However, this can only be done if enable-bean-class-redeploy is set to True in weblogic-ejb.jar.xml or the corresponding annotation. If this is the behavior you want, set this value to True and redeploy.
Cause: A command was issued to update the specified class.
Action: No action is necessary. This is just an informative message indicating why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010206: The EJB module, {0}, will be rolled back and redeployed to update the class {1}. This bean implementation class could not be updated without redeploying the entire EJB module because it was changed incompatibly. Incompatible changes are any changes that cause the EJB compiler to be run. This includes modifying a public variable name or a public method signature.
Cause: A command was issued to update the specified class.
Action: No action is necessary. This is just an informative message to let the user know why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010207: License validation not passed for {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010208: ddl-file {0} created.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010209: ddl-file {0} could not be deleted.
Cause:
Action: Check the file permissions.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010210: Unable to write to ddl-file {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010211: Unable to alter the table, as the primary key has changed.
Cause:
Action: Use the DropAndCreate option to create the table.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010212: The EJB {0} contains at least one method without an explicit transaction attribute setting. The default transaction attribute of {1} will be used for the following methods: {2}.
Cause: The ejb-jar.xml deployment descriptor or corresponding annotation does not contain transaction attribute settings for the specified EJB methods.
Action: Assign transaction attributes for all methods of your EJB.

Level: 1

Type: WARNING

Impact: EJB

BEA-010213: Message-Driven EJB: {0}'s transaction was rolled back. The transaction details are: {1}.
Cause: The transaction was rolled back by the MDB container.
Action: This is an informational message. No action is needed.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010214: Error starting MDB {0}.
Cause: This error itself does not provide the cause of the error. The log file will contain an exception stack indicating the root cause of the failure.
Action: Inspect the log file for indications of the root cause of the failure.

Level: 1

Type: ERROR

Impact: EJB

BEA-010215: The durable subscription store with jms-client-id equal to {0} is deleted when MDB {1} is removed from the server.
Cause: The durable subscription store is deleted when the MDB is removed from the server and its durable-subscription-deletion is set to true.
Action: This is an informational message. No action is needed.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010216: The Message-Driven EJB: {0} is generating an exception when processing the messages. Delivery failed after {1} attempts. The EJB container will suspend the message delivery for {2} seconds before retry.
Cause: The Message-Driven Bean is generating an exception.
Action: Check the message delivery methods and resolve the exception condition.

Level: 1

Type: WARNING

Impact: EJB

BEA-010221: The Message-Driven EJB: {0} is unable to bind to the JCA resource adapter: {1}. The Error was: {2}
Cause: The JCA resource adapter is not deployed, or the configuration information in the MDB deployment descriptor or corresponding annotation is incorrect.
Action: Check that the JCA resource adapter is deployed and the configuration information in the MDB deployment descriptor or corresponding annotation is correct.

Level: 1

Type: WARNING

Impact: EJB

BEA-010222: The aggregate query {0} has a primitive return type but the query returned null because there were no values to which to apply the aggregate function.
Cause: There were no values to which to apply the aggregate function
Action: Handle ObjectNotFoundException correctly on the application side.

Level: 1

Type: ERROR

Impact: EJB

BEA-010223: EJB deployed Message Driven Bean {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010224: The EJB Timer: {0} has failed to successfully time out in {1} consecutive attempts. The container will delay the timeout for {2} milliseconds as configured for the timer.
Cause: This was caused by a failed ejbTimeout.
Action: It is possible that no action needs to be taken. However, it may be good to investigate why the original ejbTimeout failed.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010225: The EJB Timer: {0} has failed to successfully time out in {1} consecutive attempts. Since no retry delay was configured for this timer, the container will automatically delay the timeout for {2} seconds.
Cause: This was caused by a failed ejbTimeout.
Action: It is possible that no action needs to be taken. However, it may be good to investigate why the ejbTimeout has consecutively failed.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010226: Error executing clustered EJB timer for EJB {0} of module {1} of application {2}. While executing, the timer was unable to find a necessary internal resource required to execute. The most likely cause of this issue is that the EJB is no longer configured to use the clustered EJB timer service but timers still exist in the database.
Cause: The most likely cause of this error is that the EJB associated with this timer is no longer configured to use the clustered EJB timer service.
Action: If the EJB in question is no longer configured to use EJB timers, the timers associated with it should be removed from the database. This can be achieved by re-enabling clustered EJB timers for the EJB and then undeploying the EJB. This will cause any timers associated with the EJB to be removed from the database.

Level: 1

Type: ERROR

Impact: EJB

BEA-010227: EJB exception occurred during invocation from home or business: {0} generated exception: {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-010228: Failed to update the secondary copy of a stateful session bean business: {0}.
Cause: The server was unable to update the secondary server.
Action: Check the exception for the exact error message.

Level: 1

Type: ERROR

Impact: EJB

BEA-010230: EJB {0} : method name {1} and method name {2} are equal under case-insensitive comparison but both methods have declarative security settings. Declarative security checks are case-insensitive.
Cause: Both of the specified methods have declarative security settings.
Action: Avoid case-insensitive method name conflicts if method permissions are configured.

Level: 1

Type: WARNING

Impact: EJB

BEA-010231: The lock request from EJB {0} with primary key {1} timed-out after waiting {3} ns. The transaction or thread requesting the lock was {2}.
Cause: See error message body.
Action: See error message body.

Level: 1

Type: ERROR

Impact: EJB

BEA-010232: The version of EJB in Module ''{0}'' is ''{1}''. However, the deprecated ''enable-bean-class-redeploy'' feature is not supported in EJB 3.
Cause: See error message body.
Action: Use the FastSwap feature instead and remove the ''enable-bean-class-redeploy'' settings in the weblogic-ejb-jar.xml.

Level: 1

Type: WARNING

Impact: EJB

BEA-011047: In ejb-jar.xml or annotation, EJB {0} has container-transactions set when the EJB has a transaction-type of Bean. The container-transaction settings will be ignored.
Cause: The specified EJB has container-transactions set when the EJB has a transaction-type of Bean.
Action: No action is required.

Level: 1

Type: WARNING

Impact: EJB

BEA-011057: The table {0} was created by the user. The container does not drop or alter user-created tables. The container would verify the table in this case.
Cause: The table was already created by the user.
Action: Drop the table if the existing table is not correct. The container will then be able to create the table.

Level: 1

Type: WARNING

Impact: EJB

BEA-011059: The container was unable to create the DDL file.
Cause: This error does not provide the cause of the error. The log file will contain an exception stack indicating the root cause of the failure.
Action: Inspect the log file for indications of the root cause of the failure.

Level: 1

Type: WARNING

Impact: EJB

BEA-011061: Stack trace associated with message {0} follows:
Cause: An error condition was reported.
Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011062: The following exception has occurred:
Cause: An error condition was reported.
Action: Review the stack trace, which will help with debugging an existing problem.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011063: Stateless session beans with bean-managed transactions must commit or roll back their transactions before completing a business method. The method {0} of EJB {1} either returned or generated an Exception without properly completing a transaction.
Cause: A transaction started by the stateless session bean method did not complete before the method completed.
Action: Check the bean code to determine what caused the transaction to not commit or roll back, and fix code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.

Level: 1

Type: ERROR

Impact: EJB

BEA-011070: In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <field-group>(s) are defined but are not used in any <weblogic-query>, <weblogic-relationship-role> or <relationship-caching> <caching-element>s. The <group-name>(s) of the unreferenced <field-group>(s) are: {1}
Cause: Some field group definitions are not referenced in any query or relationship.
Action: Remove the field groups listed in the logged message from the descriptor or include its usage appropriately.

Level: 1

Type: WARNING

Impact: EJB

BEA-011071: In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <relationship-caching>(s) are defined but are not used in any <weblogic-query>. The <caching-name>(s) of the unreferenced <relationship-caching>(s) are: {1}
Cause: There are unused relation cachings defined in the weblogic-rdbms descriptor.
Action: Remove the unused relationship cachings listed in the logged message from the descriptor or include its usage appropriately.

Level: 1

Type: WARNING

Impact: EJB

BEA-011073: An error occurred while the EJB container was attempting to obtain information about the table {0} from the database. This information is necessary to validate the mapping between the fields of the EJB {1} and the table. The exception is: {2}
Cause: The most likely cause is an error communicating with the database. The error message should include the specific error message.
Action: The action depends on the specific error that occurred. Actions may range from retrying the failed deployment to seeking help from your database administrator. Also, ensure that you are using a supported database.

Level: 1

Type: ERROR

Impact: EJB

BEA-011076: Unable to deploy the EJB {0} because the database table {1} is not accessible. Ensure that this table exists and is accessible.
Cause: A required database table was not accessible.
Action: Ensure that the database table exists and is accessible.

Level: 1

Type: ERROR

Impact: EJB

BEA-011077: The EJB deployment contains settings for automatically creating or altering database tables. However, the server is in production mode, so no database tables will be created or altered.
Cause: The server is in production mode so the create-default-dbms-tables settings are being ignored.
Action: No action is required. To suppress the warning, remove the create-default-dbms-tables setting from your EJB deployment.

Level: 1

Type: WARNING

Impact: EJB

BEA-011078: An exception occurred while starting the freepool idle timeout timer for ejb: {0}, {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011079: An exception occurred while stopping the freepool idle timeout timer for ejb: {0}, {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011080: An exception occurred while starting the Cache idle timeout timer for cache: {0}, {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011081: An exception occurred while stopping the Cache idle timeout timer for cache: {0}, {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011082: Error: The message-destination-link {0} for the Message-Driven Bean {1} in the application module {2} could not be resolved. The target message-destination for the Message-Driven Bean could not be found. Ensure that the link is correct.
Cause: The target of the message-destination-link could not be found in the application.
Action: Fix the message-destination-link to point to a valid message-destination.

Level: 1

Type: ERROR

Impact: EJB

BEA-011083: The EJB specification prohibits stateful session beans from using the TimerService.
Cause: An illegal call was made to the getTimerService() method on the stateful session beans SessionContext.
Action: Correct the stateful session bean code so that it does not call the getTimerService() method from the bean class.

Level: 1

Type: ERROR

Impact: EJB

BEA-011084: This EJB class does not support EJB timers and therefore is prohibited from using the TimerService. To use EJB timers, the bean class must implement javax.ejb.TimedObject or have a method that is annotated with @Timeout.
Cause: An illegal call to the getTimerService() method on the EJBContext.
Action: Correct the EJB class so it either implements the javax.ejb.TimedObject interface or ensure that it does not call the getTimerService() method on the EJBContext.

Level: 1

Type: ERROR

Impact: EJB

BEA-011085: This timer has either expired or been canceled and therefore cannot be invoked.
Cause: An illegal call to a timer object after the timer had expired or was canceled.
Action: Ensure your bean class does not invoke expired or canceled timers.

Level: 1

Type: ERROR

Impact: EJB

BEA-011086: The timer associated with this TimerHandle has either expired or been canceled.
Cause: The timer associated with the TimerHandle has expired or been canceled.
Action: No action is required.

Level: 1

Type: ERROR

Impact: EJB

BEA-011087: This TimerHandle is being invoked outside of the context of the application in which it was created. Since timers are local objects, they can only be called from within the same application in which they were created.
Cause: This TimerHandle is being invoked outside of the context of the application in which it was created.
Action: Ensure that your application does not pass any TimerHandle references outside of the scope of the application.

Level: 1

Type: ERROR

Impact: EJB

BEA-011088: The following error occurred while invoking the ejbTimeout(javax.ejb.Timer) method of EJB {0}.
Cause: This could be caused by erroneous code in the ejbTimeout method or by the failure of a dependent resource.
Action: All exceptions that occur while invoking or attempting to invoke the ejbTimeout method should be investigated and resolved. If the ejbTimeout method is non-transactional, that is, has a transaction attribute of NotSupported, or if the bean uses bean-managed transactions, the ejbTimeout method may not be retried, leading to missed timeout notifications.

Level: 1

Type: ERROR

Impact: EJB

BEA-011089: The following error occurred while attempting to remove an EJB timer from the persistent store for EJB {0}.
Cause: This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.
Action: This cause of this error should be investigated and resolved promptly.

Level: 1

Type: ERROR

Impact: EJB

BEA-011090: The following error occurred while preparing to invoke the ejbTimeout(javax.ejb.Timer) method of EJB {0}.
Cause: This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.
Action: All exceptions that occur while attempting to invoke the ejbTimeout method should be investigated and resolved.

Level: 1

Type: ERROR

Impact: EJB

BEA-011091: The table {0} cannot be dropped or created since it uses a trigger to update the optimistic column of the EJB. The container will only verify the existence of the table.
Cause: The table uses a trigger to update the optimistic column of the EJB.
Action: To suppress this warning, set the create-default-dbms-tables value in the RDBMS deployment descriptor to Disabled.

Level: 1

Type: WARNING

Impact: EJB

BEA-011092: In production mode, the DropAndCreate, DropAndCreateAlways, and AlterOrCreate options are ignored. The container will only attempt to verify the existence and increment value of the sequence {0}.
Cause: Options that apply only to development mode are ignored in production mode.
Action: Do not use these values for Automatic Oracle SEQUENCE Generation in production mode.

Level: 1

Type: WARNING

Impact: EJB

BEA-011093: The SEQUENCE named {0} with INCREMENT {1} was not found in the database. This SEQUENCE was specified in the CMP deployment descriptor to be used for automatic primary key generation.
Cause: The SEQUENCE was not found.
Action: Examine the <automatic-key-generation> tag in the CMP deployment descriptor. In particular, re-examine the <generator-name> and verify that this is the correct name of the SEQUENCE. Also, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.

Level: 1

Type: ERROR

Impact: EJB

BEA-011094: The SEQUENCE named {0} does not have INCREMENT value of {1} in the database as specified in the CMP deployment descriptor. Either modify the key-cache-value for this SEQUENCE in the deployment descriptor or update the SEQUENCE in the database.
Cause: The SEQUENCE named {0} does not have an INCREMENT value of {1} in the database as specified in the CMP deployment descriptor.
Action: In the <automatic-key-generation> tag of the CMP deployment descriptor, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.

Level: 1

Type: ERROR

Impact: EJB

BEA-011095: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}. {2}
Cause: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}.
Action: The message contains the cause of the error. See the message body and resolve the reported error.

Level: 1

Type: ERROR

Impact: EJB

BEA-011096: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}. {2}
Cause: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}.
Action: The message contains the cause of the error. See the message body and resolve the reported error.

Level: 1

Type: ERROR

Impact: EJB

BEA-011097: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}. {2}
Cause: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}.
Action: The message contains the cause of the error. See message body and resolve the reported error.

Level: 1

Type: ERROR

Impact: EJB

BEA-011098: No generated primary key was returned from the database insert statement as expected. Verify that the primary key database column for this EJB is an IDENTITY column as declared in the CMP deployment descriptor for this EJB.
Cause: This is most likely caused by a database configuration error. It may also be caused by a JDBC driver that doesn't support the getGeneratedKeys() method on java.sql.Statement.
Action: Verify that the primary key column in the database is marked as an IDENTITY column (or a functional equivalent is setup for the column such as a database trigger to insert a value into the primary key column).

Level: 1

Type: ERROR

Impact: EJB

BEA-011099: Multiple generated keys were returned from the database insert statement. The EJB container is unable to determine which generated key corresponds to the primary key column. To use the IDENTITY primary key generator, you must only have a single automatically generated database column per EJB.
Cause: This is most likely caused by a database configuration error. Each EJB may only have a single automatically generated database column.
Action: Verify that the database table corresponding to the EJB only has a single generated column.

Level: 1

Type: ERROR

Impact: EJB

BEA-011109: Failed to register JACC policy context handlers for the EJB container.
Cause: An unexpected error condition occurred while registering JACC context policy handlers.
Action: See the error message stack trace for details on how to resolve this issue.

Level: 1

Type: ERROR

Impact: EJB

BEA-011110: The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database. This may generate missing keys.
Cause: The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database.
Action: In the <automatic-key-generation> tag, re-examine the <key-cache-size> and verify that it is set correctly.

Level: 1

Type: WARNING

Impact: EJB

BEA-011111: The SEQUENCE named {0} has key-cache-size set to {1} which is greater than the INCREMENT_BY value for the sequence in the database. This is not allowed as it may generate duplicate keys.
Cause: The key-cache-set size for the SEQUENCE is not valid.
Action: in the <automatic-key-generation> tag, re-examine the <key-cache-size> and set it to a value less than or equal to the INCREMENT_BY value for the sequence in the database.

Level: 1

Type: ERROR

Impact: EJB

BEA-011120: The CMP EJB {0} has enable-batch-operations set to true. The update queries, however, are not suitable for batching. Batched operations are turned off for this batch and the queries will be executed with multiple update statements.
Cause: Batching is turned off for update queries.
Action: No action is required.

Level: 1

Type: WARNING

Impact: EJB

BEA-011121: Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be found in the server classpath.
Cause: The plugin-class could not be found in the server classpath.
Action: Add the plugin-class in the server classpath.

Level: 1

Type: ERROR

Impact: EJB

BEA-011122: Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be instantiated.
Cause: The plugin-class could not be instantiated.
Action: Add the plugin-class in the server classpath.

Level: 1

Type: ERROR

Impact: EJB

BEA-011123: Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be found in the server classpath.
Cause: The plugin-class could not be accessed.
Action: Add the plugin-class in the server classpath.

Level: 1

Type: ERROR

Impact: EJB

BEA-011124: Error in Message-Driven Bean EJB {0}. The plugin-class {1} does not implement weblogic.ejb.spi.SecurityPlugin.
Cause: The plugin-class does not implement weblogic.ejb.spi.SecurityPlugin.
Action: Make the plugin-class implement weblogic.ejb.spi.SecurityPlugin.

Level: 1

Type: ERROR

Impact: EJB

BEA-011125: An unexpected error was encountered while attempting to remove any EJB timers from the persistent store for the EJB {0}.
Cause: An unexpected error occurred while attempting to remove EJB timers from the persistent store.
Action: See the particular error message for details about the error. If your application is failing to deploy because of this error, it may be necessary to manually remove the timers from the store.

Level: 1

Type: ERROR

Impact: EJB

BEA-011126: The same exception has consecutively caused the expiration to fail for EJB timer {0}. Consecutive errors of this type will no longer be logged for the current timer expiration.
Cause: The same exception has consecutively caused expiration of an EJB timer to fail.
Action: Investigate what caused the ejbTimeout method to fail. The original exception will be logged in a previous error message.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011127: Error deserializing one or more EJB timers from the persistent store for the EJB deployment {0}. An incompatible change to the class of a Serializable object associated with the timer may be the cause. If this is the case, you can either undeploy your application entirely to remove the EJB timers from the persistent store or revert the incompatible changes to the Serializable class so the EJB timer can be deserialized. The error was: {1}
Cause: A common cause of this error is an incompatible serializable class change in your application.
Action: If the error is due to an incompatible serializable class change in your application, there are two options for dealing with the serialization errors. The first option is to completely undeploy the EJB. which will cause all of the EJB timers in the persistent store to be permanently removed. The second option is to revert changes to the serializable class that is associated with the EJB timer and redeploy the application. This allows the EJB timer to be deserialized.

Level: 1

Type: ERROR

Impact: EJB

BEA-011128: Error creating an instance of the EJB {0}: {1}
Cause: See the reported error message for the cause. This error may be due to a configuration issue or a bug in the EJB container.
Action: See the specific error message for details and take appropriate action.

Level: 1

Type: ERROR

Impact: EJB

BEA-011129: Error deploying EJB {0} to server {1}. This EJB is configured to use the clustered EJB Timer implementation but this server is not part of a cluster.
Cause: It is illegal to deploy an EJB that uses clustered EJB timers to a server that is not part of a cluster.
Action: You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or ensure that any servers to which you deploy the EJB are part of a cluster.

Level: 1

Type: ERROR

Impact: EJB

BEA-011130: Error deploying EJB {0}. This EJB is configured to use the clustered EJB timer implementation but the data-source-for-job-scheduler cluster attribute is not configured.
Cause: While deploying this EJB, the EJB container determined the data-source-for-job-scheduler cluster attribute has not been set.
Action: You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or configure the data-source-for-job-scheduler attribute for your cluster.

Level: 1

Type: ERROR

Impact: EJB

BEA-011132: Error deploying EJB {0}. While binding a business interface to the JNDI name {1}, the following error occurred: {2}
Cause: See the specific error for details.
Action: The action to take depends on the specific error that occurred. If the error was a JNDI naming conflict, you may need to choose a different JNDI name for the interface.

Level: 1

Type: ERROR

Impact: EJB

BEA-011135: The EJB {0} is a singleton session bean. EJB 2.1 client views are not supported for singleton session beans.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011136: wasCancelCalled() should only be invoked from within an asynchronous business method invocation with return type Future.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011137: A singleton session bean with bean-managed transactions must commit or roll back a transaction before the business method completes.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011138: Singleton session beans with bean-managed transactions must commit or rollback their transactions before completing a business method. The method {0} of EJB {1} either returned or generated an exception without properly completing a transaction.
Cause: A transaction started by the singleton session bean method did not complete before the method completed.
Action: Check the bean code to determine what caused the transaction to not commit or roll back and fix the code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.

Level: 1

Type: ERROR

Impact: EJB

BEA-011139: The following exception occurred when processing the asynchronous invocation : {0}.
Cause: There error was encountered during the asynchronous invocation.
Action: See the exception stack trace for details.

Level: 1

Type: ERROR

Impact: EJB

BEA-011140: The argument {0} is not a valid local client view for the EJB {1}.
Cause: The argument is not a valid local client view for the EJB.
Action: Review the EJB configuration and calling code to determine the discrepancy.

Level: 1

Type: ERROR

Impact: EJB

BEA-011141: This EJB has already been removed.
Cause: The EJB has already been removed.
Action: Avoid the call for removed objects.

Level: 1

Type: ERROR

Impact: EJB

BEA-011142: Error creating EJB reference: {0}
Cause: An exception occurred while creating an EJB reference.
Action: The reported exception contains the root cause of the issue. Review the exception to identify the exact problem.

Level: 1

Type: ERROR

Impact: EJB

BEA-011143: Error removing stateful session bean: {0}
Cause: An unexpected error occured while trying to remove a stateful session bean.
Action: The reported exception has the root cause of the issue. Review the exception to identify the actual problem.

Level: 1

Type: ERROR

Impact: EJB

BEA-011144: Singleton EJB {0} failed to initialize.
Cause: A singleton EJB {0} failed to initialize.
Action: The message body has the root cause of the issue. Review it to identify the essential problem.

Level: 1

Type: ERROR

Impact: EJB

BEA-011145: Illegal call to a Write method from a Thread holding Read lock.
Cause: An illegal call to a Write method was made
Action: Remove or rewrite the call.

Level: 1

Type: ERROR

Impact: EJB

BEA-011146: Timed out while trying to aquire lock on Singleton {0} to invoke method {1}.
Cause: A timeout occurred while trying to aquire a lock.
Action: Check Singleton concurrency. A timeout has been reached.

Level: 1

Type: ERROR

Impact: EJB

BEA-011147: Singleton {0} is in use by another thread.
Cause: While this Singleton is being invoked, it cannot be called from other threads.
Action: Check Singleton concurrency.

Level: 1

Type: ERROR

Impact: EJB

BEA-011148: Singleton {0} not initialized as Singleton {1} from the DependsOn transitive, closure failed initialization.
Cause: A singleton was not initialized as a Singleton from the DependsOn transitive, closure failed initialization.
Action: Check the server log for the cause of the dependent Singleton initialization error and resolve it.

Level: 1

Type: ERROR

Impact: EJB

BEA-011223: Cannot invoke stateful callback on {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011224: Unable to bind the interface {0} to {1}. Another EJB has already bound an interface to that name.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011225: Unable to bind the interface {0} to {1}. This EJB has declared another interface already bound to that name.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011226: Error during {0}. Could not get connection: {1} {2}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011227: Error during finder {0}. Exception while preparing query: {1} {2} {3}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011232: Error during finder {0}. Exception while setting parameters for query {1} {2} {3}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011233: Error during finder {0}. Exception while executing query {1} {2}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011234: Could not find an EJB with a field that is mapped to table {0} and column {1}. The SQL query is {2}. Try using an SqlShape annotation to describe the query results or check that the SqlShape annotation in use is correct.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011235: Error in {0}, could not map relationship {1} role {2} to an EJB populated by the query {3}. EJBs populated by this query are: {4}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011236: Error executing finder {0}: SqlShape {1} contains {2} columns, but the result set returned by JDBC contains {3} columns. The number of columns in the SqlShape and the JDBC result set must match.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011237: A stored procedure or function is used by {0}, but no SqlShape is specified.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011238: Error in {0}. SQL query {1} does not select column values for all primary key fields of bean {2}. No columns were selected for the following fields: {3}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011239: Query-caching is not supported for read-write beans.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011240: Error obtaining nativeQuery: {0}, {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011241: An attempt was made to do an executeQuery on query {0}, using a non-WebLogic EntityManager.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011242: Internal Error: Extended Persistence Context has been closed!
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011243: attempt at illegal state transaction from {0} to {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011244: An illegal call was made to the EJBContext method. getMessageContext can only be called from SLSBs with web-service endpoint interfaces.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011245: The EJB {0} is not an EJB3.0 bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011246: The EJB {0} does not declare a {1} home interface.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011247: The EJB {0} does not implement the business interface {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011248: The bean has not been invoked through a business interface.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011249: It is illegal to invoke UserTransaction methods in ejbCreate or the PostConstruct method of a Message-Driven Bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011250: It is illegal to invoke UserTransaction methods in ejbRemove or the PreDestroy method of a Message-Driven Bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011251: It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a Message-Driven Bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011252: It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a stateful session bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011253: It is illegal to invoke UserTransaction methods in ejbCreate or the PostConstruct method of a stateless session bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011254: It is illegal to invoke UserTransaction methods in ejbRemove or the PreDestroy method of a stateless session bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011255: It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a stateless session bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011256: Single expiration timers cannot be cancelled from within ejbTimeout.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011257: It is illegal to invoke Timer methods in ejbRemove or a PreDestroy method from asession bean or Message-Driven Bean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011258: It is illegal to invoke Timer methods in ejbActivate or a PostActivate method.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011259: It is illegal to invoke Timer methods in ejbPassivate or a PrePassivate method.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011260: It is illegal to invoke Timer methods during a dependency injection.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011261: Invocation timed out. Timer is busy.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011262: Error cancelling timer
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011263: EjbJarBean is not set yet.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011264: Method {0} is marked TX_NEVER, but was called within a transaction.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011265: Unexpected exception in afterDelivery(): {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011266: An attempt was made to execute getDatabaseProductName using a non-WebLogic EntityManager.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011267: Error calling getDatabaseProductName: {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011268: An attempt was made to execute nativeQuery on query {0}, using a non-WebLogic EntityManager.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011269: Error obtaining nativeQuery: {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011270: Error preparing query: {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011276: An illegal attempt was made to make a re-entrant call to a stateful session bean: {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011277: An illegal attempt was made to make a re-entrant call to a stateful session bean from home: {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011278: The following dependency that was declared by {0} is not a Singleton Session Bean: {1}.
Cause: A dependency that was specified by a Singleton Session Bean must also be a Singleton Session Bean.
Action: Remove the illegal dependency from the dependency list or replace it with a Singleton Session Bean.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-011279: The following exception occured in PreDestroy processing for singleton session bean {0}: {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-012030: Illegal DOCTYPE for a WebLogic RDBMS CMP EJB11 descriptor file. DOCTYPE {0} not permitted. Only DOCTYPE {1} permitted here.
Cause: An illegal DOCTYPE was used.
Action: Make sure to update appropriate DOCTYPE to the descriptor file.

Level: 1

Type: ERROR

Impact: EJB

BEA-012031: The EJB {0} has a finder {1} for which the sql-select-distinct attribute has been specified. This attribute has been deprecated and will not be supported in future releases.
Cause: The deprecated sql-select-distinct attribute was used.
Action: Use the EJB-QL DISTINCT clause instead. The container will automatically filter duplicates if necessary.

Level: 1

Type: WARNING

Impact: EJB

BEA-012032: For EJB {0}, a weblogic-query element in the CMP deployment descriptor has no matching query element in the ejb-jar.xml descriptor. The settings specified in the weblogic-query element will be ignored. The EJB method referred to by the weblogic-query element is {1}.
Cause: The weblogic-query element references a wrong or non-existent query method for this entity EJB.
Action: Remove the weblogic-query element or update it so that it references the correct query method.

Level: 1

Type: WARNING

Impact: EJB

BEA-012033: Compiling generated EJB classes produced the following Java compiler output: {0}
Cause: While compiling EJB generated classes, the Java compiler produced output.
Action: Typically, there is no action to take. The Java compiler output is printed for informational purposes. If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact support.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-012034: The message-destination {0} declared in the ejb-jar.xml deployment descriptor or annotation of the EJB module {1} does not have a corresponding message-destination-descriptor element in the weblogic-ejb-jar.xml descriptor or corresponding annotation.
Cause: A declared message-destination is not mapped correctly.
Action: Map the declared message-destination to the actual message destination using the message-destination-descriptor element in weblogic-ejb-jar.xml.

Level: 1

Type: ERROR

Impact: EJB

BEA-012035: The Remote interface method: {0} in EJB {1} contains a parameter of type {2} which is not serializable. Though the EJB {1} has call-by-reference set to false, this parameter is not serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is serializable.
Cause: The EJB has call-by-reference set to false. A parameter can be passed using call-by-value only if the parameter type is serializable. As this parameter is not serializable, the parameter will be passed by reference.
Action: The parameter should implement the java.io.Serializable interface for it to be passed by value.

Level: 1

Type: WARNING

Impact: EJB

BEA-012036: Compiling generated EJB classes produced the following Java compiler error message: {0}
Cause: While compiling EJB generated classes, the Java compiler produced output.
Action: If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact My Oracle Support.

Level: 1

Type: ERROR

Impact: EJB

BEA-012037: In weblogic-ejb-jar.xml or annotation, a singleton-session-descriptor element was found for EJB {0}. This EJB was not declared as a singleton session bean in ejb-jar.xml or annotation.
Cause: There is an incompatible configuration between weblogic-ejb-jar.xml and ejb-jar.xml.
Action: Modify weblogic-ejb-jar.xml or ejb-jar.xml to keep configuration consistency whether singleton or non-singleton.

Level: 1

Type: ERROR

Impact: EJB

BEA-014000: Problem, encountered illegal value for transaction-isolation {0}.
Cause: See the error message body.
Action: Specify one of the following legal values: TransactionSerializable, TransactionReadCommitted, TransactionReadCommittedForUpdate, TransactionReadCommittedForUpdateNoWait, TransactionReadUncommitted, or TransactionRepeatableRead.

Level: 1

Type: ERROR

Impact: EJB

BEA-014001: RDBMS descriptor {0} contains transaction-isolation settings. These settings may conflict with isolation-level settings in your weblogic-ejb-jar.xml descriptor and will be lost if you edit this descriptor in the console.
Cause: The specified RDBMS descriptor contains transaction-isolation settings.
Action: Move the isolation-level settings to the weblogic-ejb-jar.xml descriptor.

Level: 1

Type: ERROR

Impact: EJB

BEA-014003: EJB {0} uses optimistic concurrency and contains a finder or select method, {1}, for which include-updates is true. This combination of features does not work properly with database {2}.
Cause: Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks, unless Oracle is used as the database. Oracle read consistency does not hold read locks, so in this case reads are performed using the current JTA transaction. When reads are performed in a local transaction updates that have been flushed prior to commit of the transaction are not visible.
Action: Set include-updates for the query to false to avoid this warning message, or if you are using Oracle as your database, set the database-type to Oracle in weblogic-cmp-jar.xml.

Level: 1

Type: WARNING

Impact: EJB

BEA-014004: In EJB {0}, <generator-type> is set to {1}. It is incompatible with Batch Operations due to database limitations. Both order-database-operations and enable-batch-operations are turned off by EJB container.
Cause: These are database limitations.
Action: Turn off automatic-key-generation in order to use batch operations.

Level: 1

Type: WARNING

Impact: EJB

BEA-014005: The configured dispatch policy {1} for Message-Driven Bean (MDB) {0} will be ignored: the MDB is not running in a WebLogic thread.
Cause: The queue MDB is driven asynchronously by a non-WebLogic JMS implementation and runs in a non-WebLogic thread mechanism, so the MDBs application thread pool is not configurable.
Action: To disable this warning, remove the dispatch-policy setting from the MDBs WebLogic descriptor file.

Level: 1

Type: WARNING

Impact: EJB

BEA-014006: The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.
Cause: The specified MDB named has a dispatch policy that refers to an unknown execute queue thread pool.
Action: Create an execute thread queue pool for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing execute queue thread pool.

Level: 1

Type: WARNING

Impact: EJB

BEA-014007: The bean named {0} contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified. This may result in corruption of BLOB and CLOB data.
Cause: The specified bean contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified.
Action: Specify "version" or "timestamp" in the <table-map> <verify-columns> element and specify the name of the <version> or <timestamp> column in the <optimistic-column> element.

Level: 1

Type: WARNING

Impact: EJB

BEA-014008: In EJB {0}, {1} references an SqlShape element {2} that is not defined. The list of SqlShape elements that are defined for this EJB is: {3}.
Cause: An undefined SqlShape element was referenced.
Action: Use an existing SqlShape or create the SqlShape that you wish to use.

Level: 1

Type: WARNING

Impact: EJB

BEA-014009: The Message-Driven Bean {0} of application {1} will now be suspended, as it listens to global JMS destination {2} and a new application version {3} is being redeployed.
Cause:
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-014010: The Message-Driven Bean {0} of application {1} will now be suspended, as it listens to global JMS topic {2} and a new application version {3} is being redeployed. Note also that the current Message-Driven Bean is not a durable subscriber to the topic, and messages published by the topic after the currently active version of the Message-Driven Bean is suspended may not be received by the new application version.
Cause: The specified Message-Driven Bean listens to the specified global JMS topic and a new application version is being redeployed.
Action: To ensure that the new application version will receive all messages published while the Message-Driven Bean was suspended, set the activation config property "subscriptionDurability" to "durable" in the deployment descriptor or annotation.

Level: 1

Type: WARNING

Impact: EJB

BEA-014011: EJB {0} uses optimistic-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. This combination of features is incompatible. The use-select-for-update is turned off by the EJB container in this case.
Cause: Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks. The element use-select-for-update in the RDBMS deployment descriptor when set to true, will cause SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the table. This conflicts with the Optimistic Concurrency strategy.
Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.

Level: 1

Type: WARNING

Impact: EJB

BEA-014012: EJB {0} uses optimistic-concurrency and disables cluster invalidation, but does not have verify-rows set to Read. This combination will prevent detection of stale data if the bean is never modified in a transaction.
Cause: Optimistic concurrency beans verify consistency of data only if the bean has been modified, unless verify-rows is set to Read. If some other member of a cluster modifies a bean, other members will not be notified of this modification and will continue to store stale data unless the other members also attempt to modify the bean.
Action: Set either of the elements verify-rows to Read or cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.

Level: 1

Type: WARNING

Impact: EJB

BEA-014013: EJB {0} does not have a concurrency-strategy of either optimistic or readOnly and disables cluster invalidation. Cluster invalidation is relevant only for these concurrency strategies.
Cause: When an EJB is using either optimistic or readOnly concurrency-strategy and is deployed to a cluster, the container invalidates such beans on modification to avoid throwing OptimisticConcurrencyExceptions. This invalidation can be turned off by setting the cluster-invalidation-disabled to true in the RDBMS deployment descriptor.
Action: Set cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.

Level: 1

Type: WARNING

Impact: EJB

BEA-014014: The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown work manager. The default work manager will be used instead.
Cause: The specified MDB has a dispatch policy that refers to an unknown work manager.
Action: Create a work manager for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing work manager.

Level: 1

Type: WARNING

Impact: EJB

BEA-014016: EJB {0} uses readonly-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is read-only, select-for-update is unnecessary.
Cause: Read-only beans cannot be updated. Therefore, use-select-for-update is unnecessary.
Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.

Level: 1

Type: WARNING

Impact: EJB

BEA-014017: EJB {0} uses exclusive-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is locked at the server level during a transaction, select-for-update on the database is unnecessary.
Cause: Exclusive concurrency is implemented by locking the bean at the server level when the bean participates in a transaction. Setting the element use-select-for-update in the RDBMS deployment descriptor to true causes SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the row in the database too. This may be unnecessary, as the bean is locked by the container.
Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.

Level: 1

Type: WARNING

Impact: EJB

BEA-014018: EJB {0} uses a verify-columns element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.
Cause: verify-columns is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.
Action: Remove verify-columns element in the RDBMS deployment descriptor to avoid this warning message.

Level: 1

Type: WARNING

Impact: EJB

BEA-014019: EJB {0} uses a verify-rows element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.
Cause: verify-rows is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.
Action: Remove the verify-rows element in the RDBMS deployment descriptor to avoid this warning message.

Level: 1

Type: WARNING

Impact: EJB

BEA-014020: EJB {0} uses an optimistic-column element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.
Cause: optimistic-column element is applicable only for optimistic concurrency beans. If the bean does not use optimistic concurrency, this element will be ignored.
Action: Remove the optimistic-column element in the RDBMS deployment descriptor to avoid this warning message.

Level: 1

Type: WARNING

Impact: EJB

BEA-014021: The EJB {0} has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-014022: {0} is bound with JNDI name {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015001: Unable to link class {0} in Jar {1} : {2}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015002: Unable to load class {0} in Jar {1} : {2}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015003: Unable to create virual Jar {0} : {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015004: The super class {0} of session bean class {1} is also a session bean class.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015005: The session type is not set in the deployment descriptor or annotation for session bean {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015007: No ejbCreate method was found for init method {0} in bean {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015008: No matching create method for @Init method {0} in bean {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015009: Could not load interceptor class {0}: {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015010: In bean {0}, there are multiple method permission annotations for method {1}, which is illegal.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015011: There are multiple method permission annotations for class {0}, which is illegal.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015012: Unable to load interface class {0}: {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015013: Bean class {0} does not implement interface method {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015014: ServiceEndpoint class {0} was specified but cannot be found.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015015: The super class {0} of Message-Driven Bean class {1} is also a Message-Driven Bean class.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015016: Message-Drive Bean {0} implements multiple interfaces and no messageListenerInterface was specified in the @MessageDriven annotation.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015017: In bean class {0}, the @EJB annotation is at class level, so the beanInterface must be explicitly specified.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015018: In interceptor class {0}, the @EJB annotation is at class level, so the beanInterface must be explicitly specified.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015022: {0} is not valid in this context. Bean class: {1}.
Cause: {0} is not valid in this context. Bean class: {1}.
Action: Remove {0} from the invalid location.

Level: 1

Type: ERROR

Impact: EJB

BEA-015023: {0} is not valid in this context. Bean method: {1}.{2}.
Cause: {0} is not valid in this context. Bean method: {1}.{2}.
Action: Remove {0} annotation from invalid location.

Level: 1

Type: ERROR

Impact: EJB

BEA-015024: Could not specify @JNDIName on local business interface {0} of Bean {1}.
Cause: The @JNDIName could not be specified on the local business interface {0} of Bean {1}.
Action: Remove the annotation from the local business interface.

Level: 1

Type: ERROR

Impact: EJB

BEA-015025: Unable to load a class that is specified in your ejb-jar.xml: {0}.
Cause: A class that is specified in your ejb-jar.xml cannot be loaded.
Action: Check ejb-jar.xml in the EJB JAR file.

Level: 1

Type: ERROR

Impact: EJB

BEA-015026: Reference name {0} of @{1} annotation on class {2} is not unique.
Cause: Reference name {0} of @{1} annotation on class {2} is not unique.
Action: Change the reference name {0} of @{1} annotation on class {2}.

Level: 1

Type: ERROR

Impact: EJB

BEA-015027: The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.
Cause: The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.
Action: Make the Message-Driven EJB non-transactional, or use a different connection factory that supports XA.

Level: 1

Type: ERROR

Impact: EJB

BEA-015028: The EJB {0} contains an illegal value for the activation config property DistributedDestinationConnection. The specified value is {1} but the legal values are EveryMember and LocalOnly.
Cause: See the error message body.
Action: Correct the activation config property.

Level: 1

Type: ERROR

Impact: EJB

BEA-015029: The EJB {0} contains an illegal value for the activation config property TopicMessagesDistributionMode. The specified value is {1} but the legal values are Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application.
Cause: See the error message body.
Action: Correct the activation config property.

Level: 1

Type: ERROR

Impact: EJB

BEA-015030: The EJB {0} has an illegal permutation on distributed topic type and topicMessagesDistributionMode. Replicated distributed topics work with Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application, but partitioned distributed topics only work with One-Copy-Per-Server or One-Copy-Per-Application. The EJB is configured to partitioned distributed topic and Compatibility.
Cause: See the error message body.
Action: Review the compatibility of distributed topic types and topicMessagesDistributionMode and fix them.

Level: 1

Type: ERROR

Impact: EJB

BEA-015031: The EJB {0} has a distributedDestinationConnection configured but the EJB is configured to connect to a remote cluster. Since the distributedDestinationConnection configuration is only valid in a local cluster, the setting will be ignored.
Cause: See the error message body.
Action: Connect to a local cluster, or remove the distributedDestinationConnection configuration.

Level: 1

Type: WARNING

Impact: EJB

BEA-015032: The EJB {0} is configured with the activation config property topicMessagesDistributionMode but the EJB is configured to connect to a JMS Queue. The topicMessagesDistributionMode is valid only for JMS Topic destinations.
Cause: See the error message body.
Action: Correct the activation config property.

Level: 1

Type: ERROR

Impact: EJB

BEA-015033: The EJB {0} has an invalid value configured for the activation config property {1}. Only WebLogic JMS server 10.3.4 or later versions support the values One-Copy-Per-Server or One-Copy-Per-Application. Prior to 10.3.4.0 Weblogic JMS server or other non-Weblogic JMS vendors, only the Compatibility value is supported.
Cause: See the error message body.
Action: Correct the activation config property.

Level: 1

Type: ERROR

Impact: EJB

BEA-015034: This destinaiton {1} is a remote replicated distribution topic which does not support durable subscriptions when the Message-Drive Bean {0} works in Compatibility mode.
Cause: See the error message body.
Action: Review and fix the compatibility of the activation config property SubscriptionDurability and topicMessagesDistributionMode.

Level: 1

Type: ERROR

Impact: EJB

BEA-015035: The EJB {0} is configured to support One-Copy-Per-Server mode but the partitioned topic is configured as LocalOnly. To support One-Copy-Per-Server mode, the LocalOnly setting will be overridden with EveryMember.
Cause: See the error message body.
Action: Change distributed-destination-connection to EveryMember to remove the warning.

Level: 1

Type: WARNING

Impact: EJB

BEA-015036: In the EJB {0}, the value for the activation config property {1} will be ignored since it is overridden with the value {2}.
Cause: See the error message body.
Action: To remove this warning, remove the duplicated configuration from the activation config property.

Level: 1

Type: WARNING

Impact: EJB

BEA-015037: In EJB {0}, the throws clause for method {1} in the bean class contains exceptions that are NOT in the throws clause of the corresponding {2} interface method.
Cause: See the error message body.
Action: Correct the throws clause. Implementation methods must have all exceptions that are provided by the corresponding interfaces.

Level: 1

Type: WARNING

Impact: EJB

BEA-015038: Problems definitively matching up the interface method {0} with a method in the bean class. Please modify your bean class to implement the interface {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015039: Cannot start an inactive Message-Driven Bean {0}. A redployment may be needed.
Cause: See the error message body.
Action: Redeploy the application and restart it.

Level: 1

Type: ERROR

Impact: EJB

BEA-015040: The Message-Driven Bean {0} is inactive now.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015041: The Message-Driven Bean {0} is active now.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015042: The JNDI name {0} is set for {1} home interface of EJB {2}, but can't find {1} home in deployment descriptor. Specify {1} home in ejb-jar.xml.
Cause: See the error message body.
Action: Specify {1} home in ejb-jar.xml.

Level: 1

Type: WARNING

Impact: EJB

BEA-015043: A concurrent-call attempt failed on a stateful session bean instance because the lock was held by another thread or transaction, either because concurrent-access is prohibited or access could not be granted in a specific time period. You may change the concurrent-access behavior using the @AccessTimeout annotation or a corresponding element in deployment descriptor.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: EJB

BEA-015044: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.
Cause: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.
Action: Remove @JNDIName from either {1} or {2}.

Level: 1

Type: ERROR

Impact: EJB

BEA-015045: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.
Cause: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.
Action: Remove @JNDIName from {0} or provide the class name of each client view.

Level: 1

Type: ERROR

Impact: EJB

BEA-040010: JMSServer "{0}" configured {1,choice,0#no session pools|1#1 session pool|2#{1} session pools}.
Cause: This message indicates the number of session pools that were configured or deployed for the JMSServer while processing the configuration file.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040014: Failed to start JMSServer. JMS is shutting down.
Cause: The JMS server failed to initialize.
Action: Modify the configuration and restart the server file. Then reboot the system. There should be earlier messages that indicate the cause of the failure.

Level: 1

Type: ERROR

Impact: JMS

BEA-040015: JMS shutdown is complete.
Cause: JMS has been shut down, either at the request of the administrator or due to configuration errors.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040017: JMSServer "{0}" connection factory JNDI binding failed, {1}. JMS is shutting down.
Cause: An error was found when binding the connection factory to a JNDI name during configuration.
Action: Modify the configuration and restart the server file. Then reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040018: Could not obtain a replicated or non-replicated InitialContext from the default provider, {0}.
Cause: An error was encountered when binding a JMS Server to a JNDI name during configuration.
Action: Modify the configuration and restart the server file. Then reboot the server.

Level: 1

Type: ERROR

Impact: JMS

BEA-040019: JMSServer "{0}" failed to bind to JNDI name: {1}.
Cause: An error was encountered when binding a JMS Server to a JNDI name during configuration.
Action: Modify the configuration and restart the server file. Then reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040024: JMSServer "{0}" byte threshold for destination {1} has been exceeded.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040025: JMSServer "{0}" byte threshold condition for destination {1} has cleared.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040026: JMSServer "{0}" message threshold for destination {1} has been exceeded.
Cause: This is an informational message.
Action: No action

Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040027: JMSServer "{0}" message threshold condition for destination {1} has cleared.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040028: JMSServer "{0}" byte threshold for the server has been exceeded.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040029: JMSServer "{0}" byte threshold for server has cleared.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040030: JMSServer "{0}" message threshold for the server has been exceeded.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040031: JMSServer "{0}" message threshold for the server has cleared.
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040068: JMSServer "{0}" error occurred while unregistering destination {1}.
Cause: Look for earlier messages that might explain the error.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMS

BEA-040069: JMSServer "{0}" error occurred while unregistering producer {1}.
Cause: Look for earlier messages that might explain the error.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMS

BEA-040070: JMSServer "{0}" error occurred while unregistering connection {1}.
Cause: Look for earlier messages that might explain the error.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMS

BEA-040071: JMSServer "{0}" error occurred while unregistering session {1}.
Cause: Look for earlier messages that might explain the error.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMS

BEA-040072: JMSServer "{0}" error occurred while unregistering consumer {1}.
Cause: Look for earlier messages that might explain the error.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMS

BEA-040089: JMSServer "{0}". JMS messages in store ({1}) were migrated from version {2} to 600.
Cause: Message migration happens automatically when starting JMS and an old store exists.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040090: Deployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.
Cause: This message indicates the number of default connection factories deployed while processing the configuration file.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040095: JMSServer "{0}". Store I/O failure, {1}.
Cause: There is no more of file space, a disk failure occurred, or a database failure occurred.
Action: Restart the database, if applicable, and restart JMS.

Level: 1

Type: INTERNAL_ERROR

Impact: JMS

BEA-040107: Undeployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.
Cause: This message indicates the number of default connection factories that were undeployed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040108: User connection factory "{0}" is started.
Cause: The specified user connection factory has been started.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040109: JMSServer "{0}" is started.
Cause: The specified JMS Server has been started.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040113: JMSServer "{0}", Opening file store "{1}" in directory "{2}". Starting scan of {3,choice,0#0 files|1#1 file|2#{3} files} totaling {4} bytes.
Cause: A JMS server has opened its persistent file store and is about to scan its contents for messages.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040119: Failed to deploy a JMS connection factory "{0}" due to {1}.
Cause: The JMS connection factory failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new connection factory.
Action: Modify the configuration and restart the server file. Then reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040120: Failed to bind JMS connection factory "{0}" with its JNDI name due to {1}.
Cause: This is a JNDI failure.
Action: Modify the configuration and restart the server file. Then reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040121: JMSServer "{0}". Cannot be deployed on multiple servers.
Cause: A JMS Server was deployed on more than one WebLogic Server instance, and this is not allowed.
Action: Change the configuration file and reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040122: Failed to deploy JMS Server "{0}" due to {1}.
Cause: The JMS server failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server.
Action: Modify the configuration and restart the server file. Then reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040123: Failed to start JMS Server "{0}" due to {1}.
Cause: A JNDI failure occurred, or there was a failure when starting destinations, server session pools and/or connection consumers.
Action: Modify the configuration and restart the server file. Then reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040124: JMSServer "{0}". Failed to create JMS server session pool "{1}" due to {2}.
Cause: The JMS server session pool failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server session pool.
Action: Modify the configuration and restart the server file. Then reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040125: JMSServer "{0}". Failed to create JMS connection consumer "{1}" due to {2}.
Cause: The JMS connection consumer failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS connection consumer.
Action: Modify the configuration and restart the server file. Then reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040127: Failed to create JMS multicast socket due to {0}.
Cause: The JMS multicast socket failed to initialize.
Action: Reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040215: JMS server "{0}". Cannot set "{1}" to -1 when paging is enabled. The value of the attribute remains unchanged.
Cause: This is caused by an invalid configuration.
Action: Disable paging before setting this value to -1.

Level: 1

Type: ERROR

Impact: JMS

BEA-040305: JMS service is initialized and in standby mode.
Cause: The initialization phase of the JMS service is completed and the JMS service is in standby mode.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040306: JMS service is active now.
Cause: The activation phase of the JMS service is completed, and the JMS service is in active mode.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040307: JMS service is suspending gracefully.
Cause: The JMS service has started the suspension phase. No new work will be accepted and JMS Service will attempt to complete all existing work before it brings itself to standby mode.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040308: JMS service is suspending.
Cause: The JMS service has started the suspension phase. No new work will be accepted and all the existing work will be terminated immediately before the JMS service brings itself to standby mode.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040321: JMSServer "{0}" is resuming.
Cause: The JMSServer "{0}" is resuming.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040324: JMSServer "{0}" is suspending.
Cause: The JMSServer "{0}" is suspending.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040325: JMSServer "{0}" is suspended.
Cause: The JMSServer "{0}" is suspended.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040351: ExpiredJMSMessage JMSMessageID={0} > {1} {2} </ExpiredJMSMessage
Cause: A message has been expired and the policy is to log the message header fields and messages properties so that they are printed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040352: ExpiredJMSMessage JMSMessageID={0} > {1} </ExpiredJMSMessage
Cause: A message has been expired and the policy is to log the message header fields so that they are printed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040353: ExpiredJMSMessage JMSMessageID={0} > {1} </ExpiredJMSMessage
Cause: A message has been expired and the policy is to log the messages properties so that they are printed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040354: ExpiredJMSMessage JMSMessageID={0} > </ExpiredJMSMessage
Cause: A message has been expired and the policy is to log only the MessageId, or there are no matching message header fields or message properties.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040359: Distributed Destination "{0}", member "{1}" is not associated with a physical destination.
Cause: This was caused by a onfiguration error.
Action: Modify the configuration and restart the server.

Level: 1

Type: WARNING

Impact: JMS

BEA-040368: The following exception has occurred:
Cause: An error condition has occurred.
Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help in debugging an existing problem.

Level: 1

Type: ERROR

Impact: JMS

BEA-040370: Linked Exception -----------
Cause: An error condition was reported.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040371: JMSServer "{0}" JMS server session pool is invalid and has not been started "{1}". Exception is "{2}".
Cause: The server session pool is invalid because it has an invalid Connection Factory or Listener.
Action: Edit the JMS session pool, verify that it has valid attributes, and reboot the server. Alternatively, delete the session pool and add a new valid JMS session pool.

Level: 1

Type: ERROR

Impact: JMS

BEA-040372: JMSServer "{0}" error occurred while unregistering the runtime MBean, {1}.
Cause: Unable to contact the Administration Server or unable to find the runtime MBean.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JMS

BEA-040373: Could not find a license for JMS. Please contact Oracle to get a license.
Cause: Unable to get a license for JMS.
Action: Contact your Oracle sales representative to get a license.

Level: 1

Type: ERROR

Impact: JMS

BEA-040376: Destination {0} has been paused for new message production.
Cause: A Production Pause request was issued for the specified destination.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040377: Destination {0} has been resumed for new message production.
Cause: A Production Resume request was issued for the specified destination.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040378: Destination {0} has been paused for insertion of messages from in-flight work completion.
Cause: An Insertion Pause request was issued for the specified destination.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040379: Destination {0} has been resumed for insertion of messages from in-flight work completion.
Cause: An Insertion Resume request was issued for the specified destination.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040380: Destination {0} has been paused for consumption.
Cause: A Consumption Pause request has been issued for the specified destination.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040381: Destination {0} has been resumed for consumption.
Cause: A Consumption Resume request has been issued for the specified destination.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040382: JMSServer {0} has been paused for new message production.
Cause: A Production Pause request was issued for the specified JMSServer.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040383: JMSServer {0} has been resumed for new message production.
Cause: A Production Resume request was issued for the specified JMSServer.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040384: JMSServer {0} has been paused for insertion of messages from in-flight work completion.
Cause: An Insertion Pause request was issued for the specified JMS server.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040385: JMSServer {0} has been resumed for insertion of messages from in-flight work completion.
Cause: An Insertion Resume request has been issued for the specified JMS server.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040386: JMSServer {0} has been paused for consumption.
Cause: A Consumption Pause request has been issued for the specified JMS server.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040387: JMSServer {0} has been resumed for consumption.
Cause: A Consumption Resume request has been issued for the specified JMS server.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040404: Foreign JMS Server "{0}" is started.
Cause: The specified foreign JMS server was started.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040405: Failed to bind an entity of Foreign JMS Server "{0}" with their JNDI names due to {1}.
Cause: This was caused by a JNDI failure.
Action: Modify the JMS module descriptor of the corresponding application and redeploy the application.

Level: 1

Type: ERROR

Impact: JMS

BEA-040406: Distributed destination "{0}" is started.
Cause: The specified distributed destination was started.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040407: Default connection factory "{0}" with its JNDI name "{1}" is started.
Cause: The specified default connection factory was started.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040408: Failed to bind default connection factory "{0}" with its JNDI name "{1}" due to {2}.
Cause: This was caused by a JNDI failure.
Action: Modify the configuration and restart the server file. Then reboot the system.

Level: 1

Type: ERROR

Impact: JMS

BEA-040409: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} {2} </FailedJMSMessage
Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040410: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage
Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040411: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage
Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040412: FailedJMSMessage for store-and-forward: JMSMessageID={0} > </FailedJMSMessage
Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log only the MessageId. Alternatively, there are no matching message header fields or message properties.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040420: The JMS transaction branch {1} for destination {0} was administratively committed.
Cause: This was caused by an administrative action.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040421: An administrative request to commit the JMS transaction branch {1} on destination {0} failed with the following exception. {2}
Cause: The cause of the failure may be indicated by the exception provided in the error message.
Action: The transaction may be in an invalid state to allow commit processing. Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040422: The JMS transaction branch {1} for destination {0} was administratively rolled back.
Cause: This was caused by an administrative action.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040423: An administrative request to rollback the JMS transaction branch {1} on destination {0} failed with the following exception. {2}
Cause: The cause of the failure may be indicated by the exception provided in the error message.
Action: Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040430: The "UserTransactionsEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.
Cause: A deprecated attribute was used.
Action: Use the XAConnectionFactoryEnabled attribute instead.

Level: 1

Type: WARNING

Impact: JMS

BEA-040431: The "XAServerEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.
Cause: A deprecated attribute is used.
Action: Use the XAConnectionFactoryEnabled attribute instead.

Level: 1

Type: WARNING

Impact: JMS

BEA-040442: While attempting to bind JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI.
Cause: Some other entity has already bound this JNDI name globally.
Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.

Level: 1

Type: WARNING

Impact: JMS

BEA-040443: While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer globally bound into JNDI under any name.
Cause: Some other entity has already bound this JNDI name globally.
Action: Determine the owner the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.

Level: 1

Type: WARNING

Impact: JMS

BEA-040444: While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised globally.
Cause: A network connection between the local server and the Administration Server may have gone down.
Action: Make sure that network connectivity is working properly and that the Administration Server is reachable.

Level: 1

Type: WARNING

Impact: JMS

BEA-040445: While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer locally bound into JNDI under any name.
Cause: Some other entity has already bound this JNDI name locally.
Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there or change the JNDI name of this destination so that it does not conflict with the existing one.

Level: 1

Type: WARNING

Impact: JMS

BEA-040446: While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised locally.
Cause: A network connection between the local server and the Administration Server may have gone down.
Action: Make sure that network connectivity is working properly and that the Administration Server is reachable.

Level: 1

Type: WARNING

Impact: JMS

BEA-040447: While attempting to bind the JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI locally.
Cause: Some other entity has already bound this JNDI name locally.
Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.

Level: 1

Type: WARNING

Impact: JMS

BEA-040448: JMSFileStoreMBean has been deprecated, and has been replaced with FileStoreMBean. The JMSFileStoreMBean "{0}" has been replaced in the configuration with a FileStoreMBean with the same name.
Cause: A deprecated MBean was replaced in the configuration.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JMS

BEA-040449: JMSJDBCStoreMBean has been deprecated, and has been replaced with JDBCStoreMBean. The JMSJDBCStoreMBean "{0}" has been replaced in the configuration with a JDBCStoreMBean with the same name.
Cause: A deprecated MBean was replaced in the configuration.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JMS

BEA-040450: The "PagingStore" attribute on the JMSServerMBean "{0}" has been deprecated. It is being replaced in the configuration with the new "PagingDirectory" attribute.
Cause: A deprecated MBean attribute was replaced in the configuration.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JMS

BEA-040451: The PagingStore attribute on the JMSServerMBean {0} has been deprecated. Since it currently refers to a JMSJDBCStoreMBean, and paging to a JDBC store is not supported, the JMS server will page messages to its local working directory.
Cause: A deprecated MBean attribute was replaced in the configuration.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JMS

BEA-040452: The server session pool feature has been deprecated, and it will be removed in an upcoming release. New applications should use message-driven beans (MDBs) instead.
Cause: A deprecated feature was detected in the configuration.
Action: Plan to replace use of server session pools in your application.

Level: 1

Type: WARNING

Impact: JMS

BEA-040453: The BytesPagingEnabled and MessagesPagingEnabled parmeters on the JMSServer {0} have been deprecated. These parameters are now ignored. The MessageBufferSize parameter should be used to configure paging in this release.
Cause: A deprecated parameter was encountered.
Action: Plan to use the new MessageBufferSize to control paging.

Level: 1

Type: WARNING

Impact: JMS

BEA-040455: Flow control has been enabled on JMS server "{0}" because memory is low
Cause: Too much memory is being used.
Action: Either increase the amount of memory available to the server, or decrease the MessageBufferSize parameter on the JMS server so that fewer messages remain in memory.

Level: 1

Type: WARNING

Impact: JMS

BEA-040456: An entity of type "{3}" with name "{2}" in JMS module "{0}" is not targeted. There is no subdeployment with name "{1}" in the configuration repository (config.xml). Therefore, this entity will not exist anywhere in the domain.
Cause: The entity of the given name and type in the given JMS module does not have a corresponding subdeployment in the configuration repository (config.xml). In order for this entity to exist in the domain, it must be targeted with a sub-deployment element.
Action: Add a sub-deployment stanza to the appropriate deployment descriptor in config.xml. This will either be a jms-system-resource for a system module, or an app-deployment for a stand-alone JMS deployable module. If the JMS module is inside a J2EE application (an EAR file), then you must add the sub-deployment stanza to the subdeployment that represents this JMS module in the J2EE application. You do not necessarily have to target the subdeployment yet. Simply adding the subdeployment with no targets will remove this warning. However, if you wish for this entity to exist somewhere in your domain you must target the sub-deployment.

Level: 1

Type: WARNING

Impact: JMS

BEA-040457: The Template named "{1}" element of Distributed Destination "{0}" is not supported and hence ignored. Please consider using a Uniform Distributed Destination.
Cause: An unsupported attribute JMSTemplate is used in a Distributed Destination.
Action: Use a Uniform Distributed Destination instead.

Level: 1

Type: WARNING

Impact: JMS

BEA-040458: Unable to unprepare {0} in module {1} due to {2}.
Cause: The prepared entity could not unprepare itself in a failure case.
Action: Refer to the available exception for more information.

Level: 1

Type: WARNING

Impact: JMS

BEA-040459: Unable to deactivate {0} in module {1} due to {2}.
Cause: The activated entity could not deactivate itself in a failure case.
Action: Refer to the available exception for more information.

Level: 1

Type: WARNING

Impact: JMS

BEA-040460: Unable to close the JMS component of module {0} due to {1}.
Cause: The JMS component could not close itself.
Action: Refer to the available exception for more information.

Level: 1

Type: WARNING

Impact: JMS

BEA-040461: Unable to deactivate {0} in module {1} due to {2}.
Cause: The activated entity could not deactivate itself in a failure case.
Action: Refer to the available exception for more information.

Level: 1

Type: WARNING

Impact: JMS

BEA-040464: Unable to destroy {0} in module {1} due to {2}.
Cause: The initialized entity could not destroy itself in a failure case.
Action: More information may be available from the exception.

Level: 1

Type: WARNING

Impact: JMS

BEA-040467: Unable to deactivate {0} in module {1} due to {2}.
Cause: The activated entity could not deactivate itself in a failure case.
Action: More information may be available from the exception.

Level: 1

Type: WARNING

Impact: JMS

BEA-040470: Unable to deactivate {0} in module {1} due to {2}.
Cause: The activated entity could not deactivate itself during dynamic deletion.
Action: More information may be available from the exception.

Level: 1

Type: WARNING

Impact: JMS

BEA-040475: The destination {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.
Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases, a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.

Level: 1

Type: WARNING

Impact: JMS

BEA-040476: The destination {0} does not have an associated quota object. The setting of messagesMaximum to {1} will have no effect.
Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.

Level: 1

Type: WARNING

Impact: JMS

BEA-040477: An error occurred while unbinding a remote JNDI object from local JNDI name "{0}". The exception encountered was {1}.
Cause: There may be an error in the JNDI subsystem. See the exception for more information.
Action: Check the exception message for more detail.

Level: 1

Type: WARNING

Impact: JMS

BEA-040478: The JMS subsystem could not deploy or undeploy the default JMS connection factories due to {0}.
Cause: There may be an error in the JNDI subsystem. See the exception for more information.
Action: Check the exception message for more detail.

Level: 1

Type: WARNING

Impact: JMS

BEA-040479: The system failed to roll back an added connection consumer of name {0}. The exception received was {1}.
Cause: See the exception for more information.
Action: Check the exception message for more detail.

Level: 1

Type: WARNING

Impact: JMS

BEA-040480: The system failed to remove a connection consumer of name {0}. The exception received was {1}.
Cause: See the exception for more information.
Action: Check the exception message for more detail.

Level: 1

Type: WARNING

Impact: JMS

BEA-040490: {0} {1} has a conflicting name attribute value, which is now changed to have a unique name with its JMSServer name. The new destination-name attribute now holds the original name value.
Cause: A name conflict has been detected during upgrade for JMS destinations, maybe because in WebLogic Server versions prior to 9.2, more than one destination was allowed to have the same name, as long as the destinations belonged to different JMS servers.
Action: Ensure that destinations are created with their name decorated with the target JMS server name to avoid conflict.

Level: 1

Type: WARNING

Impact: JMS

BEA-040491: A {0} {1} with multiple targets has been split into multiple deployments one for each unique target.
Cause: A JMS Deployment found with multiple unique targets configured.
Action: In WebLogic Server versions prior to 9.2, both JMSConnectionFactory and ForeignJMSServer were allowed to be targeted to more than one server, cluster, or both. During upgrade of this configuration to WebLogic Server 9.2, these configuration entities are split into more than one entity, one for each unique target.

Level: 1

Type: WARNING

Impact: JMS

BEA-040494: An error occurred while shutting down the JMS server {0}: {1}.
Cause: See the detail message.
Action: The server should still shut down normally. No action is required.

Level: 1

Type: WARNING

Impact: JMS

BEA-040496: The template {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.
Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
Action: Please consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.

Level: 1

Type: WARNING

Impact: JMS

BEA-040497: The template {0} does not have an associated quota object. The setting of MessagesMaximum to {1} will have no effect.
Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
Action: Consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.

Level: 1

Type: WARNING

Impact: JMS

BEA-040498: An error occurred while forwarding a message for distributed destination member {0}: {1}
Cause: There may be a temporary network problem, or one of the members of the cluster may be unavailable.
Action: See the detail message.

Level: 1

Type: WARNING

Impact: JMS

BEA-040499: An error occurred while pushing messages to a JMS client: {0}
Cause: There may be a network failure.
Action: The JMS protocol will recover automatically from such a problem eventually. Check for networking issues or crashed clients.

Level: 1

Type: WARNING

Impact: JMS

BEA-040500: Unable to deactivate entity "{0}" in module "{1}" due to {2}.
Cause: The activated entity could not rollback the proposed targeting change.
Action: More information may be available from the exception.

Level: 1

Type: WARNING

Impact: JMS

BEA-040501: Unable to roll back targeting change of the entity "{0}" in module "{1}" due to {2}.
Cause: The changed entity could not roll back in a failure case.
Action: More information may be available from the exception.

Level: 1

Type: WARNING

Impact: JMS

BEA-040502: While attempting to change the targeting of JMS module "{0}", an error occurred while activating the change. The exception returned is: {1}
Cause: The JMS module failed to activate a prepared change during a targeting update.
Action: More information may be available from the exception.

Level: 1

Type: ERROR

Impact: JMS

BEA-040503: The delivery mode override value of destination "{0}" hosted on JMS server "{1}" has been changed from {2} to {3}.
Cause: During the upgrade process, a configuration was detected that would force all messages through the given destination to be non-persistent. Therefore, the upgrade process made that override explicit.
Action: Review your application code and configuration. If you need a behavior other than the one that the upgrade process chose, you can modify the resulting configuration using the DeliveryMode parameter of the OverridesParams of the destination, or with the HasStore or AllowsPersistentDowngrade parameters of the JMS server on which the destination is targeted.

Level: 1

Type: WARNING

Impact: JMS

BEA-040504: While attempting to add an entity with name "{0}", an error occurred while trying to convert the old style entity to the new style entity. The error was "{1}".
Cause: See the description of the exception that occurred for more information on the cause of this failure.
Action: Take appropriate action based on the determined cause.

Level: 1

Type: WARNING

Impact: JMS

BEA-040505: The JMS module named "{0}" inside application "{1}" does not have a sub-deployment stanza named "{0}". Without such a stanza, no entities inside the module will be deployed, since the subdeployments inside of the sub-deployment stanza named "{0}" control where JMS entities inside this module are targeted.
Cause: When a JMS module is inside an EAR file, the targeting information for entities inside that module are nested within a sub-deployment named after the name of the JMS module found in the weblogic-application.xml file of the EAR file. If no sub-deployment exists with the name of the JMS module, then no targeted entities inside the module will become available. This is usually an oversight on the part of the administrator.
Action: Add a sub-deployment stanza with the name of the JMS module as specified in the weblogic-application.xml file to the app-deployment stanza. Nested inside that sub-deployment, you can target the entities in the module as you normally would.

Level: 1

Type: WARNING

Impact: JMS

BEA-040506: The JMS store-and-forward (SAF) forwarder has successfully connected to the remote destination "{0}".
Cause: This is an informational message.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040507: The JMS store-and-forward (SAF) forwarder failed to connect to the remote destination "{0}", because of {1}.
Cause: This is either due to a configuration error, a network failure, or the remote destination being temporarily unavailable.
Action: Check the configuration, network connection, or remote destination.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040508: BridgeDestinationMBean has been deprecated. The BridgeDestination "{0}" has been replaced in the configuration with a JMSBridgeDestination with the same name.
Cause: A deprecated MBean is being replaced in the configuration.
Action: No action is required.

Level: 1

Type: WARNING

Impact: JMS

BEA-040509: Failed to ${1} JMS Server "{0}" because the earlier attempt to ${2} was failed.
Cause: This error occurred during deployment of the JMS server.
Action: Fix any deployment errors related to this JMS server.

Level: 1

Type: ERROR

Impact: JMS

BEA-040510: While attempting to rename a connection factory named "{0}", an error occurred while attempting to establish a JNDI listener. The cause was {1}.
Cause: There was an error while attempting to establish a JNDI listener. The description of the cause may provide more information about the true cause of the error.
Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMS

BEA-040511: The system is waiting to unbind connection factory "{0}". An attempt is being made to change the JNDI name of this connection factory from "{1}" to "{2}".
Cause: An attempt is being made to unbind a connection factory from a JNDI name in order to dynamically change the JNDI from one name to another. This message will repeat every twenty seconds for five minutes.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: JMS

BEA-040512: An attempt is being made to change the JNDI name of connection factory "{0}" from "{1}" to "{2}". The system has waited to unbind "{1}" for five minutes. The new JNDI name "{2}" may or may not be bound properly.
Cause: The connection factory was not fully unbound after five minutes. Some error may have occurred while attempting to unbind this connection factory.
Action: In order to maintain the integrity of the connection factory it is recommended you untarget and retarget the connection factory that failed. Otherwise, the connection factory is in an indeterminate state.

Level: 1

Type: ERROR

Impact: JMS

BEA-040513: While attempting to rename a connection factory named "{0}", an error occurred while attempting to remove a JNDI listener. The cause was {1}.
Cause: There was an error while attempting to remove a JNDI listener. The description of the cause may provide more information about the true cause of the error.
Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.

Level: 1

Type: WARNING

Impact: JMS

BEA-040514: While attempting to rename a connection factory named "{0}" an error occurred in the JNDI listener. The error was {1}
Cause: While attempting to dynamically change the JNDI name of a connection factory, a JNDI error occurred. The error itself will tell more about the cause of this failure.
Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.

Level: 1

Type: WARNING

Impact: JMS

BEA-040515: A failured occured while attempting to unregister an InterceptionPoint, {0}.
Cause: An exceptoin coccurred while attempting to unregister an InterceptionPoint. The error will provide more details about the cause of this failure.
Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.

Level: 1

Type: WARNING

Impact: JMS

BEA-040520: One or more Weighted Distributed Destination (WDD) resources were detected in JMS configuration module "{1}": {0}. This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.
Cause: Deprecated resource was used.
Action: Use the Uniform Distributed Destination instead.

Level: 1

Type: WARNING

Impact: JMS

BEA-040521: The JMS resource "{0}" that you are trying to create in module "{1}" is a Weighted Distributed Destination (WDD). This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.
Cause: A deprecated resource is trying to create.
Action: Use the Uniform Distributed Destination instead.

Level: 1

Type: WARNING

Impact: JMS

BEA-045002: An error occurred while binding the remote JNDI object to the local JNDI name "{0}".
Cause: The local JNDI name that is attempting to bind to may not be valid.
Action: Check the JNDI name to see if its syntax is correct.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045028: The messages threshold for the JMS server {0} has been exceeded for more than one hour.
Cause: The threshold of the JMS server was exceeded.
Action: Verify that the messages are being consumed and that sufficient memory is available.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045029: The messages threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.
Cause: The messages threshold of the JMS server was exceeded.
Action: Verify that the messages are being consumed and that sufficient memory is available.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045030: The bytes threshold for the JMS server {0} has been exceeded for more than one hour.
Cause: The bytes threshold of the JMS server was exceeded.
Action: Verify that the messages are being consumed and that sufficient memory is available.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045031: The bytes threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.
Cause: The bytes threshold of the JMS server was exceeded.
Action: Verify that the messages are being consumed and that sufficient memory is available.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045032: While attempting to create destination {1} in module {2} the JMS server {0} could not be found.
Cause: The JMS server may be shutting down or may not have completed startup.
Action: Deploy the module again once the JMS server has completed startup.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045039: An attempt was made to add a JMS entity of an unknown type {1} in the module {0}.
Cause: The JMS module given to the update was invalid. It contained an unknown type.
Action: Ensure that the JMS module is valid.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045040: While attempting to add a {1} named {2} in module {0}, an error occurred.
Cause: A linked ModuleException will contain more detail about the cause of the failure.
Action: Examine the linked exception, which will contain more information about the cause of this failure.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045041: An attempt was made to remove a JMS entity of an unknown type {1} in the module {0}.
Cause: The JMS module given to the update was invalid. It contained an unknown type.
Action: Ensure that the JMS module is valid.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045042: An error occurred while adding {1} to the JMS module {0}.
Cause: See the linked exception for more detail.
Action: The linked exception will contain more information about why this add operation failed.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045043: An error occurred while removing {1} from the JMS module {0}.
Cause: See the linked exception for more detail.
Action: The linked exception will contain more information about why this add operation failed.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045045: A subdeployment named {1} was not found in the module {0}.
Cause: A subdeployment removal was attempted, but the subdeployment was unknown to the module.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045047: The SubDeploymentMBean {0} in deployment {1} can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue, topic or quota) has a sub-deployment-name element with value {0}
Cause: The SubDeploymentMBean of the given name cannot be targeted to anything but a single JMS server because an element of the JMS module that points to that subdeployment can only be targeted to a single JMS server.
Action: Modify the target of the subdeployment so that it only contains a single JMS server.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045048: The JMS server named {0} has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is {1}, and the template name is {2}. However, a JMSSystemResourceMBean of name {1} could not be found. The JMS server {0} will not boot until this problem has been fixed.
Cause: The temporary template for a JMS server must come from a JMSSystemResourceMBean. A common mistake is to put the temporary template into an AppDeployment. However, because the temporary template must be owned by the administrator, all temporary templates must come from JMSSystemResourceMBeans, not AppDeployments.
Action: Put the temporary template into a JMSSystemResource.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045049: JMS server {0} does not have a configured temporary template. However an attempt was made to create a temporary destination. This is not allowed.
Cause: A JMS server without a configured temporary template was used to create a temporary destination. This usage is not allowed.
Action: Create a JMSSystemResource that contains a template. Use that template as the temporary template for this JMS server.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045050: A destination named {3} has a jms-create-destination-identifier named {1}. However, another destination named {2} has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot both be located on the JMS server named {0}.
Cause: Two destinations cannot both have the same jms-create-destination-identifier on the same JMS server, even if the two destinations are from different modules.
Action: Either deploy the destination with the offending jms-create-destination-identifier to a different JMS server, or change the value of the jms-create-destination-identifier attribute.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045051: Two destinations with name {1} were deployed to the JMS server {0}.
Cause: Two destinations with the same fully qualified name cannot be deployed to the same JMS server. This error should have been caught during the validation phase of the JMS module.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045052: An attempt was made to change the target of a JMS entity that cannot have its target changed. The entity has name "{0}". The original target has name "{1}". The proposed target has name "{2}"
Cause: An attempt was made to change the target of an entity that cannot have its target changed dynamically.
Action: Untarget a subdeployment and then retarget that subdeployment elsewhere. However, by doing so, the persistent state maintained for entities retargeted in this fashion will not be kept on the old target and may or may not be removed by the system.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045054: Cannot dynamically add member {1} to sistributed destination {0}.
Cause: This member has either not been prepared yet or has already been removed.
Action: Ensure that the distributed destination member is not removed and is in a prepared state.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045055: Cannot dynamically remove member {1} from distributed destination {0}.
Cause: This member has either not been activated yet or is an invalid member.
Action: Ensure that the distributed destination member is valid and is in an activated state.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045060: The JMS module named "{0}" is neither an AppDeployment nor a JMSSystemResource.
Cause: An invalid application context was passed to a JMS module.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045061: An attempt was made to create a durable subscription on a queue named "{3}". The client identifier is "{0}", the subscriptionName is "{1}" and the selector is "{2}". Durable subscriptions may only be created on topics.
Cause: An attempt was made to create a durable subscription on a queue.
Action: Do not attempt to create a durable subscription on a queue.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045062: There can be no more than one jms-interop-module element in the config.xml file.
Cause: More than one jms-interop-module element was found in the config.xml file.
Action: Do not attempt to define more than one jms-interop-module element in the config.xml file.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045063: The jms-interop-module must have name interop-jms and a descriptor file name jms/interop-jms.xml. This has name "{0}".
Cause: An attempt was made to use a jms-interop-module with a name other than interop-jms.
Action: Do not attempt to define a jms-interop-module element in the config.xml file with a name other than interop-jms.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045064: The target named "{1}" of a JMS module inside a deployment named "{0}" must be a WebLogic Server instance or a cluster. Instead, it is of type "{2}".
Cause: An attempt was made to target a JMS module to an invalid type of target.
Action: Do not attempt to target a JMS module to anything other than WebLogic Server instances or clusters. Any other type of target is not understood.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045065: A JMS module with fully qualified name "{1}" in an application named "{0}" does not have the proper hierarchy of targets. In particular, the subdeployment named "{2}" has a target "{3}" that is not a subtarget of any of the targets of "{0}". For example, the target "{3}" is not a subtarget of "{4}".
Cause: A target of a subdeployment of a JMS module was not contained within the targets of the whole JMS module.
Action: Ensure that the JMS module is targeted to a super-set of all the targets of the subdeployment, or retarget the subdeployment within the set of targets for the JMS module.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045066: The target named "{1}" of a JMS subdeployment named "{3}" inside a deployment named "{0}" must be a JMS server, WebLogic Server instance, or a cluster. Instead, it is of type {2}.
Cause: An attempt was made to target a JMS subdeployment to an invalid type of target.
Action: Do not attempt to target a JMS subdeployment to anything other than JMS servers, WebLogic Server instances or clusters. Any other type of target is not understood.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045067: The field "destination-name" was set to "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}". The destination-name field of a distributed destination may only be set in the interop module.
Cause: An attempt was made to set the destination-name field of a distributed destination member type. This is only allowed in the interop module in order to accommodate older clients.
Action: Change the name of the distributed destination member to the name of the physical queue or topic being referenced, and unset the destination-name field.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045068: The physical destination named "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}" does not exist.
Cause: An attempt was made by a distributed destination member to reference a destination that does not exist. The physical destination referenced to by a distributed destination must already exist.
Action: Create the physical destination before referring to it, or create the physical destination in the same edit session as the creation of the distributed destination member.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045069: The JMS module entity named "{2}" of type "{1}" does not exist in the JMSSystemResource "{0}".
Cause: An attempt was made to reference a JMS module entity that does not exist in the specified JMSSytemResource.
Action: Create the JMS module entity in the specified JMSSystemResource before referring to it.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045070: The configuration entity named "{2}" of type "{1}" does not exist in the domain "{0}".
Cause: An attempt was made to reference a configuration entity that does not exist in the specified domain.
Action: Create the configuration entity in the specified domain before referring to it.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045071: The JMS module entity named "{2}" of type "{1}" cannot be created in JMSSystemResource "{0}".
Cause: The JMS module entity creation using the the JMSModuleHelper API failed. See the accompanying exception for details.
Action: Resolve the problem identified by the accompanying exception, and retry the operation.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045072: The configuration entity named "{2}" of type "{1}" cannot be created in domain "{0}".
Cause: The configuration entity creation using the JMSModuleHelper API failed. See the accompanying exception for details.
Action: Resolve the problem identified by the accompanying exception, and retry the operation.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045073: The JMS module entity named "{2}" of type "{1}" cannot be deleted from JMSSystemResource "{0}".
Cause: The JMS module entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.
Action: Resolve the problem identified by the accompanying exception, and retry the operation.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045074: The configuration entity named "{2}" of type "{1}" cannot be deleted from the domain "{0}".
Cause: The configuration entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.
Action: Resolve the problem identified by the accompanying exception, and retry the operation.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045075: The JMS module managed entity named "{2}" of type "{1}" cannot be found in the JMSSytemResource "{0}" for modification.
Cause: The JMS module entity modification using the JMSModuleHelper API failed. See the accompanying exception for details.
Action: Resolve the problem identified by the accompanying exception, and retry the operation.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045076: An attempt was made to find and modify a JMS module entity named "{2}", of type "{1}", from the JMSSystemResource "{0}" using a null modifier.
Cause: The JMSEntityModifier argument for the findAndModifyEntity() helper API cannot be null.
Action: Use a valid weblogic.jms.extensions.JMSEntityModifer implementation as the modifier argument.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045077: The destination named "{0}" on the JMS server "{1}" would have caused the JMS server not to boot because the destination StoreEnabled value is true, but the JMS server does not have a store.
Cause: This configuration does not work in older releases because the destination StoreEnabled value is true, but the JMS server does not have a store.
Action: Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the StoreEnabled parameter on the destination.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045078: The destination named "{0}" on the JMS server "{1}" has a DeliveryParamsOverrides.DeliveryMode parameter set to persistent, but the JMS server does not have a store.
Cause: Messages cannot be made persistent on this JMS server because it does not have a store.
Action: Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the DeliveryParamsOverrides.DeliveryMode parameter.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045079: An attempt was made to send a persistent message to the destination "{0}" hosted on the JMS server "{1}". This JMS server does not have a store, so the quality of service requested is not available.
Cause: An attempt was made to send a persistent message to a destination hosted by a JMS server that does not have a store. Since the message cannot be persisted, this message cannot be sent at the required quality of service.
Action: There is a parameter on the JMS server called "AllowsPersistentDowngrade". If this parameter is set to true, then persistent messages sent to this JMS server will be downgraded to non-persistent.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045080: The flow steps value {1} is larger than the flow interval value {2} in the connection factory "{0}". The flow steps value must be less than or equal to the flow interval value.
Cause: This is an invalid configuration. The flow steps value must be less than the entire flow interval.
Action: Modify the configuration of the connection factory to have the flow steps value be less than or equal to the flow interval.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045081: The SessionsMaximum attribute of a JMSSessionPoolMBean has the bad value {0}. The value should be -1 or a positive integer.
Cause: This is an invalid configuration.
Action: Modify the configuration of the JMSSessionPoolMBean.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045082: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}".
Cause: The naming exception should contain more information about why this operation failed.
Action: See the attached naming exception message, which should have more information about why this operation failed.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045083: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the local JNDI context.
Cause: The naming exception should contain more information about why this operation failed.
Action: See the attached naming exception, which should have more information about why this operation failed.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045084: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the application JNDI context.
Cause: The naming exception should contain more information about why this operation failed.
Action: See the attached naming exception, which should have more information about why this operation failed.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045085: Could not find a license for JMS. Contact Oracle to obtain a license.
Cause: A license for JMS was not obtained.
Action: Contact Oracle to obtain a license.

Level: 1

Type: WARNING

Impact: JMSExceptions

BEA-045086: The jms-system-resource cannot have the name interop-jms.
Cause: An attempt was made to define a jms-system-resource with the name interop-jms.
Action: Do not attempt to define a jms-system-resource element in the config.xml file with the name interop-jms.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045087: The JMS deployment "{0}" has the descriptor file name "{1}", which is reserved for internal use only.
Cause: An attempt was made to define a JMS deployment with the reserved file name "interop-jms.xml". This name is reserved by the system for use as the interop module.
Action: Do not attempt to define a JMS deployment with the reserved name "interop-jms.xml" as its file name.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045088: The JMS module descriptor file "{1}" used by the JMS system resource "{0}" is illegal. Either the descriptor file name does not end with -jms.xml or the descriptor is being used by another JMS system resource in the configuration.
Cause: An attempt was made to define a JMS system resource with the illegal descriptor file name.
Action: Do not attempt to define a jms-system-resource element in the config.xml file with the illegal descriptor file name.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045089: SAF error destination {2} of {1} is targeted to a different subdeployment from {0}.
Cause: The configuration was invalid.
Action: Correct the deployment descriptor.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045090: The error handling {1} configured for {0} does not exist in the module.
Cause: The configuration was invalid.
Action: Correct the deployment descriptor.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045091: One of the target ("{1}") of the subdeployment "{2}" for the imported destinations "{0}" is not a legal target type.
Cause: The configuration was invalid.
Action: Correct the configuration.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045092: Imported destinations "{0}": its subdeployment is targeted to a target ("{1}"), which is a receiving-only SAF agent.
Cause: The configuration was invalid.
Action: Correct the configuration.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045093: A UDQ named "{0}" was found in the JMS interop module. UDQs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDQ in that module.
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045094: A UDT named "{0}" was found in the JMS interop module. UDTs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDT in that module.
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045095: An SAF imported destinanation named "{0}" was found in the JMS interop module. SAF imported destinations were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF imported destinations in that module.
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045096: An SAF remote context named "{0}" was found in the JMS interop module. SAF remote contexts were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF remote context in that module.
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045097: An SAF error handlings named "{0}" was found in the JMS interop module. SAF error handlings were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF error handlings in that module.
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045098: There is a JMS system resource and an application deployment both named "{0}". The names of all JMS system resources and all application deployments must be different.
Cause: Both a JMS system resource and an application deployment have the same name. This would cause similarly named resources in a JMS module descriptor file to have conflicting runtime names, and therefore is not allowed.
Action: Change the name of either the JMS system resource or application deployment so that there is no name conflict.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045099: An attempt was made to create a temporary destination. However, no JMS server in the cluster is able to host temporary destinations. Ensure that at least one of the JMS servers in the cluster has the HostingTemporaryDestinations parameter set to true (which is the default).
Cause: None of the JMS servers in the cluster are available for hosting temporary destinations.
Action: Modify the HostingTemporaryDestinations parameter on at least one JMS server in the cluster. Note that in releases prior to 9.0, the default for the ability to host temporary destinations was false, while in 9.0 and beyond, the default for the ability to host temporary destinations is true.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045100: The createQueue or createTopic call was made with a null or zero length destination name.
Cause: The createQueue or createTopic call must be made with the name of a destination to find.
Action: Do not pass a null or zero length string to createQueue or createTopic.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045101: The destination name passed to the createTopic or createQueue "{0}" is invalid. If the destination name does not contain a "/" character, then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character, then the string before the "/" must be the name of a JMS server or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WebLogic Server instance will be returned.
Cause: Either a distributed destination of the given name does not exist in the cluster to which the client is attached or the destination name passed to createTopic or createQueue does not contain a "/" character, or there is nothing before the "/" character.
Action: Ensure that the distributed destination is available on the same cluster where the client is located, or format the destination name string properly.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045102: A destination named "{0}" was not found on WebLogic Server instance "{1}".
Cause: An attempt was made to find a destination of a given name on a particular WebLogic Server instance. No destination of that name could be found on that WebLogic Server instance.
Action: It is possible that the createTopic or createQueue call was routed to a WebLogic Server instance that does not contain a destination with the given name. The set of WebLogic Server instances where this request can be routed can be controlled by using a connection factory that is only targeted to WebLogic Werver instances that have destinations of the desired name.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045103: While trying to find a topic or a queue, the specific JMS server requested could not be found. The linked exception may contain more information about the reason for failure.
Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.
Action: The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045104: While trying to find a topic or a queue, the specific JMS server requested could not be found.
Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.
Action: Ensure that the JMS server requested exists in the configuration of the cluster to which the client is attached.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045105: While trying to find a topic or a queue, communication failed with the specific JMS server requested. The linked exception may contain more information about the reason for failure.
Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not communicate with the JMS server of that name.
Action: The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045106: A destination named "{0}" was found. However, the requested destination was of type "{1}", and the destination found was not of that type.
Cause: Either the user called createTopic and the destination found was a queue or the user called createQueue and the destination found was a topic.
Action: Ensure that the destination name requested is of the correct type.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045107: A communication failure occurred while attempting to remove a durable subscription. The linked exception may contain more details about the cause of the failure.
Cause: While attempting to remove a durable subscription a communication failure occurred.
Action: Check on the status of WebLogic Server instance where the destination which the durable subscription refers to resides. Check the linked exception for more information about the cause of this failure.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045108: The JMS system does not understand request ID {0}.
Cause: An invalid request ID was presented to the front end manager.
Action: If this condition persists, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045109: A foreign server named "{0}" was found which does not have a connection URL specified. However, it contains a "{2}" named "{1}" that has the same local and remote JNDI name value "{3}". This is an invalid configuration and is not allowed.
Cause: The user has configured a foreign server without a connection URL and has either a foreign connection factory or a foreign destination with both the local and remote JNDI name matching.
Action: Ensure that either the foreign server has a connection URL to the foreign server or that the local and remote JNDI names are different.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045110: The JMS resource named "{0}" has incorrect targeting information. This resource has the default-targeting-enabled attribute set to true and has a valid sub-deployment-name value specified.
Cause: A JMS resource cannot have both default targeting enabled and a subdeployment name specified.
Action: Ensure that either the default targeting is enabled or that the valid subdeployment name is specified.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045111: The JMS resource named "{0}" has incorrect targeting information. A JMS physical destination cannot have the default-targeting-enabled attribute set.
Cause: A JMS physical destination cannot have the default-targeting-enabled attribute set.
Action: Ensure that the default-targeting-enabled attribute is not set for the physical destinations.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045112: The flow minimum value {1} is larger than or equal to the flow maximum value {2} in connection factory "{0}". The flow minimum value must be less than the flow maximum value.
Cause: This is an invalid configuration. The flow minimum value must be less than the flow maximum value.
Action: Modify the configuration of the connection factory to have the flow minimum value be less than the flow maximum value.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-045113: JMS distributed destination forward request denied for the destination named "{1}". Reason "{0}".
Cause: JMS distributed destinations may not have been fully initialized.
Action: If forwarding does not begin after a few minutes, contact My Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: JMSExceptions

BEA-045114: Failed to unsubscribe the subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription without a topic object.
Cause: An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a client ID policy of UNRESTRICTED.
Action: Use the weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a client ID policy of UNRESTRICTED. If using a pre-AS11gR1PS3 Java client, upgrade to a AS11gR1PS3 client. If using a non-Java client, clean up the durable subscription from the Administration Console or use WebLogic Scripting Tool (WLST) commands or scripts.

Level: 1

Type: ERROR

Impact: JMSExceptions

BEA-050000: {0} is an obsolete property. Use {1} to create the context instead.
Cause: Property {0} is obsolete. However, this property name can still be used to retrieve the property value.
Action: Use property {1} instead of {0} in the future.

Level: 1

Type: WARNING

Impact: JNDI

BEA-050001: WLContext.close() was called in a different thread than the one in which it was created.
Cause: The threads used to create and close the context are different. As a result, the context entries associated with the creating thread might not be cleaned up.
Action: Close the context in the creating thread.

Level: 1

Type: WARNING

Impact: JNDI

BEA-050002: Cannot replicate the object that is bound in the JNDI under the name {0}.
Cause: A non-serializable object cannot be serialized.
Action: If the object was not intended to be replicated, set the replicate bindings to false. If the object should be replicated to all nodes in the cluster, ensure that the object is serializable or externalizable.

Level: 1

Type: ERROR

Impact: JNDI

BEA-050003: Cannot create initial context. Reason: {0}
Cause: Initial context cannot be created.
Action: Check the exception in the message body.

Level: 1

Type: ERROR

Impact: JNDI

BEA-050004: Unable to bind. Reason: {0}
Cause: This was unable to bind.
Action: Check the exception in the message body.

Level: 1

Type: ERROR

Impact: JNDI

BEA-050005: Unable to unbind. Reason: {0}
Cause: This was unable to unbind.
Action: Check the exception in the message body.

Level: 1

Type: ERROR

Impact: JNDI

BEA-050006: An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.
Cause: An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.
Action: Ensure that the possibility of premature retirement of the application version is either tolerated or handled properly. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_EXTERNAL_LOOKUP to "true" when performing lookup of the versioned object.

Level: 1

Type: WARNING

Impact: JNDI

BEA-050007: An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.
Cause: An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.
Action: Ensure that usages of the global resource by multiple application versions do not conflict. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_GLOBAL_RESOURCE_LOOKUP to "true" when performing lookup of the global resource.

Level: 1

Type: WARNING

Impact: JNDI

BEA-055001: Invalid time-to-deliver, must be >= -1
Cause: The time-to-deliver parameter passed to setTimeToDeliver was invalid.
Action: Change the code to pass a time-to-deliver parameter that is >= -1.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055002: Cannot convert {0} to a boolean.
Cause: An object that was not null, not a boolean, and not a string could not be converted to a boolean value.
Action: Ensure that the object passed in is either a boolean or a string.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055003: Cannot convert null to a byte.
Cause: The null object cannot be converted to a byte value
Action: Avoid passing null where a byte value is expected

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055004: Cannot convert {0} to a byte.
Cause: An object that was not null, not a byte, and not a string could not be converted to a byte value
Action: Ensure that the object passed in is either a byte or a string.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055005: Cannot convert null to a short.
Cause: The null object cannot be converted to a short value.
Action: Avoid passing null where a short value is expected.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055006: Cannot convert {0} to a short.
Cause: An object that was not null, not a short, and not a string could not be converted to a short value.
Action: Ensure that the object passed in is either a short or a string.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055007: Could not serialize object.
Cause: An object could not be serialized. The linked exception may contain more details.
Action: See the linked exception which may contain more details.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055008: Invalid RedeliveryLimit, must be >= -1.
Cause: The RedeliveryLimit parameter passed to setRedeliveryLimit was invalid.
Action: Change the code to pass a RedeliveryLimit parameter that is >= -1.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055009: Invalid SendTimeout, must be >= 0
Cause: The SendTimeout parameter passed to setSendTimeout was invalid.
Action: Change the code to pass a SendTimeout parameter that is >= 0.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055014: Error sending message
Cause: The linked exception will contain more details concerning the failure to send the message.
Action: The action will depend on the error that occurred. More information about the specific error that occurred can be found in the linked exception.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055015: Invalid DeliveryMode
Cause: The DeliveryMode parameter passed to setDeliveryMode was invalid.
Action: Change the code to pass a valid DeliveryMode value.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055016: Invalid Priority
Cause: The Priority parameter passed to setPriority was invalid.
Action: Change the code to pass a valid Priority value.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055017: Durable connection consumers are not supported.
Cause: The system does not support durable connection consumers.
Action: Do not attempt to create a durable connection consumer.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055018: QueueSessions do not support multicast.
Cause: The MULTICAST_NO_ACKNOWLEDGE flag was set in createQueueSession.
Action: Do not use MULTICAST_NO_ACKNOWLEDGE when creating a QueueSession.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055019: Duplicate session
Cause: The cause is unknown.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055021: ClientID is null
Cause: ClientID is null in a call to setClientID.
Action: Do not use null in a call to setClientID.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055022: Zero length clientID
Cause: The clientID passed to setClientID was zero length.
Action: The clientID must not be zero length.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055023: Invalid value for messagesMaximum, {0}
Cause: The value given for messagesMaximum in createConnectionConsumer is invalid.
Action: Change the code to pass a valid messagesMaximum value.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055024: No such method {0}
Cause: An internal error occurred.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055025: Invalid messagesMaximum value
Cause: The messagesMaximum parameter passed to setMessagesMaximum was invalid.
Action: Change the code to pass a valid messagesMaximum value.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055026: Invalid overrunPolicy value, {0}
Cause: The overrun policy passed to setOverrunPolicy is invalid.
Action: Change the code to pass a valid overrun policy value.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055027: Invalid redelivery delay, must be >= -1
Cause: The redeliveryDelay parameter passed to setRedeliveryDelay was invalid.
Action: Change the code to pass a valid redeliveryDelay value.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055028: Name must not be null.
Cause: The name parameter passed to createDurableSubscriber was null.
Action: Change the code to pass a valid name to createDurableSubscriber.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055029: Name must not be an empty string.
Cause: The name parameter passed to createDurableSubscriber had a length of zero.
Action: Change the code to pass a valid name to createDurableSubscriber.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055030: This topic does not support durable subscriptions.
Cause: Durable subscribers are not supported on Distributed Topics and no subscribers at all are supported on SAF topics
Action: Avoid attempting to create a durable subscriber on a distributed topic or do not create a subscriber on an SAF topic.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055031: This connection does not have a clientID.
Cause: Unsubscribe was called on a connection without a clientID.
Action: Avoid attempting to unsubscribe a connection with no clientID

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055032: An attempt was made to create a named consumer ({0}) on a connection with no clientID.
Cause: An attempt was made to create a named consumer on a connection with no clientID.
Action: Avoid attempting to create a named consumer on a connection with no clientID.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055033: Queues do not support multicast.
Cause: Queues do not support multicast.
Action: Avoid attempting to create a multicast consumer on a queue

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055034: Topic {0} does not support multicast.
Cause: An attempt was made to create a multicast consumer on a topic that does not support multicast.
Action: Avoid attempting to create a multicast consumer on the given topic.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055035: Cannot open multicast socket, {0}.
Cause: An attempt was made to open a multicast socket and failed. The reason for the failure may be in the exception
Action: For more details, check the printed exception on the failure to open the multicast socket.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055036: Cannot join multicast group ({0}) {1}
Cause: An attempt was made to join a multicast group and failed. The reason for failure may be in the exception.
Action: For more details, check the printed exception on the failure to join the multicast group.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055037: Subscription {0} is in use.
Cause: Two subscriptions with the same name are not allowed.
Action: Avoid attempting to use a subscription name more than once. If necessary, unsubscribe the previous subscription

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055038: An unexpected response ({0}) was received from the server.
Cause: An internal protocol error has occurred.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055039: A system error has occurred. The error is {0}.
Cause: The cause of this error may be contained in the printed exception.
Action: The action will depend on the error that has occurred. Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055040: Subscription {0} is in use.
Cause: An attempt was made to remove the named subscription while the subscription was in use.
Action: Avoid attempting to remove a subscription that is currently in use.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055041: Cannot leave multicast group ({0}) {1}
Cause: An attempt was made to leave a multicast group and failed. The reason for failure may be in the exception.
Action: For more details, check the printed exception on the failure to leave the multicast group.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055042: No such method {0} for class {1}
Cause: An internal error has occurred.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055043: No such method {0} for class {1}
Cause: An internal error has occurred.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055044: Multicast sessions do not support synchronous receives.
Cause: An attempt was made to do a synchronous receive on a multicast consumer.
Action: Avoid attempting to make a synchronous receive with a multicast consumer.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055045: An invalid value ({0}) for timeout was specified.
Cause: The timeout given to a receive call is invalid. Timeout values must be positive.
Action: Change the code so that it does not pass a negative number into a receive call.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055046: A listener already exists.
Cause: A call to receive cannot be made if the consumer already has a listener.
Action: Avoid attempting to call receive if a listener already exists for the consumer.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055047: No such method {0}
Cause: An internal error occurred.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055048: Multicast selectors are not supported in the thin client.
Cause: Multicast selectors are not supported in the thin client.
Action: If selectors are required, avoid using the JMS thin client. If selectors are not required, avoid using them while using the thin client.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055049: Internal error {0}.
Cause: An internal error occurred. More detail about the error can be found in the exception.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055050: Internal error {0}
Cause: An internal error occurred. More detail about the error can be found in the exception.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055051: Internal error {0}
Cause: An internal error occurred. More detail about the error can be found in the exception.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055052: Invalid selector {0}
Cause: An error occurred while parsing a selector. The printed exception should have more detail.
Action: The course of action will depend on the nature of the error. Use a well-formed selector.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055053: Error creating connection to the server: {0}.
Cause: The printed exception may have information regarding the cause of this failure.
Action: The course of action will depend on the error printed out in the exception.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055054: Error finding dispatcher: {0}.
Cause: An internal error has occurred.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055055: No transaction
Cause: A call to commit was made on a session but there is no current transaction.
Action: Avoid calling commit on a session that is not currently in a transaction.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055056: Error committing session
Cause: An error occurred while committing an XA session.
Action: Examine the transaction logs to see what occurred to the transaction

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055057: No transaction
Cause: A call to rollback was made on a session but there is no current transaction.
Action: Do not call rollback on a session that is not currently in a transaction.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055058: Error committing session
Cause: An error occurred while committing an XA session.
Action: Examine the transaction logs to see what occurred to the transaction.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055059: getXAResource can be called only from the server.
Cause: A call to getXAResource was made from a client JVM; getXAResource is not supported in the client.
Action: Avoid calling getXAResource from a client JVM.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055060: No transaction.
Cause: A call to commit was made on a session but there is no current transaction.
Action: Avoid calling commit on a session that is not currently in a transaction.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055061: No transaction.
Cause: A call to rollback was made on a session but there is no current transaction.
Action: Avoid calling rollback on a session that is not currently in a transaction.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055062: This session is transacted.
Cause: A call to recover was made on a transacted session.
Action: Avoid calling recover on a transacted session. Use rollback instead.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055063: This session has consumer listeners.
Cause: The session on which setMessageListener was called already has consumer listeners.
Action: Avoid calling setMessageListener on a session that already has consumer listeners.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055064: Unsupported topic operation on a queue session
Cause: A call to createTopic was made on a QueueSession.
Action: Avoid calling createTopic on a QueueSession.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055065: Unsupported topic operation on a queue session
Cause: A call to createDurableSubscriber was made on a QueueSession.
Action: Avoid calling createDurableSubscriber on a QueueSession.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055066: Unsupported topic operation on a queue session
Cause: A call to createTemporaryTopic was made on a QueueSession.
Action: Avoid calling createTemporaryTopic on a QueueSession.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055067: Unsupported topic operation on a queue session
Cause: A call to unsubscribe was made on a QueueSession.
Action: Avoid calling unsubscribe on a QueueSession.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055068: There is no subscription from which to unsubscribe.
Cause: The user called unsubscribe on a session that does not have a subscription.
Action: Avoid calling unsubscribe on a session that does not have a subscription.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055069: Unsupported queue operation on a topic session
Cause: A call to createQueue was made on a TopicSession.
Action: Avoid calling createQueue on a TopicSession.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055070: Unsupported queue operation on a topic session
Cause: A call to createBrowser was made on a TopicSession.
Action: Avoid calling createBrowser on a TopicSession.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055071: Unsupported queue operation on a topic session
Cause: A call to createTemporaryQueue was made on a TopicSession.
Action: Avoid calling createTemporaryQueue on a TopicSession.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055072: Wrong connection for this temporary destination
Cause: An attempt was made to call createConsumer on an invalid connection from a temporary destination.
Action: Create consumers using the same connection that was used to create the temporary destination.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055073: Dropping new message
Cause: A new message is being dropped because too many messages have arrived.
Action: Either consume messages faster or produce messages slower for this session.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055074: Dropping old message
Cause: An old message is being dropped because too many messages have arrived.
Action: Either consume messages faster or produce messages slower for this session.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055075: It is possible that the client is malfunctioning: a RuntimeException was thrown from its onMessage method.
Cause: The onMessage method of the client threw a RuntimeException.
Action: Modify the code such that the RuntimeException does not occur from within the body of the user code. This warning is required by section 4.5.2 of the JMS Specification.

Level: 1

Type: WARNING

Impact: JMSClientExceptions

BEA-055076: The session is closed.
Cause: An operation was attempted on a closed session.
Action: Avoid attempting this operation on a closed session.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055077: Cannot override producer destination.
Cause: A call to send with a non-null destination was made on a producer that is already bound to a destination.
Action: Avoid calling send with a non-null destination on a producer that is already bound to a destination.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055078: Cannot override producer destination
Cause: A call to send with a non-null destination was made on a producer that is already bound to a destination.
Action: Avoid calling send with a non-null destination on a producer that is already bound to a destination.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055079: Must provide destination to send to
Cause: There is no destination to send to.
Action: Use the version of send that has a destination or bind a destination to the producer before calling send.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055080: Must provide destination to send to
Cause: There is no destination to send to.
Action: Use the version of send that has a destination or bind a destination to the producer before calling send.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055081: Unsupported topic operation on a queue session
Cause: A call to createDurableConnectionConsumer was made on a QueueConnection.
Action: Avoid calling createDurableConnectionConsumer on a QueueConnection.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055082: The connection is closed.
Cause: The connection has been closed. Only a few operations are valid on a closed connection.
Action: Avoid calling any illegal operations on a closed queue connection.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055083: Cannot set clientid to {0}. The client ID is already set to {1}
Cause: The clientID {1} is already set on this connection. The clientID cannot be set to {0}
Action: Avoid attempting to set a clientID on a connection that already has one.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055084: A connection consumer works only on the server.
Cause: A connection consumer can be created only in the same JVM in which the server is running.
Action: Avoid attempting to create a connection consumer on a JVM that is not running the server.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055085: Destination is null.
Cause: In a call to createConnectionConsumer or createConsumer, the destination parameter was null.
Action: Avoid using null for the destination in a call to createConnectionConsumer or createConsumer.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055086: Foreign destination
Cause: Foreign destinations are not supported when creating connectionConsumers.
Action: Avoid using a foreign destination in a call to createConnectionConsumer.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055087: The session already has a message listener.
Cause: A consumer may not have an individual message listener if its parent session already has one defined.
Action: Avoid attempting to set a message listener for a consumer if the session already has a listener defined.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055088: The consumer is closed.
Cause: The consumer has been closed. Only a few operations are valid on a closed consumer.
Action: Avoid calling any illegal operations on a closed consumer.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055089: Destination is null.
Cause: In a call to send, the destination parameter was null.
Action: Avoid using null for the destination in a call to send.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055090: Foreign destination
Cause: Foreign destinations are not supported when sending.
Action: Avoid using a foreign destination in a call to send.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055091: Destination {0} must be a queue.
Cause: An attempt was made to publish to a queue.
Action: Avoid using publish to a queue. Use send instead.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055092: Destination {0} must be a topic.
Cause: An attempt was made to send to a topic.
Action: Avoid using send to a topic. Use publish instead.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055093: Error converting foreign message
Cause: An I/O exception occurred while converting a foreign message. The cause of the failure may be contained in the linked exception.
Action: Examine the linked I/O exception.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055094: The producer is closed.
Cause: The producer has been closed. Only a few operations are valid on a closed producer.
Action: Avoid calling any illegal operations on a closed producer.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055095: The browser is closed.
Cause: The browser has been closed. Only a few operations are valid on a closed browser.
Action: Avoid calling any illegal operations on a closed browser.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055096: Cannot convert null to a char.
Cause: The null object cannot be converted to a char value.
Action: Avoid passing null where a char value is expected.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055097: Cannot convert {0} to a char.
Cause: An object that was not null, not a character, and not a string could not be converted to a char value.
Action: Ensure that the object passed in is either a character or a string.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055098: Cannot convert null to an int.
Cause: The null object cannot be converted to an int value.
Action: Avoid passing null where an int value is expected.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055099: Cannot convert {0} to an int.
Cause: An object that was not null, not an integer, and not a string could not be converted to an int value.
Action: Ensure that the object passed in is either an intenger or a string.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055100: Cannot convert null to a long.
Cause: The null object cannot be converted to a long value.
Action: Avoid passing null where a long value is expected.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055101: Cannot convert {0} to a long.
Cause: An object that was not null, not a long, and not a string could not be converted to a long value.
Action: Ensure that the object passed in is either a long or a string.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055102: Cannot convert null to a float
Cause: The null object cannot be converted to a float value.
Action: Avoid passing null where a float value is expected.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055103: Cannot convert {0} to a float
Cause: An object that was not null, not a float, and not a string could not be converted to a float value.
Action: Ensure that the object passed in is either a float or a string.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055104: Cannot convert null to a double
Cause: The null object cannot be converted to a double value.
Action: Avoid passing null where a double value is expected.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055105: Cannot convert {0} to a double.
Cause: An object that was not null, not a double, and not a string could not be converted to a short value.
Action: Ensure that the object passed in is either a double or a string.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055106: A byte[] cannot be converted to a string.
Cause: A byte[] cannot be converted to a string.
Action: Avoid passing a byte array that needs to be converted to a string.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055107: Cannot convert {0} to a byte[].
Cause: The given object could not be converted to a byte[].
Action: Ensure that the object passed in can be converted to a byte array.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055108: Read past end of message
Cause: An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information
Action: Avoid attempting to read past the end of a StreamMessage. See the linked EOFException for more information.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055109: Error reading from stream
Cause: There was an error reading the stream from a StreamMessage. A linked IOException may contain more information.
Action: See the linked IOException for more information.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055110: Error writing to stream
Cause: There was an error writing to the stream of a StreamMessage. A linked IOException may contain more information.
Action: See the linked IOException for more information.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055111: Cannot convert from {0} to {1}
Cause: A StreamMessage was unable to convert one type to another.
Action: Ensure that the two types are compatible. Avoid attempting to convert incompatible types

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055112: Error reading from stream
Cause: There was an error reading the stream from a StreamMessage. A linked ArrayIndexOutOfBoundsException may contain more information.
Action: See the linked ArrayIndexOutOfBoundsException for more information.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055113: Error reading from stream
Cause: There was an error reading the stream from a StreamMessage. A linked ArrayStoreException may contain more information.
Action: See the linked ArrayStoreException for more information.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055114: There was an eeror when deserializing an object. Some typical reasons for failure are: missing application class, application class version mismatch, or Java objects not being supported.
Cause: There was an error deserializing an object. A linked IOException may have more details.
Action: See the linked IOException for more details.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055115: Error deserializing an object
Cause: There was an error deserializing an object. A linked ClassNotFoundException may have more details.
Action: See the linked ClassNotFoundException for more details.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055116: Internal error unknown message type {0}
Cause: This error should never happen.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055117: Invalid delivery mode {0}
Cause: The delivery mode passed into setJMSDeliveryMode is invalid
Action: Change the code so that it calls setJMSDeliveryMode with a valid delivery mode.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055118: Invalid redelivery limit, must be >= -1
Cause: The redelivery limit parameter passed to setJMSRedeliveryLimit was invalid.
Action: Change the code to pass a redelivery limit parameter that is >= -1.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055119: Invalid priority, {0}
Cause: The priority parameter passed to setJMSPriority was invalid.
Action: Change the code to pass a valid priority value.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055121: Invalid property name, "{0}"
Cause: The property name passed to setObjectProperty was invalid.
Action: Change the code to pass a valid property name.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055122: Property write attempted in READ mode.
Cause: An attempt was made to write a property but the message is read-only.
Action: Avoid attempting to write a property to a message in read-only mode.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055123: Invalid property value, {0}
Cause: The property value passed to setObjectProperty was invalid.
Action: Change the code to pass a valid property value.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055125: Unknown underlying stream type, cannot convert 6.0 class.
Cause: While attempting to read a message created by an older version of WebLogic Server, a failure occurred.
Action: It may not be possible to read the older version of the message. Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055126: Stream is corrupted. Possible older version
Cause: While attempting to read a message created by an older version of WebLogic Server, a failure occurred.
Action: It may not be possible to read the older version of the message. Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055127: Unsupported version
Cause: The version of the message being read is unsupported.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055128: Read attempted in WRITE mode.
Cause: An attempt was made to read a message in WRITE mode.
Action: Avoid attempting to read a message in WRITE mode.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055129: Write attempted in READ mode.
Cause: An attempt was made to write a message that is read-only.
Action: Avoid attempting to write to a message in read-only mode.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055130: Invalid data type: {0}
Cause: The class name given is not a valid data type. The type for setObject must be number, string, boolean, byte, character, or null.
Action: Pass one of the acceptable data types to setObject in a MapMessage.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055131: Illegal name: {0}
Cause: The given name is not legal. It is either null or of zero length.
Action: Pass a non-null or non-zero-length string as the name of a MapMessage element.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055132: Could not copy message.
Cause: The system could not copy a MapMessage. The linked IOException should contain more information about the nature of the error.
Action: Examine the linked exception to discover what caused the failure.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055133: Could not deserialize message.
Cause: The system could not deserialize a MapMessage. The linked IOException should contain more information about the nature of the error.
Action: Examine the linked exception to discover what caused the failure.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055134: Unsupported class version {0}. Expected a value between {1} and {2} inclusive.
Cause: While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {1} then it is possible an attempt was made to access a newer JMS version than the current version. Otherwise a possible attempt has been made to interoperate with an unsupported older version of JMS.
Action: Ensure that the versions of Oracle products that are interoperating are supported. If the versions should be supported, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055135: Could not write object, expected simple type, but got class {0}
Cause: The given object class could not be written because it is not a simple type.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055136: Could not read object, unrecognized class code {0}.
Cause: An unknown class code was received. The object cannot be read.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055137: JMSProducerSendResponse versions {0}, {1} not compatible with peer: {2}
Cause: An interoperability error occurred.
Action: Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055138: Peer not compatible with DistributedDestinationImpl version {0}. Peer Major Version is less than 6.
Cause: An interoperability error occurred.
Action: Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055139: Invalid Temporary Destination
Cause: An attempt was made to delete an invalid temporary destination.
Action: Avoid attempting to delete invalid temporary destinations.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055140: Internal error or marshalling error, unknown destination type {0}
Cause: An unknown type was encountered when marshalling a destination.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055141: Destination is null.
Cause: While checking a destination type, the incoming destination was null.
Action: Avoid attempting to discover the type of a null destination.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055142: Foreign destination, {0}
Cause: While checking a destination type, the incoming destination was foreign.
Action: Avoid attempting to discover the type of a foreign destination.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055143: Destination must be a queue, {0}
Cause: The given destination must be a queue, but it is not a queue.
Action: Use the proper type of destination when checking types.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055144: Destination must be a topic, {0}
Cause: The given destination must be a topic, but it is not a topic.
Action: Use the proper type of destination when checking types.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055145: Unknown stream version: {0}
Cause: The given version number is invalid for a buffered stream.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055146: The stream cannot handle raw objects.
Cause: The stream is probably from an unintended source, such as a Web browser.
Action: Only connect to the Oracle product TCP port with a proper client. If the client is a proper client, contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055147: Not implemented
Cause: readLine was called, but it has not been implemented.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055148: The stream cannot handle raw objects.
Cause: A raw object could not be written to the buffered stream.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055149: Attempt to read past end of message ({0})
Cause: The end of the BytesMessage was reached, but an attempt was made to read past it. {0} indicates where the attempt was made and will only be significant to My Oracle Support.
Action: Avoid attempting to read past the end of the BytesMessage.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055150: Error reading from stream ({0}).
Cause: The linked IOException will have more detail on the cause of the failure.
Action: Examine the linked exception to discover what caused the problem.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055151: Length ({0}) is negative.
Cause: In a call to readBytes, the length parameter is negative.
Action: Fix the code to ensure a negative length is not passed to readBytes.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055152: length ({0}) is greater than the length of the array ({1}).
Cause: In a call to readBytes, the length parameter is larger than the size of the bytes array to fill.
Action: Fix the code to ensure the length passed to readBytes is less than or equal to the length of the output array.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055153: Error writing to stream ({0}).
Cause: The linked IOException will have more detail on the cause of the failure.
Action: Examine the linked exception to discover what caused the problem.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055154: Invalid object type: {0}
Cause: The object passed to writeObject is not valid.
Action: Only send valid object types to writeObject. Example valid types include boolean, byte, short, and integer.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055155: Cannot forward message
Cause: Modified received messages are not supported when using forward methods.
Action: Avoid modifying a received message in a call to forward.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055156: Peer neither compatible with {0} or {1} or {2} or {3}. PeerInfo is {4}.
Cause: A version mismatch occurred in a message.
Action: This is an internal error that should not occur. Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055157: Invalid compression threshold
Cause: The compression threshold was invalid.
Action: Change the code to pass a valid compression threshold.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055158: WebLogic Server JMS failed to decompress the message body.
Cause: The linked IOException will have more detail on the cause of the failure.
Action: Examine the linked exception to discover what caused the problem.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055159: Message consumer received a compressed message with unknown compression tag - {0}
Cause: Contact My Oracle Support.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055160: WebLogic Server JMS failed to deserialize the text message.
Cause: Contact My Oracle Support.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055161: Cannot forward foreign messages.
Cause: Foreign messages are not supported when using forward methods.
Action: Avoid forwarding a foreign message.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055162: WebLogic Server JMS failed to serialize the text message for interoperability.
Cause: Contact My Oracle Support.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055163: WebLogic Server JMS failed to serialize the XML message for interoperability.
Cause: Contact My Oracle Support.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055164: Cannot forward a message to a WebLogic Server instance prior than version 9.0.
Cause: Cannot forward a message to a WebLogic Server instance prior than 9.0.
Action: Avoid forwarding a message to a WebLogic Server instance prior than 9.0.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055165: The following exception has occurred: {0}.
Cause: An error condition has occurred.
Action: Look for the associated exception in the log or the program to see what the results are. In general, this stack trace will help in debugging an existing problem.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055167: Single session cannot support more than one synchronous message-prefetching consumer.
Cause: There is another opened synchronous message-prefetching consumer.
Action: Close the other synchronous message-prefetching consumer.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055168: Synchronous message-prefetching consumer cannot support user transaction.
Cause: Synchronous message-prefetching consumer cannot support user transaction.
Action: Disable the user transaction or the synchronous message-prefetching consumer in the jms connection factory setting.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055169: Network connection to server was lost.
Cause: The network connection to the server was lost.
Action: This is usually a recoverable error when the JMS client is using the auto-reconnect/failover feature. This error is exposed to the user (JMS client code developer) when the auto-reconnect feature cannot make a decision without user input on a particular course of action after failover. The user can consciously code to continue to use relevant refreshed JMS objects with a potential lowered quality of service such as duplicate/lost/out-of-order messages, or decide to close the relevant JMS object.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055170: Cannot convert string property from its internal format.
Cause: The string property cannot be converted from its internal format.
Action: Contact My Oracle Support.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055171: Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe() API.
Cause: An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a Client ID policy of UNRESTRICTED.
Action: Use weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a Client ID policy of UNRESTRICTED.

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055172: Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a Client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription with a null topic or distributed topic instance.
Cause: An attempt was made to unsubscribe a durable subscription with a null Topic object or a distributed topic object from a connection that has a Client ID policy of UNRESTRICTED.
Action: Provide a standalone topic object or a member of a distributed topic when calling weblogic.jms.extensions.WLSession.unsubscribe(String topic, String name).

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055173: Read past end of message ({0})
Cause: An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information
Action: Do not attempt to read past the end of a StreamMessage. See the linked EOFException for more information

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055174: Error reading from stream ({0})
Cause: There was an error reading the stream from a StreamMessage. A linked IOException may contain more information
Action: See the linked IOException for more information

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-055175: Error writing to stream ({0})
Cause: There was an error writing to the stream of a StreamMessage. A linked IOException may contain more information
Action: See the linked IOException for more information

Level: 1

Type: ERROR

Impact: JMSClientExceptions

BEA-080001: Error in dispatcher {0}
Cause: A runtime error occurred while dispatching a request to the server.
Action: If the error is not application related, contact My Oracle Support with the stack trace for further analysis.

Level: 1

Type: ERROR

Impact: RMI

BEA-080002: Unexport failed for: {0}.
Cause: The remote object was unexported twice.
Action: No action is required.

Level: 1

Type: ERROR

Impact: RMI

BEA-080003: A RuntimeException was generated by the RMI server: {0} {1}.
Cause: A runtime exception occurred while dispatching the request to the server.
Action: No action is required.

Level: 1

Type: WARNING

Impact: RMI

BEA-080004: An error was generated by the RMI server: {0} {1}.
Cause: A runtime error occurred while dispatching a response to the client.
Action: The associated stack trace contains information about the error. Check the server logs for more details.

Level: 1

Type: WARNING

Impact: RMI

BEA-080005: An exception was generated by the RMI server: {0} {1}.
Cause: The error response could not be sent to the client. The underlying socket caused an IOException while dispatching the error response.
Action: The associated stack trace contains information about the error.

Level: 1

Type: WARNING

Impact: RMI

BEA-080006: Failed to associate the transaction context with the response while marshalling an exception to the client: {0}.
Cause: An IOException occurred while associating a transaction context with the response. This happened when marshalling an exception in the response. Most likely, the socket has been torn down or an error occurred in the stream.
Action: Check the server logs for more details.

Level: 1

Type: WARNING

Impact: RMI

BEA-080007: RMI runtime is disabled, since it could not initialize the DGC {0}.
Cause: RMI runtime could not be initialized.
Action: Restart the server. If the problem continues, contact My Oracle Support with the stack trace information.

Level: 1

Type: ERROR

Impact: RMI

BEA-080008: Failed to send error reply to client {0}.
Cause: An exception occurred while dispatching an error response to the client.
Action: No action is required.

Level: 1

Type: ERROR

Impact: RMI

BEA-080009: An error was generated by the RMI server: {0} invoking: {1}.
Cause: A java.lang.Error occurred while invoking method {1} on {0}. A ServerError occurred due to the server side RMI method call.
Action: Check the nested exception in the ServerError for more details.

Level: 1

Type: WARNING

Impact: RMI

BEA-080011: Empty workingSet found while assembling the heartbeat for {0}.
Cause: An empty set of references for {0} was found while assembling the deterministic garbage collector (DGC) heartbeats for all remote virtual machines that are referenced from this virtual machine.
Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080012: No workingSet found for {0} residing in {1}.
Cause: An empty working set for {0} was found while periodically scanning the list of finalized references and decrementing the count for any reference found. This is related to the deterministic garbage collector (DGC).
Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.

Level: 1

Type: ERROR

Impact: RMI

BEA-080013: Reference for {0} not found in working set.
Cause: Did not find {0} in the working set while attempting to decrement the reference count. This is related to the deterministic garbage collector (DGC).
Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.

Level: 1

Type: ERROR

Impact: RMI

BEA-080015: Could not mark references {0}.
Cause: An exception occurred during the execution of the DGC trigger.
Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.

Level: 1

Type: ERROR

Impact: RMI

BEA-080016: No connection available to: {0}. References to objects hosted by it are in jeopardy.
Cause: The client lost connection to the server {0}. If the server does not receive lease renewal messages on the server, RMI runtime removes the remote objects whose leases are not renewed.
Action: If the server {0} has been shut down or crashed, no action is required. Otherwise, ensure that the network is healthy.

Level: 1

Type: WARNING

Impact: RMI

BEA-080017: Failed to renew lease for: {0} objects hosted by: {1}.
Cause: This message is logged only in debug mode.
Action: No action is required.

Level: 1

Type: WARNING

Impact: RMI

BEA-080019: Marked in: {0} milliseconds
Cause: This message is logged only if the LogDGCStatistics debug flag is enabled.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080020: An exception occurred in the DGC server sweep {0}.
Cause: A runtime error occurred while the DGC server (host of remote objects) requested a sweep to periodically clean up server references.
Action: Provide the log files to My Oracle Support for further analysis of the problem.

Level: 1

Type: ERROR

Impact: RMI

BEA-080021: Sweep freed: {0} objects in: {1} milliseconds. {2} exported objects remain.
Cause: This message is logged only if the LogDGCStatistics debug flag is enabled.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080022: Tried to enroll lost reference: {0}.
Cause: This message is logged when an attempt is made to increment the reference count of a lost reference. The reference may have already been released.
Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.

Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080023: Tried to unenroll a lost reference: {0}.
Cause: This message is logged only if the DebugDGCEnrollment flag is enabled for debugging.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080024: Tried to renew the lease on the lost reference: {0}.
Cause: This message is logged only if the DebugDGCEnrollment flag is enabled for debugging.
Action: No action is required.

Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080026: Exporting remote object {0} with ID {1}.
Cause: When a remote object is exported into RMI, RMI runtime assigns an object ID to it, thus setting up the environment for remote invocation.
Action: This is an informational message. No action is required.

Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-080027: A heartbeat was not sent due to probable client disconnect.
Cause: A thin-client was disconnected from the server.
Action: This is an informational message. No action is required.

Level: 1

Type: NOTIFICATION

Impact: RMI

BEA-090000: Unsupported circular group definition, {0}.
Cause: Unsupported Feature.
Action: Do not define circular groups.

Level: 1

Type: ERROR

Impact: Security

BEA-090001: Failed to broadcast LoginFailureRecord to the other cluster servers, {0}.
Cause: IO Exception.
Action: For more information on how the invalid login attempts are handled, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.

Level: 1

Type: ERROR

Impact: Security

BEA-090002: Failed to broadcast unlock user {0} to the other clustered servers. {1}
Cause: IO Exception.
Action: For more information on how locked user account lockouts are handled, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.

Level: 1

Type: ERROR

Impact: Security

BEA-090004: Problem closing enumeration : {0}.
Cause: Unexpected exception.
Action: Review the exception message in the log message and see if the message identifies the cause of the exception.

Level: 1

Type: WARNING

Impact: Security

BEA-090010: ACL {0} contains non-existent principal {1} - ignoring principal.
Cause: The principal contained in the ACL does not exist.
Action: Modify the ACL and remove the principal.

Level: 1

Type: WARNING

Impact: Security

BEA-090020: User lockout expired, unlocking user {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090022: Explicitly unlocked, user {0}.
Cause:
Action: For information about unlocking a user account, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.

Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090034: Not listening for SSL, {0}.
Cause: An IOException was thrown when creating the SSL listen thread.
Action: Read the exception text for more help on diagnosing the problem. Contact the system administrator.

Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090038: Checking User {0} for Permission {1} {2}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090039: Access failed (Thread = {0}), caused {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090040: The File realm contains more users than the maximum specified. Maximum = {0}, currently have {1}.
Cause: The File realm sets a limit on the maximum number of supported users. The system has exceeded that limit.
Action: Raise the value of the Max Users attribute.

Level: 1

Type: WARNING

Impact: Security

BEA-090041: The File realm contains more groups than the maximum specified. Maximum = {0}, currently have {1}.
Cause: The File realm sets a limit on the maximum number of supported groups. The system has exceeded that limit.
Action: Raise the value of the Max Groups attribute.

Level: 1

Type: WARNING

Impact: Security

BEA-090042: The File realm contains more ACLs than the maximum specified. Maximum = {0}, currently have {1}.
Cause: The File realm sets a limit on the maximum number of supported ACLs. The system has exceeded that limit.
Action: Raise the value of the Max ACLs attribute.

Level: 1

Type: WARNING

Impact: Security

BEA-090043: Group {0} should exist but doesn''t.
Cause: When adding members to a group, the specified group was not found.
Action: Verify that the group is defined in the fileRealm.properties file or in the Groups tab of the Administration Console.

Level: 1

Type: WARNING

Impact: Security

BEA-090044: Principal {0} does not exist and therefore cannot be added to group {1}.
Cause: When specifying group members, a principal that does not exist was specified.
Action: Add the specified principal to a security realm.

Level: 1

Type: WARNING

Impact: Security

BEA-090045: Permission {0} does not exist.
Cause: When loading ACLs, the specified permission was not found.
Action: Verify that the ACL and the permission are specified correctly.

Level: 1

Type: WARNING

Impact: Security

BEA-090046: ACL {0} does not exist.
Cause: When loading ACLs, the specified permission was not found.
Action: Verify that the ACL is specified correctly.

Level: 1

Type: WARNING

Impact: Security

BEA-090047: Principal {0} does not exist thus cannot be added to ACL {1}.
Cause: The principal specified in the ACL does not exist in any security realm.
Action: Add the principal to a security realm.

Level: 1

Type: WARNING

Impact: Security

BEA-090048: Made an in-memory only change to the File realm.
Cause: Changes made to the File realm cannot be written to filerealm.properties.
Action: Make the changes on the Admin server and the changes are propagated to the Managed servers.

Level: 1

Type: WARNING

Impact: Security

BEA-090049: System user {0} does not exist, creating it.
Cause: The system user is required.
Action: Ensure the system user was created in a security realm before booting the server.

Level: 1

Type: WARNING

Impact: Security

BEA-090051: Error creating security runtime management.
Cause: During initialization, the security runtime registers with the OAM infrastructure. If this process fails, a management exception is thrown.
Action: Verify that the user booting the server is a member of the admin group.

Level: 1

Type: ERROR

Impact: Security

BEA-090052: Server installed as Windows NT service with incorrect password for user {0}; The password may have been changed since the server was installed as a Windows NT Service. Contact the Windows NT system administrator.
Cause: The server is incorrectly configured as Windows NT service.
Action: Contact the Windows NT system administrator.

Level: 1

Type: INTERNAL_ERROR

Impact: Security

BEA-090055: The LDAP realm V1 is deprecated. Please use the LDAP realm V2.
Cause: The LDAP realm V1 is deprecated and will be removed in a future release.
Action: Use LDAP realm V2 or one of the LDAP Authentication providers.

Level: 1

Type: WARNING

Impact: Security

BEA-090056: User {0} had{1,choice,1# one invalid login attempt|2# {1,number} invalid login attempts}, locking account for {2} minutes.
Cause: User exceeded the value of Lockout Threshhold attempts within the period of time specified in the Lockout Reset Duration attribute. The user account is locked.
Action: For more information about protecting user accounts, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.

Level: 1

Type: NOTIFICATION

Impact: Security

BEA-090060: The AccessDecision class "{0}" returned an error: {1}.
Cause: There are multiple possible causes.
Action: Carefully read the returned error to determine if any action is required.

Level: 1

Type: ERROR

Impact: Security

BEA-090063: The DeployableRoleMapper "{0}" returned an error: {1}.
Cause: There ar