2 BEA-000001 to BEA-2194843

BEA-000001
Server must be started by Node Manager when consensus leasing is enabled.
Category:
ConsensusLeasing
Cause:
The server was not started by Node Manager.
Action:
Start the server using Node Manager.
BEA-000101
Cannot resolve ClusterAddress: {0}
Category:
Cluster
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.
BEA-000102
Joining cluster {0} on {1}:{2}
Category:
Cluster
Cause:
The server has joined cluster {0}.
Action:
No action is required.
BEA-000103
Disconnecting from cluster {0}
Category:
Cluster
Cause:
When a server is suspended, it is no longer a member of cluster {0}.
Action:
No action is required.
BEA-000104
Cluster members are running incompatible versions. Local version: {0}. Remote version ({1}): {2}
Category:
Cluster
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.
BEA-000105
The server is leaving the cluster because it is an incompatible version.
Category:
Cluster
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.
BEA-000107
Failed to install {0} in place of those currently installed due to {1}.
Category:
Cluster
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.
BEA-000108
Attempt to retract offer {0}, which is neither installed nor pending.
Category:
Cluster
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.
BEA-000109
An error occurred while sending multicast message: {0}.
Category:
Cluster
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.
BEA-000110
Multicast socket receive error: {0}.
Category:
Cluster
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.
BEA-000111
Adding {0} with ID:{2} to cluster:{1} view.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000112
Removing {0} with ID:{2} from cluster:{1} view due to timeout.
Category:
Cluster
Cause:
Removing {0} from cluster as it failed to send heartbeats 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.
BEA-000113
Removing {0} from cluster view due to PeerGone.
Category:
Cluster
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.
BEA-000114
Failed to find cluster license: {0}
Category:
Cluster
Cause:
A valid license file is required to run clusters.
Action:
Contact an Oracle sales representative for a valid license.
BEA-000115
Lost {0} multicast message(s).
Category:
Cluster
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.
BEA-000116
Failed to join cluster {0} at address {1} due to: {2}.
Category:
Cluster
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.
BEA-000117
Received a stale replication request for object {0}.
Category:
Cluster
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.
BEA-000118
Lost {0} replication updates of object {1}.
Category:
Cluster
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.
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.
Category:
Cluster
Cause:
The cluster does not have a defined multicast address.
Action:
Specify a valid multicast address.
BEA-000120
Received error while creating ClusterRuntimeMBean.
Category:
Cluster
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.
BEA-000121
Two domains in the same LAN should not use the same multicast address. Domains in conflict are {0} and {1}.
Category:
Cluster
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}.
BEA-000122
Clusters {0} and {1} cannot use the same multicast address.
Category:
Cluster
Cause:
Multiple clusters in the same domain are using the same multicast address.
Action:
For efficiency purposes, use two different multicast addresses.
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.
Category:
Cluster
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.
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.
Category:
Cluster
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.
BEA-000125
Conflict resolved: {0} for the object {1} under the bind name {0} in the JNDI tree.
Category:
Cluster
Cause:
Corrective action was taken to resolve the conflict.
Action:
No action is required.
BEA-000126
All session objects should be serializable to replicate. Check the objects in the session. Failed to replicate a non-serializable object.
Category:
Cluster
Cause:
Objects in the session are not serializable or externalizable.
Action:
Ensure that all user-defined objects in the HTTP session are serializable.
BEA-000127
Adding {0} to the cluster.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000128
Updating {0} in the cluster.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000129
Removing {0} from the cluster.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required unless you did not shut down a server.
BEA-000133
Waiting to synchronize with other running members of {0}.
Category:
Cluster
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.
BEA-000137
Error sending multicast message: {0}.
Category:
Cluster
Cause:
The multicast message failed to send due to an IOException.
Action:
Enable cluster debugging to see a detailed message.
BEA-000138
Listening for announcements from cluster {0} on {1}:{2}.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
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}.
Category:
Cluster
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.
BEA-000140
Failed to deserialize statedump from server {0} with {1}.
Category:
Cluster
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.
BEA-000141
TCP/IP socket failure occurred while fetching state dump over HTTP from {0}.
Category:
Cluster
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.
BEA-000142
Trying to download cluster JNDI tree from server {0}.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000143
Trying to download {1} from a server listening on {0}.
Category:
Cluster
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.
BEA-000144
Managed Server {0} has been suspended or shut down.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
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.
Category:
Cluster
Cause:
The cluster is misconfigured.
Action:
Configure the DataSourceForAutomaticMigration property.
BEA-000147
Server "{0}" failed to renew lease in the {1}.
Category:
Cluster
Cause:
The server failed to renew the lease on time.
Action:
No action is required.
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.
Category:
Cluster
Cause:
The migratable server is misconfigured.
Action:
Ensure that the server is targeted to a machine and restart the migratable server.
BEA-000149
Server failed to get a connection to the {1} during {0}.
Category:
Cluster
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.
BEA-000150
Server failed to get a connection to the {1} in the past {0} seconds for lease renewal. Or, Server could get a connection but failed to renew the lease. Server will shut itself down.
Category:
Cluster
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. If this message continues to appear even when the database is accessible, something may be wrong in the database. Contact My Oracle Support for further assistance.
BEA-000151
Server "{0}" has taken over the role of Cluster Master.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000152
Server "{0}" lost the privileges to be the Cluster Master.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
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.
Category:
Cluster
Cause:
The cluster is misconfigured.
Action:
Assign a pool of machines for automatic migration and refer to WebLogic Server documentation for more details.
BEA-000154
Cluster is misconfigured. The remote cluster address {0} is not a valid URL.
Category:
Cluster
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.
BEA-000155
Configured cluster address is invalid : {0}. Constructing cluster address dynamically.
Category:
Cluster
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).
BEA-000156
Could not send out new attributes for cluster member {0}: {1}.
Category:
Cluster
Cause:
There was a problem sending out changed member attributes.
Action:
Examine the server logs.
BEA-000158
Server has stopped sending cluster heartbeats and announcements. It is still receiving heartbeats and announcements from other cluster members.
Category:
Cluster
Cause:
The server is going out of the cluster as a result of the suspend or shutdown operation.
Action:
No action is required
BEA-000159
The clocks of the machines hosting local server and remote server "{0}" are off by {1} seconds
Category:
Cluster
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.
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.
Category:
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.
BEA-000161
Multicast message from server {0} appears to have been tampered with.
Category:
Cluster
Cause:
The authenticity of the message could not be verified.
Action:
Ensure that the network is not being hijacked.
BEA-000162
Starting "{0}" replication service with remote cluster address "{1}"
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000163
Stopping "{0}" replication service
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000164
Synchronized cluster JNDI tree from server {0}.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
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.
Category:
Cluster
Cause:
Two clusters on the local area network are using the same multicast address.
Action:
Change the multicast address of either domain.
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.
Category:
Cluster
Cause:
Multiple clusters in the same domain are using the same multicast address.
Action:
For efficiency purposes, use two different multicast addresses.
BEA-000167
Some services failed to roll back successfully when trying to abort the migration: {0}.
Category:
Cluster
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.
BEA-000168
Failed to restart/migrate server "{0}" because of {1}
Category:
Cluster
Cause:
There was an error while restarting migratable server: {1}
Action:
Examine the server logs.
BEA-000170
The server {0} did not receive the multicast packets that it sent.
Category:
Cluster
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
BEA-000171
Failed to load the custom Singleton Services SQL Query Helper: {0}, because of {1}.
Category:
Cluster
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.
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}
Category:
Cluster
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.
BEA-000176
{0} does not specify a machine.
Category:
Cluster
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.
BEA-000178
Failed to execute {0} because of {1}.
Category:
Cluster
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.
BEA-000179
{0} failed while altering its lease.
Category:
Cluster
Cause:
An exception occurred: {1}.
Action:
Ensure that, if a database is being used for leasing, it is available.
BEA-000180
Unable to retrieve Job {0} from the database. The retrieval failed with {1}
Category:
Cluster
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.
BEA-000182
Job Scheduler created a job with ID {0} for TimerListener with description {1}
Category:
Cluster
Cause:
Job Scheduler created an entry in the database for a submitted job.
Action:
No action is required.
BEA-000183
Successfully cancelled job with ID {0}
Category:
Cluster
Cause:
Job Scheduler removed a job entry from the database based on application request
Action:
No action is required.
BEA-000184
This server did not attempt to renew its lease for {0} seconds. The server may need to be restarted or migrated.
Category:
Cluster
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.
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.
Category:
Cluster
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.
BEA-000186
An error was encountered while migrating {0}: {1}
Category:
Cluster
Cause:
See the error in the message body.
Action:
Ensure that there are enough candidate servers running in the cluster.
BEA-000187
The Singleton Service {0} is now registered on this server. This server may be chosen to host this service.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000188
The Singleton Service {0} is no longer registered on this server.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000189
The Singleton Service {0} is now active on this server.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000190
The Singleton Service {0} has been deactivated on this server.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000191
Now monitoring the Migratable Server {0}
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-000192
A running server was not found to host {0}. The server will retry in a few seconds.
Category:
Cluster
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.
BEA-000193
The JTA service for {0} has failed, but {0} is still running. JTA cannot be migrated from a running server.
Category:
Cluster
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.
BEA-000194
An error was encountered while trying to report a migration event: {0}.
Category:
Cluster
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.
BEA-000195
An error was encountered while trying to save a migration event. The error was: {0}.
Category:
Cluster
Cause:
An internal WebLogic Server 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.
BEA-000196
Received data about a migration of type {0}, but no such type is recognized by the Administration Server.
Category:
Cluster
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.
BEA-000197
Listening for announcements from cluster using unicast cluster messaging
Category:
Cluster
Cause:
Unicast cluster messaging mode is enabled.
Action:
No action is required.
BEA-000198
All replication calls for cluster {0} must be made over channel {1}
Category:
Cluster
Cause:
All replication calls for cluster {0} must be made over channel {1}
Action:
Check the configured channel for replication calls.
BEA-000199
Replication calls can only be made by {0} over {1} channel
Category:
Cluster
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.
BEA-000214
WebLogic Server "{1}" version: {0} Copyright (c) 1995,2017, Oracle and/or its affiliates. All rights reserved.
Category:
WebLogicServer
Cause:
The startup banner used when a server starts.
Action:
No action is needed.
BEA-000215
Loaded license: {0}.
Category:
WebLogicServer
Cause:
This prints from the location from which the license file was loaded.
Action:
No action is needed.
BEA-000220
Cannot shut down the server because the request was from a null user (Principal).
Category:
WebLogicServer
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.
BEA-000221
Cannot shut down the server because the request was from a nameless user (Principal).
Category:
WebLogicServer
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.
BEA-000222
Cannot disable server logins because the request was from a null user (Principal).
Category:
WebLogicServer
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.
BEA-000223
Cannot disable server logins because the request was from a nameless user (Principal).
Category:
WebLogicServer
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.
BEA-000224
Cannot enable server logins because the request was from a null user (Principal).
Category:
WebLogicServer
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.
BEA-000225
Cannot enable server logins because the request was from a nameless user (Principal).
Category:
WebLogicServer
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.
BEA-000226
The enabling of server logins has been requested by {0}.
Category:
WebLogicServer
Cause:
The server has been requested to unlock itself and enable server logins again.
Action:
No action is needed.
BEA-000227
Server logins have been enabled.
Category:
WebLogicServer
Cause:
Server logins have been enabled.
Action:
No action is needed.
BEA-000228
The disabling of server logins has been requested by {0}.
Category:
WebLogicServer
Cause:
A LOCK command was issued by an administrator.
Action:
No action is needed.
BEA-000229
Server logins have been disabled.
Category:
WebLogicServer
Cause:
A LOCK command was issued by an administrator.
Action:
No action is needed.
BEA-000231
Waiting {0} seconds for server shutdown.
Category:
WebLogicServer
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.
BEA-000232
Server shutdown is commencing now and is irreversible.
Category:
WebLogicServer
Cause:
A shutdown command was issued by an administrator.
Action:
No action is needed.
BEA-000236
Stopping execute threads.
Category:
WebLogicServer
Cause:
An administrator issued a shutdown command.
Action:
No action is needed.
BEA-000238
Shutdown has completed.
Category:
WebLogicServer
Cause:
Shutdown has completed.
Action:
No action needed.
BEA-000240
Cannot cancel the server shutdown because the request was from a null user (Principal).
Category:
WebLogicServer
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.
BEA-000241
Cannot cancel the server shutdown because the request was from a nameless user (Principal).
Category:
WebLogicServer
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.
BEA-000242
Cannot cancel server shutdown because there is no shutdown in progress.
Category:
WebLogicServer
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.
BEA-000243
It is too late to cancel the server shutdown because the shutdown is already in progress.
Category:
WebLogicServer
Cause:
The server has already started to shut down. It is too late to cancel shutdown at this point.
Action:
No action is needed.
BEA-000244
Canceling server shutdown.
Category:
WebLogicServer
Cause:
An administrator has issued a cancel shutdown operation.
Action:
No action is needed.
BEA-000246
Server shutdown has been canceled and logins are enabled.
Category:
WebLogicServer
Cause:
The cancel shutdown operation was successful.
Action:
No action is needed.
BEA-000248
An exception occurred while trying to find a localized T3Srvr message, message ID {0}, {1}
Category:
WebLogicServer
Cause:
The localized version of the message could not be found.
Action:
No action is required.
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.
Category:
WebLogicServer
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.
BEA-000251
The server switched to the group "{0}".
Category:
WebLogicServer
Cause:
A non-privileged group was specifed. The server switched to the specified group after starting.
Action:
No action is needed.
BEA-000252
Cannot switch to the group "{0}". {1}
Category:
WebLogicServer
Cause:
The server was unable to switch to the specified group.
Action:
Ensure that the specified group exists.
BEA-000253
Switched to the user "{0}".
Category:
WebLogicServer
Cause:
A non-privileged user was specified. The server switched to the specified user after starting.
Action:
No action is needed.
BEA-000254
Cannot switch to the user "{0}". {1}
Category:
WebLogicServer
Cause:
The server could not switch to the specified non-privileged user.
Action:
Ensure that the specified user exists.
BEA-000256
Invoking {0}.main({1})
Category:
WebLogicServer
Cause:
The server configuration specifies startup and shutdown classes to run.
Action:
No action is required.
BEA-000257
Exception reading command: {0}
Category:
WebLogicServer
Cause:
An exception occurred while reading commands from the shell window.
Action:
Disable the shell command input property weblogic.ConsoleInputEnabled.
BEA-000258
Command [{0}]
Category:
WebLogicServer
Cause:
The Administration Console received the specified command and is about to execute it.
Action:
No action is needed.
BEA-000259
Administration Console: profiling enabled.
Category:
WebLogicServer
Cause:
Profiling has been enabled in the Administration Console.
Action:
No action is needed.
BEA-000260
Administration Console: profiling disabled.
Category:
WebLogicServer
Cause:
Profiling has been disabled in the Administration Console.
Action:
No action is required.
BEA-000261
The system user is not permitted to shut down, {0}.
Category:
WebLogicServer
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.
BEA-000262
No such command: {0}.
Category:
WebLogicServer
Cause:
The unknown command was entered.
Action:
Refer to the list of known commands.
BEA-000263
GC: before free/total={0}/{1} ({2}%).
Category:
WebLogicServer
Cause:
The GS statistics are shown before forcing GC.
Action:
No action is needed.
BEA-000264
GC: after free/total={0}/{1} ({2}%).
Category:
WebLogicServer
Cause:
The GS statistics are shown after forcing GC.
Action:
No action is needed.
BEA-000265
Attempt to unbind ClientContext "{0}" that is not bound.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000266
{0} has {1,choice,1#one pending ExecuteRequest|2#{1,number} pending ExecuteRequests}.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000267
{0} had a negative workQueueDepth of {1}.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000268
Failed to send unsolicted message "{0}" to client, {1}
Category:
WebLogicServer
Cause:
Deprecated functionality
Action:
Deprecated functionality
BEA-000269
The connection to the client using "{0}" has been unexpectedly lost due to {1}. The server is initiating a hard disconnect.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000270
Timing out "{0}" because it was idle.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000271
Ignoring a repeated request to schedule the death of "{0}".
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000272
Scheduling the death of "{0}".
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000273
Removing "{0}" because of hard disconnect timeout.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000274
Removing "{0}" because of soft disconnect timeout.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000275
Soft disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000276
Hard disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000277
Idle disconnect pending for {0,choice,0#less than a minute|1#one minute|2#{0} minutes}.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000283
Failed to marshal response, {0}
Category:
WebLogicServer
Cause:
Deprecated functionality
Action:
Deprecated functionality
BEA-000284
Unexpected failure to marshal response, {0}
Category:
WebLogicServer
Cause:
Deprecated functionality
Action:
Deprecated functionality
BEA-000286
Failed to invoke startup class "{0}", {1}.
Category:
WebLogicServer
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.
BEA-000287
Invoking startup class: {0}.startup({1}).
Category:
WebLogicServer
Cause:
The startup class was invoked with the specified arguments.
Action:
No action is needed.
BEA-000288
{0} reports: {1}.
Category:
WebLogicServer
Cause:
The return value of the startup class was logged.
Action:
No action is needed.
BEA-000289
Failed to invoke shutdown class "{0}", {1}.
Category:
WebLogicServer
Cause:
An exception occurred in a shutdown class.
Action:
Determine the error in the shutdown class code and restart the server.
BEA-000290
Invoking shutdown class: {0}.shutdown({1}).
Category:
WebLogicServer
Cause:
The server is invoking shutdown classes as a part of shutdown.
Action:
No action is needed.
BEA-000291
{0} reports: {1}.
Category:
WebLogicServer
Cause:
The server logs the return value of the shutdown class.
Action:
No action is needed.
BEA-000297
Inconsistent security configuration, {0}
Category:
WebLogicServer
Cause:
An exception occurred in SSL initialization.
Action:
Look at the exception in {0} for more information on diagnosing the problem.
BEA-000298
Certificate expires in {0} days: {1}
Category:
WebLogicServer
Cause:
The certificate is about to expire.
Action:
Obtain a new server certificate or trusted CA certificate before it expires.
BEA-000306
Cannot use SSL because no certificates have been specified in the WebLogic Server configuration.
Category:
WebLogicServer
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.
BEA-000307
Exportable key maximum lifespan set to {0} uses.
Category:
WebLogicServer
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.
BEA-000314
The execution class "{0}" did not retrieve a T3Executable or T3ExecutableLazy.
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000315
Unexpected failure of T3ExecutableLazy, {0}
Category:
WebLogicServer
Cause:
This is an informational message.
Action:
No action is required.
BEA-000316
enableWatchDog() is not permitted from within a server.
Category:
WebLogicServer
Cause:
Deprecated functionality
Action:
Deprecated functionality
BEA-000317
disableWatchDog() is not permitted from within a server.
Category:
WebLogicServer
Cause:
Deprecated functionality
Action:
Deprecated functionality
BEA-000320
Error creating runtime MBean for execute queue {0}.
Category:
WebLogicServer
Cause:
An internal system error occurred.
Action:
Contact My Oracle Support with the server logs.
BEA-000329
Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in production mode.
Category:
WebLogicServer
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.
BEA-000330
Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in production mode.
Category:
WebLogicServer
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.
BEA-000331
Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in development mode.
Category:
WebLogicServer
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.
BEA-000332
Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in development mode.
Category:
WebLogicServer
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.
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.
Category:
WebLogicServer
Cause:
The server is under high load.
Action:
Review the execute queue settings.
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 in "{4}". Stack trace: {5}
Category:
WebLogicServer
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).
BEA-000339
{0} has become "unstuck".
Category:
WebLogicServer
Cause:
A thread previously stuck is now available.
Action:
No action is needed.
BEA-000342
Unable to initialize the server: {0}.
Category:
WebLogicServer
Cause:
An exception occurred during the server initialization.
Action:
Analyze the weblogic.log file to determine why the server did not initialize completely.
BEA-000343
The health monitor for "{0}" failed to register because of exception "{1}".
Category:
WebLogicServer
Cause:
Refer to the exception printed in the log message.
Action:
Refer to the exception printed in the log message.
BEA-000344
The health monitor for "{0}" failed to unregister because of exception "{1}".
Category:
WebLogicServer
Cause:
Refer to the exception printed in the log message.
Action:
Refer to the exception printed in the log message.
BEA-000345
******* * * The selected version of Java, {0}, contains a known security flaw. Please upgrade to at least {1} * *******
Category:
WebLogicServer
Cause:
JEP-290 support is missing.
Action:
Upgrade the version of Java used to run WebLogic Server.
BEA-000357
Started WebLogic Server independent Managed Server "{0}" for domain "{1}" running in development mode.
Category:
WebLogicServer
Cause:
The server started with the Managed Server independence mode enabled.
Action:
No action is required.
BEA-000358
Started WebLogic Server independent Managed Server "{0}" for the domain "{1}" running in production mode.
Category:
WebLogicServer
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.
BEA-000360
The server started in {0} mode.
Category:
WebLogicServer
Cause:
The startup mode was set to SUSPENDED.
Action:
No action is required.
BEA-000362
Server failed. Reason: {0}
Category:
WebLogicServer
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.
BEA-000365
Server state changed to {0}.
Category:
WebLogicServer
Cause:
The server progressed through the startup or shutdown sequence.
Action:
No action is required.
BEA-000366
The server failed to shut down. Exception: {0}
Category:
WebLogicServer
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.
BEA-000371
An error occurred during server shutdown: {0}.
Category:
WebLogicServer
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.
BEA-000374
Waiting for ExecuteQueue {0} to finish {1} pending requests.
Category:
WebLogicServer
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.
BEA-000377
Starting WebLogic Server with {0} Version {1} from {2}.
Category:
WebLogicServer
Cause:
The server is starting.
Action:
No action is needed.
BEA-000378
The server failed to shut down within the configured timeout of {0} seconds. The server process will now exit.
Category:
WebLogicServer
Cause:
Forced shutdown is taking too long to complete.
Action:
No action is needed.
BEA-000381
ServerLifeCycle operation failed. Message: {0} {1}
Category:
WebLogicServer
Cause:
A server operation, such as shutdown, failed.
Action:
If the error is not application related, contact My Oracle Support.
BEA-000382
A critical service failed. The server will automatically transition to the ADMIN state.
Category:
WebLogicServer
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.
BEA-000383
A critical service failed. The server will shut itself down.
Category:
WebLogicServer
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.
BEA-000384
A fatal configuration failure occurred during startup. Check if the config.xml file contains invalid entries. Reason: {0}
Category:
WebLogicServer
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.
BEA-000385
Server health failed. Reason: {0}
Category:
WebLogicServer
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.
BEA-000386
Server subsystem failed. Reason: {0}
Category:
WebLogicServer
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.
BEA-000388
JVM called the WebLogic Server shutdown hook. The server will force shutdown now.
Category:
WebLogicServer
Cause:
The JVM called the WebLogic Server shutdown hook. The server will force shutdown now.
Action:
No action is needed.
BEA-000394
Deadlock detected: {0}.
Category:
WebLogicServer
Cause:
There are threads deadlocked in the server.
Action:
Report this error to My Oracle Support if the deadlock involves WebLogic Server internal code.
BEA-000395
The following extensions directory contents added to the end of the classpath: {0}.
Category:
WebLogicServer
Cause:
Extensions directory contents were added to the classpath.
Action:
No action is needed.
BEA-000396
Server {0} has been requested by {1}.
Category:
WebLogicServer
Cause:
A request was made to perform the specified server operation.
Action:
No action is needed.
BEA-000398
Secure mode enabled for WebLogic Server "{0}".
Category:
WebLogicServer
Cause:
Secure mode is enabled.
Action:
None.
BEA-000401
Socket queue full, dropping socket {0}.
Category:
Socket
Cause:
The internal queue for socket read requests is full. Additional read requests for sockets will be dropped.
Action:
Check for other log messages that give more information about the failure.
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.
Category:
Socket
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.
BEA-000403
IOException occurred on socket: {0} {1}.
Category:
Socket
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.
BEA-000404
ThreadDeath in processSockets {0}.
Category:
Socket
Cause:
A ThreadDeath error occurred while processing sockets.
Action:
Check for other log messages that give more information about the failure.
BEA-000405
Uncaught Throwable in processSockets {0}.
Category:
Socket
Cause:
A Throwable was caught while processing sockets.
Action:
Check for other log messages that give more information about the failure.
BEA-000406
{0}
Category:
Socket
Cause:
This is an informational message.
Action:
No action is required.
BEA-000409
Problem on socket: {0} {1}
Category:
Socket
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.
BEA-000414
Could not initialize the POSIX performance pack.
Category:
Socket
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.
BEA-000415
System has file descriptor limits of soft: {0}, hard: {1}
Category:
Socket
Cause:
This is an informational message.
Action:
No action is required.
BEA-000416
Using effective file descriptor limit of: {0} open sockets and files.
Category:
Socket
Cause:
This is an informational message.
Action:
No action is required.
BEA-000421
Uncaught Throwable in processSockets {0}.
Category:
Socket
Cause:
A Throwable was caught while processing sockets.
Action:
Check for other log messages that give more information about the failure.
BEA-000429
Muxer received error: {0} {1}.
Category:
Socket
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.
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}"
Category:
Socket
Cause:
This is an informational message for the administrator.
Action:
No action is required.
BEA-000432
Unable to load performance pack. Using Java I/O instead. {0}
Category:
Socket
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.
BEA-000435
Unable to initiate read for the socket. The maximum allowed number of pending I/O requests ({0}) has been exceeded.
Category:
Socket
Cause:
The maximum allowed number of pending I/O requests ({0}) has been exceeded. Further read requests for the socket cannot be initiated.
Action:
Check for other log messages that give more information about the failure.
BEA-000436
Allocating {0} reader threads.
Category:
Socket
Cause:
This is an informational message.
Action:
No action is required.
BEA-000437
The default setting for MuxerClass was overridden and no muxer class name was specified. Resorting to implementation class: {0}.
Category:
Socket
Cause:
This is an informational message.
Action:
No action is required.
BEA-000438
Unable to load performance pack. Using Java I/O instead. {0}
Category:
Socket
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.
BEA-000439
Unable to create the Java socket muxer.
Category:
Socket
Cause:
Creation of the Java socket muxer failed.
Action:
Ensure that the classpath is set properly.
BEA-000440
Unable to initiate I/O for {0} {1}.
Category:
Socket
Cause:
The initiation of the I/O operation failed, which could have been caused by the network, I/O or other problems.
Action:
Correct any conditions as suggested by the error message, if applicable.
BEA-000441
Unable to find internal data record for the socket {0}, with I/O completion result {1}
Category:
Socket
Cause:
The internal data record for the socket could not be found while completing an I/O operation.
Action:
Check for other log messages that give more information about the failure.
BEA-000442
The connection attempt was rejected because the incoming protocol is not enabled on channel "{0}".
Category:
Socket
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.
BEA-000443
The connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.
Category:
Socket
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.
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.
Category:
Socket
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.
BEA-000445
Connection rejected, filter blocked {0}, {1}
Category:
Socket
Cause:
The incoming message was not recognized as one of the supported protocols.
Action:
Ensure that the server is configured for the relevant protocol.
BEA-000446
Native I/O enabled.
Category:
Socket
Cause:
This is an informational message.
Action:
No action is required.
BEA-000447
Native I/O disabled. Using Java I/O.
Category:
Socket
Cause:
This is an informational message.
Action:
No action is required.
BEA-000448
Socket channel support has been enabled for a JVM on which the feature is unsupported.
Category:
Socket
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.
BEA-000449
Closing the socket, as no data read from it on {1}:{2} during the configured idle timeout of {0} seconds.
Category:
Socket
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.
BEA-000451
Closing the socket, as end of file is encountered while reading from the socket to the ONS server at {0}.
Category:
Socket
Cause:
The connection to the remote Oracle Notification Server (ONS) process might have been disconnected.
Action:
Check the status of the remote ONS process.
BEA-000452
An exception occurred on the socket to the ONS server at {0}: {1}.
Category:
Socket
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.
BEA-000453
An exception occurred while processing the message sent from the ONS at {0}: {1}
Category:
Socket
Cause:
An error occurred while parsing the message received from the remote ONS.
Action:
Check the ONS log file for additional details.
BEA-000454
Unable to establish connection to the remote ONS process at {0}:{1}. Exception occurred while doing handshake: {2}
Category:
Socket
Cause:
An exception occurred while doing handshake with the remote ONS process.
Action:
Check the exception and ONS log file for additional details.
BEA-000455
Attempting to remove unregistered HandshakeCompletedListener: class={0}, instance={1}.
Category:
Socket
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.
BEA-000456
Unable to load performance pack. Using Java I/O instead.
Category:
Socket
Cause:
The native library for the performance pack could not be loaded.
Action:
Ensure that the classpath and the environment is set up properly. If the situation persists, contact My Oracle Support.
BEA-000457
NIOInputStream received error while closing java.nio.channels.Selector: : {0} {1}.
Category:
Socket
Cause:
An unexpected error occurred while processing socket I/O requests.
Action:
If the situation persists, capture the errors and send the server log files to My Oracle Support.
BEA-000458
{0}
Category:
Socket
Cause:
See the message body.
Action:
Review the message body to determine the appropriate action to take.
BEA-000501
Peergone send failed - target unreachable.
Category:
RJVM
Cause:
This is an informational message.
Action:
No action is required.
BEA-000502
Peergone send failed - target already gone.
Category:
RJVM
Cause:
This is an informational message.
Action:
No action is required.
BEA-000503
Incoming message header or abbreviation processing failed. {0}
Category:
RJVM
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.
BEA-000504
Unmarshal exception: received illegal command code: {0}
Category:
RJVM
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.
BEA-000505
Peer did not send us a valid heartbeat interval; using the default heartbeat specified as a property.
Category:
RJVM
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.
BEA-000506
Closing: {0} because of {1}
Category:
RJVM
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.
BEA-000507
Could not create/send request to close duplicate connection message. {0}
Category:
RJVM
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.
BEA-000508
ID: {0} in use by: {1}, can not install {2}
Category:
RJVM
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.
BEA-000509
Finder not initialized.
Category:
RJVM
Cause:
This JVM was created without a valid finder.
Action:
Ensure that a valid finder is used when creating this JVM.
BEA-000510
Unsolicited response: {0}
Category:
RJVM
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.
BEA-000511
Unsolicited error response for: {0}
Category:
RJVM
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.
BEA-000512
New heartbeat period: {0} is different from established heartbeat period: {1}; using established heartbeat period
Category:
RJVM
Cause:
This is an informational message.
Action:
No action is required.
BEA-000513
Failure in heartbeat trigger for RJVM: {0}. {1}
Category:
RJVM
Cause:
This error indicates a temporary failure in the heartbeat trigger mechanism.
Action:
No action is required. This is usually a temporary failure.
BEA-000514
openConnection() failed. {0}
Category:
RJVM
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.
BEA-000515
execute failed {0}
Category:
RJVM
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.
BEA-000519
Unable to connect to a remote server on address {1} and port {2,number,0} with protocol {0}. The exception is {3}
Category:
RJVM
Cause:
The target is either not reachable or is not active.
Action:
Ensure that the target is active.
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} ResolveDNSName Enabled {7}
Category:
RJVM
Cause:
This is an informational message.
Action:
No action is required.
BEA-000572
The server rejected a connection attempt {0} probably due to an incorrect firewall configuration or administrative command.
Category:
RJVM
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.
BEA-000573
RequestTimeout for message id {0} with message: {1}.
Category:
RJVM
Cause:
The server timed out while waiting for a response to a request. The configured timeout may not be sufficient enough for the runtime environment.
Action:
Consider raising the value of the "weblogic.jndi.responseReadTimeout" property.
BEA-000574
Bootstrap to {0} failed. The remote side declared peer may be gone on this JVM.
Category:
RJVM
Cause:
Bootstrapping to the remote address has failed likely due to a PeerGone on this JVM.
Action:
Check whether the remote server is up and running
BEA-000577
Unable to get weblogic.rjvm.WebRjvmSupport.webRjvmSupport from HK2 services. exception: {0}
Category:
RJVM
Cause:
weblogic.rjvm.WebRjvmSupport is not registered as an HK2 service.
Action:
Contact My Oracle Support with the server logs and configuration.
BEA-000578
Unable to load weblogic.rjvm.WebRjvmSupport.webRjvmSupport. exception: {0}
Category:
RJVM
Cause:
Class weblogic.servlet.internal.utils.WebRjvmSupportImpl can be loaded.
Action:
Contact My Oracle Support with the server logs and configuration.
BEA-000579
Failed to get client certificate. exception: {0}
Category:
RJVM
Cause:
Failed to get client certificate. exception: {0}
Action:
Check the custom class which is specified by the system property weblogic.security.SSL.ClientCertPlugin.
BEA-000580
Failed to send {0}. {1}
Category:
RJVM
Cause:
While sending a message an error was encountered.
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.
BEA-000600
Callback {0} failed: {1}
Category:
Common
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000601
AdminProxyWatchDog: Enabled. Interval = {0} secs.
Category:
Common
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000602
AdminProxyWatchDog: Enable failed.
Category:
Common
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000603
AdminProxyWatchDog: Disabled.
Category:
Common
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000604
AdminProxyWatchDog: Disable failed.
Category:
Common
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000605
Connectivity lost to WatchDog Client. Shutting down.
Category:
Common
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000606
AdminProxyWatchDog: No echo received in last {0} minutes. Shutting down.
Category:
Common
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000607
AdminProxyWatchDog: Echo Received.
Category:
Common
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000608
AdminProxyWatchDog: Tick. diff = {0}
Category:
Common
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000609
An error occurred during server shutdown: {0}.
Category:
Common
Cause:
The indicated error has occurred while the server was shutting down.
Action:
Check for other log messages that give more information about the failure.
BEA-000610
Expected RemoteException, RuntimeException, or Error {0}
Category:
Common
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.
BEA-000611
No resources in the pool {0} will be tested, as specified MaxUnavailable {1} has been reached.
Category:
Common
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 (as resources become unavailable to the application during the testing).
Action:
If necessary, tune the value for the MaxUnavailable attribute for the pool.
BEA-000612
All {1} resource instances currently available in the pool {0} are being tested.
Category:
Common
Cause:
This is a warning indicating that all currently available resources in the pool are being tested. 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.
BEA-000613
Testing of resources upon creation has been dynamically enabled for pool "{0}".
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000614
Testing of resources upon creation has been dynamically disabled for pool "{0}".
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000615
Testing of resources when being reserved has been dynamically disabled for pool "{0}".
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000616
Testing of resources when being reserved has been dynamically enabled for pool "{0}".
Category:
Common
Cause:
This is an informational message.
Action:
No action required.
BEA-000617
Testing of resources when being released has been dynamically enabled for pool "{0}".
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000618
Testing of resources when being released has been dynamically disabled for pool "{0}".
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000619
Unable to forcibly release resource "{1}" back into the pool "{0}". Received exception: {2}.
Category:
Common
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.
BEA-000620
Forcibly releasing inactive resource "{1}" back into the pool "{0}".
Category:
Common
Cause:
The resource was found to be unused by the application for the specified duration, and hence is being forcibly released back into the pool.
Action:
Check application code for leakages of resource objects, or tune the configured value of the relevant pool attribute.
BEA-000621
Expected RemoteException, RuntimeException, or Error {0}
Category:
Common
Cause:
An unexpected low-level message was sent to the server.
Action:
This is likely to be due to an internal server/client error that should be reported to My Oracle Support.
BEA-000622
Ignoring attempt to release resource "{1}" to pool "{0}" after the pool has been shut down.
Category:
Common
Cause:
Application is trying to release a resource to a pool after the pool has been shutdown.
Action:
Check application behaviour. All resources should be closed before the application is shutdown.
BEA-000623
Setting CapacityIncrement for pool "{0}" to 1. The specified value of "{1}" is not valid.
Category:
Common
Cause:
The application had specified an invalid value for CapacityIncrement.
Action:
Check and correct the specified value for CapacityIncrement for the indicated pool.
BEA-000624
Setting frequency of testing of free resources in pool "{0}" to 5 seconds, since the specified value of "{1}" is not valid.
Category:
Common
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.
BEA-000625
The application has disabled periodic testing of free resources in pool "{0}".
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000626
Free resources in pool "{0}" will be tested every "{1}" seconds.
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000627
Reached maximum capacity of pool "{0}", making "{2}" new resource instances instead of "{1}".
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000628
Created "{1}" resources for pool "{0}", out of which "{2}" are available and "{3}" are unavailable.
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000629
Recreated "{2}" out of "{1}" resources for pool "{0}".
Category:
Common
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.
BEA-000630
Unable to create "{1}" resources for pool "{0}".
Category:
Common
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 whether the failure condition that prevents the resources from being created (for example, the database server or downed network connectivity to it) is still persisting.
BEA-000631
Unknown resource "{1}" being released to pool "{0}": {2}
Category:
Common
Cause:
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 application behavior.
BEA-000632
Resource Pool "{0}" shutting down, ignoring {1} resources still in use by applications..
Category:
Common
Cause:
The administrator is shutting down the pool while applications are still using resources that they have obtained from the pool. It is possible that these resources may have been leaked by the applications.
Action:
Check application behavior.
BEA-000633
Resource Pool "{0}" suspending due to consecutive number of resource creation failures exceeding threshold of {1}
Category:
Common
Cause:
Resource creation or resource tests have repeatedly failed.
Action:
Determine the cause of resource failures and take corrective action.
BEA-000634
Resource hang detected for pool "{0}", group "{1}". Waited {2} milliseconds where a typical test has been taking {3}.
Category:
Common
Cause:
Resource tests have been taking longer than expected.
Action:
Correct the condition that causes the resource tests to block for extended periods of time.
BEA-000635
Resource Pool "{0}", group "{1}" disabled due to number of resource creation or test failures exceeding threshold of {2}.
Category:
Common
Cause:
Resource creation or resource tests have repeatedly failed.
Action:
Determine the cause of resource failures and correct.
BEA-000636
Resource Pool "{0}", group "{1}" enabled.
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000637
Resource Pool "{0}" resuming due to successful resource creation or test.
Category:
Common
Cause:
This is an informmational message.
Action:
No action is required.
BEA-000638
Resource Pool "{0}" is being suspended by an external command (multi data source or console or other).
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000639
Resource Pool "{0}" is being force-suspended by an external command (multi data source or console or other).
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000640
Resource Pool "{0}" resuming by external command (multi data source or console or other).
Category:
Common
Cause:
This is an informational message.
Action:
No action is required.
BEA-000701
Unable to mount the fileSystem named {0} {1}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000702
Unable to unmount the fileSystem named {0} {1}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000703
Unable to get fileSystem context from Root {0}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000704
Cannot create file system at {0} {1}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000705
Created file system at {0}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000706
Unable to find remote file {0} {1}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000707
Unable to open remote file {0} {1}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000708
T3RemoteOutputStreamProxy: write timed out or interrupted - {0}, {1}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000709
T3RemoteOutputStreamProxy: flush timed out or interrupted - {0}, {1}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000710
TimeRepeat trigger scheduled to run at a date in the past : {0}, trigger will not repeat
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000711
Uncaught throwable in run {0}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000712
Exception invoking {0} {1}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000713
Exception closing stream {0}
Category:
T3Misc
Cause:
Deprecated functionality.
Action:
Deprecated functionality.
BEA-000800
{0} stopped.
Category:
Kernel
Cause:
A ThreadDeath exception caused a shutdown.
Action:
No action is required.
BEA-000801
ExecuteRequest: {0} cancelled.
Category:
Kernel
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.
BEA-000802
ExecuteRequest failed {0}.
Category:
Kernel
Cause:
An execute request generated an exception that was not handled.
Action:
Contact My Oracle Support.
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}.
Category:
Kernel
Cause:
No constructor that takes a String argument was found for the declared attribute type.
Action:
Provide a constructor with a String argument.
BEA-000804
The Class {0} attribute {1} could not be initialized with value {2}. The exception message is {3}.
Category:
Kernel
Cause:
See the exception stack trace for details.
Action:
Take the appropriate action based on the error message.
BEA-000805
The self-tuning thread pool is disabled. An execute queue will be created for each Work Manager definition.
Category:
Kernel
Cause:
The server is starting.
Action:
No action is required.
BEA-000807
Work Manager {0} has reached its capacity. It is rejecting from thread {1}. The message is {2}. Throwable is {3}.
Category:
Kernel
Cause:
This is a Work Manager bug.
Action:
No action is required.
BEA-000808
The executing thread is a non-WebLogic Server thread. Modify the application to use the Commonj Work Manager API.
Category:
Kernel
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.
BEA-000810
The memory pressure field has changed from {0} to {1}.
Category:
Kernel
Cause:
The memory pressure in the system has gone either up or down.
Action:
The system should be responding to the memory pressure level. No further action should be taken.
BEA-000902
A duplicate expression was found in the system property {0}.nonProxyHosts: {1}.
Category:
Net
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".
BEA-000903
Failed to communicate with proxy: {0}/{1}. Will try connection {2}/{3} now.
Category:
Net
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.
BEA-000904
{0} initializing the URL stream handler with custom factory: {1}.
Category:
Net
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.
BEA-000905
Could not open connection with host: {0} and port: {1}.
Category:
Net
Cause:
The connection attempt failed.
Action:
Ensure that the server is running on the specified host and port.
BEA-000906
Failed to communicate with proxy: {0}/{1}.
Category:
Net
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.
BEA-001035
The following error has occurred: {0}.
Category:
JDBC
Cause:
The embedded message should contain an explanation of the failure.
Action:
Take appropriate action based on the reported error.
BEA-001058
Could not get JNDI context: {0}
Category:
JDBC
Cause:
Look at the printed exception to see why the call failed.
Action:
Correct the problem and re-run the operation.
BEA-001064
Ignoring the property "enableTwoPhaseCommit" for JDBCTxDataSource "{0}". This property is used only for those drivers that do not natively support XA.
Category:
JDBC
Cause:
The property EnableTwoPhaseCommit was configured to "true" for an XADataSource and will be ignored.
Action:
No action is required.
BEA-001066
Delaying {0,number} seconds before making a {1} pool connection.
Category:
JDBC
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.
BEA-001067
Connection for pool "{0}" refreshed.
Category:
JDBC
Cause:
A connection for the specified pool has been refreshed.
Action:
No action is required.
BEA-001068
Connection for pool "{0}" created.
Category:
JDBC
Cause:
A connection for the specified pool has been created.
Action:
No action is required.
BEA-001072
Connection for XA pool "{0}" created.
Category:
JDBC
Cause:
A connection for the specified XA pool has been created.
Action:
No action is required.
BEA-001073
Connection for XA pool "{0}" refreshed.
Category:
JDBC
Cause:
A connection for the specified XA pool has been refreshed.
Action:
No action is required.
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}
Category:
JDBC
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.
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.
Category:
JDBC
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.
BEA-001083
Multi data source "{0}" was created with {1,number} connection pools for {2}.
Category:
JDBC
Cause:
A multi data source was created with the specified number of connection pools.
Action:
No action is required.
BEA-001084
Multi data source "{0}" will be shutdown
Category:
JDBC
Cause:
The specified multi data source is being shut down.
Action:
No action is required.
BEA-001086
Data source "{0}" with JNDI name "{1}" will be shut down.
Category:
JDBC
Cause:
The specified data source is being shut down.
Action:
No action is required.
BEA-001089
Data source connection pool {0} has been started for application {1}, module {2}.
Category:
JDBC
Cause:
The specified data source connection pool is being started.
Action:
No action is required.
BEA-001099
Data source connection pool "{0}" reset by "{1}".
Category:
JDBC
Cause:
The specified connection pool has been reset.
Action:
No action is required.
BEA-001100
Data source connection pool "{0}" shut down by "{1}".
Category:
JDBC
Cause:
The specified data source connection pool has been shut down, as requested by the application.
Action:
No action is required.
BEA-001101
Data source connection pool "{0}" disabled by "{1}".
Category:
JDBC
Cause:
The specified data source connection pool has been disabled.
Action:
No action is required.
BEA-001102
Data source connection pool "{0}" enabled by "{1}".
Category:
JDBC
Cause:
The specified data source connection pool has been enabled.
Action:
No action is required.
BEA-001104
A globally scoped data source connection pool named ({0}) already exists.
Category:
JDBC
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.
BEA-001105
Referenced global pool ({0}) has the same name as a locally defined data source connection pool or data source ({1}).
Category:
JDBC
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.
BEA-001107
There is a globally defined data source ({0}) with the same JNDI name ({1}) as a locally defined data source.
Category:
JDBC
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.
BEA-001108
A locally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).
Category:
JDBC
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.
BEA-001109
A globally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).
Category:
JDBC
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.
BEA-001110
No test table set up for pool "{0}". Connections will not be tested.
Category:
JDBC
Cause:
TestConnectionsOnReserve, TestConnectionsOnRelease, TestConnectionsOnCreate, TestFrequencySeconds were configured but TestTableName was not configured.
Action:
Configure a valid TestTableName for the data source connection pool.
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.
Category:
JDBC
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.
BEA-001112
Test "{1}" set up for pool "{0}" failed with exception: "{2}".
Category:
JDBC
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.
BEA-001113
Data source connection pool "{0}" shrunk by "{1}".
Category:
JDBC
Cause:
The data source connection pool has been shrunk by the specified amount as requested by the application.
Action:
No action is required.
BEA-001114
Soft shutdown called on data source connection pool "{0}" by "{1}".
Category:
JDBC
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.
BEA-001115
Hard shutdown called on data source connection pool "{0}" by "{1}".
Category:
JDBC
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.
BEA-001116
Disable and freeze users called on data source connection pool "{0}" by "{1}".
Category:
JDBC
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.
BEA-001117
Disable and drop users called on data source connection pool "{0}" by "{1}".
Category:
JDBC
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.
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.
Category:
JDBC
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.
BEA-001119
Unable to delete configuration MBean for pool "{0}": "{1}"
Category:
JDBC
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.
BEA-001120
Created data source named {0} for Pool {1}.
Category:
JDBC
Cause:
There was a user request to create a data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001121
Created TX data source named {0} for Pool {1}.
Category:
JDBC
Cause:
The user requested that the TX data source be created, either implicitly or explicitly.
Action:
No action is required.
BEA-001122
Destroyed TX data source named {0} for Pool {1}.
Category:
JDBC
Cause:
There was a user request to destroy the TX data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001123
Destroyed data source named {0} for Pool {1}.
Category:
JDBC
Cause:
There was a user request to destroy the data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001124
Created Connection Pool named {0}.
Category:
JDBC
Cause:
There was a user request to create the data source connection pool, either implicitly or explicitly.
Action:
No action is required.
BEA-001125
Created multi data source named {0}.
Category:
JDBC
Cause:
There was a user request to create the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001126
Destroyed Connection Pool named {0}.
Category:
JDBC
Cause:
There was a user request to destroy the data source connection pool, either implicitly or explicitly.
Action:
No action is required.
BEA-001127
Destroyed multi data source named {0}.
Category:
JDBC
Cause:
There was a user request to destroy the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001128
Connection for pool "{0}" has been closed.
Category:
JDBC
Cause:
A connection for the specified data source connection pool has been closed.
Action:
No action is required.
BEA-001129
Received exception while creating connection for pool "{1}": {0}.
Category:
JDBC
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.
BEA-001130
Disabled statement caching for connection in pool "{0}" as it is using the WebLogic Type-2 XA driver.
Category:
JDBC
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.
BEA-001131
Received an exception when closing a cached statement for the pool "{0}": {1}.
Category:
JDBC
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.
BEA-001132
Initialized statement cache of size "{1}" for connection in pool "{0}".
Category:
JDBC
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.
BEA-001133
Statement caching is not enabled for connection in specified data source connection pool "{0}".
Category:
JDBC
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.
BEA-001134
Statement caches of connections in the data source connection pool "{0}" have been cleared by "{1}".
Category:
JDBC
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.
BEA-001135
Initializing the JDBC service.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001136
Initialization failed.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001137
Initialization complete.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001138
Resuming the JDBC service.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001139
Resume failed.
Category:
JDBC
Cause:
Check earlier messages that are printed in the log.
Action:
No action is required.
BEA-001140
Resume complete.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001141
Suspending the JDBC service.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001142
Suspend of JDBC service failed.
Category:
JDBC
Cause:
Check earlier messages that are printed in the log.
Action:
No action is required.
BEA-001143
Suspend completed.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001144
Force Suspending the JDBC service.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001145
Force suspend of the JDBC service failed.
Category:
JDBC
Cause:
Check earlier messages that are printed in the log.
Action:
No action is required.
BEA-001146
Force suspend of the JDBC service completed.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001147
Shutting down the JDBC service.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001148
Shutdown of the JDBC service failed.
Category:
JDBC
Cause:
Check earlier messages that are printed in the log.
Action:
No action is required.
BEA-001149
Shutdown of the JDBC service has completed.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001150
Connection pool "{0}" deployment failed with the following error: {1}.
Category:
JDBC
Cause:
The cause should be indicated in the exception message.
Action:
Correct the problem described in the exception message.
BEA-001151
Data source "{0}" deployment failed with the following error: {1}.
Category:
JDBC
Cause:
The cause should be indicated in the exception message.
Action:
Correct the problem described in the exception message.
BEA-001152
Cannot enable statement caching for connection in pool "{0}", because it is using the WebLogic Type-2 XA driver.
Category:
JDBC
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.
BEA-001154
Disabling statement caching for connection in pool "{0}".
Category:
JDBC
Cause:
Statement caching has been disabled for the specified data source connection pool for one or more reasons. 1. The size is explicitly configured to 0. 2. The Oracle replay driver is being used. 3. The Oracle statement cache is enabled.
Action:
No action required.
BEA-001155
The following exception has occurred:
Category:
JDBC
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.
BEA-001156
Stack trace associated with message {0} follows:
Category:
JDBC
Cause:
An error condition was reported.
Action:
No action is required.
BEA-001157
Data source connection pool "{0}" being suspended by user "{1}".
Category:
JDBC
Cause:
The specified data source connection pool is being suspended, as requested by the application.
Action:
No action is required.
BEA-001158
Data source connection pool "{0}" being forcibly suspended by user "{1}".
Category:
JDBC
Cause:
The specified data source connection pool is being forcibly suspended, as requested by the application.
Action:
No action is required.
BEA-001159
Data source connection pool "{0}" is being resumed by user "{1}".
Category:
JDBC
Cause:
The specified data source connection pool is being resumed, as requested by the application.
Action:
No action is required.
BEA-001160
Data source connection pool "{0}" being forcibly destroyed by user "{1}"
Category:
JDBC
Cause:
The specified data source connection pool is being forcibly destroyed, as requested by the application.
Action:
No action is required.
BEA-001161
Data source connection pool "{0}" being destroyed by user "{1}".
Category:
JDBC
Cause:
The specified data source connection pool is being destroyed, as requested by the application.
Action:
No action is required.
BEA-001162
Data source connection pool "{0}" being forcibly shutdown by user "{1}".
Category:
JDBC
Cause:
The specified data source connection pool is being forcibly shutdown, as requested by the application.
Action:
No action is required.
BEA-001163
Data source connection pool "{0}" being shut down by user "{1}".
Category:
JDBC
Cause:
The specified data source connection pool is being shut down, as requested by the application.
Action:
No action is required.
BEA-001164
Unable to initialize connection in pool "{0}". Initialization SQL = "{1}". Received exception: "{2}".
Category:
JDBC
Cause:
The exception message should contain a reason for the failure.
Action:
Take appropriate corrective action.
BEA-001165
Invalid statment cache size "{1}" specified for connection in pool "{0}".
Category:
JDBC
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.
BEA-001166
Activation of application-scoped data source connection pool "{1}":"{2}":"{0}" failed. Received exception: "{3}".
Category:
JDBC
Cause:
The error message should contain the reason for the failure.
Action:
Take appropriate corrective action.
BEA-001167
Deactivation of application-scoped pool "{1}":"{2}":"{0}" failed. Received exception: "{3}".
Category:
JDBC
Cause:
The error message should contain the reason for the failure.
Action:
Take appropriate corrective action.
BEA-001168
Attempt to resume JDBCService when it is already running...Ignoring.
Category:
JDBC
Cause:
The application attempted to resume JDBCService, although the service is already running.
Action:
Take appropriate corrective action.
BEA-001169
Error occured during shutdown of pool "{0}". Received exception: "{1}".
Category:
JDBC
Cause:
The exception should contain the reason for the failure.
Action:
Take appropriate corrective action.
BEA-001170
Unable to initialize JDBC Log. Received exception: "{0}".
Category:
JDBC
Cause:
The message should contain the reason for the failure.
Action:
Take appropriate corrective action.
BEA-001171
Unable to close connection "{0}". Received exception: "{1}".
Category:
JDBC
Cause:
The message should contain the reason for the failure.
Action:
Take suitable action if possible. Otherwise, contact My Oracle Support.
BEA-001172
Error occurred during shutdown of data source "{0}". Received exception: "{1}".
Category:
JDBC
Cause:
The message should contain the reason for the failure.
Action:
Take appropriate corrective action.
BEA-001173
"TestTableName" attribute for pool "{0}" being dynamically changed to "{1}".
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001174
Creating data source named {0}, JNDI Name = {1}.
Category:
JDBC
Cause:
The user requested that the data source be created, either implicitly or explicitly.
Action:
No action is required.
BEA-001175
Creating transactional data source named {0} for Pool {1}.
Category:
JDBC
Cause:
The user requested that the transactional data source be created, either implicitly or explicitly.
Action:
No action is required.
BEA-001176
Creating multi data source named {0}.
Category:
JDBC
Cause:
The user requested that the multi data source be created, either implicitly or explicitly.
Action:
No action is required.
BEA-001177
Creating data source connection pool named {0}, URL = {1}, Properties = {2}.
Category:
JDBC
Cause:
A request was issued to create the data source connection pool, either implicitly or explicitly.
Action:
No action is required.
BEA-001178
Attempt to set query timeout on a statement failed : {0}.
Category:
JDBC
Cause:
The reported message should contain a description of the failure.
Action:
Contact My Oracle Support.
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.
Category:
JDBC
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.
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.
Category:
JDBC
Cause:
The configured callback {1} does not implement the required interface {2}.
Action:
Refer to the WebLogic Server documentation.
BEA-001252
Unable to add notification listener for Config MBean for multi data source {0} failed, got exception: {1}.
Category:
JDBC
Cause:
The reported exception should indicate the cause of the failure.
Action:
Refer to the WebLogic Server documentation.
BEA-001254
Multi data source {0} unable to disable connection pool {1}, got exception: {2}.
Category:
JDBC
Cause:
The reported exception should indicate the cause of the failure.
Action:
Refer to the WebLogic Server documentation.
BEA-001255
Multi data source {0} unable to disable connection pool {1}, got exception: {2}.
Category:
JDBC
Cause:
The reported exception should indicate the cause of the failure.
Action:
Refer to the WebLogic Server documentation.
BEA-001256
Dynamically changing the value of attribute FailoverRequestIfBusy for multi data source {0} from {1} to {2}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001257
Dynamically changing value of attribute HealthCheckFrequencySeconds for multi data source {0} from {1} to {2}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001258
Unable to setup timer for multi data source {0}, got exception: {1}.
Category:
JDBC
Cause:
The reported exception should indicate the cause of the failure.
Action:
Refer to the WebLogic Server documentation.
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.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001260
Multi data source {0} unable to enable connection pool {1}, got exception: {2}.
Category:
JDBC
Cause:
The reported exception should indicate the cause of the failure.
Action:
Refer to the WebLogic Server documentation.
BEA-001261
Multi data source {0} unable to enable connection pool {1}, got exception: {2}.
Category:
JDBC
Cause:
The reported exception should indicate the cause of the failure.
Action:
Refer to the WebLogic Server documentation.
BEA-001262
Registered application callback {1} for multi data source {0} to control multi data source failover behavior.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001500
Creating application-coped multi data source {0}, algorithm type {3} for Application {1}, Module {2}.
Category:
JDBC
Cause:
The user requested that the multi data source be created, either implicitly or explicitly.
Action:
No action is required.
BEA-001501
Creating multi data source {0}, algorithm type {1}.
Category:
JDBC
Cause:
A request was made to create the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001503
Creating application-scoped data source connection pool {0} for Application {1}, Module {2}, URL = {3}, Properties = {4}.
Category:
JDBC
Cause:
A request was made to create the data source connection pool, either implicitly or explicitly.
Action:
No action is required.
BEA-001504
Destroying multi data source {0}, created for Application {1}, Module {2}.
Category:
JDBC
Cause:
A request was made to destroy the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001505
Destroying multi data source Pool {0}.
Category:
JDBC
Cause:
A request was made to destroy the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001507
Destroying data source connection pool {0}, created for Application {1}, Module {2}.
Category:
JDBC
Cause:
A request was made to destroy the data source connection pool, either implicitly or explicitly.
Action:
No action is required.
BEA-001508
Destroying data source connection pool {0}.
Category:
JDBC
Cause:
A request was made to destroy the data source connection pool, either implicitly or explicitly.
Action:
No action is required.
BEA-001510
Creating application-scoped data source {0} for Application {1}, Module {2}, Application Context Name = {3}.
Category:
JDBC
Cause:
A request was made to create the data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001512
Data source {0} has been successfully created.
Category:
JDBC
Cause:
A request was made to create the data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001513
Destroying application-scoped data source {0}, created for Application {1}, Module {2}.
Category:
JDBC
Cause:
A request was made to destroy the data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001514
Destroying data source {0}.
Category:
JDBC
Cause:
A request was made to destroy the data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001515
Data source {0} has been successfully destroyed.
Category:
JDBC
Cause:
A request was made to destroy the data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001516
Data source connection pool "{0}" connected to Database: "{1}", Version: "{2}".
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001517
Data source connection pool "{0}" using Driver: "{1}", Version: "{2}".
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001518
Data source connection pool "{0}" Connection Usage Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001519
Id : "{0}"
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001520
Timestamp : "{0}"
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001521
User : "{0}"
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001522
Data source connection pool "{0}" Connection Wait Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001523
Data source connection pool "{0}" Connection Leak Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001524
Data source connection pool "{0}" Connection Reserve Fail Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001525
Data source connection pool "{0}" Statement Cache Entry Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001526
Unable to load class "{0}", got exception : {1}. Driver Interception feature disabled.
Category:
JDBC
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.
BEA-001527
Application configured class {0} does not implement required interface {1}. Driver Interception feature disabled.
Category:
JDBC
Cause:
The configured class {0} does not implement the required interface {1}.
Action:
Refer to the WebLogic Server documentation.
BEA-001528
Driver Interceptor class {0} loaded.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
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}
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001530
JDBC loggging last resource (LLR) connection pool {0} retrieved {1} record(s) from the database table {2}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001531
Received updated event for unexpected type of bean: {0}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001532
Data source connection pool "{0}" Statement Usage Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001533
Pool Name : "{0}"
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001534
Data source connection pool "{0}" Connection Last Usage Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001535
Data source connection pool "{0}" Connection Multi-threaded Usage Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001536
Creating multi data source named {0}, JNDI Name = {1}.
Category:
JDBC
Cause:
A request was made to create the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001537
Creating application-scoped multi data source {0} for Application {1}, Module {2}, Application Context Name = {3}.
Category:
JDBC
Cause:
A request was made to create the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001538
Created multi data source named {0}.
Category:
JDBC
Cause:
A request was made to create the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001539
Destroying multi data source {0}.
Category:
JDBC
Cause:
A request was made to destroy the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001540
Destroying application-scoped multi data source {0}, created for Application {1}, Module {2}.
Category:
JDBC
Cause:
A request was made to destroy the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001541
Destroyed multi data source named {0}.
Category:
JDBC
Cause:
A request was made to destroy the multi data source, either implicitly or explicitly.
Action:
No action is required.
BEA-001542
JVM DriverManager Login Timeout value set to {0}.
Category:
JDBC
Cause:
The application has specified this behavior to be enabled, via the corresponding configuration setting.
Action:
No action is required.
BEA-001543
Received change event: {1} for unexpected type of bean: {0}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001544
Received add event: {1} for unexpected type of bean: {0}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001545
Received unexpected event: {1} for unexpected type of bean: {0}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001546
Data source connection pool "{0}" is being started by user "{1}".
Category:
JDBC
Cause:
The specified data source connection pool is being started, as requested by the administrator.
Action:
No action is required.
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.
Category:
JDBC
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.
BEA-001548
Empty field value in table reference "{0}" (format [[[catalog.]schema.]table).
Category:
JDBC
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.
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}.
Category:
JDBC
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.
BEA-001550
WebLogic Oracle driver is being used. The driver URL is {0}. WebLogic Server no longer supports the WebLogic Oracle driver.
Category:
JDBC
Cause:
The WebLogic Oracle driver has been deprecated and removed.
Action:
Stop using the WebLogic Oracle driver, use the Oracle Thin driver instead.
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.
Category:
JDBC
Cause:
The deployment order of the multi data source is the same or lower than one of its member data sources.
Action:
Change the deployment order of the standalone multi data source to be greater than each member data source's deployment order.
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.
Category:
JDBC
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.
BEA-001553
Unable to deploy JDBC data source {0}. No credential mapper entry found for password indirection user {1}
Category:
JDBC
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.
BEA-001554
Data source connection pool "{0}" Connection Unwrap Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
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.
Category:
JDBC
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.
BEA-001556
Data source {0} for service {1} registering with ONS daemons using configuration string {2}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001557
Data source {0} for service {1} unregistering with ONS daemons {2}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001558
Data source {0} for service {1} received a service down event for instance {2}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001559
Data source {0} for service {1} received a node down event for node {2}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001560
Data source {0} for service {1} received a service up event for instance {2}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001561
Data source {0} for service {1} received a node up event for node {2}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001562
Data source {0} for service {1} not registering for Fast Application Notification (FAN) events.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001563
ADM_DDL LLR (logging last resource) connection pool {0} did not find its table {1}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001564
JTSLoggableResourceTable.existsForADMDDL about to return: return value = {0}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001565
Logging last resource (LLR) data source {0} using LLR table {1} defined by system property weblogic.llr.table.{0}
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001566
JTSLoggableResourceTable.init for ADMDDL is generating SQL statement(createSQL): {0}.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001567
SQLRuntimeException caught at existsForADMDDL for poolName: {0} ddlName: {1} by: {2}.
Category:
JDBC
Cause:
Look at the printed exception to see why the call failed.
Action:
Correct the problem and run the operation again.
BEA-001568
Data source {0} for service {1} received a service up event
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001569
Data source {0} failed to create runtime MBean for RAC instance {1}. Exception={2}
Category:
JDBC
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.
BEA-001570
Attempt to enable Fast Application Notification (FAN) support for a non-GridLink data source {0}, which is not supported.
Category:
JDBC
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.
BEA-001571
Unable to load the connection labeling callback class "{0}", got exception : {1}.
Category:
JDBC
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.
BEA-001572
Application-configured connection labeling callback class {0} does not implement required interface {1}.
Category:
JDBC
Cause:
The configured class {0} does not implement the required interface {1}.
Action:
Refer to the WebLogic Server documentation.
BEA-001573
Connection labeling callback class {0} loaded.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001574
Unable to load the connection Initialization callback class "{0}", got exception : {1}.
Category:
JDBC
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.
BEA-001575
Application configured connection initialization callback class {0} does not implement required interface {1}.
Category:
JDBC
Cause:
The configured class {0} does not implement the required interface {1}.
Action:
Refer to the WebLogic Server documentation.
BEA-001576
Connection Initialization callback class {0} loaded.
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001580
An exception was thrown from the ConnectionHarvestingCallback: {0}.
Category:
JDBC
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.
BEA-001581
An invalid scope of Application instead of Global is specified for data source {0}, URI = {1}.
Category:
JDBC
Cause:
The configuration is invalid. The specified data source must have a Global scope.
Action:
Correct the configuration for the specified data source.
BEA-001582
oracle.jdbc.DRCPConnectionClass must be specified if and only if a Database Resident Connection Pooling (DRCP) pool is defined.
Category:
JDBC
Cause:
The configuration is invalid.
Action:
Correct the configuration for the specified data source.
BEA-001583
The WebLogic statement cache size is disabled because Oracle statement cache is configured.
Category:
JDBC
Cause:
The WebLogic statement cache is disabled.
Action:
No action is required.
BEA-001584
Data source connection pool "{0}" disabled by multi data source "{1}".
Category:
JDBC
Cause:
The specified data source connection pool has been disabled by a multi data source.
Action:
No action is required.
BEA-001585
Data source connection pool "{0}" re-enabled by multi data source "{1}".
Category:
JDBC
Cause:
The specified data source connection pool has been re-enabled by a multi data source.
Action:
No action is required.
BEA-001586
EndRequest failed: {0}
Category:
JDBC
Cause:
This generally happens because the application failed to complete a local transaction before closing the connection. See the associated message to determine if this is the case.
Action:
The error is ignored if the connection can be cleared. This is, however, an application error to not complete the transaction. Fix the software.
BEA-001587
For LLR RAC DataSource {0} Member of MultiDataSource, test-on-reserve is disabled, and the health of the DataSource cannot be verified.
Category:
JDBC
Cause:
test-on-reserve is disabled in the data source configuration.
Action:
Enable test-on-reserve in the data source configuration. If all member data sources are marked as unhealthy and the WLS Administration Server fails to boot, use WLST to change the configuration.
BEA-001588
Shrinking connection pools due to memory pressure level of {0} exceeding shrink threshold of {1}.
Category:
JDBC
Cause:
There is increased memory consumption in the server.
Action:
No action is required.
BEA-001589
Setting all data source statement cache sizes to {0}% of configured sizes due to memory pressure level of {1}.
Category:
JDBC
Cause:
There is increased memory consumption in the server.
Action:
No action is required.
BEA-001590
Setting {0} statement cache size to {1} ({2}% of configured size {3}).
Category:
JDBC
Cause:
There is increased memory consumption in the server.
Action:
No action is required.
BEA-001591
Configuring data source {0} for partition {1}: {2}.
Category:
JDBC
Cause:
See the message body.
Action:
No action required.
BEA-001592
Forcibly releasing inactive connection "{1}" back into the data source connection pool "{0}".
Category:
JDBC
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 the pool.
Action:
Check the application code for leakages of connection objects, or tune the configured value of the specified connection pool attribute.
BEA-001593
Forcibly releasing harvested connection "{1}" back into the data source connection pool "{0}".
Category:
JDBC
Cause:
The connection was harvested and the application callback did not close the connection. This occurs only when Connection Leak Profiling is enabled.
Action:
Close the connection in the ConnectionHarvestingCallback.cleanup() method.
BEA-001594
Forcibly releasing an already closed connection "{1}" back into the data source connection pool "{0}".
Category:
JDBC
Cause:
When isClosed() is called on the connection, either directly by the application or when accessing a connection, the driver indicates that the connection is already closed. The connection is closed in the WLS data source and returned to the pool. The connection will be replaced in the pool with a new connection.
Action:
No action is required.
BEA-001595
Forcibly releasing connection "{1}" back into the data source connection pool "{0}" because of an initialization failure.
Category:
JDBC
Cause:
A failure occurred on the connection during initialization. The connection will be removed from the pool if it continues to have problems.
Action:
This may indicate a problem with the database. Review other errors in the WLS data source or the database logs.
BEA-001596
Data source connection pool "{0}" Connection Local Transaction Leak Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001597
Data source connection pool "{0}" Closed JDBC Object Usage Data:
Category:
JDBC
Cause:
This is an informational message.
Action:
No action is required.
BEA-001598
Oracle Notification Service (ONS) initialization failed for data source {0}. ONS events will not be processed.
Category:
JDBC
Cause:
The ONS host and pair list is invalid or was unavailable for connection.
Action:
Check the ONS configuration to make sure that it is correct and available.
BEA-001599
When creating Active GridLink (AGL) data source named {0}, the URL should be the long format with a SERVICE_NAME.
Category:
JDBC
Cause:
An incorrect URL is specified for an AGL data source.
Action:
Correct the URL specified for the AGL data source.
BEA-001600
An error occurred while repurposing connection for pool {0}: {1}
Category:
JDBC
Cause:
Refer to the exception message for information about the condition that caused the error.
Action:
Correct the condition that led to the error.
BEA-002001
Received an unknown message type.
Category:
IIOP
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.
BEA-002002
Failed to parse method name {0}.
Category:
IIOP
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.
BEA-002003
Unable to send the message: {0}.
Category:
IIOP
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.
BEA-002005
OutOfMemoryError in adapter: {0}.
Category:
IIOP
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.
BEA-002006
Cannot scavenge idle connections, {0}
Category:
IIOP
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.
BEA-002008
Failed to export {0}. The following exception occurred: {1}.
Category:
IIOP
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.
BEA-002011
Failed to marshal exception {0}: {1}.
Category:
IIOP
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.
BEA-002012
Failed to send exception {0}: {1}.
Category:
IIOP
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.
BEA-002013
Complete failure to send exception {0}: {1}.
Category:
IIOP
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.
BEA-002014
IIOP subsystem enabled.
Category:
IIOP
Cause:
The IIOP subsystem is operational and is listening for incoming IIOP requests.
Action:
No action is required.
BEA-002015
Using javax.rmi.CORBA.UtilClass {0}; The IIOP subsystem requires a WebLogic Server-compatible UtilClass.
Category:
IIOP
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.
BEA-002016
Using javax.rmi.CORBA.PortableRemoteObjectClass {0}, the IIOP subsystem requires a WebLogic Server-compatible PortableRemoteObjectClass.
Category:
IIOP
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.
BEA-002017
LocateRequest is {0}.
Category:
IIOP
Cause:
This is an informational message.
Action:
No action is required.
BEA-002018
Default GIOP version is 1.{0}
Category:
IIOP
Cause:
This is an informational message.
Action:
No action is required.
BEA-002019
LocationForward policy is {0}.
Category:
IIOP
Cause:
This is an informational message.
Action:
No action is required.
BEA-002021
SecurityService registered under {0}.
Category:
IIOP
Cause:
This is an informational message.
Action:
No action is required.
BEA-002022
Could not bind SecurityService {0}.
Category:
IIOP
Cause:
This is an internal JNDI problem.
Action:
Contact My Oracle Support.
BEA-002023
Could not resolve SendingContext RunTime: {0}.
Category:
IIOP
Cause:
An invalid object reference for SendingContext RunTime was provided by the client.
Action:
Contact My Oracle Support.
BEA-002026
Transaction mechanism is {0}.
Category:
IIOP
Cause:
This is an informational message.
Action:
No action is required.
BEA-002027
Complete failure to rewrite exception from {0}: {1}.
Category:
IIOP
Cause:
This error should not occur.
Action:
Contact My Oracle Support.
BEA-002028
An OTS error occurred: {0}, {1}.
Category:
IIOP
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.
BEA-002033
Codeset for {0} data set to {1}, OSF registry entry {2}.
Category:
IIOP
Cause:
This is an informational message.
Action:
No action is required.
BEA-002037
CosNaming Service registered under {0}.
Category:
IIOP
Cause:
This is an informational message.
Action:
No action is required.
BEA-002038
Could not bind the CosNaming Service {0}.
Category:
IIOP
Cause:
This is an internal JNDI problem.
Action:
Contact My Oracle Support.
BEA-002039
Replacer: {0}
Category:
IIOP
Cause:
The replacer did not have enough information to do a proper replacement.
Action:
Contact My Oracle Support.
BEA-002041
Connection attempt was rejected because IIOP is not enabled on this channel.
Category:
IIOP
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.
BEA-002043
Naming exception: {0}
Category:
IIOP
Cause:
A standard exception was generated by the naming implementation.
Action:
No action is required.
BEA-002044
Class not found: class= {0}, repId={1}, codebase={2}
Category:
IIOP
Cause:
Class not found.
Action:
Add the required class to CLASSPATH.
BEA-002605
Adding address: {0} to the licensed client list.
Category:
Server
Cause:
The server accepted a connection from the specified client.
Action:
No action is required.
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}
Category:
Server
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.
BEA-002607
Channel "{2}", listening on {0}:{1,number,0}, was shut down.
Category:
Server
Cause:
The server or channel was shut down.
Action:
No action is required. If this was an unexpected error, contact My Oracle Support.
BEA-002608
The ListenThread failed because of an error: {0}
Category:
Server
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.
BEA-002609
Channel Service initialized.
Category:
Server
Cause:
The Channel subsystem is operational.
Action:
No action is required.
BEA-002610
Dynamic Listener Service initialized.
Category:
Server
Cause:
The dynamic listener subsystem is operational.
Action:
No action is required.
BEA-002611
The hostname "{0}", maps to multiple IP addresses: {1}.
Category:
Server
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.
BEA-002612
Channel "{2}", listening on {0}:{1,number,0}, did not start did not start properly.
Category:
Server
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.
BEA-002613
Channel "{2}" is now listening on {0}:{1,number,0} for protocols {3}.
Category:
Server
Cause:
The server successfully started the listen thread and server socket.
Action:
No action is required.
BEA-002614
Reopening channel "{2}" on {0}:{1,number,0}.
Category:
Server
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.
BEA-002615
After having failed to listen, the server is now listening on channel "{2}" on {0}:{1,number,0}.
Category:
Server
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.
BEA-002616
Failed to listen on channel "{2}" on {0}:{1,number,0}, failure count: {3}, failing for {4} seconds, {5}
Category:
Server
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).
BEA-002617
Attempting to close and reopen the server socket on channel "{2}" on {0}:{1,number,0}.
Category:
Server
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.
BEA-002618
An invalid attempt was made to configure a channel for unconfigured protocol "{0}".
Category:
Server
Cause:
The server configuration specified a channel that uses a protocol that is not enabled.
Action:
Enable the protocol in the server configuration.
BEA-002619
One or more listen ports did not start properly.
Category:
Server
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.
BEA-002620
An invalid attempt was made to configure a channel for server "{0}" on an unknown listen address "{1}".
Category:
Server
Cause:
The server configuration specified a channel that uses a listen address that does not exist.
Action:
Correct the server configuration.
BEA-002621
The connection was rejected because the server license only allows connections from {0} unique IP addresses.
Category:
Server
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.
BEA-002622
The protocol "{0}" is now configured.
Category:
Server
Cause:
The server has loaded a protocol making it available for outbound traffic and configurable for inbound traffic.
Action:
No action is required.
BEA-002623
Connection rejected, the server is in the {0} state. Remote Server contacting us is {1}
Category:
Server
Cause:
Clients tried to connect to the server before it was in the RUNNING state.
Action:
Connect to the server after it has started.
BEA-002624
The administration protocol is "{0}" and is now configured.
Category:
Server
Cause:
The server has loaded the administration protocol making it available for outbound traffic and configurable for inbound traffic.
Action:
No action is required.
BEA-002625
An attempt to configure channel "{0}" failed because of {1}.
Category:
Server
Cause:
The cause is detailed in the accompanying exception.
Action:
Review the exception.
BEA-002626
The protocol "{0}" could not be loaded: {1}
Category:
Server
Cause:
Consult the exception for why the protocol could not be loaded.
Action:
Consult the exception for why the protocol could not be loaded.
BEA-002627
The domain configuration must have at least one administration channel on every server or no administration channels at all.
Category:
Server
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.
BEA-002628
Unable to export RemoteLifeCycleOperations RMI object due to {0}.
Category:
Server
Cause:
The RMI export failed.
Action:
Contact My Oracle Support and provide the logs.
BEA-002630
Accepting connections again.
Category:
Server
Cause:
The server is accepting client connections again after refusing connections as part of server throttling.
Action:
No action is required.
BEA-002631
Max threshold reached for open sockets [total open sockets: {0}, allowed max: {1}]. No more connections allowed.
Category:
Server
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.
BEA-002632
Found jrmp.jar in {0} directory. JRMP service is now enabled.
Category:
Server
Cause:
JRMP is enabled.
Action:
No action is required.
BEA-002633
A port conflict was detected in the server "{4}" configuration. The server "{4}" 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}".
Category:
Server
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.
BEA-002634
The server "{0}" disconnected from this server.
Category:
Server
Cause:
The remote server may have crashed, been shut down normally or been partitioned from the network.
Action:
No action is required.
BEA-002635
The server "{0}" connected to this server.
Category:
Server
Cause:
The remote server may have been booted or a network partition may have been resolved.
Action:
No action is required.
BEA-002636
Unable to update server "{0}" with local channel information.
Category:
Server
Cause:
The remote server may have crashed, been shut down normally or been partitioned from the network.
Action:
No action is required.
BEA-002637
Failed to register a disconnect listener because of {0}
Category:
Server
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.
BEA-002638
{0} was issued remotely from {1}.
Category:
Server
Cause:
Log the host address of the machine that issued the SLC operation.
Action:
No action is required.
BEA-002639
ServerRuntime:{0}
Category:
Server
Cause:
This is an informational message.
Action:
No action is required.
BEA-002640
A request has been received to force a shutdown of the server.
Category:
Server
Cause:
This is an informational message.
Action:
No action is required.
BEA-002641
-DserverType is set to an unrecognized value: {0}. The server will start with all services enabled.
Category:
Server
Cause:
An undefined server type was specified or a typographical error was made.
Action:
See the WebLogic Server documentation for valid values for -DserverType.
BEA-002642
{0} not found. The server will start with all services enabled.
Category:
Server
Cause:
The file was deleted or moved.
Action:
Replace the file from the WebLogic Server installation.
BEA-002643
Attempt to read {0}, failed: {1}
Category:
Server
Cause:
The file has been corrupted or had its permissions changed.
Action:
Replace the file with one from the WebLogic Server installation.
BEA-002644
The JAR file {0} being processed as a potential service plug-in could not be read: {1}
Category:
Server
Cause:
The file may be damaged.
Action:
Check the file, replace & and try again.
BEA-002645
The manifest of the JAR file {0} being processed as a potential service plug-in, could not be read: {1}
Category:
Server
Cause:
The manifest may be corrupted.
Action:
Replace the file and retry.
BEA-002646
Unable to load the service plug-in activator class from {0}: {1}
Category:
Server
Cause:
The plug-in JAR file does not meet the service plug-in requirements.
Action:
Check the contents of the JAR file and retry.
BEA-002647
The service plug-in, {1}, was added from {0}.
Category:
Server
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.
BEA-002648
Could not obtain the relevant ServerRuntimeMBean for server {0}.
Category:
Server
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.
BEA-002649
A port conflict was detected in the server "{3}" 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}".
Category:
Server
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.
BEA-002650
Unable to schedule reconnection to a disconnected server.
Category:
Server
Cause:
The default timer manager has stopped. This is normal during server shutdown.
Action:
None required if the server is in the process of shutting down.
BEA-002651
The process for the server {0} has not completely shut down. This problem should be reported and you may have to kill the process manually.
Category:
Server
Cause:
The process for the server {0} has not completely shut down.
Action:
Kill the process manually.
BEA-002652
The server has no configured channels.
Category:
Server
Cause:
The server has no configured channels.
Action:
Create or define a correct channel configuration.
BEA-002653
The server''s administration channel conflicts with the Administration Server''s channel.
Category:
Server
Cause:
The server's administration channel conflicts with the Administration Server's channel.
Action:
Check the server channel configuration and fix the conflicts.
BEA-002654
Initialization Failed: {0}
Category:
Server
Cause:
Initialization Failed: {0}
Action:
Review the returned error and take appropriate action to fix it.
BEA-002655
Cannot dynamically create new channel with admin protocol on Managed server {0} while it is running.
Category:
Server
Cause:
An attempt was made to create a new channel with admin protocol on Managed server {0} while the server is running.
Action:
Shut down the Managed Server and then try creating the channel again.
BEA-002656
Cannot dynamically enable or disable adminstration port on Managed Server {0} while it is running.
Category:
Server
Cause:
An attempt was made to dynamically enable or disable the adminstration port on Managed Server {0} while the server is running.
Action:
Shut down the Managed Server and then try enabling or disabling the port again.
BEA-002657
Cannot change MaxOpenSockCount enablement dynamically on Managed Server {0} while it is running.
Category:
Server
Cause:
An attempt was made to dynamically change MaxOpenSockCount enablement on Managed Server {0} while the server is running.
Action:
Shut down the Managed Server and then try to change MaxOpenSockCount enablement again.
BEA-002658
No configured outbound channel for {0}.
Category:
Server
Cause:
No configured outbound channel for {0}.
Action:
Review the returned error and take appropriate action to fix it.
BEA-002659
Only local HostID is supported {0}.
Category:
Server
Cause:
Only the local HostID is supported {0}
Action:
Check and fix the error.
BEA-002660
Failed to parse replication ports for server {0} port range: {1}.
Category:
Server
Cause:
Parsing replication ports for server {0} port range: {1} failed.
Action:
Check and fix the error.
BEA-002661
Server failed to bind to any usable port.
Category:
Server
Cause:
The server failed to bind to any usable port.
Action:
See the preceding log message for details.
BEA-002662
Server was unable to verify whether {0} maps to multiple addresses due to {1}.
Category:
Server
Cause:
Review the contents of the included error message for the cause.
Action:
Review the contents of the included error message to determine the appropriate action to take.
BEA-002663
Uncaught Throwable in processSockets {0}.
Category:
Server
Cause:
An unhandled Throwable error occurred while processing sockets.
Action:
Check for other log messages that give more information about the failure.
BEA-002664
Failed to start Admin Channel {0}.
Category:
Server
Cause:
There was an error binding to the Admin Channel port. The port may already be in use.
Action:
Check for a port conflict.
BEA-002665
A partition "{0}" appears to use a server resource; channel: {1}.
Category:
Server
Cause:
The server channel is a shared resource and cannot belong to a partition.
Action:
Check whether this is not a Coherence partition. Otherwise configure either port-offset or explicit-port or uri-prefix.
BEA-002666
RemoteChannelService: {0} {1}
Category:
Server
Cause:
managed server failed to connect AdminServer due to this error.
Action:
Check exception message to resolve connection error.
BEA-002900
Initializing self-tuning thread pool.
Category:
WorkManager
Cause:
The server is starting.
Action:
No action is required.
BEA-002901
Creating Work Manager "{2}" with configured minimum threads constraint "{3}" and maximum threads constraint "{4}" for module "{0}" and application "{1}"
Category:
WorkManager
Cause:
The application is being initialized.
Action:
No action is required.
BEA-002902
Creating execute queue "{0}".
Category:
WorkManager
Cause:
The server is starting.
Action:
No action is required.
BEA-002903
Creating Work Manager from "{1}" WorkManagerMBean for application "{0}"
Category:
WorkManager
Cause:
The application is being initialized.
Action:
No action is required.
BEA-002908
Unable to create runtime MBean for Work Manager {0}. {1}
Category:
WorkManager
Cause:
A fatal error occurred while creating the runtime MBeans.
Action:
Contact My Oracle Support with the server logs.
BEA-002911
Work Manager {0} failed to schedule a request due to {1}
Category:
WorkManager
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.
BEA-002912
Overload Manager {0} rejected request as current length {1} exceeds max capacity of {2}
Category:
WorkManager
Cause:
A request was rejected as the overload capacity was reached or exceeded.
Action:
No action is required.
BEA-002913
Work Manager {0} rejected request as the server is low on memory
Category:
WorkManager
Cause:
A request was rejected as the server was low on memory.
Action:
No action is required.
BEA-002914
Shutdown callback invocation failed with: {0}
Category:
WorkManager
Cause:
There was an internal WebLogic Server error in the application shutdown.
Action:
Report to My Oracle Support with the logs.
BEA-002916
Request belonging to Work Manager {0}, application {1} is rejected as the WorkManager is shutdown.
Category:
WorkManager
Cause:
The request was refused entry because the Work Manager was shutdown.
Action:
No action is required.
BEA-002917
Enqueued request belonging to Work Manager {0}, application {1} is cancelled as the Work Manager is shutdown.
Category:
WorkManager
Cause:
The request was refused because the Work Manager was shutdown.
Action:
No action was required.
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.
Category:
WorkManager
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.
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}
Category:
WorkManager
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.
BEA-002920
An instance of the mSA Work Manager
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002921
The name of the Work Manager
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002922
The number of waiting requests in the queue
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002923
The number of requests that have been processed
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002924
An instance of the MinThreadsConstraint for a particular Work Manager
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002925
Completed request count
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002926
Pending requests that are waiting for an available thread
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002927
Number of requests that are currently executing
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002928
Number of requests executed out of turn to satisfy this constraint
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002929
Number of requests that must be executed to satisfy the constraint
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
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.
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002931
Number of requests that must be executed to satisfy the constraint
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002932
An instance of the MaxThreadsConstraint for a particular Work Manager
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002933
Number of requests that are currently executing
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002934
Number of requests that are denied a thread for execution because the constraint is exceeded
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-002935
request-class-name reference within ContextCase element for entry {0} with value: {1} ;cannot be resolved for Work Manager.
Category:
WorkManager
Cause:
The request class specified in the context case is not defined.
Action:
Ensure that a request class with the same name as was specified in the context case request-class-name is configured.
BEA-002936
maximum thread constraint {0} is reached
Category:
WorkManager
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.
BEA-002937
The maximum thread constraint {0} is no longer reached.
Category:
WorkManager
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.
BEA-002938
Global work manager "{0}" created with customized configuration
Category:
WorkManager
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
BEA-002939
The maximum thread constraint {0} has been reached {1} times for the last {2} seconds.
Category:
WorkManager
Cause:
The number of threads assigned to this work manager has reached the configured value for the maximum threads constraint.
Action:
No action is required.
BEA-002940
Shutting down work manager "{0}" according to the configured work manager shutdown trigger.
Category:
WorkManager
Cause:
A work manager is being shut down because the number of stuck threads has reached the configured value in a work manager shutdown trigger.
Action:
Monitor the stuck threads to determine the reason why the requests have been taking a long time to process. If resumeWhenUnstuck is true, the work manager will be resumed when there are no more stuck threads for the work manager.
BEA-002941
Removed {0} threads from the standby thread pool.
Category:
WorkManager
Cause:
The server is reducing the number of threads in the standby thread pool either because they are not needed or to reduce overall resource usages of the server.
Action:
No action is required as the server auto tunes.
BEA-002942
CMM memory level becomes {0}. Setting standby thread pool size to {1}.
Category:
WorkManager
Cause:
CMM memory level has changed. Standby thread pool size may be adjusted accordingly.
Action:
No action is required.
BEA-002943
Maximum Threads Constraint "{0}" queue for work manager "{1}" reached maximum capacity of {2} elements. Consider setting a larger queue size for the maximum threads constraint.
Category:
WorkManager
Cause:
The max threads constraint queue is full.
Action:
Consider setting a larger queue size for the max threads constraint.
BEA-002944
Maximum Threads Constraint "{0}" queue for work manager "{1}" reached maximum capacity of {2} elements {3} times for the last {4} seconds. Consider setting a larger queue size for the maximum threads constraint.
Category:
WorkManager
Cause:
The max threads constraint queue is full.
Action:
Consider setting a larger queue size for the max threads constraint.
BEA-002945
Unable to perform ThreadLocal cleanup for self-tuning thread pool threads due to error: {0}
Category:
WorkManager
Cause:
Please see the error in the message for additional information.
Action:
Check the error in the message for details of the error and take approriate action if possible. It is also possible that ThreadLocal cleanup is not supported on your platform.
BEA-002946
Partition configuration for partition {0} is not available while loading work manager components for the partition.
Category:
WorkManager
Cause:
This message can be ignored if partition configuration is available at a later time. This could happen if the partition has just been created or if it has just been migrated from another server.
Action:
Check whether there is a log message WLS-002947 in the log file for the same partition. If not, verify if the partition is being created properly.
BEA-002947
Partition configuration for partition {0} is available. Work manager components for the partition have been loaded successfully.
Category:
WorkManager
Cause:
Partition configuration was not available earlier when trying to load work manager components for the partition. This message indicates that the partition configuration is now available and the work manager components have been loaded successfully.
Action:
No action is required. Earlier warning messages WLS-002946 and WLS-002948 for the same partition can now be disregarded.
BEA-002948
Error occurred while loading work manager components for partition {0}: {1}
Category:
WorkManager
Cause:
Please see the error in the message for additional information.
Action:
Check the error in the message for details of the error and take approriate action if possible.
BEA-002949
Work manager components configured for partition {0} is being accessed, but the partition is not deployed to this server.
Category:
WorkManager
Cause:
This can occur when there are possible inconsistencies in partition or resource group target configuration.
Action:
Check the partition or resource group targets configuration.
BEA-002950
Partition "{0}" is configured with a minimum threads constraint cap of {1}, which is less than the sum of all configured minimum threads constraints in the partition.
Category:
WorkManager
Cause:
The WebLogic administrator has set a cap on the number of threads that will be allocated to this partition for satifying its minimum threads constraints. The configured value is less than the sum of all configured minimum threads constraints configured in this partition.
Action:
Request a higher partition minimum threads constraint cap setting from the WebLogic administrator.
BEA-002951
An error occurred while trying to create a thread under the global context due to error: {0}. A thread wass created under the context of partition "{1}" instead.
Category:
WorkManager
Cause:
Check the error in the message for additional information about what might have caused the error.
Action:
Resource Consumption Management may not work properly with this error. Contact My Oracle Support and provide them with the logs.
BEA-002952
Partition maximum threads constraint for partition {0} has been reached.
Category:
WorkManager
Cause:
The number of threads assigned to this partition has reached the configured partition maximum threads constraint value.
Action:
No action is required.
BEA-002953
The partition maximum threads constraint for partition {0} has been reached {1} times in the last {2} seconds.
Category:
WorkManager
Cause:
The number of threads assigned to this partition has reached the configured partition maximum threads constraint value.
Action:
No action is required.
BEA-002954
The Partition Maximum Threads Constraint "{0}" queue reached maximum capacity of {2} elements when trying to add a work entry for work manager "{1}" to the queue. Consider setting a larger queue size for the partition maximum threads constraint.
Category:
WorkManager
Cause:
The partition maximum threads constraint queue is full.
Action:
Consider setting a larger queue size for the partition max threads constraint.
BEA-002955
The Partition Maximum Threads Constraint "{0}" reached maximum capacity of {2} elements {3} times in the last {4} seconds when trying to add work entries for work managers including "{1}". Consider setting a larger queue size for the partition maximum threads constraint.
Category:
WorkManager
Cause:
The partition maximum threads constraint queue is full.
Action:
Consider setting a larger queue size for the partition maximum threads constraint.
BEA-002956
The thread count tuning feature in the self-tuning thread pool has stopped due to {0}.
Category:
WorkManager
Cause:
The self-tuning timer task has to stop due to an unrecoverable error.
Action:
The self-tuning thread pool would continue to process work request, althought without further adjustment of the thread pool size. Consider restarting the server if the thread pool size can no longer handle the work load of the server.
BEA-002957
Fair share request class "{0}" is configured with a fair share value of {1}, which is higher than the recommended maximum value of 100.
Category:
WorkManager
Cause:
The configured fair share value is higher than the recommended maximum value of 100.
Action:
Consider configuring a fair share value between 1 and 100 for the fair share request class.
BEA-002958
WorkManager state dump has been enabled.
Category:
WorkManager
Cause:
WorkManager state dump is enabled.
Action:
No action is required.
BEA-002959
Self-tuning thread pool contains {0} running threads, {1} idle threads, and {2} standby threads
Category:
WorkManager
Cause:
This is an informational message.
Action:
No action is required.
BEA-003000
Could not send cache multicast message for key "{0}", {1}.
Category:
Cache
Cause:
UThis error is usually caused by some communication failure.
Action:
Check the exception message for details.
BEA-003001
Leasing failure: {0}
Category:
Cache
Cause:
This error is usually caused by some communication failure.
Action:
Check the exception message for details.
BEA-003002
Replication failure: {0}
Category:
Cache
Cause:
This error is usually caused by some communication failure.
Action:
Check the exception message for details.
BEA-003004
Unexpected failure {0}
Category:
Cache
Cause:
This is a general purpose warning message.
Action:
No action is required. The cache will try to adjust to the failure.
BEA-003005
CacheFilter not caching the response for uri: {0} reason: {1}
Category:
Cache
Cause:
CacheFilter does not cache responses unless the status is 200.
Action:
Check the message for information on how to fix the problem.
BEA-003090
Could not send cache multicast message for key "{0}", {1}.
Category:
LLD
Cause:
This error is usually caused by some communication failure.
Action:
Check the exception message for details.
BEA-003101
Modified non-dynamic {0} property on the Administration Server.
Category:
Cluster
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.
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.
Category:
Cluster
Cause:
The execution of the post deactivation script failed.
Action:
Fix the post deactivation script and migrate the MigratableTarget manually.
BEA-003103
{0} failed to release its lease because of {1}. This may affect its automatic migration behavior.
Category:
Cluster
Cause:
An exception occurred: {1}.
Action:
If a database is being used for leasing, ensure that it is available.
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.
Category:
Cluster
Cause:
An exception occurred: {2}.
Action:
Ensure that the network is working properly.
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.
Category:
Cluster
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.
BEA-003106
An unexpected exception occured during replication: {0}. Future session updates should replicate as expected.
Category:
Cluster
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 and provide them with the stack trace for further analysis.
BEA-003107
Lost {0} unicast message(s).
Category:
Cluster
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.
BEA-003108
Unicast receive error : {0}
Category:
Cluster
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.
BEA-003109
Cluster {0} uses a database as the migration basis but no data source for migration has been configured.
Category:
Cluster
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 exists and is set for database migration basis.
BEA-003110
Connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.
Category:
Cluster
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.
BEA-003111
No channel exists for replication calls for cluster {0}.
Category:
Cluster
Cause:
No channel exists for replication calls for cluster {0}.
Action:
Configure the channels for replication calls.
BEA-003112
Channels "{0}" configured for replication traffic.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003113
Using one-way RMI for replication
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003114
Ignoring one-way RMI calls for replication because multiple replication channels are not present.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003115
Failed to synchronize a secondary session due to missing updates.
Category:
Cluster
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 restart).
BEA-003116
Starting Member Death Detector.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003117
Starting Member Death Detector Heartbeat Receiver.
Category:
Cluster
Cause:
None.
Action:
None.
BEA-003118
WLS Server "{0}" does not have an associated machine configured. Member Death Detector will not be enabled for this server.
Category:
Cluster
Cause:
No associated machine configured with the server.
Action:
Please associate a machine with this server.
BEA-003119
The singleton service {0} is now registered on this server but will not be activated because this server is not part of a cluster.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003120
Hostname {0} failed to resolve during cluster initialization.
Category:
Cluster
Cause:
A name service such as DNS is unavailable or unstable.
Action:
Check the name service configuration or name service availability.
BEA-003121
Unicast cluster may not function correctly as the listen address of server {0} is not specified.
Category:
Cluster
Cause:
The listen address of the Managed Server was not specified.
Action:
Set the listen address of the Managed Servers.
BEA-003122
{0} : A cluster that has migratable servers could not create/execute an SQL statement when validating the database connection. The cluster is misconfigured. Check the leasing table on the database and connection configuration.
Category:
Cluster
Cause:
The cluster is not configured correctly.
Action:
Check the leasing table in the database and connection configuration.
BEA-003123
Singleton Monitor has detected that the singleton service {0} is in a failed state.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003124
Singleton Monitor has detected that the singleton service {0} has an expired status.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003125
Singleton Monitor has detected that the singleton service {0} has no lease.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003126
{0} will attempt to auto-migrate.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003127
{0} will attempt to restart in place on server {1}.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003128
{0} has been completed to restart in place.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003129
{0} will attempt to auto-migrate from {1} to {2}.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003130
{0} successfully activated on server {1}.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003131
The singleton service {0} has failed with failure state : {1}. Summary of reason Code : {2}
Category:
Cluster
Cause:
A critical service has failed, most likely due to an exception.
Action:
Depending on the cause, corrective action must be taken to resolve the failure. If the problem still persists, contact My Oracle Support for further analysis.
BEA-003132
An EJB is configured to use the clustered EJB timer implementation but the data-source-for-job-scheduler cluster attribute is not configured.
Category:
Cluster
Cause:
While deploying an EJB, the EJB container determined that 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.
BEA-003133
An EJB is configured to use the clustered EJB timer implementation but the data-source-for-job-scheduler attribute is not configured in partition "{0}".
Category:
Cluster
Cause:
While deploying this EJB, the EJB container determined that the data-source-for-job-scheduler partition 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 partition.
BEA-003134
An EJB is configured to use the clustered EJB Timer implementation but this server is not part of a cluster.
Category:
Cluster
Cause:
You cannot 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.
BEA-003135
Job Scheduler service was not started for this partition because the data source for the job scheduler is not configured for this partition.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required unless the job scheduler service is needed in this partition, in which case you can configure a data source for the job scheduler for this partition and restart the partition.
BEA-003136
Job scheduler service was not started for this partition because this server does not belong to a cluster.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003137
Server in cluster {0} was unable to bind MulticastSocket to address {0}. Will bind to IP_ANY instead.
Category:
Cluster
Cause:
This was caused by an invalid multicast IP address.
Action:
Configure the cluster to use a valid multicast IPv4 or IPv6 address.
BEA-003138
Synchronized {1} from server {0}.
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003139
AssertionError is raised on installing ServiceOffer from remote node : {0}
Category:
Cluster
Cause:
Internal data structure is corrupted.
Action:
If there is no other problems, no action is required. Corrupted offer will be simply ignored.
BEA-003140
Partition {0} from server {1} {2} for cluster view {3}
Category:
Cluster
Cause:
The partition has been started/stopped on a particular server in the cluster
Action:
No action is required
BEA-003141
Thread {0} attempted a re-entrant call to the WLS Replication Service while actively replicating session state to a secondary server.
Category:
Cluster
Cause:
During replication of the application''s session state, an attempt was made by the same thread to access the same session instance that is actively being serialized..
Action:
None
BEA-003142
An exception occurred while ensuring replica {0} replicated: {1}
Category:
Cluster
Cause:
An exception occurred while ensuring replica {0} replicated: {1}
Action:
Please check the exception for the exact error message.
BEA-003143
An exception occurred while locally cleaning up replica {0} for replication key {1}: {2}
Category:
Cluster
Cause:
An exception occurred while locally cleaning up replica {0} for replication key {1}: {2}
Action:
Please check the exception for the exact error message.
BEA-003144
All session objects should be serializable to replicate. Check the objects in the session. Failed to replicate a non-serializable object in context {0}.
Category:
Cluster
Cause:
Objects in the session are not serializable or externalizable.
Action:
Ensure that all user-defined objects in the HTTP session are serializable.
BEA-003145
An exception occurred while starting TimerMaster for {0}: {1}
Category:
Cluster
Cause:
An exception occurred while starting TimerMaster service for job scheduler for {0}. The exception is {1}
Action:
Please check the exception for the cause and take appropriate action.
BEA-003146
Unicast cluster may not function correctly as the listen address of server {0} is not specified.
Category:
Cluster
Cause:
The listen address of the Managed Server was not specified.
Action:
Set the listen address of the Managed Servers.
BEA-003147
Detected Exception occurred when calling {0} method. Timer info: {1}
Category:
Cluster
Cause:
An exception occurred: {2}.
Action:
See transaction error and check the root cause
BEA-003148
The Clustered Timer: {0} has failed to successfully time out in {1} consecutive attempts. Scheduler will automatically delay the timeout for {2} seconds. Timer info: {3}
Category:
Cluster
Cause:
This is an informational message.
Action:
No action is required.
BEA-003149
Failed to fire retry timer because of Leasing problem and reset retry state. Timer info: {0}
Category:
Cluster
Cause:
An exception occurred: {1}.
Action:
If the problem persists, contact My Oracle Support and provide them with the stack trace for further analysis.
BEA-003150
Server "{0}" has acquired the role of Singleton Master for the cluster.
Category:
Cluster
Cause:
TBD
Action:
TBD
BEA-003151
Server "{0}" is no longer the Singleton Master for the cluster.
Category:
Cluster
Cause:
TBD
Action:
TBD
BEA-003501
The migration of server {0} from machine {1} has failed. No suitable candidate machines could be found.
Category:
Cluster
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.
BEA-003502
Beginning the migration of server {0} from machine {1} to machine {2}
Category:
Cluster
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}.
BEA-003503
The migration of server {0} from machine {1} to machine {2} has succeeded.
Category:
Cluster
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.
BEA-003504
The migration of server {0} from machine {1} to machine {2} has failed, because machine {2} is not reachable.
Category:
Cluster
Cause:
Machine {2} was not reachable. A new machine for server {0} will be chosen.
Action:
No action is required.
BEA-003800
Could not parse the user random seed property whose value is {0}. Using seed {1}
Category:
WebLogicServer
Cause:
The seed used to randomize startup services was not parseable. The seed is given to the server with the com.oracle.weblogic.debug.RandomizeServerServices.seed system property.
Action:
Check the value of the com.oracle.weblogic.debug.RandomizeServerServices.seed property given to the server, and make sure it can be parsed into a valid long value
BEA-003801
Could not read server service randomizer file {0}. The seed used in this run is randomSeed
Category:
WebLogicServer
Cause:
The seed file used to randomize startup services was not parseable. The name of the seed file is given to the server with the com.oracle.weblogic.debug.RandomizeServerServices.filename system property.
Action:
Check the value of the com.oracle.weblogic.debug.RandomizeServerServices.filename property given to the server, and make sure it points to a file that contains one line that can be parsed into a long which should be used for the random seed
BEA-003802
The order in which the server services are started has been randomized with seed {0}{1}
Category:
WebLogicServer
Cause:
The server service randomizer was used to randomize server services with the given seed
Action:
No action necessary
BEA-003803
Could not write server service randomizer file {0}. The seed used in this run is {1}
Category:
WebLogicServer
Cause:
When using the service randomizer the system attempted to write the seed used to a file for later use, but the system could not write the file
Action:
Ensure that the randomizer file is in a directory where the system can write and that there is enough disk space in that file system
BEA-003804
The randomizer file with location {0} is not readable. The seed used in this run is {1}
Category:
WebLogicServer
Cause:
The randomizer file at the given location is not readable
Action:
Ensure that the randomizer file is readable by the system
BEA-003805
The data found in randomizer file with location {0} is not parseable into a long. The seed used in this run is {1}
Category:
WebLogicServer
Cause:
The randomizer file at the given location has bad data in it
Action:
Ensure that the randomizer file has one line that can be parsed into a long value
BEA-003806
There was an error redirecting {0}. The stream will not be redirected.
Category:
WebLogicServer
Cause:
This is caused due to an I/O error in initializing the new stream.
Action:
Correct the error based on the exception messages reported and restart the server.
BEA-004501
Bootstrap request was rejected from server {0} of cluster {1}.
Category:
ConsensusLeasing
Cause:
Server configuration parameters, such as listen-address and port, are duplicated between servers in different clusters.
Action:
Change server configuration parameters of the servers in the domain.
BEA-004502
Exception occurred during unicast connection bootstrapping: {0}
Category:
ConsensusLeasing
Cause:
See displayed exception.
Action:
Report this error to My Oracle Support.
BEA-010000
Exception occurred during ejbActivate: {0}
Category:
EJB
Cause:
An error occurred while calling ejbActivate() on the bean.
Action:
Check your implementation of the ejbActivate method.
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.
Category:
EJB
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.
BEA-010002
An error occurred while undeploying: {0}.
Category:
EJB
Cause:
An error occurred while undeploying.
Action:
Please check the exception for the exact error message.
BEA-010003
Exception occurred while loading _WL_TIMESTAMP FILE.
Category:
EJB
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.
BEA-010006
Error occurred while saving ejb deployment timestamps. {0}
Category:
EJB
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.
BEA-010007
License validation passed for {0}.
Category:
EJB
Cause:
See the message body.
Action:
No action required.
BEA-010008
EJB Deploying file: {0}.
Category:
EJB
Cause:
See the message body.
Action:
No action required.
BEA-010009
EJB deployed EJB with JNDI name {0}.
Category:
EJB
Cause:
See the message body.
Action:
No action required.
BEA-010011
Exception looking up current transaction: {0}
Category:
EJB
Cause:
See the message body.
Action:
No action required.
BEA-010012
Exception looking up current transaction: {0}
Category:
EJB
Cause:
See the message body.
Action:
No action required.
BEA-010014
Error occurred while attempting to rollback transaction: {0}
Category:
EJB
Cause:
There was an error when rolling back the transaction.
Action:
Please check the exception for the exact error message.
BEA-010015
Error occurred while marking transaction for rollback: {0}.
Category:
EJB
Cause:
The container was unable to mark the transaction for rollback.
Action:
Please check the exception for exact error message.
BEA-010016
Exception occurred while marking transaction for rollback: {0}.
Category:
EJB
Cause:
The container was unable to mark the transaction for rollback.
Action:
Please check the exception for the exact error message.
BEA-010017
Exception occurred during rollback of transaction {0}: {1}.
Category:
EJB
Cause:
The container was unable to rollback the transaction.
Action:
Please check the exception for the exact error message.
BEA-010018
Error occurred while resuming caller transaction: {0}
Category:
EJB
Cause:
The container was unable to resume the transaction.
Action:
Please check the exception for the exact error message.
BEA-010019
Running in a cluster, but DNS name of cluster is not set. This may prevent EJB handles from operating properly.
Category:
EJB
Cause:
The DNS name of the cluster is not set.
Action:
Set the DNS cluster name.
BEA-010020
EJB-20 - MessageDriven - Could not start the JMS connection: {0}
Category:
EJB
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.
BEA-010022
Error occurred in ejbPassivate: {0}.
Category:
EJB
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.
BEA-010024
Error occurred during passivation: {0}
Category:
EJB
Cause:
The container was unable to passivate the bean.
Action:
Check the exception for the exact error message.
BEA-010025
Exception occurred during rollback of transaction {0}: {1}
Category:
EJB
Cause:
An error occurred when rolling back the transaction.
Action:
Check the exception for the exact error message.
BEA-010026
Exception occurred during commit of transaction {0}: {1}.
Category:
EJB
Cause:
An error occurred when committing the transaction.
Action:
Check the exception for the exact error message.
BEA-010029
Exception occurred during commit of transaction {0}: {1}.
Category:
EJB
Cause:
An error occurred while committing the transaction.
Action:
Check the exception for the exact error message.
BEA-010030
Ignoring exception that occurred when rolling back a transaction during undeployment of {0}.
Category:
EJB
Cause:
An error occurred while undeploying the bean.
Action:
Check the exception for the exact error message.
BEA-010031
EJB exception in method: {0}: {1}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010032
Exception during ejbActivate(): {0}
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010033
Exception from ejbLoad: {0}
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010034
Exception from ejbStore: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010036
Exception from ejbStore: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010038
Exception from __WL_superEjbLoad: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010039
Exception in ejbStore: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010040
Exception in ejbStore: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010043
Exception in ejbActivate: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010044
Exception trying to resume transaction: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010045
Exception in afterBegin: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010046
Exception in beforeCompletion: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010047
Exception during setRollbackOnly: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010048
Exception in afterCompletion: {0}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010049
EJB exception in method: {0}: {1}.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010050
A stateless session bean with bean-managed transactions must commit or roll back a transaction before the business method completes.
Category:
EJB
Cause:
See the message body.
Action:
Check the exception for the exact error message.
BEA-010051
EJB exception occurred during invocation from home: {0} generated exception: {1}
Category:
EJB
Cause:
See the message body.
Action:
No action required.
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}
Category:
EJB
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.
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.
Category:
EJB
Cause:
{1} is in the classpath.
Action:
Remove this class from the classpath. It should only be in the ejb-jar.
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}.
Category:
EJB
Cause:
{1} is missing from the JAR file.
Action:
Please add the missing file to the JAR file.
BEA-010057
Could not find a license for EJB 3.0. Please contact Oracle to get a license.
Category:
EJB
Cause:
Unable to get license for EJB 3.0.
Action:
Contact Oracle to get a license.
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.
Category:
EJB
Cause:
See the message body.
Action:
No action required.
BEA-010059
An error occurred while attempting to invalidate the target Read-Only Entity EJB: {0}. The error was: {1}
Category:
EJB
Cause:
The invalidation of read-only beans failed.
Action:
Check the message for the cause.
BEA-010060
The Message-Driven EJB {0} has connected or reconnected to the JMS destination {1}.
Category:
EJB
Cause:
The JMS connection has been re-established.
Action:
No action is required.
BEA-010061
The Message-Driven EJB {0} is unable to connect to the JMS destination {1}. The Error was: {2}
Category:
EJB
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.
BEA-010065
MessageDrivenBean threw an Exception in onMessage(). The exception is: {0}.
Category:
EJB
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.
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}
Category:
EJB
Cause:
See the message body.
Action:
No action required.
BEA-010067
Exception during ejbRemove: {0}
Category:
EJB
Cause:
See the message body.
Action:
No action required.
BEA-010071
Error occurred while performing Pop of Caller Principal: {0}
Category:
EJB
Cause:
This is a possible internal container error.
Action:
Check the security settings related to the run-as roles and principals setting.
BEA-010072
Error occurred while starting EJB module {0}. Exception is: {1}
Category:
EJB
Cause:
The container was unable to start the EJB module.
Action:
Check the exception for the exact error message.
BEA-010073
Unable to add the {0} interface "{1}" and any dependent classes to the client-jar since it was loaded from the classpath.
Category:
EJB
Cause:
EJB interface and other dependent classes exist in the system classpath.
Action:
Please remove the classes from the system classpath.
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.
Category:
EJB
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.
BEA-010075
Skipping creation of the client-jar since no EJBs with a remote client view are contained in the JAR file.
Category:
EJB
Cause:
See the message body.
Action:
No action required.
BEA-010076
Client-jar {0} created.
Category:
EJB
Cause:
See the message body.
Action:
No action required.
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}
Category:
EJB
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.
BEA-010080
An error occurred while attempting to process a message inside a Message-Driven Bean: {0} Exception is : {1}
Category:
EJB
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.
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.
Category:
EJB
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.
BEA-010082
Failed to undeploy security role for resource {0}, while undeploying EJB.
Category:
EJB
Cause:
Unable to remove the role from the security layer.
Action:
Check the exception for the exact error message.
BEA-010083
Failed to undeploy security policy for resource {0}, while undeploying EJB.
Category:
EJB
Cause:
The policy could not be removed from the security layer.
Action:
Check the exception for the exact error message.
BEA-010084
The Message-Driven Beans are being suspended. This may take a minute or two.
Category:
EJB
Cause:
The server is being suspended or shut down.
Action:
No action is required.
BEA-010085
The Message-Driven Beans have all been suspended.
Category:
EJB
Cause:
The server is being suspended or shut down.
Action:
No action is required.
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.
Category:
EJB
Cause:
The beans were started after having been undeployed.
Action:
No action is required.
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}.
Category:
EJB
Cause:
See the message body.
Action:
No action is required.
BEA-010088
Could not find a license for in-memory replication of the EJB. This feature is disabled.
Category:
EJB
Cause:
See the message body.
Action:
No action is required.
BEA-010089
Failed to create copy of bean {0} with error: {1}.
Category:
EJB
Cause:
The server was unable to create the secondary server.
Action:
Check the exception for the exact error message.
BEA-010090
Failed to update secondary copy with: {0}
Category:
EJB
Cause:
The server was unable to update the secondary.
Action:
Check the exception for the exact error message.
BEA-010091
Failure during stateful session bean replication: {0}
Category:
EJB
Cause:
The container was unable to replicate the stateful session bean.
Action:
Check the exception for the exact error message.
BEA-010092
Failure while updating secondary server during replication of {0}. The error was: {1}
Category:
EJB
Cause:
The server was unable to update the secondary server.
Action:
Check the exception for the exact error message.
BEA-010094
Failed to update the secondary copy of a stateful session bean from home {0}.
Category:
EJB
Cause:
The server was unable to update the secondary server.
Action:
Check the exception for the exact error message.
BEA-010096
The Message-Driven EJB {0} is unable to connect to the JMS destination or bind to JCA resource adapter {1}. The connection 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.
Category:
EJB
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.
BEA-010097
Exception occurred during the invocation of EJB {0} with primary key {1}.
Category:
EJB
Cause:
The bean generated a system exception.
Action:
Check the exception for the exact error message.
BEA-010098
The database type {0} mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver {1}.
Category:
EJB
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.
BEA-010099
WARNING(S) from EJB QL Compiler. {0}
Category:
EJB
Cause:
The compilation of EJB-QL succeeded. These are some non-fatal warnings.
Action:
Check the message for the exact warnings.
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.
Category:
EJB
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.
BEA-010102
Error encountered while attempting to create default DBMS table {0}. Error text: {1}
Category:
EJB
Cause:
An error was encountered while attempting to create the default DBMS table.
Action:
Take appropriate action based on the logged error message.
BEA-010124
Method SecurityHelper.{0} returned a NULL principal. The CallerPrincipal stack has been corrupted.
Category:
EJB
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.
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.
Category:
EJB
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.
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.
Category:
EJB
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.
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.
Category:
EJB
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.
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.
Category:
EJB
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.
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.
Category:
EJB
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.
BEA-010139
Bean with primary key {0} already exists.
Category:
EJB
Cause:
A bean with the indicated primary key value already exists.
Action:
Do not use a non-unique value as a primary key.
BEA-010141
Creation of Many-To-Many relationship for primary key: {0} and {1} effected {2} rows in {3}, instead of just 1.
Category:
EJB
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.
BEA-010144
The setXXX method for a primary key field may only be called during ejbCreate.
Category:
EJB
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.
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.
Category:
EJB
Cause:
The cmp-field is read-only.
Action:
Remove the setXXX method call if cmp-filed is also used as cmr-field.
BEA-010146
The setXXX method for a cmr-field that is mapped to a primary key may not be called.
Category:
EJB
Cause:
The cmr-field is read-only.
Action:
Remove the setXXX method call if it is cmr-field mapped to a primary key.
BEA-010147
The setXXX method for a cmr-field may not be called during ejbCreate. The setXXX method should be called during ejbPostCreate instead.
Category:
EJB
Cause:
The setXXX method should be called during ejbPostCreate instead.
Action:
Move the setXXX method call for a cmr-field to ejbPostCreate.
BEA-010148
In EJB {0}, the primary key field {1} was not set during ejbCreate.
Category:
EJB
Cause:
All primary key fields must be initialized during ejbCreate.
Action:
Be sure to initialize the primary key field during ejbCreate.
BEA-010149
According to the EJB 2.0 specification, a value of "null" may not be assigned to a collection valued cmr-field.
Category:
EJB
Cause:
This violates the EJB 2.0 specification.
Action:
Avoid using a null argument for a collection valued cmr-field.
BEA-010152
Illegal value for concurrency-strategy. Value was {0}, but must be one of ReadOnly, Exclusive, Database, or Optimistic.
Category:
EJB
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
BEA-010153
Only instances of beans with a remote client view can invoke getEJBObject().
Category:
EJB
Cause:
See the error message body.
Action:
Remove the getEJBObject() method call from the local client.
BEA-010154
Only instances of beans with a local client view can invoke getEJBLocalObject().
Category:
EJB
Cause:
See the error message body.
Action:
Remove the getEJBLocalObject() method call from remote client.
BEA-010155
Only instances of beans with container-managed transaction demarcation can use getRollbackOnly().
Category:
EJB
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.
BEA-010156
Illegal attempt to call EJBContext.getRollbackOnly() from an EJB that was not participating in a transaction
Category:
EJB
Cause:
See the error message body.
Action:
Make sure to begin the transaction before calling the getRollbackOnly() method.
BEA-010157
Only instances of beans with container-managed transaction demarcation can use setRollbackOnly().
Category:
EJB
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.
BEA-010158
Illegal attempt to call EJBContext.setRollbackOnly() from an EJB that was not participating in a transaction
Category:
EJB
Cause:
See the error message body.
Action:
Begin the transaction before calling the setRollbackOnly() method.
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.
Category:
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.
BEA-010160
Security violation: User {0} has insufficient permission to access EJB {1}.
Category:
EJB
Cause:
The specified user has insufficient permission to access the EJB.
Action:
Grant sufficient permissions to the user to enable to access the EJBResource.
BEA-010166
Error occurred while starting transaction: {0}.
Category:
EJB
Cause:
An exception occurred while starting the Message-Drive Bean transaction.
Action:
Take appropriate action based on the text of the exception message.
BEA-010167
Message-Driven Beans are not allowed to call {0}.
Category:
EJB
Cause:
The method is unavailable for MDBs.
Action:
Remove the method call from the MDBs.
BEA-010168
Method {0} has been declared in an assembly-descriptor exclude-list and cannot be executed.
Category:
EJB
Cause:
The specified method is declared in the exclude-list.
Action:
Remove the method name from the exclude-list or remove the method call.
BEA-010173
env-entry for type java.lang.Character had length = 0.
Category:
EJB
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.
BEA-010188
Error encountered while attempting to drop Default DBMS Table {0}.
Category:
EJB
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.
BEA-010189
Error encountered while attempting to alter Default DBMS Table: {0}.
Category:
EJB
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.
BEA-010191
The alter table option is not supported in {0}. Use the DropAndCreate option.
Category:
EJB
Cause:
The alter table option is not supported in the given database.
Action:
Use the DropAndCreate option.
BEA-010194
Only instances of beans with bean-managed transaction demarcation can use getUserTransaction().
Category:
EJB
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.
BEA-010195
Security violation: User {0} has insufficient permission to access method {1}.
Category:
EJB
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.
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.
Category:
EJB
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.
BEA-010198
An exception occurred while uninitializing the EJB module {0}.
Category:
EJB
Cause:
Check the exception for the exact cause.
Action:
Check the exception for the exact error message, and take appropriate action.
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.
Category:
EJB
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.
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.
Category:
EJB
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.
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.
Category:
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.
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.
Category:
EJB
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.
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.
Category:
EJB
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.
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.
Category:
EJB
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.
BEA-010207
License validation not passed for {0}.
Category:
EJB
Cause:
See the message body.
Action:
No action is required.
BEA-010208
ddl-file {0} created.
Category:
EJB
Cause:
See the message body.
Action:
No action is required.
BEA-010209
ddl-file {0} could not be deleted.
Category:
EJB
Cause:
See the message body.
Action:
Check the file permissions.
BEA-010210
Unable to write to ddl-file {0}.
Category:
EJB
Cause:
See the message body.
Action:
No action is required.
BEA-010211
Unable to alter the table, as the primary key has changed.
Category:
EJB
Cause:
See the message body.
Action:
Use the DropAndCreate option to create the table.
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}.
Category:
EJB
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.
BEA-010213
Message-Driven EJB: {0}''s transaction was rolled back, because {1}. The transaction details are: {2}.
Category:
EJB
Cause:
The transaction was rolled back by the MDB container.
Action:
This is an informational message. No action is needed.
BEA-010214
Error starting MDB {0}.
Category:
EJB
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.
BEA-010215
The durable subscription store with jms-client-id equal to {0} is deleted when MDB {1} is removed from the server.
Category:
EJB
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.
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.
Category:
EJB
Cause:
The Message-Driven Bean is generating an exception.
Action:
Check the message delivery methods and resolve the exception condition.
BEA-010221
The Message-Driven EJB: {0} is unable to bind to the JCA resource adapter: {1}. The Error was: {2}
Category:
EJB
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.
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.
Category:
EJB
Cause:
There were no values to which to apply the aggregate function
Action:
Handle ObjectNotFoundException correctly on the application side.
BEA-010223
EJB deployed Message Driven Bean {0}.
Category:
EJB
Cause:
See the message body.
Action:
No action is required.
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.
Category:
EJB
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.
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.
Category:
EJB
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.
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.
Category:
EJB
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.
BEA-010227
EJB exception occurred during invocation from home or business: {0} generated exception: {1}
Category:
EJB
Cause:
See the message body.
Action:
No action is required.
BEA-010228
Failed to update the secondary copy of a stateful session bean business: {0}.
Category:
EJB
Cause:
The server was unable to update the secondary server.
Action:
Check the exception for the exact error message.
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.
Category:
EJB
Cause:
Both of the specified methods have declarative security settings.
Action:
Avoid case-insensitive method name conflicts if method permissions are configured.
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}.
Category:
EJB
Cause:
See error message body.
Action:
See error message body.
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.
Category:
EJB
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.
BEA-010233
The configuration of "MessagesMaximum" is ignored for non Weblogic JMS.
Category:
EJB
Cause:
See error message body.
Action:
No action is required.
BEA-010234
Failed to unbind {0} from JNDI tree due to {1}.
Category:
EJB
Cause:
See the message body.
Action:
If the application is redeployed, restart the target cluster/server on which the application has been deployed. Please report the issue to My Oracle Support with relevant details.
BEA-010235
The Message-Driven EJB {0} has connected or reconnected to the JCA resource adapter {1}.
Category:
EJB
Cause:
The Message-Driven EJB has been re-associated with the JCA resource adapter.
Action:
No action is required.
BEA-010236
The Message-Driven EJB {0} (status: {1}) has not been associated with the JCA resource adapter, so trying suspending it actually did nothing.
Category: