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:
- EJB
- Cause:
- The Message-Driven EJB has not been associated with the JCA resource adapter, so trying suspending it actually did nothing.
- Action:
- No action is required.
- BEA-010237
- The Message-Driven Bean {0} was configured to use a JMS Topic, does not require transactions, and uses a non-WebLogic JMS provider. Only one thread will be used to receive and process all messages.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-010239
- EJB container creates a {0} bean with name {1} belonging to {2} module.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-010240
- The Message-Driven Bean {0} has connected to JMS destination {1}, but was suspended on its startup because property {2} is set.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-010241
- The Message-Driven Bean {0} has connected to Resource Adapter {1}. Property {2} is ignored, because it is not supported by JCA-Based Message-Driven Bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011047
- In ejb-jar.xml or annotation, EJB {0} has container-transactions set when the EJB has a transaction-type of Bean. The container-transaction settings will be ignored.
- Category:
- EJB
- Cause:
- The specified EJB has container-transactions set when the EJB has a transaction-type of Bean.
- Action:
- No action is required.
- BEA-011057
- The table {0} was created by the user. The container does not drop or alter user-created tables. The container would verify the table in this case.
- Category:
- EJB
- Cause:
- The table was already created by the user.
- Action:
- Drop the table if the existing table is not correct. The container will then be able to create the table.
- BEA-011059
- The container was unable to create the DDL file.
- Category:
- EJB
- Cause:
- This error does not provide the cause of the error. The log file will contain an exception stack indicating the root cause of the failure.
- Action:
- Inspect the log file for indications of the root cause of the failure.
- BEA-011061
- Stack trace associated with message {0} follows:
- Category:
- EJB
- Cause:
- An error condition was reported.
- Action:
- Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem.
- BEA-011062
- The following exception has occurred:
- Category:
- EJB
- Cause:
- An error condition was reported.
- Action:
- Review the stack trace, which will help with debugging an existing problem.
- BEA-011063
- Stateless session beans with bean-managed transactions must commit or roll back their transactions before completing a business method. The method {0} of EJB {1} either returned or generated an Exception without properly completing a transaction.
- Category:
- EJB
- Cause:
- A transaction started by the stateless session bean method did not complete before the method completed.
- Action:
- Check the bean code to determine what caused the transaction to not commit or roll back, and fix code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.
- BEA-011070
- In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <field-group>(s) are defined but are not used in any <weblogic-query>, <weblogic-relationship-role> or <relationship-caching> <caching-element>s. The <group-name>(s) of the unreferenced <field-group>(s) are: {1}
- Category:
- EJB
- Cause:
- Some field group definitions are not referenced in any query or relationship.
- Action:
- Remove the field groups listed in the logged message from the descriptor or include its usage appropriately.
- BEA-011071
- In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <relationship-caching>(s) are defined but are not used in any <weblogic-query>. The <caching-name>(s) of the unreferenced <relationship-caching>(s) are: {1}
- Category:
- EJB
- Cause:
- There are unused relation cachings defined in the weblogic-rdbms descriptor.
- Action:
- Remove the unused relationship cachings listed in the logged message from the descriptor or include its usage appropriately.
- BEA-011073
- An error occurred while the EJB container was attempting to obtain information about the table {0} from the database. This information is necessary to validate the mapping between the fields of the EJB {1} and the table. The exception is: {2}
- Category:
- EJB
- Cause:
- The most likely cause is an error communicating with the database. The error message should include the specific error message.
- Action:
- The action depends on the specific error that occurred. Actions may range from retrying the failed deployment to seeking help from your database administrator. Also, ensure that you are using a supported database.
- BEA-011076
- Unable to deploy the EJB {0} because the database table {1} is not accessible. Ensure that this table exists and is accessible.
- Category:
- EJB
- Cause:
- A required database table was not accessible.
- Action:
- Ensure that the database table exists and is accessible.
- BEA-011077
- The EJB deployment contains settings for automatically creating or altering database tables. However, the server is in production mode, so no database tables will be created or altered.
- Category:
- EJB
- Cause:
- The server is in production mode so the create-default-dbms-tables settings are being ignored.
- Action:
- No action is required. To suppress the warning, remove the create-default-dbms-tables setting from your EJB deployment.
- BEA-011078
- An exception occurred while starting the freepool idle timeout timer for ejb: {0}, {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011079
- An exception occurred while stopping the freepool idle timeout timer for ejb: {0}, {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011080
- An exception occurred while starting the Cache idle timeout timer for cache: {0}, {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011081
- An exception occurred while stopping the Cache idle timeout timer for cache: {0}, {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011082
- Error: The message-destination-link {0} for the Message-Driven Bean {1} in the application module {2} could not be resolved. The target message-destination for the Message-Driven Bean could not be found. Ensure that the link is correct.
- Category:
- EJB
- Cause:
- The target of the message-destination-link could not be found in the application.
- Action:
- Fix the message-destination-link to point to a valid message-destination.
- BEA-011083
- The EJB specification prohibits stateful session beans from using the TimerService.
- Category:
- EJB
- Cause:
- An illegal call was made to the getTimerService() method on the stateful session beans SessionContext.
- Action:
- Correct the stateful session bean code so that it does not call the getTimerService() method from the bean class.
- BEA-011084
- This EJB class does not support EJB timers and therefore is prohibited from using the TimerService. To use EJB timers, the bean class must implement javax.ejb.TimedObject or have a method that is annotated with @Timeout.
- Category:
- EJB
- Cause:
- An illegal call to the getTimerService() method on the EJBContext.
- Action:
- Correct the EJB class so it either implements the javax.ejb.TimedObject interface or ensure that it does not call the getTimerService() method on the EJBContext.
- BEA-011085
- This timer has either expired or been canceled and therefore cannot be invoked.
- Category:
- EJB
- Cause:
- An illegal call to a timer object after the timer had expired or was canceled.
- Action:
- Ensure your bean class does not invoke expired or canceled timers.
- BEA-011086
- The timer associated with this TimerHandle has either expired or been canceled.
- Category:
- EJB
- Cause:
- The timer associated with the TimerHandle has expired or been canceled.
- Action:
- No action is required.
- BEA-011087
- This TimerHandle is being invoked outside of the context of the application in which it was created. Since timers are local objects, they can only be called from within the same application in which they were created.
- Category:
- EJB
- Cause:
- This TimerHandle is being invoked outside of the context of the application in which it was created.
- Action:
- Ensure that your application does not pass any TimerHandle references outside of the scope of the application.
- BEA-011088
- The following error occurred while invoking the ejbTimeout(javax.ejb.Timer) method of EJB {0}.
- Category:
- EJB
- Cause:
- This could be caused by erroneous code in the ejbTimeout method or by the failure of a dependent resource.
- Action:
- All exceptions that occur while invoking or attempting to invoke the ejbTimeout method should be investigated and resolved. If the ejbTimeout method is non-transactional, that is, has a transaction attribute of NotSupported, or if the bean uses bean-managed transactions, the ejbTimeout method may not be retried, leading to missed timeout notifications.
- BEA-011089
- The following error occurred while attempting to remove an EJB timer from the persistent store for EJB {0}.
- Category:
- EJB
- Cause:
- This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.
- Action:
- This cause of this error should be investigated and resolved promptly.
- BEA-011090
- The following error occurred while preparing to invoke the ejbTimeout(javax.ejb.Timer) method of EJB {0}.
- Category:
- EJB
- Cause:
- This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.
- Action:
- All exceptions that occur while attempting to invoke the ejbTimeout method should be investigated and resolved.
- BEA-011091
- The table {0} cannot be dropped or created since it uses a trigger to update the optimistic column of the EJB. The container will only verify the existence of the table.
- Category:
- EJB
- Cause:
- The table uses a trigger to update the optimistic column of the EJB.
- Action:
- To suppress this warning, set the create-default-dbms-tables value in the RDBMS deployment descriptor to Disabled.
- BEA-011092
- In production mode, the DropAndCreate, DropAndCreateAlways, and AlterOrCreate options are ignored. The container will only attempt to verify the existence and increment value of the sequence {0}.
- Category:
- EJB
- Cause:
- Options that apply only to development mode are ignored in production mode.
- Action:
- Do not use these values for Automatic Oracle SEQUENCE Generation in production mode.
- BEA-011093
- The SEQUENCE named {0} with INCREMENT {1} was not found in the database. This SEQUENCE was specified in the CMP deployment descriptor to be used for automatic primary key generation.
- Category:
- EJB
- Cause:
- The SEQUENCE was not found.
- Action:
- Examine the <automatic-key-generation> tag in the CMP deployment descriptor. In particular, re-examine the <generator-name> and verify that this is the correct name of the SEQUENCE. Also, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.
- BEA-011094
- The SEQUENCE named {0} does not have INCREMENT value of {1} in the database as specified in the CMP deployment descriptor. Either modify the key-cache-value for this SEQUENCE in the deployment descriptor or update the SEQUENCE in the database.
- Category:
- EJB
- Cause:
- The SEQUENCE named {0} does not have an INCREMENT value of {1} in the database as specified in the CMP deployment descriptor.
- Action:
- In the <automatic-key-generation> tag of the CMP deployment descriptor, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.
- BEA-011095
- During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}. {2}
- Category:
- EJB
- Cause:
- During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}.
- Action:
- The message contains the cause of the error. See the message body and resolve the reported error.
- BEA-011096
- During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}. {2}
- Category:
- EJB
- Cause:
- During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}.
- Action:
- The message contains the cause of the error. See the message body and resolve the reported error.
- BEA-011097
- During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}. {2}
- Category:
- EJB
- Cause:
- During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}.
- Action:
- The message contains the cause of the error. See message body and resolve the reported error.
- BEA-011098
- No generated primary key was returned from the database insert statement as expected. Verify that the primary key database column for this EJB is an IDENTITY column as declared in the CMP deployment descriptor for this EJB.
- Category:
- EJB
- Cause:
- This is most likely caused by a database configuration error. It may also be caused by a JDBC driver that does not support the getGeneratedKeys() method on java.sql.Statement.
- Action:
- Verify that the primary key column in the database is marked as an IDENTITY column (or a functional equivalent is setup for the column such as a database trigger to insert a value into the primary key column).
- BEA-011099
- Multiple generated keys were returned from the database insert statement. The EJB container is unable to determine which generated key corresponds to the primary key column. To use the IDENTITY primary key generator, you must only have a single automatically generated database column per EJB.
- Category:
- EJB
- Cause:
- This is most likely caused by a database configuration error. Each EJB may only have a single automatically generated database column.
- Action:
- Verify that the database table corresponding to the EJB only has a single generated column.
- BEA-011109
- Failed to register JACC policy context handlers for the EJB container.
- Category:
- EJB
- Cause:
- An unexpected error condition occurred while registering JACC context policy handlers.
- Action:
- See the error message stack trace for details on how to resolve this issue.
- BEA-011110
- The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database. This may generate missing keys.
- Category:
- EJB
- Cause:
- The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database.
- Action:
- In the <automatic-key-generation> tag, re-examine the <key-cache-size> and verify that it is set correctly.
- BEA-011111
- The SEQUENCE named {0} has key-cache-size set to {1} which is greater than the INCREMENT_BY value for the sequence in the database. This is not allowed as it may generate duplicate keys.
- Category:
- EJB
- Cause:
- The key-cache-set size for the SEQUENCE is not valid.
- Action:
- in the <automatic-key-generation> tag, re-examine the <key-cache-size> and set it to a value less than or equal to the INCREMENT_BY value for the sequence in the database.
- BEA-011120
- The CMP EJB {0} has enable-batch-operations set to true. The update queries, however, are not suitable for batching. Batched operations are turned off for this batch and the queries will be executed with multiple update statements.
- Category:
- EJB
- Cause:
- Batching is turned off for update queries.
- Action:
- No action is required.
- BEA-011121
- Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be found in the server classpath.
- Category:
- EJB
- Cause:
- The plugin-class could not be found in the server classpath.
- Action:
- Add the plugin-class in the server classpath.
- BEA-011122
- Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be instantiated.
- Category:
- EJB
- Cause:
- The plugin-class could not be instantiated.
- Action:
- Add the plugin-class in the server classpath.
- BEA-011123
- Error in Message-Driven Bean EJB {0}. The plugin-class {1} could not be found in the server classpath.
- Category:
- EJB
- Cause:
- The plugin-class could not be accessed.
- Action:
- Add the plugin-class in the server classpath.
- BEA-011124
- Error in Message-Driven Bean EJB {0}. The plugin-class {1} does not implement weblogic.ejb.spi.SecurityPlugin.
- Category:
- EJB
- Cause:
- The plugin-class does not implement weblogic.ejb.spi.SecurityPlugin.
- Action:
- Make the plugin-class implement weblogic.ejb.spi.SecurityPlugin.
- BEA-011125
- An unexpected error was encountered while attempting to remove any EJB timers from the persistent store for the EJB {0}.
- Category:
- EJB
- Cause:
- An unexpected error occurred while attempting to remove EJB timers from the persistent store.
- Action:
- See the particular error message for details about the error. If your application is failing to deploy because of this error, it may be necessary to manually remove the timers from the store.
- BEA-011126
- The same exception has consecutively caused the expiration to fail for EJB timer {0}. Consecutive errors of this type will no longer be logged for the current timer expiration.
- Category:
- EJB
- Cause:
- The same exception has consecutively caused expiration of an EJB timer to fail.
- Action:
- Investigate what caused the ejbTimeout method to fail. The original exception will be logged in a previous error message.
- BEA-011127
- Error deserializing one or more EJB timers from the persistent store for the EJB deployment {0}. An incompatible change to the class of a Serializable object associated with the timer may be the cause. If this is the case, you can either undeploy your application entirely to remove the EJB timers from the persistent store or revert the incompatible changes to the Serializable class so the EJB timer can be deserialized. The error was: {1}
- Category:
- EJB
- Cause:
- A common cause of this error is an incompatible serializable class change in your application.
- Action:
- If the error is due to an incompatible serializable class change in your application, there are two options for dealing with the serialization errors. The first option is to completely undeploy the EJB. which will cause all of the EJB timers in the persistent store to be permanently removed. The second option is to revert changes to the serializable class that is associated with the EJB timer and redeploy the application. This allows the EJB timer to be deserialized.
- BEA-011128
- Error creating an instance of the EJB {0}: {1}
- Category:
- EJB
- Cause:
- See the reported error message for the cause. This error may be due to a configuration issue or a bug in the EJB container.
- Action:
- See the specific error message for details and take appropriate action.
- BEA-011132
- Error deploying EJB {0}. While binding a business interface to the JNDI name {1}, the following error occurred: {2}
- Category:
- EJB
- Cause:
- See the specific error for details.
- Action:
- The action to take depends on the specific error that occurred. If the error was a JNDI naming conflict, you may need to choose a different JNDI name for the interface.
- BEA-011135
- The EJB {0} is a singleton session bean. EJB 2.1 client views are not supported for singleton session beans.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011136
- wasCancelCalled() should only be invoked from within an asynchronous business method invocation with return type Future.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011137
- A singleton 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:
- No action is required.
- BEA-011139
- The following exception occurred when processing the asynchronous invocation : {0}.
- Category:
- EJB
- Cause:
- There error was encountered during the asynchronous invocation.
- Action:
- See the exception stack trace for details.
- BEA-011140
- The argument {0} is not a valid local client view for the EJB {1}.
- Category:
- EJB
- Cause:
- The argument is not a valid local client view for the EJB.
- Action:
- Review the EJB configuration and calling code to determine the discrepancy.
- BEA-011141
- This EJB has already been removed.
- Category:
- EJB
- Cause:
- The EJB has already been removed.
- Action:
- Avoid the call for removed objects.
- BEA-011142
- Error creating EJB reference: {0}
- Category:
- EJB
- Cause:
- An exception occurred while creating an EJB reference.
- Action:
- The reported exception contains the root cause of the issue. Review the exception to identify the exact problem.
- BEA-011143
- Error removing stateful session bean: {0}
- Category:
- EJB
- Cause:
- An unexpected error occured while trying to remove a stateful session bean.
- Action:
- The reported exception has the root cause of the issue. Review the exception to identify the actual problem.
- BEA-011144
- Singleton EJB {0} failed to initialize.
- Category:
- EJB
- Cause:
- A singleton EJB {0} failed to initialize.
- Action:
- The message body has the root cause of the issue. Review it to identify the essential problem.
- BEA-011145
- Illegal call to a Write method from a Thread holding Read lock.
- Category:
- EJB
- Cause:
- An illegal call to a Write method was made
- Action:
- Remove or rewrite the call.
- BEA-011146
- Timed out while trying to aquire lock on Singleton {0} to invoke method {1}.
- Category:
- EJB
- Cause:
- A timeout occurred while trying to aquire a lock.
- Action:
- Check Singleton concurrency. A timeout has been reached.
- BEA-011147
- Singleton {0} is in use by another thread.
- Category:
- EJB
- Cause:
- While this Singleton is being invoked, it cannot be called from other threads.
- Action:
- Check Singleton concurrency.
- BEA-011148
- Singleton {0} not initialized as Singleton {1} from the DependsOn transitive, closure failed initialization.
- Category:
- EJB
- Cause:
- A singleton was not initialized as a Singleton from the DependsOn transitive, closure failed initialization.
- Action:
- Check the server log for the cause of the dependent Singleton initialization error and resolve it.
- BEA-011149
- The EJB {0} contains an illegal value for the activation config property MessagesMaximum. The specified value is {1} but the legal values are -1, and 1 through 2^63-1.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Correct the activation config property.
- BEA-011151
- Unable to determine the {3} to use for Message Driven Bean {0}. Activation Configuration of Message Driven Bean {0} includes conflicting values specified using {1} and {2}. Consider dropping {2} and specifying the intended {3} using property {1}.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- See the error message body.
- BEA-011152
- ConnectionFactoryResourceLink and DestinationResourceLink configuration attributes cannot be mixed with any of the following settings: DestinationJNDIName, InitialContextFactory, ProviderUrl, ConnectionFactoryJNDIName. Ensure that they are mutually exclusive for ejb {0}.
- Category:
- EJB
- Cause:
- Conflicting configuration attributes were specified.
- Action:
- Ensure that these configuration attributes are mutually exclusive.
- BEA-011153
- EJB {0} has a redundant Activation configuration, property {1} will be used, property {2} can be dropped.
- Category:
- EJB
- Cause:
- There is a redundant configuration property.
- Action:
- See the message body.
- BEA-011154
- The EJB {0} contains an illegal value for the activation config property TopicMessagePartitionMode. The specified value is {1} but the legal values are Isolated or Shared.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Correct the activation config property.
- BEA-011155
- Access is denied on a nonexistent method.
- Category:
- EJB
- Cause:
- The specified method is not existing.
- Action:
- Make sure the method is existing.
- BEA-011156
- Non numeric value was configured for activation config property {0}.
- Category:
- EJB
- Cause:
- Non numeric value was configured for activation config property {0}.
- Action:
- Correct activation config property setting.
- BEA-011157
- An exception occurred while preparing 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-011158
- An exception occurred while initializing 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-011159
- An exception occurred while starting 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-011160
- The {0} operation has been scheduled for Message-Driven Bean {1} (listening to JMS destination {3}) of application {2}, but error occurred during {0} operation's execution : {4}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- Review the reported exception details to identify the exact problem. Correct it and then try again.
- BEA-011161
- An exception occurred while creating JMS {0} for JMS destination {2} for Message-Driven Bean {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required, as Message-Driven Bean will try recovering from the error. If Message-Driven Bean cannot be recovered, please check and ensure JMS resources are available.
- BEA-011162
- The Timeout(javax.ejb.Timer) method of EJB {0} cannot be invoked because it was already undeployed.
- Category:
- EJB
- Cause:
- This could be caused when EJB is being undeployed or in production redeployment.
- Action:
- No action is required.
- BEA-011223
- Cannot invoke stateful callback on {0}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011224
- Unable to bind the interface {0} to {1}. Another EJB has already bound an interface to that name.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011225
- Unable to bind the interface {0} to {1}. This EJB has declared another interface already bound to that name.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011226
- Error during {0}. Could not get connection: {1} {2}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011227
- Error during finder {0}. Exception while preparing query: {1} {2} {3}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011232
- Error during finder {0}. Exception while setting parameters for query {1} {2} {3}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011233
- Error during finder {0}. Exception while executing query {1} {2}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011234
- Could not find an EJB with a field that is mapped to table {0} and column {1}. The SQL query is {2}. Try using an SqlShape annotation to describe the query results or check that the SqlShape annotation in use is correct.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011235
- Error in {0}, could not map relationship {1} role {2} to an EJB populated by the query {3}. EJBs populated by this query are: {4}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011236
- Error executing finder {0}: SqlShape {1} contains {2} columns, but the result set returned by JDBC contains {3} columns. The number of columns in the SqlShape and the JDBC result set must match.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011237
- A stored procedure or function is used by {0}, but no SqlShape is specified.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011238
- Error in {0}. SQL query {1} does not select column values for all primary key fields of bean {2}. No columns were selected for the following fields: {3}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011239
- Query-caching is not supported for read-write beans.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011240
- Error obtaining nativeQuery: {0}, {1}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011241
- An attempt was made to do an executeQuery on query {0}, using a non-WebLogic EntityManager.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011242
- Internal Error: Extended Persistence Context has been closed!
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011243
- attempt at illegal state transaction from {0} to {1}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011244
- An illegal call was made to the EJBContext method. getMessageContext can only be called from SLSBs with web-service endpoint interfaces.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011245
- The EJB {0} is not an EJB3.0 bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011246
- The EJB {0} does not declare a {1} home interface.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011247
- The EJB {0} does not implement the business interface {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011248
- The bean has not been invoked through a business interface.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011249
- It is illegal to invoke UserTransaction methods in ejbCreate or the PostConstruct method of a Message-Driven Bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011250
- It is illegal to invoke UserTransaction methods in ejbRemove or the PreDestroy method of a Message-Driven Bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011251
- It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a Message-Driven Bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011252
- It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a stateful session bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011253
- It is illegal to invoke UserTransaction methods in ejbCreate or the PostConstruct method of a stateless session bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011254
- It is illegal to invoke UserTransaction methods in ejbRemove or the PreDestroy method of a stateless session bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011255
- It is illegal to invoke UserTransaction methods in setSessionContext or a dependency injection of a stateless session bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011256
- Single expiration timers cannot be cancelled from within ejbTimeout.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011257
- It is illegal to invoke Timer methods in ejbRemove or a PreDestroy method from asession bean or Message-Driven Bean.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011258
- It is illegal to invoke Timer methods in ejbActivate or a PostActivate method.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011259
- It is illegal to invoke Timer methods in ejbPassivate or a PrePassivate method.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011260
- It is illegal to invoke Timer methods during a dependency injection.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011261
- Invocation timed out. Timer is busy.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011262
- Error cancelling timer
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011263
- EjbJarBean is not set yet.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011264
- Method {0} is marked TX_NEVER, but was called within a transaction.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011265
- Unexpected exception in afterDelivery(): {0}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011266
- An attempt was made to execute getDatabaseProductName using a non-WebLogic EntityManager.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011267
- Error calling getDatabaseProductName: {0}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011268
- An attempt was made to execute nativeQuery on query {0}, using a non-WebLogic EntityManager.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011269
- Error obtaining nativeQuery: {0}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011270
- Error preparing query: {0}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011276
- An illegal attempt was made to make a re-entrant call to a stateful session bean: {0}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011277
- An illegal attempt was made to make a re-entrant call to a stateful session bean from home: {0}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-011278
- The following dependency that was declared by {0} is not a Singleton Session Bean: {1}.
- Category:
- EJB
- Cause:
- A dependency that was specified by a Singleton Session Bean must also be a Singleton Session Bean.
- Action:
- Remove the illegal dependency from the dependency list or replace it with a Singleton Session Bean.
- BEA-011279
- The following exception occured in PreDestroy processing for singleton session bean {0}: {1}.
- Category:
- EJB
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-012030
- Illegal DOCTYPE for a WebLogic RDBMS CMP EJB11 descriptor file. DOCTYPE {0} not permitted. Only DOCTYPE {1} permitted here.
- Category:
- EJB
- Cause:
- An illegal DOCTYPE was used.
- Action:
- Make sure to update appropriate DOCTYPE to the descriptor file.
- BEA-012031
- The EJB {0} has a finder {1} for which the sql-select-distinct attribute has been specified. This attribute has been deprecated and will not be supported in future releases.
- Category:
- EJB
- Cause:
- The deprecated sql-select-distinct attribute was used.
- Action:
- Use the EJB-QL DISTINCT clause instead. The container will automatically filter duplicates if necessary.
- BEA-012032
- For EJB {0}, a weblogic-query element in the CMP deployment descriptor has no matching query element in the ejb-jar.xml descriptor. The settings specified in the weblogic-query element will be ignored. The EJB method referred to by the weblogic-query element is {1}.
- Category:
- EJB
- Cause:
- The weblogic-query element references a wrong or non-existent query method for this entity EJB.
- Action:
- Remove the weblogic-query element or update it so that it references the correct query method.
- BEA-012033
- Compiling generated EJB classes produced the following Java compiler output: {0}
- Category:
- EJB
- Cause:
- While compiling EJB generated classes, the Java compiler produced output.
- Action:
- Typically, there is no action to take. The Java compiler output is printed for informational purposes.
- BEA-012035
- The Remote interface method: {0} in EJB {1} contains a parameter of type {2} which is not serializable. Though the EJB {1} has call-by-reference set to false, this parameter is not serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is serializable.
- Category:
- EJB
- Cause:
- The EJB has call-by-reference set to false. A parameter can be passed using call-by-value only if the parameter type is serializable. As this parameter is not serializable, the parameter will be passed by reference.
- Action:
- The parameter should implement the java.io.Serializable interface for it to be passed by value.
- BEA-012036
- Compiling generated EJB classes produced the following Java compiler error message: {0}
- Category:
- EJB
- Cause:
- While compiling EJB generated classes, the Java compiler produced output.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-012037
- In weblogic-ejb-jar.xml or annotation, a singleton-session-descriptor element was found for EJB {0}. This EJB was not declared as a singleton session bean in ejb-jar.xml or annotation.
- Category:
- EJB
- Cause:
- There is an incompatible configuration between weblogic-ejb-jar.xml and ejb-jar.xml.
- Action:
- Modify weblogic-ejb-jar.xml or ejb-jar.xml to keep configuration consistency whether singleton or non-singleton.
- BEA-014000
- Problem, encountered illegal value for transaction-isolation {0}.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Specify one of the following legal values: TransactionSerializable, TransactionReadCommitted, TransactionReadCommittedForUpdate, TransactionReadCommittedForUpdateNoWait, TransactionReadUncommitted, or TransactionRepeatableRead.
- BEA-014001
- RDBMS descriptor {0} contains transaction-isolation settings. These settings may conflict with isolation-level settings in your weblogic-ejb-jar.xml descriptor and will be lost if you edit this descriptor in the console.
- Category:
- EJB
- Cause:
- The specified RDBMS descriptor contains transaction-isolation settings.
- Action:
- Move the isolation-level settings to the weblogic-ejb-jar.xml descriptor.
- BEA-014003
- EJB {0} uses optimistic concurrency and contains a finder or select method, {1}, for which include-updates is true. This combination of features does not work properly with database {2}.
- Category:
- EJB
- Cause:
- Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks, unless Oracle is used as the database. Oracle read consistency does not hold read locks, so in this case reads are performed using the current JTA transaction. When reads are performed in a local transaction updates that have been flushed prior to commit of the transaction are not visible.
- Action:
- Set include-updates for the query to false to avoid this warning message, or if you are using Oracle as your database, set the database-type to Oracle in weblogic-cmp-jar.xml.
- BEA-014004
- In EJB {0}, <generator-type> is set to {1}. It is incompatible with Batch Operations due to database limitations. Both order-database-operations and enable-batch-operations are turned off by EJB container.
- Category:
- EJB
- Cause:
- These are database limitations.
- Action:
- Turn off automatic-key-generation in order to use batch operations.
- BEA-014005
- The configured dispatch policy {1} for Message-Driven Bean (MDB) {0} will be ignored: the MDB is not running in a WebLogic thread.
- Category:
- EJB
- Cause:
- The queue MDB is driven asynchronously by a non-WebLogic JMS implementation and runs in a non-WebLogic thread mechanism, so the MDBs application thread pool is not configurable.
- Action:
- To disable this warning, remove the dispatch-policy setting from the MDBs WebLogic descriptor file.
- BEA-014006
- The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.
- Category:
- EJB
- Cause:
- The specified MDB named has a dispatch policy that refers to an unknown execute queue thread pool.
- Action:
- Create an execute thread queue pool for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing execute queue thread pool.
- BEA-014007
- The bean named {0} contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified. This may result in corruption of BLOB and CLOB data.
- Category:
- EJB
- Cause:
- The specified bean contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified.
- Action:
- Specify "version" or "timestamp" in the <table-map> <verify-columns> element and specify the name of the <version> or <timestamp> column in the <optimistic-column> element.
- BEA-014008
- In EJB {0}, {1} references an SqlShape element {2} that is not defined. The list of SqlShape elements that are defined for this EJB is: {3}.
- Category:
- EJB
- Cause:
- An undefined SqlShape element was referenced.
- Action:
- Use an existing SqlShape or create the SqlShape that you wish to use.
- BEA-014009
- The Message-Driven Bean {0} of application {1} will now be suspended, as it listens to global JMS destination {2} and a new application version {3} is being redeployed.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-014010
- The Message-Driven Bean {0} of application {1} will now be suspended, as it listens to global JMS topic {2} and a new application version {3} is being redeployed. Note also that the current Message-Driven Bean is not a durable subscriber to the topic, and messages published by the topic after the currently active version of the Message-Driven Bean is suspended may not be received by the new application version.
- Category:
- EJB
- Cause:
- The specified Message-Driven Bean listens to the specified global JMS topic and a new application version is being redeployed.
- Action:
- To ensure that the new application version will receive all messages published while the Message-Driven Bean was suspended, set the activation config property "subscriptionDurability" to "durable" in the deployment descriptor or annotation.
- BEA-014011
- EJB {0} uses optimistic-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. This combination of features is incompatible. The use-select-for-update is turned off by the EJB container in this case.
- Category:
- EJB
- Cause:
- Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks. The element use-select-for-update in the RDBMS deployment descriptor when set to true, will cause SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the table. This conflicts with the Optimistic Concurrency strategy.
- Action:
- Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
- BEA-014012
- EJB {0} uses optimistic-concurrency and disables cluster invalidation, but does not have verify-rows set to Read. This combination will prevent detection of stale data if the bean is never modified in a transaction.
- Category:
- EJB
- Cause:
- Optimistic concurrency beans verify consistency of data only if the bean has been modified, unless verify-rows is set to Read. If some other member of a cluster modifies a bean, other members will not be notified of this modification and will continue to store stale data unless the other members also attempt to modify the bean.
- Action:
- Set either of the elements verify-rows to Read or cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.
- BEA-014013
- EJB {0} does not have a concurrency-strategy of either optimistic or readOnly and disables cluster invalidation. Cluster invalidation is relevant only for these concurrency strategies.
- Category:
- EJB
- Cause:
- When an EJB is using either optimistic or readOnly concurrency-strategy and is deployed to a cluster, the container invalidates such beans on modification to avoid throwing OptimisticConcurrencyExceptions. This invalidation can be turned off by setting the cluster-invalidation-disabled to true in the RDBMS deployment descriptor.
- Action:
- Set cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.
- BEA-014014
- The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown work manager. The default work manager will be used instead.
- Category:
- EJB
- Cause:
- The specified MDB has a dispatch policy that refers to an unknown work manager.
- Action:
- Create a work manager for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing work manager.
- BEA-014016
- EJB {0} uses readonly-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is read-only, select-for-update is unnecessary.
- Category:
- EJB
- Cause:
- Read-only beans cannot be updated. Therefore, use-select-for-update is unnecessary.
- Action:
- Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
- BEA-014017
- EJB {0} uses exclusive-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is locked at the server level during a transaction, select-for-update on the database is unnecessary.
- Category:
- EJB
- Cause:
- Exclusive concurrency is implemented by locking the bean at the server level when the bean participates in a transaction. Setting the element use-select-for-update in the RDBMS deployment descriptor to true causes SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the row in the database too. This may be unnecessary, as the bean is locked by the container.
- Action:
- Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
- BEA-014018
- EJB {0} uses a verify-columns element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.
- Category:
- EJB
- Cause:
- verify-columns is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.
- Action:
- Remove verify-columns element in the RDBMS deployment descriptor to avoid this warning message.
- BEA-014019
- EJB {0} uses a verify-rows element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.
- Category:
- EJB
- Cause:
- verify-rows is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.
- Action:
- Remove the verify-rows element in the RDBMS deployment descriptor to avoid this warning message.
- BEA-014020
- EJB {0} uses an optimistic-column element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.
- Category:
- EJB
- Cause:
- optimistic-column element is applicable only for optimistic concurrency beans. If the bean does not use optimistic concurrency, this element will be ignored.
- Action:
- Remove the optimistic-column element in the RDBMS deployment descriptor to avoid this warning message.
- BEA-014021
- The EJB {0} has been successfully deployed. The following remote interfaces have been bound into JNDI with the specified JNDI names:
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-014022
- {0} is bound with JNDI name {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015000
- The following exception occured while processing annotations: {0}.
- Category:
- EJB
- Cause:
- See the exception to determine the cause.
- Action:
- See the exception to determine the action to take.
- BEA-015001
- Unable to link class {0} in Jar {1} : {2}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015002
- Unable to load class {0} in Jar {1} : {2}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015003
- Unable to create virual Jar {0} : {1}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015004
- The super class {0} of session bean class {1} is also a session bean class.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015005
- The session type is not set in the deployment descriptor or annotation for session bean {0}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015007
- No ejbCreate method was found for init method {0} in bean {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015008
- No matching create method for @Init method {0} in bean {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015009
- Could not load interceptor class {0}: {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015010
- In bean {0}, there are multiple method permission annotations for method {1}, which is illegal.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015011
- There are multiple method permission annotations for class {0}, which is illegal.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015012
- Unable to load interface class {0}: {1}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015013
- Bean class {0} does not implement interface method {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015014
- ServiceEndpoint class {0} was specified but cannot be found.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015015
- The super class {0} of Message-Driven Bean class {1} is also a Message-Driven Bean class.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015016
- Message-Drive Bean {0} does not implement the message listener interface, has no messaging-type specified in the deployment descriptor, or has no messageListenerInterface specified by using @MessageDriven annotation.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015017
- In bean class {0}, the @EJB annotation is at class level, so the beanInterface must be explicitly specified.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015018
- In interceptor class {0}, the @EJB annotation is at class level, so the beanInterface must be explicitly specified.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015022
- {0} is not valid in this context. Bean class: {1}.
- Category:
- EJB
- Cause:
- {0} is not valid in this context. Bean class: {1}.
- Action:
- Remove {0} from the invalid location.
- BEA-015023
- {0} is not valid in this context. Bean method: {1}.{2}.
- Category:
- EJB
- Cause:
- {0} is not valid in this context. Bean method: {1}.{2}.
- Action:
- Remove {0} annotation from invalid location.
- BEA-015024
- Could not specify @JNDIName on local business interface {0} of Bean {1}.
- Category:
- EJB
- Cause:
- The @JNDIName could not be specified on the local business interface {0} of Bean {1}.
- Action:
- Remove the annotation from the local business interface.
- BEA-015025
- Unable to load a class that is specified in your ejb-jar.xml: {0}.
- Category:
- EJB
- Cause:
- A class that is specified in your ejb-jar.xml cannot be loaded.
- Action:
- Check ejb-jar.xml in the EJB JAR file.
- BEA-015026
- Reference name {0} of @{1} annotation on class {2} is not unique.
- Category:
- EJB
- Cause:
- Reference name {0} of @{1} annotation on class {2} is not unique.
- Action:
- Change the reference name {0} of @{1} annotation on class {2}.
- BEA-015027
- The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.
- Category:
- EJB
- Cause:
- The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.
- Action:
- Make the Message-Driven EJB non-transactional, or use a different connection factory that supports XA.
- BEA-015028
- The EJB {0} contains an illegal value for the activation config property DistributedDestinationConnection. The specified value is {1} but the legal values are EveryMember and LocalOnly.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Correct the activation config property.
- BEA-015029
- The EJB {0} contains an illegal value for the activation config property TopicMessagesDistributionMode. The specified value is {1} but the legal values are Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Correct the activation config property.
- BEA-015030
- The EJB {0} has an illegal permutation on distributed topic type and topicMessagesDistributionMode. Replicated distributed topics work with Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application, but partitioned distributed topics only work with One-Copy-Per-Server or One-Copy-Per-Application. The EJB is configured to partitioned distributed topic and Compatibility.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Review the compatibility of distributed topic types and topicMessagesDistributionMode and fix them.
- BEA-015031
- The EJB {0} has a distributedDestinationConnection configured but the EJB is configured to connect to a remote cluster. Since the distributedDestinationConnection configuration is only valid in a local cluster, the setting will be ignored.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Connect to a local cluster, or remove the distributedDestinationConnection configuration.
- BEA-015032
- The EJB {0} is configured with the activation config property topicMessagesDistributionMode but the EJB is configured to connect to a JMS Queue. The topicMessagesDistributionMode is valid only for JMS Topic destinations.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Correct the activation config property.
- BEA-015033
- The EJB {0} has an invalid value configured for the activation config property {1}. Only WebLogic JMS server 10.3.4 or later versions support the values One-Copy-Per-Server or One-Copy-Per-Application. Prior to 10.3.4.0 Weblogic JMS server or other non-Weblogic JMS vendors, only the Compatibility value is supported.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Correct the activation config property.
- BEA-015034
- This destinaiton {1} is a remote replicated distribution topic which does not support durable subscriptions when the Message-Drive Bean {0} works in Compatibility mode.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Review and fix the compatibility of the activation config property SubscriptionDurability and topicMessagesDistributionMode.
- BEA-015035
- The EJB {0} is configured to support One-Copy-Per-Server mode but the partitioned topic is configured as LocalOnly. To support One-Copy-Per-Server mode, the LocalOnly setting will be overridden with EveryMember.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Change distributed-destination-connection to EveryMember to remove the warning.
- BEA-015036
- In the EJB {0}, the value for the activation config property {1} will be ignored since it is overridden with the value {2}.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- To remove this warning, remove the duplicated configuration from the activation config property.
- BEA-015037
- In EJB {0}, the throws clause for method {1} in the bean class contains exceptions that are NOT in the throws clause of the corresponding {2} interface method.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Correct the throws clause. Implementation methods must have all exceptions that are provided by the corresponding interfaces.
- BEA-015038
- Problems definitively matching up the interface method {0} with a method in the bean class. Please modify your bean class to implement the interface {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015039
- Cannot start an inactive Message-Driven Bean {0}. A redployment may be needed.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Redeploy the application and restart it.
- BEA-015040
- The Message-Driven Bean {0} is inactive now.
- Category:
- EJB
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-015041
- The Message-Driven Bean {0} is active now.
- Category:
- EJB
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-015042
- The JNDI name {0} is set for {1} home interface of EJB {2}, but cannot find {1} home in deployment descriptor. Specify {1} home in ejb-jar.xml.
- Category:
- EJB
- Cause:
- See the error message body.
- Action:
- Specify {1} home in ejb-jar.xml.
- BEA-015043
- A concurrent-call attempt failed on a stateful session bean instance because the lock was held by another thread or transaction, either because concurrent-access is prohibited or access could not be granted in a specific time period. You may change the concurrent-access behavior using the @AccessTimeout annotation or a corresponding element in deployment descriptor.
- Category:
- EJB
- Cause:
- See the message detail.
- Action:
- No action is required.
- BEA-015044
- @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.
- Category:
- EJB
- Cause:
- @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.
- Action:
- Remove @JNDIName from either {1} or {2}.
- BEA-015045
- @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.
- Category:
- EJB
- Cause:
- @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.
- Action:
- Remove @JNDIName from {0} or provide the class name of each client view.
- BEA-015046
- Illegal operation, context data is not supported for the Entity Bean.
- Category:
- EJB
- Cause:
- An illegal operation has occurred, context data is not supported for the Entity Bean.
- Action:
- Remove the retrieval operation for the Entity Bean's context data.
- BEA-015047
- Unable to bind portable JNDI name {0}.
- Category:
- EJB
- Cause:
- The portable JNDI name could not be bound. See the exception for the cause.
- Action:
- Check the exception for the exact error message.
- BEA-015048
- This EJB class does not have a timeout method. To use TimerService, the bean class must implement javax.ejb.TimedObject or have a method that is annotated with @Timeout.
- Category:
- EJB
- Cause:
- You are trying to create a timer but the corresponding EJB does not have a timeout method.
- Action:
- Correct the EJB class and add a timeout method.
- BEA-015049
- Interface {0} implemented by EJB class {1} will be treated as a local business interface, because all implemented interfaces by the bean class should be local business interfaces by default. Note that this interface extends java.rmi.Remote exceptionally.
- Category:
- EJB
- Cause:
- Interface {0} defaults to be a local business interface but it extends java.rmi.Remote.
- Action:
- No action is required if the default works for you. If, however, you do want to use {0} as a remote business interface, specify it explicitly using @Remote annoation or deployment descriptor.
- BEA-015050
- {2} beans with bean-managed transactions must commit or roll back their transactions before completing a lifecycle callback interceptor method. The method {0} of EJB {1} either returned or generated an exception without properly completing a transaction.
- Category:
- EJB
- Cause:
- A transaction started by the {2} bean lifecycle callback method did not complete before the method completed.
- Action:
- Check the bean code to determine what caused the transaction to not commit or roll back and fix the code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.
- BEA-015051
- The following exception occured in {1} processing for stateful session bean {0}: {2}.
- Category:
- EJB
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-015052
- Cannot find proper lifecycle callback method {0} in bean class {1} of EJB {2}.
- Category:
- EJB
- Cause:
- A lifecycle callback method in bean class must have the signature: "void <METHOD>()"
- Action:
- Check the bean code to have the correct signature of the lifecycle callback method.
- BEA-015054
- Error deploying EJB {0}. The JMS connection factory referenced by the JNDI name {0} is a PooledConnectionFactory.
- Category:
- EJB
- Cause:
- The JMS connection factory referenced by the JNDI name {0} is a PooledConnectionFactory. For example, the specified JNDI name may be the JNDI name of a resource reference.
- Action:
- Specify a JMS connection factory JNDI name that, when looked up, does not return a PooledConnectionFactory. For example, specify a JMS connection factory JNDI name that is not the JNDI name of a resource reference.
- BEA-015055
- Error occurred during full state replication for replica {1} of stateful session bean {0} of resource group {2}: {3}
- Category:
- EJB
- Cause:
- The exception was: {3}
- Action:
- Check the exception for the exact error message.
- BEA-015056
- Unregistered replicas for stateful session bean {0}
- Category:
- EJB
- Cause:
- Unregistered replicas for stateful session bean {0}
- Action:
- No action required
- BEA-015057
- An error occurred while attempting to process a message inside a Message-Driven Bean: {0} Exception is : {1}. {2} such exceptions were suppressed in logging.
- 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-015058
- Error deploying EJB {0}. It references an initial context factory {1} which enables object based security, which is not needed and is not supported by message driven beans.
- Category:
- EJB
- Cause:
- Error deploying EJB {0}. It references an initial context factory {1} which enables object based security, which is not needed and is not supported by message driven beans.
- Action:
- Do not setup MDBs to use an initial context that enables object based security. For example, use a weblogic.jndi.WLInitialContextFactory instead.
- BEA-015059
- Error deploying EJB {0}. The JMS connection factory with JNDI name {1} is object-based-security enabled and is not supported by MDBs.
- Category:
- EJB
- Cause:
- The JMS connection factory with the JNDI name {1} is object-based-security enabled and is not supported by MDBs.
- Action:
- Do not use object-based-security enabled JMS connection factorys for MDBs.
- BEA-015060
- Activation exception for stateful session ben {0}: {1}.
- Category:
- EJB
- Cause:
- An exception occurred while reading or processing the state of the bean.
- Action:
- Please check the exception for the exact error message.
- BEA-015061
- Exception reading the replicated state of stateful session bean {0}: {1}.
- Category:
- EJB
- Cause:
- An exception occurred on reading the replicated state of stateful session bean, for example an application upgrade may have introduced a Java serialization incompatibility on the bean state between old and new versions.
- Action:
- Please check the exception for the exact error message.
- BEA-015062
- Exception on creating replicated stateful session bean {0}: {1}.
- Category:
- EJB
- Cause:
- An exception occurred on creating replicated stateful session bean
- Action:
- Please check the exception for the exact error message.
- BEA-015063
- {0} following exceptions were suppressed in logging during a message processing inside Message-Driven Bean. The last occurrence of this exception has a timestamp {1}: {2} Exception is : {3}.
- Category:
- EJB
- Cause:
- This can happen if the onMessage method of the MDB consecutively throws exceptions.
- 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-015064
- An exception occurred in replication for stateful EJB {0} on {1} partition shutting down: {2}
- Category:
- EJB
- Cause:
- An exception occurred in replication for stateful EJB {0} on {1} partition shutting down: {2}
- Action:
- Please check the exception for the exact error message.
- BEA-015065
- An error occurred on check server or partition state during deactivation of stateful EJB {0}: {1}
- Category:
- EJB
- Cause:
- An error occurred on check server or partition state during deactivation of stateful EJB {0}: {1}
- Action:
- Please check the exception for the exact error message.
- BEA-015066
- An exception occurred while cleaning up replicas states locally for stateful EJB {0} on {1} partition shutting down: {2}
- Category:
- EJB
- Cause:
- An exception occurred while cleaning up replicas states locally for stateful EJB {0} on {1} partition shutting down: {2}
- Action:
- Please check the exception for the exact error message.
- BEA-015067
- Ensure bean states are replicated for stateful EJB {0} on {1} partition shutting down
- Category:
- EJB
- Cause:
- see message detail
- Action:
- No action required
- BEA-015068
- Local replicas clean up for stateful EJB {0} on {1} partition shutting down
- Category:
- EJB
- Cause:
- see message detail
- Action:
- No action required
- BEA-015073
- Message-Driven Bean {0} is configured with unknown activation-config-property name {1}
- Category:
- EJB
- Cause:
- see message detail
- Action:
- Check if activation-config-property is correct in ejb-jar.xml or annotation.
- BEA-015074
- The Message-Driven Bean {0} has connected to JMS destination {1} and the MDB is in a suspended state, message processing will start when the MDB is in an active state."
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015075
- EJB deployment state {0} for {1}
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015076
- EJB module {0} created.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015077
- Activated descriptor {0} update for EJB module {1}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015078
- The current server is becoming the primary server for replica {1} of EJB {0}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015079
- The current server is becoming the secondary server for replica {1} of EJB {0}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-015080
- The current server is becoming the secondary server for replica {1} of EJB {0}.
- Category:
- EJB
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-040010
- JMSServer "{0}" configured {1,choice,0#no session pools|1#1 session pool|2#{1} session pools}.
- Category:
- JMS
- Cause:
- This message indicates the number of session pools that were configured or deployed for the JMSServer while processing the configuration file.
- Action:
- No action is required.
- BEA-040014
- Failed to start JMSServer. JMS is shutting down.
- Category:
- JMS
- Cause:
- The JMS server failed to initialize.
- Action:
- Modify the configuration and restart the server file. Then reboot the system. There should be earlier messages that indicate the cause of the failure.
- BEA-040015
- JMS shutdown is complete.
- Category:
- JMS
- Cause:
- JMS has been shut down, either at the request of the administrator or due to configuration errors.
- Action:
- No action is required.
- BEA-040017
- JMSServer "{0}" connection factory JNDI binding failed, {1}. JMS is shutting down.
- Category:
- JMS
- Cause:
- An error was found when binding the connection factory to a JNDI name during configuration.
- Action:
- Modify the configuration and restart the server file. Then reboot the system.
- BEA-040018
- Could not obtain a replicated or non-replicated InitialContext from the default provider, {0}.
- Category:
- JMS
- Cause:
- An error was encountered when binding a JMS Server to a JNDI name during configuration.
- Action:
- Modify the configuration and restart the server file. Then reboot the server.
- BEA-040019
- JMSServer "{0}" failed to bind to JNDI name: {1}.
- Category:
- JMS
- Cause:
- An error was encountered when binding a JMS Server to a JNDI name during configuration.
- Action:
- Modify the configuration and restart the server file. Then reboot the system.
- BEA-040024
- JMSServer "{0}" byte threshold for destination {1} has been exceeded.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040025
- JMSServer "{0}" byte threshold condition for destination {1} has cleared.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040026
- JMSServer "{0}" message threshold for destination {1} has been exceeded.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action
- BEA-040027
- JMSServer "{0}" message threshold condition for destination {1} has cleared.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040028
- JMSServer "{0}" byte threshold for the server has been exceeded.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040029
- JMSServer "{0}" byte threshold for server has cleared.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040030
- JMSServer "{0}" message threshold for the server has been exceeded.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040031
- JMSServer "{0}" message threshold for the server has cleared.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040068
- JMSServer "{0}" error occurred while unregistering destination {1}.
- Category:
- JMS
- Cause:
- Look for earlier messages that might explain the error.
- Action:
- Contact My Oracle Support.
- BEA-040069
- JMSServer "{0}" error occurred while unregistering producer {1}.
- Category:
- JMS
- Cause:
- Look for earlier messages that might explain the error.
- Action:
- Contact My Oracle Support.
- BEA-040070
- JMSServer "{0}" error occurred while unregistering connection {1}.
- Category:
- JMS
- Cause:
- Look for earlier messages that might explain the error.
- Action:
- Contact My Oracle Support.
- BEA-040071
- JMSServer "{0}" error occurred while unregistering session {1}.
- Category:
- JMS
- Cause:
- Look for earlier messages that might explain the error.
- Action:
- Contact My Oracle Support.
- BEA-040072
- JMSServer "{0}" error occurred while unregistering consumer {1}.
- Category:
- JMS
- Cause:
- Look for earlier messages that might explain the error.
- Action:
- Contact My Oracle Support.
- BEA-040089
- JMSServer "{0}". JMS messages in store ({1}) were migrated from version {2} to 600.
- Category:
- JMS
- Cause:
- Message migration happens automatically when starting JMS and an old store exists.
- Action:
- No action is required.
- BEA-040090
- Deployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.
- Category:
- JMS
- Cause:
- This message indicates the number of default connection factories deployed while processing the configuration file.
- Action:
- No action is required.
- BEA-040095
- JMSServer "{0}". Store I/O failure, {1}.
- Category:
- JMS
- Cause:
- There is no more of file space, a disk failure occurred, or a database failure occurred.
- Action:
- Restart the database, if applicable, and restart JMS.
- BEA-040107
- Undeployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.
- Category:
- JMS
- Cause:
- This message indicates the number of default connection factories that were undeployed.
- Action:
- No action is required.
- BEA-040108
- User connection factory "{0}" is started.
- Category:
- JMS
- Cause:
- The specified user connection factory has been started.
- Action:
- No action is required.
- BEA-040109
- JMSServer "{0}" is started.
- Category:
- JMS
- Cause:
- The specified JMS Server has been started.
- Action:
- No action is required.
- BEA-040113
- JMSServer "{0}", Opening file store "{1}" in directory "{2}". Starting scan of {3,choice,0#0 files|1#1 file|2#{3} files} totaling {4} bytes.
- Category:
- JMS
- Cause:
- A JMS server has opened its persistent file store and is about to scan its contents for messages.
- Action:
- No action is required.
- BEA-040119
- Failed to deploy a JMS connection factory "{0}" due to {1}.
- Category:
- JMS
- Cause:
- The JMS connection factory failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new connection factory.
- Action:
- Modify the configuration and restart the server file. Then reboot the system.
- BEA-040120
- Failed to bind JMS connection factory "{0}" with its JNDI name due to {1}.
- Category:
- JMS
- Cause:
- This is a JNDI failure.
- Action:
- Modify the configuration and restart the server file. Then reboot the system.
- BEA-040121
- JMSServer "{0}". Cannot be deployed on multiple servers.
- Category:
- JMS
- Cause:
- A JMS Server was deployed on more than one WebLogic Server instance, and this is not allowed.
- Action:
- Change the configuration file and reboot the system.
- BEA-040122
- Failed to deploy JMS Server "{0}" due to {1}.
- Category:
- JMS
- Cause:
- The JMS server failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server.
- Action:
- Modify the configuration and restart the server file. Then reboot the system.
- BEA-040123
- Failed to start JMS Server "{0}" due to {1}.
- Category:
- JMS
- Cause:
- A JNDI failure occurred, or there was a failure when starting destinations, server session pools and/or connection consumers.
- Action:
- Modify the configuration and restart the server file. Then reboot the system.
- BEA-040124
- JMSServer "{0}". Failed to create JMS server session pool "{1}" due to {2}.
- Category:
- JMS
- Cause:
- The JMS server session pool failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server session pool.
- Action:
- Modify the configuration and restart the server file. Then reboot the system.
- BEA-040125
- JMSServer "{0}". Failed to create JMS connection consumer "{1}" due to {2}.
- Category:
- JMS
- Cause:
- The JMS connection consumer failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS connection consumer.
- Action:
- Modify the configuration and restart the server file. Then reboot the system.
- BEA-040127
- Failed to create JMS multicast socket due to {0}.
- Category:
- JMS
- Cause:
- The JMS multicast socket failed to initialize.
- Action:
- Reboot the system.
- BEA-040215
- JMS server "{0}". Cannot set "{1}" to -1 when paging is enabled. The value of the attribute remains unchanged.
- Category:
- JMS
- Cause:
- This is caused by an invalid configuration.
- Action:
- Disable paging before setting this value to -1.
- BEA-040305
- JMS service is initialized and in standby mode.
- Category:
- JMS
- Cause:
- The initialization phase of the JMS service is completed and the JMS service is in standby mode.
- Action:
- No action is required.
- BEA-040306
- JMS service is active now.
- Category:
- JMS
- Cause:
- The activation phase of the JMS service is completed, and the JMS service is in active mode.
- Action:
- No action is required.
- BEA-040307
- JMS service is suspending gracefully.
- Category:
- JMS
- Cause:
- The JMS service has started the suspension phase. No new work will be accepted and JMS Service will attempt to complete all existing work before it brings itself to standby mode.
- Action:
- No action is required.
- BEA-040308
- JMS service is suspending.
- Category:
- JMS
- Cause:
- The JMS service has started the suspension phase. No new work will be accepted and all the existing work will be terminated immediately before the JMS service brings itself to standby mode.
- Action:
- No action is required.
- BEA-040321
- JMSServer "{0}" is resuming.
- Category:
- JMS
- Cause:
- The JMSServer "{0}" is resuming.
- Action:
- No action is required.
- BEA-040324
- JMSServer "{0}" is suspending.
- Category:
- JMS
- Cause:
- The JMSServer "{0}" is suspending.
- Action:
- No action is required.
- BEA-040325
- JMSServer "{0}" is suspended.
- Category:
- JMS
- Cause:
- The JMSServer "{0}" is suspended.
- Action:
- No action is required.
- BEA-040351
- ExpiredJMSMessage JMSMessageID={0} > {1} {2} </ExpiredJMSMessage
- Category:
- JMS
- Cause:
- A message has been expired and the policy is to log the message header fields and messages properties so that they are printed.
- Action:
- No action is required.
- BEA-040352
- ExpiredJMSMessage JMSMessageID={0} > {1} </ExpiredJMSMessage
- Category:
- JMS
- Cause:
- A message has been expired and the policy is to log the message header fields so that they are printed.
- Action:
- No action is required.
- BEA-040353
- ExpiredJMSMessage JMSMessageID={0} > {1} </ExpiredJMSMessage
- Category:
- JMS
- Cause:
- A message has been expired and the policy is to log the messages properties so that they are printed.
- Action:
- No action is required.
- BEA-040354
- ExpiredJMSMessage JMSMessageID={0} > </ExpiredJMSMessage
- Category:
- JMS
- Cause:
- A message has been expired and the policy is to log only the MessageId, or there are no matching message header fields or message properties.
- Action:
- No action is required.
- BEA-040359
- Distributed Destination "{0}", member "{1}" is not associated with a physical destination.
- Category:
- JMS
- Cause:
- This was caused by a onfiguration error.
- Action:
- Modify the configuration and restart the server.
- BEA-040368
- The following exception has occurred:
- Category:
- JMS
- Cause:
- An error condition has occurred.
- Action:
- Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help in debugging an existing problem.
- BEA-040370
- Linked Exception -----------
- Category:
- JMS
- Cause:
- An error condition was reported.
- Action:
- No action is required.
- BEA-040371
- JMSServer "{0}" JMS server session pool is invalid and has not been started "{1}". Exception is "{2}".
- Category:
- JMS
- Cause:
- The server session pool is invalid because it has an invalid Connection Factory or Listener.
- Action:
- Edit the JMS session pool, verify that it has valid attributes, and reboot the server. Alternatively, delete the session pool and add a new valid JMS session pool.
- BEA-040372
- JMSServer "{0}" error occurred while unregistering the runtime MBean, {1}.
- Category:
- JMS
- Cause:
- Unable to contact the Administration Server or unable to find the runtime MBean.
- Action:
- No action is required.
- BEA-040373
- Could not find a license for JMS. Please contact Oracle to get a license.
- Category:
- JMS
- Cause:
- Unable to get a license for JMS.
- Action:
- Contact your Oracle sales representative to get a license.
- BEA-040376
- Destination {0} has been paused for new message production.
- Category:
- JMS
- Cause:
- A Production Pause request was issued for the specified destination.
- Action:
- No action is required.
- BEA-040377
- Destination {0} has been resumed for new message production.
- Category:
- JMS
- Cause:
- A Production Resume request was issued for the specified destination.
- Action:
- No action is required.
- BEA-040378
- Destination {0} has been paused for insertion of messages from in-flight work completion.
- Category:
- JMS
- Cause:
- An Insertion Pause request was issued for the specified destination.
- Action:
- No action is required.
- BEA-040379
- Destination {0} has been resumed for insertion of messages from in-flight work completion.
- Category:
- JMS
- Cause:
- An Insertion Resume request was issued for the specified destination.
- Action:
- No action is required.
- BEA-040380
- Destination {0} has been paused for consumption.
- Category:
- JMS
- Cause:
- A Consumption Pause request has been issued for the specified destination.
- Action:
- No action is required.
- BEA-040381
- Destination {0} has been resumed for consumption.
- Category:
- JMS
- Cause:
- A Consumption Resume request has been issued for the specified destination.
- Action:
- No action is required.
- BEA-040382
- JMSServer {0} has been paused for new message production.
- Category:
- JMS
- Cause:
- A Production Pause request was issued for the specified JMSServer.
- Action:
- No action is required.
- BEA-040383
- JMSServer {0} has been resumed for new message production.
- Category:
- JMS
- Cause:
- A Production Resume request was issued for the specified JMSServer.
- Action:
- No action is required.
- BEA-040384
- JMSServer {0} has been paused for insertion of messages from in-flight work completion.
- Category:
- JMS
- Cause:
- An Insertion Pause request was issued for the specified JMS server.
- Action:
- No action is required.
- BEA-040385
- JMSServer {0} has been resumed for insertion of messages from in-flight work completion.
- Category:
- JMS
- Cause:
- An Insertion Resume request has been issued for the specified JMS server.
- Action:
- No action is required.
- BEA-040386
- JMSServer {0} has been paused for consumption.
- Category:
- JMS
- Cause:
- A Consumption Pause request has been issued for the specified JMS server.
- Action:
- No action is required.
- BEA-040387
- JMSServer {0} has been resumed for consumption.
- Category:
- JMS
- Cause:
- A Consumption Resume request has been issued for the specified JMS server.
- Action:
- No action is required.
- BEA-040404
- Foreign JMS Server "{0}" is started.
- Category:
- JMS
- Cause:
- The specified foreign JMS server was started.
- Action:
- No action is required.
- BEA-040405
- Failed to bind an entity of Foreign JMS Server "{0}" with their JNDI names due to {1}.
- Category:
- JMS
- Cause:
- This was caused by a JNDI failure.
- Action:
- Modify the JMS module descriptor of the corresponding application and redeploy the application.
- BEA-040406
- Distributed destination "{0}" is started.
- Category:
- JMS
- Cause:
- The specified distributed destination was started.
- Action:
- No action is required.
- BEA-040407
- Default connection factory "{0}" with its JNDI name "{1}" is started.
- Category:
- JMS
- Cause:
- The specified default connection factory was started.
- Action:
- No action is required.
- BEA-040408
- Failed to bind default connection factory "{0}" with its JNDI name "{1}" due to {2}.
- Category:
- JMS
- Cause:
- This was caused by a JNDI failure.
- Action:
- Modify the configuration and restart the server file. Then reboot the system.
- BEA-040409
- FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} {2} </FailedJMSMessage
- Category:
- JMS
- Cause:
- A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.
- Action:
- No action is required.
- BEA-040410
- FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage
- Category:
- JMS
- Cause:
- A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.
- Action:
- No action is required.
- BEA-040411
- FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage
- Category:
- JMS
- Cause:
- A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.
- Action:
- No action is required.
- BEA-040412
- FailedJMSMessage for store-and-forward: JMSMessageID={0} > </FailedJMSMessage
- Category:
- JMS
- Cause:
- A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log only the MessageId. Alternatively, there are no matching message header fields or message properties.
- Action:
- No action is required.
- BEA-040420
- The JMS transaction branch {1} for destination {0} was administratively committed.
- Category:
- JMS
- Cause:
- This was caused by an administrative action.
- Action:
- No action is required.
- BEA-040421
- An administrative request to commit the JMS transaction branch {1} on destination {0} failed with the following exception. {2}
- Category:
- JMS
- Cause:
- The cause of the failure may be indicated by the exception provided in the error message.
- Action:
- The transaction may be in an invalid state to allow commit processing. Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
- BEA-040422
- The JMS transaction branch {1} for destination {0} was administratively rolled back.
- Category:
- JMS
- Cause:
- This was caused by an administrative action.
- Action:
- No action is required.
- BEA-040423
- An administrative request to rollback the JMS transaction branch {1} on destination {0} failed with the following exception. {2}
- Category:
- JMS
- Cause:
- The cause of the failure may be indicated by the exception provided in the error message.
- Action:
- Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
- BEA-040430
- The "UserTransactionsEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.
- Category:
- JMS
- Cause:
- A deprecated attribute was used.
- Action:
- Use the XAConnectionFactoryEnabled attribute instead.
- BEA-040431
- The "XAServerEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.
- Category:
- JMS
- Cause:
- A deprecated attribute is used.
- Action:
- Use the XAConnectionFactoryEnabled attribute instead.
- BEA-040442
- While attempting to bind JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI.
- Category:
- JMS
- Cause:
- Some other entity has already bound this JNDI name globally.
- Action:
- Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
- BEA-040443
- While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer globally bound into JNDI under any name.
- Category:
- JMS
- Cause:
- Some other entity has already bound this JNDI name globally.
- Action:
- Determine the owner the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
- BEA-040444
- While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised globally.
- Category:
- JMS
- Cause:
- A network connection between the local server and the Administration Server may have gone down.
- Action:
- Make sure that network connectivity is working properly and that the Administration Server is reachable.
- BEA-040445
- While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer locally bound into JNDI under any name.
- Category:
- JMS
- Cause:
- Some other entity has already bound this JNDI name locally.
- Action:
- Determine the owner of the currently bound JNDI name and remove it if it should not be there or change the JNDI name of this destination so that it does not conflict with the existing one.
- BEA-040446
- While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised locally.
- Category:
- JMS
- Cause:
- A network connection between the local server and the Administration Server may have gone down.
- Action:
- Make sure that network connectivity is working properly and that the Administration Server is reachable.
- BEA-040447
- While attempting to bind the JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI locally.
- Category:
- JMS
- Cause:
- Some other entity has already bound this JNDI name locally.
- Action:
- Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
- BEA-040448
- JMSFileStoreMBean has been deprecated, and has been replaced with FileStoreMBean. The JMSFileStoreMBean "{0}" has been replaced in the configuration with a FileStoreMBean with the same name.
- Category:
- JMS
- Cause:
- A deprecated MBean was replaced in the configuration.
- Action:
- No action is required.
- BEA-040449
- JMSJDBCStoreMBean has been deprecated, and has been replaced with JDBCStoreMBean. The JMSJDBCStoreMBean "{0}" has been replaced in the configuration with a JDBCStoreMBean with the same name.
- Category:
- JMS
- Cause:
- A deprecated MBean was replaced in the configuration.
- Action:
- No action is required.
- BEA-040450
- The "PagingStore" attribute on the JMSServerMBean "{0}" has been deprecated. It is being replaced in the configuration with the new "PagingDirectory" attribute.
- Category:
- JMS
- Cause:
- A deprecated MBean attribute was replaced in the configuration.
- Action:
- No action is required.
- BEA-040451
- The PagingStore attribute on the JMSServerMBean {0} has been deprecated. Since it currently refers to a JMSJDBCStoreMBean, and paging to a JDBC store is not supported, the JMS server will page messages to its local working directory.
- Category:
- JMS
- Cause:
- A deprecated MBean attribute was replaced in the configuration.
- Action:
- No action is required.
- BEA-040452
- The server session pool feature has been deprecated, and it will be removed in an upcoming release. New applications should use message-driven beans (MDBs) instead.
- Category:
- JMS
- Cause:
- A deprecated feature was detected in the configuration.
- Action:
- Plan to replace use of server session pools in your application.
- BEA-040453
- The BytesPagingEnabled and MessagesPagingEnabled parmeters on the JMSServer {0} have been deprecated. These parameters are now ignored. The MessageBufferSize parameter should be used to configure paging in this release.
- Category:
- JMS
- Cause:
- A deprecated parameter was encountered.
- Action:
- Plan to use the new MessageBufferSize to control paging.
- BEA-040455
- Flow control has been enabled on JMS server "{0}" because memory is low
- Category:
- JMS
- Cause:
- Too much memory is being used.
- Action:
- Either increase the amount of memory available to the server, or decrease the MessageBufferSize parameter on the JMS server so that fewer messages remain in memory.
- BEA-040456
- An entity of type "{3}" with name "{2}" in JMS module "{0}" is not targeted. There is no subdeployment with name "{1}" in the configuration repository (config.xml). Therefore, this entity will not exist anywhere in the domain.
- Category:
- JMS
- Cause:
- The entity of the given name and type in the given JMS module does not have a corresponding subdeployment in the configuration repository (config.xml). In order for this entity to exist in the domain, it must be targeted with a sub-deployment element.
- Action:
- Add a sub-deployment stanza to the appropriate deployment descriptor in config.xml. This will either be a jms-system-resource for a system module, or an app-deployment for a stand-alone JMS deployable module. If the JMS module is inside a Java EE application (an EAR file), then you must add the sub-deployment stanza to the subdeployment that represents this JMS module in the Java EE application. You do not necessarily have to target the subdeployment yet. Simply adding the subdeployment with no targets will remove this warning. However, if you wish for this entity to exist somewhere in your domain you must target the sub-deployment.
- BEA-040457
- The Template named "{1}" element of Distributed Destination "{0}" is not supported and hence ignored. Please consider using a Uniform Distributed Destination.
- Category:
- JMS
- Cause:
- An unsupported attribute JMSTemplate is used in a Distributed Destination.
- Action:
- Use a Uniform Distributed Destination instead.
- BEA-040458
- Unable to unprepare {0} in module {1} due to {2}.
- Category:
- JMS
- Cause:
- The prepared entity could not unprepare itself in a failure case.
- Action:
- Refer to the available exception for more information.
- BEA-040459
- Unable to deactivate {0} in module {1} due to {2}.
- Category:
- JMS
- Cause:
- The activated entity could not deactivate itself in a failure case.
- Action:
- Refer to the available exception for more information.
- BEA-040460
- Unable to close the JMS component of module {0} due to {1}.
- Category:
- JMS
- Cause:
- The JMS component could not close itself.
- Action:
- Refer to the available exception for more information.
- BEA-040461
- Unable to deactivate {0} in module {1} due to {2}.
- Category:
- JMS
- Cause:
- The activated entity could not deactivate itself in a failure case.
- Action:
- Refer to the available exception for more information.
- BEA-040464
- Unable to destroy {0} in module {1} due to {2}.
- Category:
- JMS
- Cause:
- The initialized entity could not destroy itself in a failure case.
- Action:
- More information may be available from the exception.
- BEA-040467
- Unable to deactivate {0} in module {1} due to {2}.
- Category:
- JMS
- Cause:
- The activated entity could not deactivate itself in a failure case.
- Action:
- More information may be available from the exception.
- BEA-040470
- Unable to deactivate {0} in module {1} due to {2}.
- Category:
- JMS
- Cause:
- The activated entity could not deactivate itself during dynamic deletion.
- Action:
- More information may be available from the exception.
- BEA-040475
- The destination {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.
- Category:
- JMS
- Cause:
- Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases, a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
- Action:
- Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
- BEA-040476
- The destination {0} does not have an associated quota object. The setting of messagesMaximum to {1} will have no effect.
- Category:
- JMS
- Cause:
- Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
- Action:
- Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
- BEA-040477
- An error occurred while unbinding a remote JNDI object from local JNDI name "{0}". The exception encountered was {1}.
- Category:
- JMS
- Cause:
- There may be an error in the JNDI subsystem. See the exception for more information.
- Action:
- Check the exception message for more detail.
- BEA-040478
- The JMS subsystem could not deploy or undeploy the default JMS connection factories due to {0}.
- Category:
- JMS
- Cause:
- There may be an error in the JNDI subsystem. See the exception for more information.
- Action:
- Check the exception message for more detail.
- BEA-040479
- The system failed to roll back an added connection consumer of name {0}. The exception received was {1}.
- Category:
- JMS
- Cause:
- See the exception for more information.
- Action:
- Check the exception message for more detail.
- BEA-040480
- The system failed to remove a connection consumer of name {0}. The exception received was {1}.
- Category:
- JMS
- Cause:
- See the exception for more information.
- Action:
- Check the exception message for more detail.
- BEA-040490
- {0} {1} has a conflicting name attribute value, which is now changed to have a unique name with its JMSServer name. The new destination-name attribute now holds the original name value.
- Category:
- JMS
- Cause:
- A name conflict has been detected during upgrade for JMS destinations, maybe because in WebLogic Server versions prior to 9.2, more than one destination was allowed to have the same name, as long as the destinations belonged to different JMS servers.
- Action:
- Ensure that destinations are created with their name decorated with the target JMS server name to avoid conflict.
- BEA-040491
- A {0} {1} with multiple targets has been split into multiple deployments one for each unique target.
- Category:
- JMS
- Cause:
- A JMS Deployment found with multiple unique targets configured.
- Action:
- In WebLogic Server versions prior to 9.2, both JMSConnectionFactory and ForeignJMSServer were allowed to be targeted to more than one server, cluster, or both. During upgrade of this configuration to WebLogic Server 9.2, these configuration entities are split into more than one entity, one for each unique target.
- BEA-040494
- An error occurred while shutting down the JMS server {0}: {1}.
- Category:
- JMS
- Cause:
- See the detail message.
- Action:
- The server should still shut down normally. No action is required.
- BEA-040496
- The template {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.
- Category:
- JMS
- Cause:
- Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
- Action:
- Please consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
- BEA-040497
- The template {0} does not have an associated quota object. The setting of MessagesMaximum to {1} will have no effect.
- Category:
- JMS
- Cause:
- Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
- Action:
- Consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
- BEA-040498
- An error occurred while forwarding a message for distributed destination member {0}: {1}
- Category:
- JMS
- Cause:
- There may be a temporary network problem, or one of the members of the cluster may be unavailable.
- Action:
- See the detail message.
- BEA-040499
- An error occurred while pushing messages to a JMS client: {0}
- Category:
- JMS
- Cause:
- There may be a network failure.
- Action:
- The JMS protocol will recover automatically from such a problem eventually. Check for networking issues or crashed clients.
- BEA-040500
- Unable to deactivate entity "{0}" in module "{1}" due to {2}.
- Category:
- JMS
- Cause:
- The activated entity could not rollback the proposed targeting change.
- Action:
- More information may be available from the exception.
- BEA-040501
- Unable to roll back targeting change of the entity "{0}" in module "{1}" due to {2}.
- Category:
- JMS
- Cause:
- The changed entity could not roll back in a failure case.
- Action:
- More information may be available from the exception.
- BEA-040502
- While attempting to change the targeting of JMS module "{0}", an error occurred while activating the change. The exception returned is: {1}
- Category:
- JMS
- Cause:
- The JMS module failed to activate a prepared change during a targeting update.
- Action:
- More information may be available from the exception.
- BEA-040503
- The delivery mode override value of destination "{0}" hosted on JMS server "{1}" has been changed from {2} to {3}.
- Category:
- JMS
- Cause:
- During the upgrade process, a configuration was detected that would force all messages through the given destination to be non-persistent. Therefore, the upgrade process made that override explicit.
- Action:
- Review your application code and configuration. If you need a behavior other than the one that the upgrade process chose, you can modify the resulting configuration using the DeliveryMode parameter of the OverridesParams of the destination, or with the HasStore or AllowsPersistentDowngrade parameters of the JMS server on which the destination is targeted.
- BEA-040504
- While attempting to add an entity with name "{0}", an error occurred while trying to convert the old style entity to the new style entity. The error was "{1}".
- Category:
- JMS
- Cause:
- See the description of the exception that occurred for more information on the cause of this failure.
- Action:
- Take appropriate action based on the determined cause.
- BEA-040505
- The JMS module named "{0}" inside application "{1}" does not have a sub-deployment stanza named "{0}". Without such a stanza, no entities inside the module will be deployed, since the subdeployments inside of the sub-deployment stanza named "{0}" control where JMS entities inside this module are targeted.
- Category:
- JMS
- Cause:
- When a JMS module is inside an EAR file, the targeting information for entities inside that module are nested within a sub-deployment named after the name of the JMS module found in the weblogic-application.xml file of the EAR file. If no sub-deployment exists with the name of the JMS module, then no targeted entities inside the module will become available. This is usually an oversight on the part of the administrator.
- Action:
- Add a sub-deployment stanza with the name of the JMS module as specified in the weblogic-application.xml file to the app-deployment stanza. Nested inside that sub-deployment, you can target the entities in the module as you normally would.
- BEA-040506
- The JMS store-and-forward (SAF) forwarder has successfully connected to the remote destination "{0}".
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040507
- The JMS store-and-forward (SAF) forwarder failed to connect to the remote destination "{0}", because of {1}.
- Category:
- JMS
- Cause:
- This is either due to a configuration error, a network failure, or the remote destination being temporarily unavailable.
- Action:
- Check the configuration, network connection, or remote destination.
- BEA-040508
- BridgeDestinationMBean has been deprecated. The BridgeDestination "{0}" has been replaced in the configuration with a JMSBridgeDestination with the same name.
- Category:
- JMS
- Cause:
- A deprecated MBean is being replaced in the configuration.
- Action:
- No action is required.
- BEA-040509
- Failed to ${1} JMS Server "{0}" because the earlier attempt to ${2} was failed.
- Category:
- JMS
- Cause:
- This error occurred during deployment of the JMS server.
- Action:
- Fix any deployment errors related to this JMS server.
- BEA-040510
- While attempting to rename a connection factory named "{0}", an error occurred while attempting to establish a JNDI listener. The cause was {1}.
- Category:
- JMS
- Cause:
- There was an error while attempting to establish a JNDI listener. The description of the cause may provide more information about the true cause of the error.
- Action:
- The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
- BEA-040511
- The system is waiting to unbind connection factory "{0}". An attempt is being made to change the JNDI name of this connection factory from "{1}" to "{2}".
- Category:
- JMS
- Cause:
- An attempt is being made to unbind a connection factory from a JNDI name in order to dynamically change the JNDI from one name to another. This message will repeat every twenty seconds for five minutes.
- Action:
- No action is required.
- BEA-040512
- An attempt is being made to change the JNDI name of connection factory "{0}" from "{1}" to "{2}". The system has waited to unbind "{1}" for five minutes. The new JNDI name "{2}" may or may not be bound properly.
- Category:
- JMS
- Cause:
- The connection factory was not fully unbound after five minutes. Some error may have occurred while attempting to unbind this connection factory.
- Action:
- In order to maintain the integrity of the connection factory it is recommended you untarget and retarget the connection factory that failed. Otherwise, the connection factory is in an indeterminate state.
- BEA-040513
- While attempting to rename a connection factory named "{0}", an error occurred while attempting to remove a JNDI listener. The cause was {1}.
- Category:
- JMS
- Cause:
- There was an error while attempting to remove a JNDI listener. The description of the cause may provide more information about the true cause of the error.
- Action:
- The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
- BEA-040514
- While attempting to rename a connection factory named "{0}" an error occurred in the JNDI listener. The error was {1}
- Category:
- JMS
- Cause:
- While attempting to dynamically change the JNDI name of a connection factory, a JNDI error occurred. The error itself will tell more about the cause of this failure.
- Action:
- The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
- BEA-040515
- A failured occured while attempting to unregister an InterceptionPoint, {0}.
- Category:
- JMS
- Cause:
- An exceptoin coccurred while attempting to unregister an InterceptionPoint. The error will provide more details about the cause of this failure.
- Action:
- The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
- BEA-040520
- One or more Weighted Distributed Destination (WDD) resources were detected in JMS configuration module "{1}": {0}. This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.
- Category:
- JMS
- Cause:
- Deprecated resource was used.
- Action:
- Use the Uniform Distributed Destination instead.
- BEA-040521
- The JMS resource "{0}" that you are trying to create in module "{1}" is a Weighted Distributed Destination (WDD). This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.
- Category:
- JMS
- Cause:
- A deprecated resource is trying to create.
- Action:
- Use the Uniform Distributed Destination instead.
- BEA-040522
- Failed to update distributed destination membership in a multi-domain environment: {0}.
- Category:
- JMS
- Cause:
- Cross domain security configuration is not properly set up.
- Action:
- Check the security configuration, especially the cross-domain security configuration if the cross domain security feature is enabled. Contact My Oracle support if the problem persists.
- BEA-040523
- One or more properties - "{4}", specified by {3} with JNDI name {1} defined in the application {0} deployed to {2} are not recognized by WebLogic Server and are ignored. To change the log level of this message, see the {5} property of {3}.
- Category:
- JMS
- Cause:
- One or more properties set for a {3} are not recognized by WebLogic Server.
- Action:
- If the intent of the application is to specify properties recognized by WebLogic Server, check for a misspelling of the property name(s).
- BEA-040524
- The subdeployment "{0}" used by an entity of type {1} with name "{2}" in JMS module "{3}" defined in {4}, has no target specified in the configuration repository (config.xml). A subdeployment without a valid target will not be deployed.
- Category:
- JMS
- Cause:
- The subdeployment "{0}" is not targeted, so the entity was ignored by the JMS module defined in {4}.
- Action:
- Specifiy a valid target for the subdeployment "{0}".
- BEA-040525
- Shut down JMS connections for resource group {0}.
- Category:
- JMS
- Cause:
- JMS connections for a resource group were shut down because the resource group has been shut down.
- Action:
- No action is required.
- BEA-040526
- JMS Module "{3}" deployed to {4} defines an entity of type {1} with name "{2}" with default targeting enabled. There is no JMS server having a persistent store with distribution policy "{0}" available in {4} to host the entity. The destination "{2}" will be hosted when a JMS server having a persistent store with distribution policy "{0}" is configured in {4}.
- Category:
- JMS
- Cause:
- For hosting the entity of type "{1}" with name "{2}" , with default targeting enabled defined in the JMS module "{3}" deployed to {4}, there should be exactly one JMS server with persistent store having distribution policy "{0}" defined in {4}. However, no candidate JMS server was found to host that entity.
- Action:
- Create a JMS server in {4} with a persistent store having the distribution policy set to "{0}".
- BEA-040527
- JMS Module "{2}" deployed to {3} defines an entity of type {0} with name "{1}" with default targeting enabled. There is no SAF agent having a persistent store with distribution policy "Distributed" available in {3} to host the entity. The destination "{1}" will be hosted when a SAF agent having a persistent store with distribution policy "Distributed" is configured in {3}.
- Category:
- JMS
- Cause:
- For hosting the entity of type "{0}" with name "{1}" , with default targeting enabled defined in the JMS module "{2}" deployed to {3}, there should be exactly one SAF agent with persistent store having distribution policy "Distributed" defined in {3}. However, no candidate SAF agent was found to host that entity.
- Action:
- Create an SAF agent in {3} with a persistent store having the distribution policy set to "Distributed".
- BEA-040528
- Start JMS service for partition [{0}]
- Category:
- JMS
- Cause:
- The partition is starting up.
- Action:
- No action is required.
- BEA-040529
- Shut down JMS service for partition [{0}].
- Category:
- JMS
- Cause:
- The partition is shutting down.
- Action:
- No action is required.
- BEA-040530
- JMS Destination Definition with JNDI name "{0}" defined in the application "{1}" deployed to {2} will not be hosted as there is no JMS Server having a persistent store with distribution policy "Distributed" available.
- Category:
- JMS
- Cause:
- For hosting the JMS destination definition with JNDI name "{0}" defined in the application "{1}" there must be at least one JMS server having a persistent store with distribution policy "Distributed" However, no JMS server is available in {2} to host the JMS destination definition.
- Action:
- Create a JMS server in {2} with a persistent store having a distribution policy set to "Distributed".
- BEA-040531
- One or more JMS Servers - "{0}" were not considered to host the entity {3} deployed to "{2} " as they do not have a persistence store with distribution policy set to "{1}".
- Category:
- JMS
- Cause:
- The JMS Servers do not have a persistent store with a persistent store set to the indicated value.
- Action:
- No action is required.
- BEA-040532
- One or more JMS Servers - "{0}" were not considered to host the destination defined by JMS Destination Definition with JNDI name "{2}" defined in the application "{3}" deployed to {4} as they do not have a persistence store with distribution policy set to "{1}".
- Category:
- JMS
- Cause:
- The JMS servers do not have a persistent store with the distribution policy set to the indicated value.
- Action:
- No action is required.
- BEA-040533
- The application "{0}" uses a JMS Destination Definition to create a WebLogic JMS {4} with JNDI name "{1}", its generated configuration name is "{3}" and its generated JMS module name is "{2}".
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040534
- Topic "{0}" in module "{1}" has a subscription limit of "{2}" configured.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-040535
- Topic "{0}" in module "{1}" has illegal subscription limit value "{2}" configured via command line system property "{3}". Values must be a positive integer. The limit will be ignored.
- Category:
- JMS
- Cause:
- Subscription limit values must be a positive integer.
- Action:
- Modify system property to specify a legal value and restart the WebLogic server.
- BEA-040536
- Multiple {1} or/and SAF {1} have been configured with the same name ("{0}") within the same security realm. This potentially may cause those destinations to have the same security policy even if different security policies are specified.
- Category:
- JMS
- Cause:
- Potential configuration error.
- Action:
- Modify the configuration to uniquely name all destinations, including both regular destinations and SAF destinations.
- BEA-040537
- No more than one {1} or SAF {1} has been configured with the same name ("{0}") within the same security realm. A previously detected warning condition has been cleared.
- Category:
- JMS
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-045002
- An error occurred while binding the remote JNDI object to the local JNDI name "{0}".
- Category:
- JMSExceptions
- Cause:
- The local JNDI name that is attempting to bind to may not be valid.
- Action:
- Check the JNDI name to see if its syntax is correct.
- BEA-045028
- The messages threshold for the JMS server {0} has been exceeded for more than one hour.
- Category:
- JMSExceptions
- Cause:
- The threshold of the JMS server was exceeded.
- Action:
- Verify that the messages are being consumed and that sufficient memory is available.
- BEA-045029
- The messages threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.
- Category:
- JMSExceptions
- Cause:
- The messages threshold of the JMS server was exceeded.
- Action:
- Verify that the messages are being consumed and that sufficient memory is available.
- BEA-045030
- The bytes threshold for the JMS server {0} has been exceeded for more than one hour.
- Category:
- JMSExceptions
- Cause:
- The bytes threshold of the JMS server was exceeded.
- Action:
- Verify that the messages are being consumed and that sufficient memory is available.
- BEA-045031
- The bytes threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.
- Category:
- JMSExceptions
- Cause:
- The bytes threshold of the JMS server was exceeded.
- Action:
- Verify that the messages are being consumed and that sufficient memory is available.
- BEA-045032
- While attempting to create destination {1} in module {2} the JMS server {0} could not be found.
- Category:
- JMSExceptions
- Cause:
- The JMS server may be shutting down or may not have completed startup.
- Action:
- Deploy the module again once the JMS server has completed startup.
- BEA-045039
- An attempt was made to add a JMS entity of an unknown type {1} in the module {0}.
- Category:
- JMSExceptions
- Cause:
- The JMS module given to the update was invalid. It contained an unknown type.
- Action:
- Ensure that the JMS module is valid.
- BEA-045040
- While attempting to add a {1} named {2} in module {0}, an error occurred.
- Category:
- JMSExceptions
- Cause:
- A linked ModuleException will contain more detail about the cause of the failure.
- Action:
- Examine the linked exception, which will contain more information about the cause of this failure.
- BEA-045041
- An attempt was made to remove a JMS entity of an unknown type {1} in the module {0}.
- Category:
- JMSExceptions
- Cause:
- The JMS module given to the update was invalid. It contained an unknown type.
- Action:
- Ensure that the JMS module is valid.
- BEA-045042
- An error occurred while adding {1} to the JMS module {0}.
- Category:
- JMSExceptions
- Cause:
- See the linked exception for more detail.
- Action:
- The linked exception will contain more information about why this add operation failed.
- BEA-045043
- An error occurred while removing {1} from the JMS module {0}.
- Category:
- JMSExceptions
- Cause:
- See the linked exception for more detail.
- Action:
- The linked exception will contain more information about why this add operation failed.
- BEA-045045
- A subdeployment named {1} was not found in the module {0}.
- Category:
- JMSExceptions
- Cause:
- A subdeployment removal was attempted, but the subdeployment was unknown to the module.
- Action:
- Contact My Oracle Support.
- BEA-045047
- The SubDeploymentMBean {0} in deployment {1} can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue, topic or quota) has a sub-deployment-name element with value {0}
- Category:
- JMSExceptions
- Cause:
- The SubDeploymentMBean of the given name cannot be targeted to anything but a single JMS server because an element of the JMS module that points to that subdeployment can only be targeted to a single JMS server.
- Action:
- Modify the target of the subdeployment so that it only contains a single JMS server.
- BEA-045048
- The JMS server named {0} has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is {1}, and the template name is {2}. However, a JMSSystemResourceMBean of name {1} could not be found. The JMS server {0} will not boot until this problem has been fixed.
- Category:
- JMSExceptions
- Cause:
- The temporary template for a JMS server must come from a JMSSystemResourceMBean. A common mistake is to put the temporary template into an AppDeployment. However, because the temporary template must be owned by the administrator, all temporary templates must come from JMSSystemResourceMBeans, not AppDeployments.
- Action:
- Put the temporary template into a JMSSystemResource.
- BEA-045049
- JMS server {0} does not have a configured temporary template. However an attempt was made to create a temporary destination. This is not allowed.
- Category:
- JMSExceptions
- Cause:
- A JMS server without a configured temporary template was used to create a temporary destination. This usage is not allowed.
- Action:
- Create a JMSSystemResource that contains a template. Use that template as the temporary template for this JMS server.
- BEA-045050
- A destination named {3} has a jms-create-destination-identifier named {1}. However, another destination named {2} has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot both be located on the JMS server named {0}.
- Category:
- JMSExceptions
- Cause:
- Two destinations cannot both have the same jms-create-destination-identifier on the same JMS server, even if the two destinations are from different modules.
- Action:
- Either deploy the destination with the offending jms-create-destination-identifier to a different JMS server, or change the value of the jms-create-destination-identifier attribute.
- BEA-045051
- Two destinations with name {1} were deployed to the JMS server {0}.
- Category:
- JMSExceptions
- Cause:
- Two destinations with the same fully qualified name cannot be deployed to the same JMS server. This error should have been caught during the validation phase of the JMS module.
- Action:
- Contact My Oracle Support.
- BEA-045052
- An attempt was made to change the target of a JMS entity that cannot have its target changed. The entity has name "{0}". The original target has name "{1}". The proposed target has name "{2}"
- Category:
- JMSExceptions
- Cause:
- An attempt was made to change the target of an entity that cannot have its target changed dynamically.
- Action:
- Untarget a subdeployment and then retarget that subdeployment elsewhere. However, by doing so, the persistent state maintained for entities retargeted in this fashion will not be kept on the old target and may or may not be removed by the system.
- BEA-045054
- Cannot dynamically add member {1} to sistributed destination {0}.
- Category:
- JMSExceptions
- Cause:
- This member has either not been prepared yet or has already been removed.
- Action:
- Ensure that the distributed destination member is not removed and is in a prepared state.
- BEA-045055
- Cannot dynamically remove member {1} from distributed destination {0}.
- Category:
- JMSExceptions
- Cause:
- This member has either not been activated yet or is an invalid member.
- Action:
- Ensure that the distributed destination member is valid and is in an activated state.
- BEA-045060
- The JMS module named "{0}" is neither an AppDeployment nor a JMSSystemResource.
- Category:
- JMSExceptions
- Cause:
- An invalid application context was passed to a JMS module.
- Action:
- Contact My Oracle Support.
- BEA-045061
- An attempt was made to create a durable subscription on a queue named "{3}". The client identifier is "{0}", the subscriptionName is "{1}" and the selector is "{2}". Durable subscriptions may only be created on topics.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to create a durable subscription on a queue.
- Action:
- Do not attempt to create a durable subscription on a queue.
- BEA-045062
- There can be no more than one jms-interop-module element in the config.xml file.
- Category:
- JMSExceptions
- Cause:
- More than one jms-interop-module element was found in the config.xml file.
- Action:
- Do not attempt to define more than one jms-interop-module element in the config.xml file.
- BEA-045063
- The jms-interop-module must have name interop-jms and a descriptor file name jms/interop-jms.xml. This has name "{0}".
- Category:
- JMSExceptions
- Cause:
- An attempt was made to use a jms-interop-module with a name other than interop-jms.
- Action:
- Do not attempt to define a jms-interop-module element in the config.xml file with a name other than interop-jms.
- BEA-045064
- The target named "{1}" of a JMS module inside a deployment named "{0}" must be a WebLogic Server instance or a cluster. Instead, it is of type "{2}".
- Category:
- JMSExceptions
- Cause:
- An attempt was made to target a JMS module to an invalid type of target.
- Action:
- Do not attempt to target a JMS module to anything other than WebLogic Server instances or clusters. Any other type of target is not understood.
- BEA-045065
- A JMS module with fully qualified name "{1}" in an application named "{0}" does not have the proper hierarchy of targets. In particular, the subdeployment named "{2}" has a target "{3}" that is not a subtarget of any of the targets of "{0}". For example, the target "{3}" is not a subtarget of "{4}".
- Category:
- JMSExceptions
- Cause:
- A target of a subdeployment of a JMS module was not contained within the targets of the whole JMS module.
- Action:
- Ensure that the JMS module is targeted to a super-set of all the targets of the subdeployment, or retarget the subdeployment within the set of targets for the JMS module.
- BEA-045066
- The target named "{1}" of a JMS subdeployment named "{3}" inside a deployment named "{0}" must be a JMS server, WebLogic Server instance, or a cluster. Instead, it is of type {2}.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to target a JMS subdeployment to an invalid type of target.
- Action:
- Do not attempt to target a JMS subdeployment to anything other than JMS servers, WebLogic Server instances or clusters. Any other type of target is not understood.
- BEA-045067
- The field "destination-name" was set to "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}". The destination-name field of a distributed destination may only be set in the interop module.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to set the destination-name field of a distributed destination member type. This is only allowed in the interop module in order to accommodate older clients.
- Action:
- Change the name of the distributed destination member to the name of the physical queue or topic being referenced, and unset the destination-name field.
- BEA-045068
- The physical destination named "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}" does not exist.
- Category:
- JMSExceptions
- Cause:
- An attempt was made by a distributed destination member to reference a destination that does not exist. The physical destination referenced to by a distributed destination must already exist.
- Action:
- Create the physical destination before referring to it, or create the physical destination in the same edit session as the creation of the distributed destination member.
- BEA-045069
- The JMS module entity named "{2}" of type "{1}" does not exist in the JMSSystemResource "{0}".
- Category:
- JMSExceptions
- Cause:
- An attempt was made to reference a JMS module entity that does not exist in the specified JMSSytemResource.
- Action:
- Create the JMS module entity in the specified JMSSystemResource before referring to it.
- BEA-045070
- The configuration entity named "{2}" of type "{1}" does not exist in the domain "{0}".
- Category:
- JMSExceptions
- Cause:
- An attempt was made to reference a configuration entity that does not exist in the specified domain.
- Action:
- Create the configuration entity in the specified domain before referring to it.
- BEA-045071
- The JMS module entity named "{2}" of type "{1}" cannot be created in JMSSystemResource "{0}".
- Category:
- JMSExceptions
- Cause:
- The JMS module entity creation using the the JMSModuleHelper API failed. See the accompanying exception for details.
- Action:
- Resolve the problem identified by the accompanying exception, and retry the operation.
- BEA-045072
- The configuration entity named "{2}" of type "{1}" cannot be created in domain "{0}".
- Category:
- JMSExceptions
- Cause:
- The configuration entity creation using the JMSModuleHelper API failed. See the accompanying exception for details.
- Action:
- Resolve the problem identified by the accompanying exception, and retry the operation.
- BEA-045073
- The JMS module entity named "{2}" of type "{1}" cannot be deleted from JMSSystemResource "{0}".
- Category:
- JMSExceptions
- Cause:
- The JMS module entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.
- Action:
- Resolve the problem identified by the accompanying exception, and retry the operation.
- BEA-045074
- The configuration entity named "{2}" of type "{1}" cannot be deleted from the domain "{0}".
- Category:
- JMSExceptions
- Cause:
- The configuration entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.
- Action:
- Resolve the problem identified by the accompanying exception, and retry the operation.
- BEA-045075
- The JMS module managed entity named "{2}" of type "{1}" cannot be found in the JMSSytemResource "{0}" for modification.
- Category:
- JMSExceptions
- Cause:
- The JMS module entity modification using the JMSModuleHelper API failed. See the accompanying exception for details.
- Action:
- Resolve the problem identified by the accompanying exception, and retry the operation.
- BEA-045076
- An attempt was made to find and modify a JMS module entity named "{2}", of type "{1}", from the JMSSystemResource "{0}" using a null modifier.
- Category:
- JMSExceptions
- Cause:
- The JMSEntityModifier argument for the findAndModifyEntity() helper API cannot be null.
- Action:
- Use a valid weblogic.jms.extensions.JMSEntityModifer implementation as the modifier argument.
- BEA-045077
- The destination named "{0}" on the JMS server "{1}" would have caused the JMS server not to boot because the destination StoreEnabled value is true, but the JMS server does not have a store.
- Category:
- JMSExceptions
- Cause:
- This configuration does not work in older releases because the destination StoreEnabled value is true, but the JMS server does not have a store.
- Action:
- Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the StoreEnabled parameter on the destination.
- BEA-045078
- The destination named "{0}" on the JMS server "{1}" has a DeliveryParamsOverrides.DeliveryMode parameter set to persistent, but the JMS server does not have a store.
- Category:
- JMSExceptions
- Cause:
- Messages cannot be made persistent on this JMS server because it does not have a store.
- Action:
- Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the DeliveryParamsOverrides.DeliveryMode parameter.
- BEA-045079
- An attempt was made to send a persistent message to the destination "{0}" hosted on the JMS server "{1}". This JMS server does not have a store, so the quality of service requested is not available.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to send a persistent message to a destination hosted by a JMS server that does not have a store. Since the message cannot be persisted, this message cannot be sent at the required quality of service.
- Action:
- There is a parameter on the JMS server called "AllowsPersistentDowngrade". If this parameter is set to true, then persistent messages sent to this JMS server will be downgraded to non-persistent.
- BEA-045080
- The flow steps value {1} is larger than the flow interval value {2} in the connection factory "{0}". The flow steps value must be less than or equal to the flow interval value.
- Category:
- JMSExceptions
- Cause:
- This is an invalid configuration. The flow steps value must be less than the entire flow interval.
- Action:
- Modify the configuration of the connection factory to have the flow steps value be less than or equal to the flow interval.
- BEA-045081
- The SessionsMaximum attribute of a JMSSessionPoolMBean has the bad value {0}. The value should be -1 or a positive integer.
- Category:
- JMSExceptions
- Cause:
- This is an invalid configuration.
- Action:
- Modify the configuration of the JMSSessionPoolMBean.
- BEA-045082
- An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}".
- Category:
- JMSExceptions
- Cause:
- The naming exception should contain more information about why this operation failed.
- Action:
- See the attached naming exception message, which should have more information about why this operation failed.
- BEA-045083
- An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the local JNDI context.
- Category:
- JMSExceptions
- Cause:
- The naming exception should contain more information about why this operation failed.
- Action:
- See the attached naming exception, which should have more information about why this operation failed.
- BEA-045084
- An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the application JNDI context.
- Category:
- JMSExceptions
- Cause:
- The naming exception should contain more information about why this operation failed.
- Action:
- See the attached naming exception, which should have more information about why this operation failed.
- BEA-045085
- Could not find a license for JMS. Contact Oracle to obtain a license.
- Category:
- JMSExceptions
- Cause:
- A license for JMS was not obtained.
- Action:
- Contact Oracle to obtain a license.
- BEA-045086
- The jms-system-resource cannot have the name interop-jms.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to define a jms-system-resource with the name interop-jms.
- Action:
- Do not attempt to define a jms-system-resource element in the config.xml file with the name interop-jms.
- BEA-045087
- The JMS deployment "{0}" has the descriptor file name "{1}", which is reserved for internal use only.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to define a JMS deployment with the reserved file name "interop-jms.xml". This name is reserved by the system for use as the interop module.
- Action:
- Do not attempt to define a JMS deployment with the reserved name "interop-jms.xml" as its file name.
- BEA-045088
- The JMS module descriptor file "{1}" used by the JMS system resource "{0}" is illegal. Either the descriptor file name does not end with -jms.xml or the descriptor is being used by another JMS system resource in the configuration.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to define a JMS system resource with the illegal descriptor file name.
- Action:
- Do not attempt to define a jms-system-resource element in the config.xml file with the illegal descriptor file name.
- BEA-045089
- SAF error destination {2} of {1} is targeted to a different subdeployment from {0}.
- Category:
- JMSExceptions
- Cause:
- The configuration was invalid.
- Action:
- Correct the deployment descriptor.
- BEA-045090
- The error handling {1} configured for {0} does not exist in the module.
- Category:
- JMSExceptions
- Cause:
- The configuration was invalid.
- Action:
- Correct the deployment descriptor.
- BEA-045091
- One of the target ("{1}") of the subdeployment "{2}" for the imported destinations "{0}" is not a legal target type.
- Category:
- JMSExceptions
- Cause:
- The configuration was invalid.
- Action:
- Correct the configuration.
- BEA-045092
- Imported destinations "{0}": its subdeployment is targeted to a target ("{1}"), which is a receiving-only SAF agent.
- Category:
- JMSExceptions
- Cause:
- The configuration was invalid.
- Action:
- Correct the configuration.
- BEA-045093
- A UDQ named "{0}" was found in the JMS interop module. UDQs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDQ in that module.
- Category:
- JMSExceptions
- Cause:
- An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
- Action:
- Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
- BEA-045094
- A UDT named "{0}" was found in the JMS interop module. UDTs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDT in that module.
- Category:
- JMSExceptions
- Cause:
- An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
- Action:
- Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
- BEA-045095
- An SAF imported destinanation named "{0}" was found in the JMS interop module. SAF imported destinations were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF imported destinations in that module.
- Category:
- JMSExceptions
- Cause:
- An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
- Action:
- Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
- BEA-045096
- An SAF remote context named "{0}" was found in the JMS interop module. SAF remote contexts were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF remote context in that module.
- Category:
- JMSExceptions
- Cause:
- An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
- Action:
- Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
- BEA-045097
- An SAF error handlings named "{0}" was found in the JMS interop module. SAF error handlings were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF error handlings in that module.
- Category:
- JMSExceptions
- Cause:
- An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
- Action:
- Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
- BEA-045098
- There is a JMS system resource and an application deployment both named "{0}". The names of all JMS system resources and all application deployments must be different.
- Category:
- JMSExceptions
- Cause:
- Both a JMS system resource and an application deployment have the same name. This would cause similarly named resources in a JMS module descriptor file to have conflicting runtime names, and therefore is not allowed.
- Action:
- Change the name of either the JMS system resource or application deployment so that there is no name conflict.
- BEA-045099
- An attempt was made to create a temporary destination. However, no JMS server in the cluster is able to host temporary destinations. Ensure that at least one of the JMS servers in the cluster has the HostingTemporaryDestinations parameter set to true (which is the default).
- Category:
- JMSExceptions
- Cause:
- None of the JMS servers in the cluster are available for hosting temporary destinations.
- Action:
- Modify the HostingTemporaryDestinations parameter on at least one JMS server in the cluster. Note that in releases prior to 9.0, the default for the ability to host temporary destinations was false, while in 9.0 and beyond, the default for the ability to host temporary destinations is true.
- BEA-045100
- The createQueue or createTopic call was made with a null or zero length destination name.
- Category:
- JMSExceptions
- Cause:
- The createQueue or createTopic call must be made with the name of a destination to find.
- Action:
- Do not pass a null or zero length string to createQueue or createTopic.
- BEA-045101
- The destination name passed to the createTopic or createQueue "{0}" is invalid. If the destination name does not contain a "/" character, then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character, then the string before the "/" must be the name of a JMS server or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WebLogic Server instance will be returned.
- Category:
- JMSExceptions
- Cause:
- Either a distributed destination of the given name does not exist in the cluster to which the client is attached or the destination name passed to createTopic or createQueue does not contain a "/" character, or there is nothing before the "/" character.
- Action:
- Ensure that the distributed destination is available on the same cluster where the client is located, or format the destination name string properly.
- BEA-045102
- A destination named "{0}" was not found on WebLogic Server instance "{1}".
- Category:
- JMSExceptions
- Cause:
- An attempt was made to find a destination of a given name on a particular WebLogic Server instance. No destination of that name could be found on that WebLogic Server instance.
- Action:
- It is possible that the createTopic or createQueue call was routed to a WebLogic Server instance that does not contain a destination with the given name. The set of WebLogic Server instances where this request can be routed can be controlled by using a connection factory that is only targeted to WebLogic Werver instances that have destinations of the desired name.
- BEA-045103
- While trying to find a topic or a queue, the specific JMS server requested could not be found. The linked exception may contain more information about the reason for failure.
- Category:
- JMSExceptions
- Cause:
- A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.
- Action:
- The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.
- BEA-045104
- While trying to find a topic or a queue, the specific JMS server requested could not be found.
- Category:
- JMSExceptions
- Cause:
- A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.
- Action:
- Ensure that the JMS server requested exists in the configuration of the cluster to which the client is attached.
- BEA-045105
- While trying to find a topic or a queue, communication failed with the specific JMS server requested. The linked exception may contain more information about the reason for failure.
- Category:
- JMSExceptions
- Cause:
- A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not communicate with the JMS server of that name.
- Action:
- The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.
- BEA-045106
- A destination named "{0}" was found. However, the requested destination was of type "{1}", and the destination found was not of that type.
- Category:
- JMSExceptions
- Cause:
- Either the user called createTopic and the destination found was a queue or the user called createQueue and the destination found was a topic.
- Action:
- Ensure that the destination name requested is of the correct type.
- BEA-045107
- A communication failure occurred while attempting to remove a durable subscription. The linked exception may contain more details about the cause of the failure.
- Category:
- JMSExceptions
- Cause:
- While attempting to remove a durable subscription a communication failure occurred.
- Action:
- Check on the status of WebLogic Server instance where the destination which the durable subscription refers to resides. Check the linked exception for more information about the cause of this failure.
- BEA-045108
- The JMS system does not understand request ID {0}.
- Category:
- JMSExceptions
- Cause:
- An invalid request ID was presented to the front end manager.
- Action:
- If this condition persists, contact My Oracle Support.
- BEA-045109
- A foreign server named "{0}" was found which does not have a connection URL specified. However, it contains a "{2}" named "{1}" that has the same local and remote JNDI name value "{3}". This is an invalid configuration and is not allowed.
- Category:
- JMSExceptions
- Cause:
- The user has configured a foreign server without a connection URL and has either a foreign connection factory or a foreign destination with both the local and remote JNDI name matching.
- Action:
- Ensure that either the foreign server has a connection URL to the foreign server or that the local and remote JNDI names are different.
- BEA-045110
- The JMS resource named "{0}" has incorrect targeting information. This resource has the default-targeting-enabled attribute set to true and has a valid sub-deployment-name value specified.
- Category:
- JMSExceptions
- Cause:
- A JMS resource cannot have both default targeting enabled and a subdeployment name specified.
- Action:
- Ensure that either the default targeting is enabled or that the valid subdeployment name is specified.
- BEA-045111
- The JMS resource named "{0}" has incorrect targeting information. A JMS physical destination cannot have the default-targeting-enabled attribute set.
- Category:
- JMSExceptions
- Cause:
- A JMS physical destination cannot have the default-targeting-enabled attribute set.
- Action:
- Ensure that the default-targeting-enabled attribute is not set for the physical destinations.
- BEA-045112
- The flow minimum value {1} is larger than or equal to the flow maximum value {2} in connection factory "{0}". The flow minimum value must be less than the flow maximum value.
- Category:
- JMSExceptions
- Cause:
- This is an invalid configuration. The flow minimum value must be less than the flow maximum value.
- Action:
- Modify the configuration of the connection factory to have the flow minimum value be less than the flow maximum value.
- BEA-045113
- JMS distributed destination forward request denied for the destination named "{1}". Reason "{0}".
- Category:
- JMSExceptions
- Cause:
- JMS distributed destinations may not have been fully initialized.
- Action:
- If forwarding does not begin after a few minutes, contact My Oracle Support.
- BEA-045114
- Failed to unsubscribe the subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription without a topic object.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a client ID policy of UNRESTRICTED.
- Action:
- Use the weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a client ID policy of UNRESTRICTED. If using a pre-AS11gR1PS3 Java client, upgrade to a AS11gR1PS3 client. If using a non-Java client, clean up the durable subscription from the Administration Console or use WebLogic Scripting Tool (WLST) commands or scripts.
- BEA-045115
- The SubDeploymentMBean {0} in JMS Module {1} contains a standalone queue, topic or quota that can only be targeted to a single non-clustered JMS Server or to a clustered JMS Server with Singleton distribution-policy.
- Category:
- JMSExceptions
- Cause:
- The SubDeploymentMBean of the given name cannot be targeted to anything but a single non-clustered JMS Server or to a clustered JMS Server with Singleton distribution-policy.
- Action:
- Modify the target of the subdeployment so that it contains only a single non-clustered JMS Server or a clustered JMS Server with Singleton distribution-policy.
- BEA-045116
- The Replicated Distributed Topic (RDT) cannot have its members hosted by a cluster targeted JMSServer. The RDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.
- Category:
- JMSExceptions
- Cause:
- The RDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.
- Action:
- Modify the target of the subdeployment so that it does not contain a cluster targeted JMSServer.
- BEA-045119
- The current JMS message is a Unit-of-Order (UOO) or Unit-of-Work (UOW) message that cannot be sent to the distributed destination (DD) "{0}". This DD has its UnitOfOrderRouting attribute configured to "Hash", which does not support UOO/UOW messages when either a DD is configured in a Resource Group scope, or a DD is hosted on a JMS server that is targeted to a cluster. To fix this issue: change the UnitOfOrderRouting attribute to "PathService" and ensure a Path Service is configured and running in the current scope.
- Category:
- JMSExceptions
- Cause:
- A Unit-of-Order (UOO) or Unit-of-Work (UOW) JMS message cannot be sent to distributed destinations that have at least one member hosted by a cluster-targeted JMS Server, but the specified Distributed destination has one or more of its members hosted by a cluster-targeted JMS server. The current JMS message is a Unit-of-Order (UOO) or Unit-of-Work (UOW) message that cannot be sent to the distributed destination (DD). This DD has its UnitOfOrderRouting attribute configured to "Hash", which does not support UOO/UOW messages when either a DD is configured in a Resource Group scope, or a DD is hosted on a JMS server that is targeted to a cluster.
- Action:
- To fix this issue: change the UnitOfOrderRouting attribute to "PathService" and ensure a Path Service is configured and running in the current scope.
- BEA-045120
- An injected JMSContext cannot be used when there is neither a transaction nor a valid request scope.
- Category:
- JMSExceptions
- Cause:
- An injected JMSContext was used when there is neither a transaction or a valid request scope.
- Action:
- Change your application so that it only uses an injected JMSContext when there is either a transaction or a valid request scope.
- BEA-045121
- Exception encountered whilst injecting a JMSContext: unable to create InitialContext: {0}
- Category:
- JMSExceptions
- Cause:
- An exception was encountered whilst injecting a JMSContext: unable to create InitialContext: {0}
- Action:
- Review the cause of the exception, fix the problem and try again.
- BEA-045122
- Error injecting JMSContext: unable to lookup connection factory with lookup name {0}. The exception was {1}.
- Category:
- JMSExceptions
- Cause:
- An error was encountered whilst injecting a JMSContext: unable to lookup connection factory with lookup name {0}. The exception was {1}.
- Action:
- Review the cause of the exception, fix the problem and try again.
- BEA-045123
- The method {0} is not permitted on a container-managed (injected) JMSContext.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to call the method {0} on a container-managed (injected) JMSContext. The use of this method is not permitted.
- Action:
- Amend the application so that it does not call methods that are not permitted on a container-managed (injected) JMSContext. Then try again.
- BEA-045124
- A session mode of SESSION_TRANSACTED is not permitted on a container-managed (injected) JMSContext.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to use a container-managed (injected) JMSContext which specified a session mode of SESSION_TRANSACTED. This session mode is not permitted because the JMS specification forbids the use of the commit method on a container-managed (injected) JMSContext.
- Action:
- Amend the code which declares the injected JMSContext to use a different value of JMSSessionMode, or omit the JMSSessionMode annotation.
- BEA-045125
- WebLogic JMS extension methods are only available on injected JMSContext objects if the JMS provider being used is WebLogic JMS
- Category:
- JMSExceptions
- Cause:
- The application injected a JMSContext for a foreign JMS provider, cast it to weblogic.jms.client.JMSContextInternal and called a method defined on that interface.
- Action:
- Amend the code to remove the cast to weblogic.jms.client.JMSContextInternal and the call to any methods on that interface.
- BEA-045126
- WebLogic JMS extension methods are only available on injected JMSContext objects if the JMS provider being used is WebLogic JMS
- Category:
- JMSExceptions
- Cause:
- The application injected a JMSContext for a foreign JMS provider, cast it to weblogic.jms.extensions.WLJMSContext and called a method defined on that interface.
- Action:
- Amend the code to remove the cast to weblogic.jms.extensions.WLJMSContext and the call to any methods on that interface.
- BEA-045127
- The application "{1}" has defined a resource using {2} Definition with JNDI name "{0}". There is, however, an object already bound to JNDI using that name.
- Category:
- JMSExceptions
- Cause:
- The JNDI name used by {1} Definition is already bound to JNDI.
- Action:
- Define the resource with a different JNDI name.
- BEA-045128
- The application "{1}" has defined duplicate resources using {2} Definition with JNDI name "{0}", but the duplicate resources defined by the application are not compatible.
- Category:
- JMSExceptions
- Cause:
- The application has defined duplicate resources that are not compatible.
- Action:
- Fix the duplicate resources defined by {2} Definition and redeploy the application.
- BEA-045129
- {0} in an application.xml and classes outside of a module, is allowed to define a resource only in java:global and java:app namespaces. the application "{1}" has, however, defined a {0} with the name "{2}", which is not valid.
- Category:
- JMSExceptions
- Cause:
- An environment entry declared in the application.xml descriptor and classes outside of a module must specify a JNDI name in the namespace java:app or java:global.
- Action:
- Define the {0} resource in one of the allowed JNDI namespaces.
- BEA-045130
- The application "{1}" has defined a {0} resource with name "{2}" in a namespace that is not a well-defined namespace by the Java EE specification. The {0} resource is allowed only in one of the JNDI namespaces - java:global, java:app, java:module and java:comp.
- Category:
- JMSExceptions
- Cause:
- An invalid JNDI namespace was used to define a {0} resource.
- Action:
- Define the {0} resource in one of the allowed JNDI namespaces.
- BEA-045131
- The application "{0}" has specified one or more properties to define a {1} resource. The value set for a property specified by {2} does not, however, match the value expected by WebLogic.
- Category:
- JMSExceptions
- Cause:
- The value set for a property does not match the value expected by WebLogic,
- Action:
- Find the nested exception for more details and correct the configuration.
- BEA-045132
- The application "{0}" has defined a {1} resource using {2} and specified a property "{3}" with value "{4}", which is not the expected type for that property.
- Category:
- JMSExceptions
- Cause:
- An unexpected type was used for the property.
- Action:
- Check all properties in the defined resource.
- BEA-045133
- The Uniform Distributed Queue/Topic cannot be hosted by a cluster targeted JMSServer that does not have its distribution-policy set to Distributed. The UDQ/UDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.
- Category:
- JMSExceptions
- Cause:
- The Uniform Distributed Queue/Topic cannot be hosted by a cluster targeted JMSServer that does not have its distribution-policy set to Distributed. The UDQ/UDT named {0} in JMS Module {2} has its subdeployment {1} targeted to the Clustered JMSServer {3}.
- Action:
- Modify the target of the UDQ/UDT subdeployment so that it is targeted cluster targeted JMSServer with distribution-policy set to Distributed.
- BEA-045134
- JMS Module "{3}" deployed to {4} defines an entity of type {1} with name "{2}" and with default targeting option enabled. There are more than one JMS servers "{5}", having a persistent store with distribution policy "{0}" available in {4} to host the entity, which is not allowed.
- Category:
- JMSExceptions
- Cause:
- For hosting the entity of type {1} with name "{2}" , and with default targeting option enabled defined in the JMS module "{3}" deployed to {4}, there must be exactly one JMS server with persistent store having distribution policy "{0}" defined in "{4}", but more than one candidate JMS servers were found to host that entity.
- Action:
- Ensure that there is exactly one JMS server with store distribution policy "{0}" defined in scope {4} or use subdeployment to target the entity to the required JMS server.
- BEA-045135
- JMS Module "{2}" deployed to {3} defines an entity of type {0} with name "{1}" and with default targeting option enabled. There are more than one SAF agents "{4}", having a persistent store with distribution policy "Distributed" available in {3} to host the entity, which is not allowed.
- Category:
- JMSExceptions
- Cause:
- For hosting the entity of type "{0}" with name "{1}" , with default targeting enabled defined in the JMS module "{2}" deployed to "{3}", there should be exactly one SAF agent with persistent store having distribution policy "Distributed" defined in "{3}", but more than one candidate SAF agents were found to host that entity.
- Action:
- Ensure that there is exactly one SAF agent with persistent store having distribution policy "Distributed" defined in scope {3} or use subdeployment to target the entity to the required SAF agent.
- BEA-045136
- The JMS Server with name "{0}" specified by the property jms-server-name of {1} with JNDI name "{2}" in application {3} is not available in the {4}.
- Category:
- JMSExceptions
- Cause:
- The client application has specified a JMS Server with name {0}, which is not available in the {4}.
- Action:
- If the intent of the application is to target the {5} to a particular JMS Server, specify a valid JMS Server using property jms-server-name.
- BEA-045137
- Weighted (Non-Uniform) Distributed Destination/Destinations configured under a JMS module "{0}" are not supported because JMS module "{0}" exists under "{1}". Weighted (Non-Uniform) Distributed Destination are not supported in the Resource Group or Resource Group Template scopes.
- Category:
- JMSExceptions
- Cause:
- Weighted (Non-Uniform) Distributed Destination/Destinations are not supported under a Resource Group or Resource Group Template scope.
- Action:
- Correct the configuration.
- BEA-045138
- A Uniform Distributed Topic "{0}" in JMS module "{1}" is configured with a forwarding policy "Replicated". This policy is unsupported in a Resource Group or Resource Group Template scope and the JMS module "{1}" is configured under "{2}"
- Category:
- JMSExceptions
- Cause:
- A Uniform Distributed Topic with forwarding policy "replicated" was used under a Resource Group or Resource Group Template deployment scope.
- Action:
- Configure the topic to use a "Partitioned" policy or configure a non-distributed topic instead.
- BEA-045139
- The JMS Server with name "{0}" specified by the property jms-server-name of JMS Destination Definition with JNDI name "{1}" in application {2} has a persistent store with distribution policy "{3}". A JMS Server with a store having distribution policy "Distributed" is only allowed to host the destination defined by JMS Destination Definition.
- Category:
- JMSExceptions
- Cause:
- The client application has specified JMS Server with name {0}, having a store with distribution policy {3}, which is not allowed to host a destination defined by a JMS Destination Definition.
- Action:
- Specify a JMS werver that has distribution policy "Distributed" for property jms-server-name of a JMS Destination Definition.
- BEA-045140
- Error using a JMSContext object that was injected using @Inject. The JNDI name {0} specified in the @JMSConnectionFactory annotation does not refer to a javax.jms.ConnectionFactory or javax.jms.XAConnectionFactory, it refers to a {1}.
- Category:
- JMSExceptions
- Cause:
- An error was encountered while using a JMSContext object that was injected using @Inject. The lookup name {0} specified in the @JMSConnectionFactory annotation does not refer to a javax.jms.ConnectionFactory or javax.jms.XAConnectionFactory, it refers to a {1}.
- Action:
- Correct the lookup name specified using @JMSConnectionFactory and try again.
- BEA-045141
- Error using a JMSContext object that was injected using @Inject. Unable to look up the connection factory using the JNDI name {0} that was specified in the @JMSConnectionFactory annotation.
- Category:
- JMSExceptions
- Cause:
- An error was encountered while using a JMSContext object that was injected using @Inject. The @JMSConnectionFactory annotation specified that the connection factory to be used could be obtained using the JNDI name (0), but an error occurred while looking up the connection factory.
- Action:
- Correct the lookup name that was specified using @JMSConnectionFactory and try again.
- BEA-045142
- WebLogic Server has detected a deprecated JMS Interop Module in your configuration. This feature will be removed in a future release. Oracle recommends that you take appropriate measures to remove dependencies on JMS Interop Modules.
- Category:
- JMSExceptions
- Cause:
- A deprecated JMS Interop Module was used in the configuration.
- Action:
- Remove JMS Interop Modules from the configuration.
- BEA-045143
- The Subdeployment "{0}" in JMS Module "{1}" contains a standalone Queue or standalone Topic that can only be targeted to the JMS Server/JMS Servers that references a store configured with "Singleton" distribution-policy.
- Category:
- JMSExceptions
- Cause:
- A SubDeployment is being referenced by a singleton style resource such as a standalone Queue or standalone Topic, so it must target to the JMS Server/JMS Servers that references a Store configured with "Singleton" distribution-policy. Note that a asubdeployment under a Resource Group or Resource Group Template scope must be targeted to a single JMS Server or to a single SAF Agent.
- Action:
- Modify the target of the subdeployment so that it contains only JMS server/JMS servers that reference a Store configured with "Singleton" distribution-policy. Note the you must target a subdeployment to single JMS Server or single SAF Agent under a Resource Group or Resource Group Template scope.
- BEA-045144
- The SubDeployment "{0}" in JMS Module "{1}" contains a Distributed Queue or Distributed Topic that can only be targeted to the JMS Server/JMS Servers that references a Store configured with "Distributed" distribution-policy.
- Category:
- JMSExceptions
- Cause:
- The SubDeployment of the given name cannot be targeted to anything but the JMS Server/JMSServers that references a Store that is configured with "Distributed" distribution-policy.
- Action:
- Modify the target of the subdeployment so that it contains only JMS server/JMS servers that references a Store with "Distributed" distribution-policy. Note the you must target a subdeployment to a single JMS Server or single SAF Agent under a Resource Group or Resource Group Template scope.
- BEA-045145
- The URL "{0};" references a WebLogic MT partition, but WebLogic JMS Client for Microsoft .NET does not support partitions.
- Category:
- JMSExceptions
- Cause:
- WebLogic MT partitions are not supported by WebLogic JMS Client for Microsoft .NET.
- Action:
- Do not use a partition-scoped url. Use a domain-level provider url instead.
- BEA-045146
- Destination "{0};" with JNDI name "{1};" is scoped to a WebLogic MT partition, but WebLogic JMS Client for Microsoft .NET do not support partitons.
- Category:
- JMSExceptions
- Cause:
- WebLogic MT partitions are not supported by WebLogic JMS Client for Microsoft .NET.
- Action:
- Do not use a partition-scoped destination. Use a domain-level destination instead.
- BEA-045147
- ConnectionFactory "{0};" is scoped to a WebLogic MT partition, but WebLogic JMS Client for Microsoft .NET does not support partitons.
- Category:
- JMSExceptions
- Cause:
- WebLogic MT partitions are not supported by WebLogic JMS Client for Microsoft .NET.
- Action:
- Do not use a partition-scoped connection factory. Use a domain-level connection factory instead.
- BEA-045148
- JMS Destination Definition with JNDI name "{0}" defined in the application "{1}" which is deployed to {2} will not be hosted as there are more than one JMS Servers having a persistent store with distribution policy "Distributed" available.
- Category:
- JMSExceptions
- Cause:
- For hosting the JMS Destination Definition with JNDI name "{0}" defined in the application "{1}" there must be at least one JMS server with a persistent store with distribution policy "Distributed" available in {2} to host the JMS destination. More than one JMS servers are available, however, as candidates in {2} to host the destination defined by the JMS Destination Definition.
- Action:
- Ensure that there is exactly one JMS server available to host the JMS Destination Definition or specify a JMS Server having distribution policy "Distributed" using the property "jms-server-name" to host the destination defined by the JMS Destination Definition on the specified JMS server.
- BEA-045149
- The application "{0}" has defined a {1} resource with name "{3}" using {2} in an application client module "{4}" and specified a resource adapter "{5}".
- Category:
- JMSExceptions
- Cause:
- A {2} in an application client module specifying a resource adapter is not allowed.
- Action:
- Update the application client module to be compliant.
- BEA-045150
- The target named "{1}" of an SAF imported destination named "{3}" inside a deployment named "{0}" must be an SAF agent, WebLogic Server instance, or a cluster. Instead, it is of type {2}.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to target an SAF imported destination to an invalid type of target.
- Action:
- Do not attempt to target an SAF imported destination to anything other than JMS servers, ServerMBean or ClusterMBean. Any other type of target is not understood.
- BEA-045151
- The target named "{1}" of an SAF imported destination named "{3}" inside a deployment named "{0}" must be an SAF agent. Instead, it is of type {2}.
- Category:
- JMSExceptions
- Cause:
- An attempt was made to target an SAF imported destination to an invalid type of target.
- Action:
- Do not attempt to target an SAF imported destination to anything other than JMS servers. Any other type of target is not understood.
- BEA-045152
- The JMS Module "{1}" deployed to {2} defines a Foreign Server with name "{0}" and is targeted to subdeployment {3}. The subdeployment {3} is, however, targeted to a JMS Server with distribution policy "Singleton", which is not allowed to be used as a target for a Foreign Server.
- Category:
- JMSExceptions
- Cause:
- A Foreign Server is not allowed to be targeted to a subdeployment that has a JMS Server with distribution policy "Singleton".
- Action:
- Change the target of the subdeployment to have a JMS Server with distribution policy "Distributed" used by the Foreign Server or use default targeting.
- BEA-045153
- The JMS resource with JNDI name "{2}" defined using {0} by the application "{1}" does not have proper hierarchy of targets. "{3}" specified by property jms-server-name is not a subtarget of "{4}".
- Category:
- JMSExceptions
- Cause:
- The JMS resource with JNDI name "{2}" defined using {0} by the application "{1}" does not have proper hierarchy of targets. "{3}" specified by property jms-server-name is not a subtarget of "{4}".
- Action:
- Specify a JMS Server for property jms-server-name which is available in the same hierarchy as that of the application deployment.
- BEA-045154
- A Uniform Distributed Destination can only be targeted to a JMS Server that is in the same Resource Group or Resource Group Template scope as the uniform distributed destination. JMS Server "{0}" is not in the same scope as the destination.
- Category:
- JMSExceptions
- Cause:
- A Uniform Distributed Destination can only be targeted to a JMS Server that is in the same Resource Group or Resource Group Template scope as the uniform distributed destination. JMS Server "{0}" is not in the same scope as the destination.
- Action:
- Target the Uniform Distributed Destination to JMS Server defined in the same Resource Group/Resource Group Template scope as the uniform distributed destination.
- BEA-045155
- There is scope conflict. Either a naming context is attached to a pre-12.2.1 WebLogic Server but the scope type is Resource Group or Resource Group Template (the Domain scope type is the only valid type in this case), or a naming context is attached to a partition but the scope type is Domain or a Resource Group Template (the Resource Group scope type is the only supported type in this case).
- Category:
- JMSExceptions
- Cause:
- There is scope conflict. Either a naming context is attached to a pre-12.2.1 WebLogic Server but the scope type is Resource Group or Resource Group Template (the Domain scope type is the only valid type in this case), or a naming context is attached to a partition but the scope type is Domain or a Resource Group Template (the Resource Group scope type is the only supported type in this case).
- Action:
- When accessing resource group template or domain level configuration ensure that the specified naming context is attached to a domain level scope.Also, when accessing either resource group or resource group template configuration, ensure that the naming context is attached to WebLogic 12.2.1 or greater server.
- BEA-045156
- Could not find partition name in the given "Context" Object.
- Category:
- JMSExceptions
- Cause:
- Could not find partition name in the given "Context" Object.
- Action:
- Verify valid partition name is attached to the "Context" Object.
- BEA-045157
- {0} named "{1} " does not exist in the {2} scope.
- Category:
- JMSExceptions
- Cause:
- {0} named "{1} " does not exist in the {2} scope.
- Action:
- Specify a {0} which exists for deleting the same.
- BEA-045158
- A {0} named "{1} " does not exist in the Resource Group or Resource Group Template {2}.
- Category:
- JMSExceptions
- Cause:
- A {0} named "{1} " does not exist in the Resource Group or Resource Group Template {2}.
- Action:
- Specify a {0} which exists.
- BEA-045159
- A {0} "{1}" does not exist under {2}.
- Category:
- JMSExceptions
- Cause:
- A {0} "{1}" does not exist under {2}.
- Action:
- Specify a correct scope name, partition name and scope type.
- BEA-045160
- The Target name "{0}" is not allowed in {1} scope. Target name must be null in Resource Group/Resource Group Template scope and It should not be null for Domain scope.
- Category:
- JMSExceptions
- Cause:
- The Target name "{0}" is not allowed in {1} scope. Target name must be null in Resource Group/Resource Group Template scope and It should not be null for Domain scope.
- Action:
- Specify a valid target.
- BEA-045161
- Parameter {0} can't be null or empty.
- Category:
- JMSExceptions
- Cause:
- Parameter {0} can't be null or empty.
- Action:
- Specify a valid {0}.
- BEA-045162
- Operation "{0}" cannot be invoked in Resource Group or Resource Group Template scope.
- Category:
- JMSExceptions
- Cause:
- Operation "{0}" cannot be invoked in Resource Group or Resource Group Template scope.
- Action:
- Operation "{0}" is not allowed in current scope. Please verify your configuration.
- BEA-045163
- Targets of Uniform Distributed Destination deployment overlap. JMS Server named: " {0} " is been identified twice as potential JMSServer for hosting the Uniform Distributed Destionation's members under the Uniform Distributed.
- Category:
- JMSExceptions
- Cause:
- Weblogic Internal Error.
- Action:
- An Uniform Destionation can be targeted to single JMS Server.Please verify the configuration.
- BEA-045164
- Invalid partition name: the given partition Name {0} does not exist under {1}.
- Category:
- JMSExceptions
- Cause:
- Invalid partition name: the given partition Name {0} does not exist under {1}.
- Action:
- Verify whether partition name exist in given scope {1}.
- BEA-045165
- Object-based security is enabled on the JMS connection factory with JNDI name "{0}", therefore it can only be used by a 12.2.2.1.0 or later client.
- Category:
- JMSExceptions
- Cause:
- Object-based security is enabled on the JMS connection factory with JNDI name "{0}", therefore it can only be used by a 12.2.2.1.0 or later client.
- Action:
- Use another JMS connection factory whose Security Policy is ThreadBased.
- BEA-045166
- The InitialContextFactory {0} is not supported by Foreign Server.
- Category:
- JMSExceptions
- Cause:
- The InitialContextFactory {0} is not supported by Foreign Server.
- Action:
- Do not use this InitialContextFactory {0} because it is not supported by Foreign Server.
- BEA-045167
- The proposed JNDI name {0} for destination {1} is already bound by another object of type {2}. {3}
- Category:
- JMSExceptions
- Cause:
- TBD
- Action:
- TBD
- BEA-045168
- Connection is closed because {0} is shutting down.
- Category:
- JMSExceptions
- Cause:
- The associated ResourceGroup or Partition is coming down.
- Action:
- No action is required.
- BEA-045169
- The method "{0}" is not supported in {1} scope. The scope type should be Resource Group.
- Category:
- JMSExceptions
- Cause:
- The method "{0}" is not supported in {1} scope. The scope type should be Resource Group.
- Action:
- Specify a valid scope.
- BEA-045170
- A JMS module has an incorrectly configured store-and-forward (SAF) error handler named "{0}". The error handler is configured with a "Redirect" error handling policy, and this policy requires an explicitly configured error destination in the error handler, where the error destination must not be the same as any of the destinations that use the error handler.
- Category:
- JMSExceptions
- Cause:
- The module configuration was invalid.
- Action:
- Correct the module configuration.
- BEA-050000
- {0} is an obsolete property. Use {1} to create the context instead.
- Category:
- JNDI
- Cause:
- Property {0} is obsolete. However, this property name can still be used to retrieve the property value.
- Action:
- Use property {1} instead of {0} in the future.
- BEA-050001
- WLContext.close() was called in a different thread than the one in which it was created.
- Category:
- JNDI
- Cause:
- The threads used to create and close the context are different. As a result, the context entries associated with the creating thread might not be cleaned up.
- Action:
- Close the context in the creating thread.
- BEA-050002
- Cannot replicate the object that is bound in the JNDI under the name {0}.
- Category:
- JNDI
- Cause:
- A non-serializable object cannot be serialized.
- Action:
- If the object was not intended to be replicated, set the replicate bindings to false. If the object should be replicated to all nodes in the cluster, ensure that the object is serializable or externalizable.
- BEA-050003
- Cannot create initial context. Reason: {0}
- Category:
- JNDI
- Cause:
- Initial context cannot be created.
- Action:
- Check the exception in the message body.
- BEA-050004
- Unable to bind. Reason: {0}
- Category:
- JNDI
- Cause:
- This was unable to bind.
- Action:
- Check the exception in the message body.
- BEA-050005
- Unable to unbind. Reason: {0}
- Category:
- JNDI
- Cause:
- This was unable to unbind.
- Action:
- Check the exception in the message body.
- BEA-050006
- An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.
- Category:
- JNDI
- Cause:
- An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.
- Action:
- Ensure that the possibility of premature retirement of the application version is either tolerated or handled properly. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_EXTERNAL_LOOKUP to "true" when performing lookup of the versioned object.
- BEA-050007
- An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.
- Category:
- JNDI
- Cause:
- An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.
- Action:
- Ensure that usages of the global resource by multiple application versions do not conflict. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_GLOBAL_RESOURCE_LOOKUP to "true" when performing lookup of the global resource.
- BEA-050008
- Illegal cross partition JNDI lookup detected for "{0}" from source context "{1}" to destination context "{2}".
- Category:
- JNDI
- Cause:
- An attempt was made to access the "{0}", the current partition is "{1}" but the target partition is "{2}". This cross partition should be taken care of by visibility control.
- Action:
- Either configure "{0}" to allow cross partition access or modify the application to avoid cross partition lookup. For example, you can use a remote (host:port) url to target the destination.
- BEA-055001
- Invalid time-to-deliver, must be >= -1
- Category:
- JMSClientExceptions
- Cause:
- The time-to-deliver parameter passed to setTimeToDeliver was invalid.
- Action:
- Change the code to pass a time-to-deliver parameter that is >= -1.
- BEA-055002
- Cannot convert {0} to a boolean.
- Category:
- JMSClientExceptions
- Cause:
- An object that was not null, not a boolean, and not a string could not be converted to a boolean value.
- Action:
- Ensure that the object passed in is either a boolean or a string.
- BEA-055003
- Cannot convert null to a byte.
- Category:
- JMSClientExceptions
- Cause:
- The null object cannot be converted to a byte value
- Action:
- Avoid passing null where a byte value is expected
- BEA-055004
- Cannot convert {0} to a byte.
- Category:
- JMSClientExceptions
- Cause:
- An object that was not null, not a byte, and not a string could not be converted to a byte value
- Action:
- Ensure that the object passed in is either a byte or a string.
- BEA-055005
- Cannot convert null to a short.
- Category:
- JMSClientExceptions
- Cause:
- The null object cannot be converted to a short value.
- Action:
- Avoid passing null where a short value is expected.
- BEA-055006
- Cannot convert {0} to a short.
- Category:
- JMSClientExceptions
- Cause:
- An object that was not null, not a short, and not a string could not be converted to a short value.
- Action:
- Ensure that the object passed in is either a short or a string.
- BEA-055007
- Could not serialize object.
- Category:
- JMSClientExceptions
- Cause:
- An object could not be serialized. The linked exception may contain more details.
- Action:
- See the linked exception which may contain more details.
- BEA-055008
- Invalid RedeliveryLimit, must be >= -1.
- Category:
- JMSClientExceptions
- Cause:
- The RedeliveryLimit parameter passed to setRedeliveryLimit was invalid.
- Action:
- Change the code to pass a RedeliveryLimit parameter that is >= -1.
- BEA-055009
- Invalid SendTimeout, must be >= 0
- Category:
- JMSClientExceptions
- Cause:
- The SendTimeout parameter passed to setSendTimeout was invalid.
- Action:
- Change the code to pass a SendTimeout parameter that is >= 0.
- BEA-055014
- Error sending message
- Category:
- JMSClientExceptions
- Cause:
- The linked exception will contain more details concerning the failure to send the message.
- Action:
- The action will depend on the error that occurred. More information about the specific error that occurred can be found in the linked exception.
- BEA-055015
- Invalid DeliveryMode
- Category:
- JMSClientExceptions
- Cause:
- The DeliveryMode parameter passed to setDeliveryMode was invalid.
- Action:
- Change the code to pass a valid DeliveryMode value.
- BEA-055016
- Invalid Priority
- Category:
- JMSClientExceptions
- Cause:
- The Priority parameter passed to setPriority was invalid.
- Action:
- Change the code to pass a valid Priority value.
- BEA-055017
- Durable connection consumers are not supported.
- Category:
- JMSClientExceptions
- Cause:
- The system does not support durable connection consumers.
- Action:
- Do not attempt to create a durable connection consumer.
- BEA-055018
- QueueSessions do not support multicast.
- Category:
- JMSClientExceptions
- Cause:
- The MULTICAST_NO_ACKNOWLEDGE flag was set in createQueueSession.
- Action:
- Do not use MULTICAST_NO_ACKNOWLEDGE when creating a QueueSession.
- BEA-055019
- Duplicate session
- Category:
- JMSClientExceptions
- Cause:
- The cause is unknown.
- Action:
- Contact My Oracle Support.
- BEA-055021
- ClientID is null
- Category:
- JMSClientExceptions
- Cause:
- ClientID is null in a call to setClientID.
- Action:
- Do not use null in a call to setClientID.
- BEA-055022
- Zero length clientID
- Category:
- JMSClientExceptions
- Cause:
- The clientID passed to setClientID was zero length.
- Action:
- The clientID must not be zero length.
- BEA-055023
- Invalid value for messagesMaximum, {0}
- Category:
- JMSClientExceptions
- Cause:
- The value given for messagesMaximum in createConnectionConsumer is invalid.
- Action:
- Change the code to pass a valid messagesMaximum value.
- BEA-055024
- No such method {0}
- Category:
- JMSClientExceptions
- Cause:
- The given method identification number does not exist.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-055025
- Invalid messagesMaximum value
- Category:
- JMSClientExceptions
- Cause:
- The messagesMaximum parameter passed to setMessagesMaximum was invalid.
- Action:
- Change the code to pass a valid messagesMaximum value.
- BEA-055026
- Invalid overrunPolicy value, {0}
- Category:
- JMSClientExceptions
- Cause:
- The overrun policy passed to setOverrunPolicy is invalid.
- Action:
- Change the code to pass a valid overrun policy value.
- BEA-055027
- Invalid redelivery delay, must be >= -1
- Category:
- JMSClientExceptions
- Cause:
- The redeliveryDelay parameter passed to setRedeliveryDelay was invalid.
- Action:
- Change the code to pass a valid redeliveryDelay value.
- BEA-055028
- Name must not be null.
- Category:
- JMSClientExceptions
- Cause:
- The name parameter passed to createDurableSubscriber was null.
- Action:
- Change the code to pass a valid name to createDurableSubscriber.
- BEA-055029
- Name must not be an empty string.
- Category:
- JMSClientExceptions
- Cause:
- The name parameter passed to createDurableSubscriber had a length of zero.
- Action:
- Change the code to pass a valid name to createDurableSubscriber.
- BEA-055030
- This topic does not support durable subscriptions.
- Category:
- JMSClientExceptions
- Cause:
- Durable subscribers are not supported on Distributed Topics and no subscribers at all are supported on SAF topics
- Action:
- Avoid attempting to create a durable subscriber on a distributed topic or do not create a subscriber on an SAF topic.
- BEA-055031
- This connection does not have a clientID.
- Category:
- JMSClientExceptions
- Cause:
- Unsubscribe was called on a connection without a clientID.
- Action:
- Avoid attempting to unsubscribe a connection with no clientID
- BEA-055032
- An attempt was made to create a named consumer ({0}) on a connection with no clientID.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to create a named consumer on a connection with no clientID.
- Action:
- Avoid attempting to create a named consumer on a connection with no clientID.
- BEA-055033
- Queues do not support multicast.
- Category:
- JMSClientExceptions
- Cause:
- Queues do not support multicast.
- Action:
- Avoid attempting to create a multicast consumer on a queue
- BEA-055034
- Topic {0} does not support multicast.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to create a multicast consumer on a topic that does not support multicast.
- Action:
- Avoid attempting to create a multicast consumer on the given topic.
- BEA-055035
- Cannot open multicast socket, {0}.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to open a multicast socket and failed. The reason for the failure may be in the exception
- Action:
- For more details, check the printed exception on the failure to open the multicast socket.
- BEA-055036
- Cannot join multicast group ({0}) {1}
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to join a multicast group and failed. The reason for failure may be in the exception.
- Action:
- For more details, check the printed exception on the failure to join the multicast group.
- BEA-055037
- Subscription {0} is in use.
- Category:
- JMSClientExceptions
- Cause:
- Two subscriptions with the same name are not allowed.
- Action:
- Avoid attempting to use a subscription name more than once. If necessary, unsubscribe the previous subscription
- BEA-055038
- An unexpected response ({0}) was received from the server.
- Category:
- JMSClientExceptions
- Cause:
- An internal protocol error has occurred.
- Action:
- Contact My Oracle Support.
- BEA-055039
- A system error has occurred. The error is {0}.
- Category:
- JMSClientExceptions
- Cause:
- The cause of this error may be contained in the printed exception.
- Action:
- The action will depend on the error that has occurred. Contact My Oracle Support.
- BEA-055040
- Subscription {0} is in use.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to remove the named subscription while the subscription was in use.
- Action:
- Avoid attempting to remove a subscription that is currently in use.
- BEA-055041
- Cannot leave multicast group ({0}) {1}
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to leave a multicast group and failed. The reason for failure may be in the exception.
- Action:
- For more details, check the printed exception on the failure to leave the multicast group.
- BEA-055042
- No such method {0} for class {1}.
- Category:
- JMSClientExceptions
- Cause:
- The given method number could not be found in the given class.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-055043
- No such method {0} for class {1}.
- Category:
- JMSClientExceptions
- Cause:
- The given method number could not be found in the given class.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-055044
- Multicast sessions do not support synchronous receives.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to do a synchronous receive on a multicast consumer.
- Action:
- Avoid attempting to make a synchronous receive with a multicast consumer.
- BEA-055045
- An invalid value ({0}) for timeout was specified.
- Category:
- JMSClientExceptions
- Cause:
- The timeout given to a receive call is invalid. Timeout values must be positive.
- Action:
- Change the code so that it does not pass a negative number into a receive call.
- BEA-055046
- A listener already exists.
- Category:
- JMSClientExceptions
- Cause:
- A call to receive cannot be made if the consumer already has a listener.
- Action:
- Avoid attempting to call receive if a listener already exists for the consumer.
- BEA-055047
- No such method {0}
- Category:
- JMSClientExceptions
- Cause:
- The given method identification number does not exist.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-055048
- Multicast selectors are not supported in the thin client.
- Category:
- JMSClientExceptions
- Cause:
- Multicast selectors are not supported in the thin client.
- Action:
- If selectors are required, avoid using the JMS thin client. If selectors are not required, avoid using them while using the thin client.
- BEA-055049
- An error occurred. See {0}.
- Category:
- JMSClientExceptions
- Cause:
- See the message body.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-055050
- An error occurred {0}
- Category:
- JMSClientExceptions
- Cause:
- See the message body.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-055051
- An error occurred {0}
- Category:
- JMSClientExceptions
- Cause:
- See the message body.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-055052
- Invalid selector {0}
- Category:
- JMSClientExceptions
- Cause:
- An error occurred while parsing a selector. The printed exception should have more detail.
- Action:
- The course of action will depend on the nature of the error. Use a well-formed selector.
- BEA-055053
- Error creating connection to the server: {0}.
- Category:
- JMSClientExceptions
- Cause:
- The printed exception may have information regarding the cause of this failure.
- Action:
- The course of action will depend on the error printed out in the exception.
- BEA-055054
- Error finding dispatcher: {0}.
- Category:
- JMSClientExceptions
- Cause:
- See the message body.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-055055
- No transaction
- Category:
- JMSClientExceptions
- Cause:
- A call to commit was made on a session but there is no current transaction.
- Action:
- Avoid calling commit on a session that is not currently in a transaction.
- BEA-055056
- Error committing session
- Category:
- JMSClientExceptions
- Cause:
- An error occurred while committing an XA session.
- Action:
- Examine the transaction logs to see what occurred to the transaction
- BEA-055057
- No transaction
- Category:
- JMSClientExceptions
- Cause:
- A call to rollback was made on a session but there is no current transaction.
- Action:
- Do not call rollback on a session that is not currently in a transaction.
- BEA-055058
- Error committing session
- Category:
- JMSClientExceptions
- Cause:
- An error occurred while committing an XA session.
- Action:
- Examine the transaction logs to see what occurred to the transaction.
- BEA-055059
- getXAResource can be called only from the server.
- Category:
- JMSClientExceptions
- Cause:
- A call to getXAResource was made from a client JVM; getXAResource is not supported in the client.
- Action:
- Avoid calling getXAResource from a client JVM.
- BEA-055060
- No transaction.
- Category:
- JMSClientExceptions
- Cause:
- A call to commit was made on a session but there is no current transaction.
- Action:
- Avoid calling commit on a session that is not currently in a transaction.
- BEA-055061
- No transaction.
- Category:
- JMSClientExceptions
- Cause:
- A call to rollback was made on a session but there is no current transaction.
- Action:
- Avoid calling rollback on a session that is not currently in a transaction.
- BEA-055062
- This session is transacted.
- Category:
- JMSClientExceptions
- Cause:
- A call to recover was made on a transacted session.
- Action:
- Avoid calling recover on a transacted session. Use rollback instead.
- BEA-055063
- This session has consumer listeners.
- Category:
- JMSClientExceptions
- Cause:
- The session on which setMessageListener was called already has consumer listeners.
- Action:
- Avoid calling setMessageListener on a session that already has consumer listeners.
- BEA-055064
- Unsupported topic operation on a queue session
- Category:
- JMSClientExceptions
- Cause:
- A call to createTopic was made on a QueueSession.
- Action:
- Avoid calling createTopic on a QueueSession.
- BEA-055065
- Unsupported topic operation {0} on a queue session.
- Category:
- JMSClientExceptions
- Cause:
- A call to {0} was made on a QueueSession.
- Action:
- Avoid calling {0} on a QueueSession.
- BEA-055066
- Unsupported topic operation on a queue session
- Category:
- JMSClientExceptions
- Cause:
- A call to createTemporaryTopic was made on a QueueSession.
- Action:
- Avoid calling createTemporaryTopic on a QueueSession.
- BEA-055067
- Unsupported topic operation on a queue session
- Category:
- JMSClientExceptions
- Cause:
- A call to unsubscribe was made on a QueueSession.
- Action:
- Avoid calling unsubscribe on a QueueSession.
- BEA-055068
- There is no subscription from which to unsubscribe.
- Category:
- JMSClientExceptions
- Cause:
- The user called unsubscribe on a session that does not have a subscription.
- Action:
- Avoid calling unsubscribe on a session that does not have a subscription.
- BEA-055069
- Unsupported queue operation on a topic session
- Category:
- JMSClientExceptions
- Cause:
- A call to createQueue was made on a TopicSession.
- Action:
- Avoid calling createQueue on a TopicSession.
- BEA-055070
- Unsupported queue operation on a topic session
- Category:
- JMSClientExceptions
- Cause:
- A call to createBrowser was made on a TopicSession.
- Action:
- Avoid calling createBrowser on a TopicSession.
- BEA-055071
- Unsupported queue operation on a topic session
- Category:
- JMSClientExceptions
- Cause:
- A call to createTemporaryQueue was made on a TopicSession.
- Action:
- Avoid calling createTemporaryQueue on a TopicSession.
- BEA-055072
- Wrong connection for this temporary destination
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to call createConsumer on an invalid connection from a temporary destination.
- Action:
- Create consumers using the same connection that was used to create the temporary destination.
- BEA-055073
- Dropping new message
- Category:
- JMSClientExceptions
- Cause:
- A new message is being dropped because too many messages have arrived.
- Action:
- Either consume messages faster or produce messages slower for this session.
- BEA-055074
- Dropping old message
- Category:
- JMSClientExceptions
- Cause:
- An old message is being dropped because too many messages have arrived.
- Action:
- Either consume messages faster or produce messages slower for this session.
- BEA-055075
- It is possible that the client is malfunctioning: a RuntimeException was thrown from its onMessage method.
- Category:
- JMSClientExceptions
- Cause:
- The onMessage method of the client threw a RuntimeException.
- Action:
- Modify the code such that the RuntimeException does not occur from within the body of the user code. This warning is required by section 4.5.2 of the JMS Specification.
- BEA-055076
- The session is closed.
- Category:
- JMSClientExceptions
- Cause:
- An operation was attempted on a closed session.
- Action:
- Avoid attempting this operation on a closed session.
- BEA-055077
- Cannot override producer destination.
- Category:
- JMSClientExceptions
- Cause:
- A call to send with a non-null destination was made on a producer that is already bound to a destination.
- Action:
- Avoid calling send with a non-null destination on a producer that is already bound to a destination.
- BEA-055078
- Cannot override producer destination
- Category:
- JMSClientExceptions
- Cause:
- A call to send with a non-null destination was made on a producer that is already bound to a destination.
- Action:
- Avoid calling send with a non-null destination on a producer that is already bound to a destination.
- BEA-055079
- Must provide destination to send to
- Category:
- JMSClientExceptions
- Cause:
- There is no destination to send to.
- Action:
- Use the version of send that has a destination or bind a destination to the producer before calling send.
- BEA-055080
- Must provide destination to send to
- Category:
- JMSClientExceptions
- Cause:
- There is no destination to send to.
- Action:
- Use the version of send that has a destination or bind a destination to the producer before calling send.
- BEA-055081
- Unsupported topic operation on a queue session
- Category:
- JMSClientExceptions
- Cause:
- A call to createDurableConnectionConsumer was made on a QueueConnection.
- Action:
- Avoid calling createDurableConnectionConsumer on a QueueConnection.
- BEA-055082
- The connection is closed.
- Category:
- JMSClientExceptions
- Cause:
- The connection has been closed. Only a few operations are valid on a closed connection.
- Action:
- Avoid calling any illegal operations on a closed queue connection.
- BEA-055083
- Cannot set clientid to {0}. The client ID is already set to {1}
- Category:
- JMSClientExceptions
- Cause:
- The clientID {1} is already set on this connection. The clientID cannot be set to {0}
- Action:
- Avoid attempting to set a clientID on a connection that already has one.
- BEA-055084
- A connection consumer works only on the server.
- Category:
- JMSClientExceptions
- Cause:
- A connection consumer can be created only in the same JVM in which the server is running.
- Action:
- Avoid attempting to create a connection consumer on a JVM that is not running the server.
- BEA-055085
- Destination is null.
- Category:
- JMSClientExceptions
- Cause:
- In a call to createConnectionConsumer or createConsumer, the destination parameter was null.
- Action:
- Avoid using null for the destination in a call to createConnectionConsumer or createConsumer.
- BEA-055086
- Foreign destination
- Category:
- JMSClientExceptions
- Cause:
- Foreign destinations are not supported when creating connectionConsumers.
- Action:
- Avoid using a foreign destination in a call to createConnectionConsumer.
- BEA-055087
- The session already has a message listener.
- Category:
- JMSClientExceptions
- Cause:
- A consumer may not have an individual message listener if its parent session already has one defined.
- Action:
- Avoid attempting to set a message listener for a consumer if the session already has a listener defined.
- BEA-055088
- The consumer is closed.
- Category:
- JMSClientExceptions
- Cause:
- The consumer has been closed. Only a few operations are valid on a closed consumer.
- Action:
- Avoid calling any illegal operations on a closed consumer.
- BEA-055089
- Destination is null.
- Category:
- JMSClientExceptions
- Cause:
- In a call to send, the destination parameter was null.
- Action:
- Avoid using null for the destination in a call to send.
- BEA-055090
- Foreign destination
- Category:
- JMSClientExceptions
- Cause:
- Foreign destinations are not supported when sending.
- Action:
- Avoid using a foreign destination in a call to send.
- BEA-055091
- Destination {0} must be a queue.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to publish to a queue.
- Action:
- Avoid using publish to a queue. Use send instead.
- BEA-055092
- Destination {0} must be a topic.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to send to a topic.
- Action:
- Avoid using send to a topic. Use publish instead.
- BEA-055093
- Error converting foreign message
- Category:
- JMSClientExceptions
- Cause:
- An I/O exception occurred while converting a foreign message. The cause of the failure may be contained in the linked exception.
- Action:
- Examine the linked I/O exception.
- BEA-055094
- The producer is closed.
- Category:
- JMSClientExceptions
- Cause:
- The producer has been closed. Only a few operations are valid on a closed producer.
- Action:
- Avoid calling any illegal operations on a closed producer.
- BEA-055095
- The browser is closed.
- Category:
- JMSClientExceptions
- Cause:
- The browser has been closed. Only a few operations are valid on a closed browser.
- Action:
- Avoid calling any illegal operations on a closed browser.
- BEA-055096
- Cannot convert null to a char.
- Category:
- JMSClientExceptions
- Cause:
- The null object cannot be converted to a char value.
- Action:
- Avoid passing null where a char value is expected.
- BEA-055097
- Cannot convert {0} to a char.
- Category:
- JMSClientExceptions
- Cause:
- An object that was not null, not a character, and not a string could not be converted to a char value.
- Action:
- Ensure that the object passed in is either a character or a string.
- BEA-055098
- Cannot convert null to an int.
- Category:
- JMSClientExceptions
- Cause:
- The null object cannot be converted to an int value.
- Action:
- Avoid passing null where an int value is expected.
- BEA-055099
- Cannot convert {0} to an int.
- Category:
- JMSClientExceptions
- Cause:
- An object that was not null, not an integer, and not a string could not be converted to an int value.
- Action:
- Ensure that the object passed in is either an integer or a string.
- BEA-055100
- Cannot convert null to a long.
- Category:
- JMSClientExceptions
- Cause:
- The null object cannot be converted to a long value.
- Action:
- Avoid passing null where a long value is expected.
- BEA-055101
- Cannot convert {0} to a long.
- Category:
- JMSClientExceptions
- Cause:
- An object that was not null, not a long, and not a string could not be converted to a long value.
- Action:
- Ensure that the object passed in is either a long or a string.
- BEA-055102
- Cannot convert null to a float.
- Category:
- JMSClientExceptions
- Cause:
- The null object cannot be converted to a float value.
- Action:
- Avoid passing null where a float value is expected.
- BEA-055103
- Cannot convert {0} to a float.
- Category:
- JMSClientExceptions
- Cause:
- An object that was not null, not a float, and not a string could not be converted to a float value.
- Action:
- Ensure that the object passed in is either a float or a string.
- BEA-055104
- Cannot convert null to a double.
- Category:
- JMSClientExceptions
- Cause:
- The null object cannot be converted to a double value.
- Action:
- Avoid passing null where a double value is expected.
- BEA-055105
- Cannot convert {0} to a double.
- Category:
- JMSClientExceptions
- Cause:
- An object that was not null, not a double, and not a string could not be converted to a short value.
- Action:
- Ensure that the object passed in is either a double or a string.
- BEA-055106
- A byte[] cannot be converted to a string.
- Category:
- JMSClientExceptions
- Cause:
- A byte[] cannot be converted to a string.
- Action:
- Avoid passing a byte array that needs to be converted to a string.
- BEA-055107
- Cannot convert {0} to a byte[].
- Category:
- JMSClientExceptions
- Cause:
- The given object could not be converted to a byte[].
- Action:
- Ensure that the object passed in can be converted to a byte array.
- BEA-055108
- Read past end of message.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information.
- Action:
- Avoid attempting to read past the end of a StreamMessage. See the linked EOFException for more information.
- BEA-055109
- Error reading from stream.
- Category:
- JMSClientExceptions
- Cause:
- There was an error reading the stream from a StreamMessage. A linked IOException may contain more information.
- Action:
- See the linked IOException for more information.
- BEA-055110
- Error writing to stream.
- Category:
- JMSClientExceptions
- Cause:
- There was an error writing to the stream of a StreamMessage. A linked IOException may contain more information.
- Action:
- See the linked IOException for more information.
- BEA-055111
- Cannot convert from {0} to {1}
- Category:
- JMSClientExceptions
- Cause:
- A StreamMessage was unable to convert one type to another.
- Action:
- Ensure that the two types are compatible. Avoid attempting to convert incompatible types.
- BEA-055112
- Error reading from stream.
- Category:
- JMSClientExceptions
- Cause:
- There was an error reading the stream from a StreamMessage. A linked ArrayIndexOutOfBoundsException may contain more information.
- Action:
- See the linked ArrayIndexOutOfBoundsException for more information.
- BEA-055113
- Error reading from stream.
- Category:
- JMSClientExceptions
- Cause:
- There was an error reading the stream from a StreamMessage. A linked ArrayStoreException may contain more information.
- Action:
- See the linked ArrayStoreException for more information.
- BEA-055114
- There was an eeror when deserializing an object. Some typical reasons for failure are: missing application class, application class version mismatch, or Java objects not being supported.
- Category:
- JMSClientExceptions
- Cause:
- There was an error deserializing an object. A linked IOException may have more details.
- Action:
- See the linked IOException for more details.
- BEA-055115
- Error deserializing an object.
- Category:
- JMSClientExceptions
- Cause:
- There was an error deserializing an object. A linked ClassNotFoundException may have more details.
- Action:
- See the linked ClassNotFoundException for more details.
- BEA-055116
- Internal error unknown message type {0}
- Category:
- JMSClientExceptions
- Cause:
- This error should never happen.
- Action:
- Contact My Oracle Support.
- BEA-055117
- Invalid delivery mode {0}
- Category:
- JMSClientExceptions
- Cause:
- The delivery mode passed into setJMSDeliveryMode is invalid
- Action:
- Change the code so that it calls setJMSDeliveryMode with a valid delivery mode.
- BEA-055118
- Invalid redelivery limit, must be >= -1.
- Category:
- JMSClientExceptions
- Cause:
- The redelivery limit parameter passed to setJMSRedeliveryLimit was invalid.
- Action:
- Change the code to pass a redelivery limit parameter that is >= -1.
- BEA-055119
- Invalid priority, {0}
- Category:
- JMSClientExceptions
- Cause:
- The priority parameter passed to setJMSPriority was invalid.
- Action:
- Change the code to pass a valid priority value.
- BEA-055121
- Invalid property name, "{0}"
- Category:
- JMSClientExceptions
- Cause:
- The property name passed to setObjectProperty was invalid.
- Action:
- Change the code to pass a valid property name.
- BEA-055122
- Property write attempted in READ mode.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to write a property but the message is read-only.
- Action:
- Avoid attempting to write a property to a message in read-only mode.
- BEA-055123
- Invalid property value, {0}
- Category:
- JMSClientExceptions
- Cause:
- The property value passed to setObjectProperty was invalid.
- Action:
- Change the code to pass a valid property value.
- BEA-055125
- Unknown underlying stream type, cannot convert 6.0 class.
- Category:
- JMSClientExceptions
- Cause:
- While attempting to read a message created by an older version of WebLogic Server, a failure occurred.
- Action:
- It may not be possible to read the older version of the message. Contact My Oracle Support.
- BEA-055126
- Stream is corrupted. Possible older version
- Category:
- JMSClientExceptions
- Cause:
- While attempting to read a message created by an older version of WebLogic Server, a failure occurred.
- Action:
- It may not be possible to read the older version of the message. Contact My Oracle Support.
- BEA-055127
- Unsupported version
- Category:
- JMSClientExceptions
- Cause:
- The version of the message being read is unsupported.
- Action:
- Contact My Oracle Support.
- BEA-055128
- Read attempted in WRITE mode.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to read a message in WRITE mode.
- Action:
- Avoid attempting to read a message in WRITE mode.
- BEA-055129
- Write attempted in READ mode.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to write a message that is read-only.
- Action:
- Avoid attempting to write to a message in read-only mode.
- BEA-055130
- Invalid data type: {0}
- Category:
- JMSClientExceptions
- Cause:
- The class name given is not a valid data type. The type for setObject must be number, string, boolean, byte, character, or null.
- Action:
- Pass one of the acceptable data types to setObject in a MapMessage.
- BEA-055131
- Illegal name: {0}
- Category:
- JMSClientExceptions
- Cause:
- The given name is not legal. It is either null or of zero length.
- Action:
- Pass a non-null or non-zero-length string as the name of a MapMessage element.
- BEA-055132
- Could not copy message.
- Category:
- JMSClientExceptions
- Cause:
- The system could not copy a MapMessage. The linked IOException should contain more information about the nature of the error.
- Action:
- Examine the linked exception to discover what caused the failure.
- BEA-055133
- Could not deserialize message.
- Category:
- JMSClientExceptions
- Cause:
- The system could not deserialize a MapMessage. The linked IOException should contain more information about the nature of the error.
- Action:
- Examine the linked exception to discover what caused the failure.
- BEA-055134
- Unsupported class version {0}. Expected a value between {1} and {2} inclusive.
- Category:
- JMSClientExceptions
- Cause:
- While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {1} then it is possible an attempt was made to access a newer JMS version than the current version. Otherwise a possible attempt has been made to interoperate with an unsupported older version of JMS.
- Action:
- Ensure that the versions of Oracle products that are interoperating are supported. If the versions should be supported, contact My Oracle Support.
- BEA-055135
- Could not write object, expected simple type, but got class {0}
- Category:
- JMSClientExceptions
- Cause:
- The given object class could not be written because it is not a simple type.
- Action:
- Contact My Oracle Support.
- BEA-055136
- Could not read object, unrecognized class code {0}.
- Category:
- JMSClientExceptions
- Cause:
- An unknown class code was received. The object cannot be read.
- Action:
- Contact My Oracle Support.
- BEA-055137
- JMSProducerSendResponse versions {0}, {1} not compatible with peer: {2}
- Category:
- JMSClientExceptions
- Cause:
- An interoperability error occurred.
- Action:
- Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.
- BEA-055138
- Peer not compatible with DistributedDestinationImpl version {0}. Peer Major Version is less than 6.
- Category:
- JMSClientExceptions
- Cause:
- An interoperability error occurred.
- Action:
- Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.
- BEA-055139
- Invalid Temporary Destination
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to delete an invalid temporary destination.
- Action:
- Avoid attempting to delete invalid temporary destinations.
- BEA-055140
- Internal error or marshalling error, unknown destination type {0}
- Category:
- JMSClientExceptions
- Cause:
- An unknown type was encountered when marshalling a destination.
- Action:
- Contact My Oracle Support.
- BEA-055141
- Destination is null.
- Category:
- JMSClientExceptions
- Cause:
- While checking a destination type, the incoming destination was null.
- Action:
- Avoid attempting to discover the type of a null destination.
- BEA-055142
- Foreign destination, {0}
- Category:
- JMSClientExceptions
- Cause:
- While checking a destination type, the incoming destination was foreign.
- Action:
- Avoid attempting to discover the type of a foreign destination.
- BEA-055143
- Destination must be a queue, {0}
- Category:
- JMSClientExceptions
- Cause:
- The given destination must be a queue, but it is not a queue.
- Action:
- Use the proper type of destination when checking types.
- BEA-055144
- Destination must be a topic, {0}
- Category:
- JMSClientExceptions
- Cause:
- The given destination must be a topic, but it is not a topic.
- Action:
- Use the proper type of destination when checking types.
- BEA-055145
- Unknown stream version: {0}
- Category:
- JMSClientExceptions
- Cause:
- The given version number is invalid for a buffered stream.
- Action:
- Contact My Oracle Support.
- BEA-055146
- The stream cannot handle raw objects.
- Category:
- JMSClientExceptions
- Cause:
- The stream is probably from an unintended source, such as a Web browser.
- Action:
- Only connect to the Oracle product TCP port with a proper client. If the client is a proper client, contact My Oracle Support.
- BEA-055147
- Not implemented
- Category:
- JMSClientExceptions
- Cause:
- readLine was called, but it has not been implemented.
- Action:
- Contact My Oracle Support.
- BEA-055148
- The stream cannot handle raw objects.
- Category:
- JMSClientExceptions
- Cause:
- A raw object could not be written to the buffered stream.
- Action:
- Contact My Oracle Support.
- BEA-055149
- Attempt to read past end of message ({0})
- Category:
- JMSClientExceptions
- Cause:
- The end of the BytesMessage was reached, but an attempt was made to read past it. {0} indicates where the attempt was made and will only be significant to My Oracle Support.
- Action:
- Avoid attempting to read past the end of the BytesMessage.
- BEA-055150
- Error reading from stream ({0}).
- Category:
- JMSClientExceptions
- Cause:
- The linked IOException will have more detail on the cause of the failure.
- Action:
- Examine the linked exception to discover what caused the problem.
- BEA-055151
- Length ({0}) is negative.
- Category:
- JMSClientExceptions
- Cause:
- In a call to readBytes, the length parameter is negative.
- Action:
- Fix the code to ensure a negative length is not passed to readBytes.
- BEA-055152
- length ({0}) is greater than the length of the array ({1}).
- Category:
- JMSClientExceptions
- Cause:
- In a call to readBytes, the length parameter is larger than the size of the bytes array to fill.
- Action:
- Fix the code to ensure the length passed to readBytes is less than or equal to the length of the output array.
- BEA-055153
- Error writing to stream ({0}).
- Category:
- JMSClientExceptions
- Cause:
- The linked IOException will have more detail on the cause of the failure.
- Action:
- Examine the linked exception to discover what caused the problem.
- BEA-055154
- Invalid object type: {0}
- Category:
- JMSClientExceptions
- Cause:
- The object passed to writeObject is not valid.
- Action:
- Only send valid object types to writeObject. Example valid types include boolean, byte, short, and integer.
- BEA-055155
- Cannot forward message
- Category:
- JMSClientExceptions
- Cause:
- Modified received messages are not supported when using forward methods.
- Action:
- Avoid modifying a received message in a call to forward.
- BEA-055156
- Peer neither compatible with {0} or {1} or {2} or {3}. PeerInfo is {4}.
- Category:
- JMSClientExceptions
- Cause:
- A version mismatch occurred in a message.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-055157
- Invalid compression threshold
- Category:
- JMSClientExceptions
- Cause:
- The compression threshold was invalid.
- Action:
- Change the code to pass a valid compression threshold.
- BEA-055158
- WebLogic Server JMS failed to decompress the message body.
- Category:
- JMSClientExceptions
- Cause:
- The linked IOException will have more detail on the cause of the failure.
- Action:
- Examine the linked exception to discover what caused the problem.
- BEA-055159
- Message consumer received a compressed message with unknown compression tag - {0}
- Category:
- JMSClientExceptions
- Cause:
- Contact My Oracle Support.
- Action:
- Contact My Oracle Support.
- BEA-055160
- WebLogic Server JMS failed to deserialize the text message.
- Category:
- JMSClientExceptions
- Cause:
- Contact My Oracle Support.
- Action:
- Contact My Oracle Support.
- BEA-055161
- Cannot forward foreign messages.
- Category:
- JMSClientExceptions
- Cause:
- Foreign messages are not supported when using forward methods.
- Action:
- Avoid forwarding a foreign message.
- BEA-055162
- WebLogic Server JMS failed to serialize the text message for interoperability.
- Category:
- JMSClientExceptions
- Cause:
- Contact My Oracle Support.
- Action:
- Contact My Oracle Support.
- BEA-055163
- WebLogic Server JMS failed to serialize the XML message for interoperability.
- Category:
- JMSClientExceptions
- Cause:
- Contact My Oracle Support.
- Action:
- Contact My Oracle Support.
- BEA-055164
- Cannot forward a message to a WebLogic Server instance prior than version 9.0.
- Category:
- JMSClientExceptions
- Cause:
- Cannot forward a message to a WebLogic Server instance prior than 9.0.
- Action:
- Avoid forwarding a message to a WebLogic Server instance prior than 9.0.
- BEA-055165
- The following exception has occurred: {0}.
- Category:
- JMSClientExceptions
- Cause:
- An error condition has occurred.
- Action:
- Look for the associated exception in the log or the program to see what the results are. In general, this stack trace will help in debugging an existing problem.
- BEA-055167
- Single session cannot support more than one synchronous message-prefetching consumer.
- Category:
- JMSClientExceptions
- Cause:
- There is another opened synchronous message-prefetching consumer.
- Action:
- Close the other synchronous message-prefetching consumer.
- BEA-055168
- Synchronous message-prefetching consumer cannot support user transaction.
- Category:
- JMSClientExceptions
- Cause:
- Synchronous message-prefetching consumer cannot support user transaction.
- Action:
- Disable the user transaction or the synchronous message-prefetching consumer in the jms connection factory setting.
- BEA-055169
- Network connection to server was lost.
- Category:
- JMSClientExceptions
- Cause:
- The network connection to the server was lost.
- Action:
- This is usually a recoverable error when the JMS client is using the auto-reconnect/failover feature. This error is exposed to the user (JMS client code developer) when the auto-reconnect feature cannot make a decision without user input on a particular course of action after failover. The user can consciously code to continue to use relevant refreshed JMS objects with a potential lowered quality of service such as duplicate/lost/out-of-order messages, or decide to close the relevant JMS object.
- BEA-055170
- Cannot convert string property from its internal format.
- Category:
- JMSClientExceptions
- Cause:
- The string property cannot be converted from its internal format.
- Action:
- Contact My Oracle Support.
- BEA-055171
- Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe() API.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a Client ID policy of UNRESTRICTED.
- Action:
- Use weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a Client ID policy of UNRESTRICTED.
- BEA-055172
- Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a Client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription with a null topic or distributed topic instance.
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to unsubscribe a durable subscription with a null Topic object or a distributed topic object from a connection that has a Client ID policy of UNRESTRICTED.
- Action:
- Provide a standalone topic object or a member of a distributed topic when calling weblogic.jms.extensions.WLSession.unsubscribe(String topic, String name).
- BEA-055173
- Read past end of message ({0})
- Category:
- JMSClientExceptions
- Cause:
- An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information
- Action:
- Do not attempt to read past the end of a StreamMessage. See the linked EOFException for more information
- BEA-055174
- Error reading from stream ({0})
- Category:
- JMSClientExceptions
- Cause:
- There was an error reading the stream from a StreamMessage. A linked IOException may contain more information
- Action:
- See the linked IOException for more information
- BEA-055175
- Error writing to stream ({0})
- Category:
- JMSClientExceptions
- Cause:
- There was an error writing to the stream of a StreamMessage. A linked IOException may contain more information
- Action:
- See the linked IOException for more information
- BEA-055176
- Active transaction detected during send, publish, or receive while using a non-XATransaction Resource Adapter.
- Category:
- JMSClientExceptions
- Cause:
- An active transaction was detected during send, publish, or receive while using a non-XATransaction Resource Adapter.
- Action:
- Use the XATransaction Resource Adapter instead.
- BEA-055177
- An invalid value ({0}) for session mode was specified.
- Category:
- JMSClientExceptions
- Cause:
- An invalid value of the sessionMode parameter was specified when creating a JMSContext. The only valid values are JMSContext.AUTO_ACKNOWLEDGE, JMSContext.CLIENT_ACKNOWLEDGE, JMSContext.DUPS_OK_ACKNOWLEDGE and JMSContext.SESSION_TRANSACTED
- Action:
- Change the code so that it passes in a valid session mode. See the JMS API for more information.
- BEA-055178
- This method may not be called in a Java EE web or EJB container
- Category:
- JMSClientExceptions
- Cause:
- The code calls a JMS method which the JMS, EJB or Java EE specification states must not be called in a Java EE web or EJB container. See section EE.6.7 "Java Message Service (JMS) 2.0 Requirements" in the Java EE 7 platform specification" and section 16.3.5 "JMS API Requirements" in the EJB 3.2 specification.
- Action:
- Change the code so that it uses methods that are valid a Java EE web or EJB container.
- BEA-055179
- JMSContext is closed
- Category:
- JMSClientExceptions
- Cause:
- The code called the close methods on a JMSContext which had been previously closed.
- Action:
- Change the code so that it uses a JMSContext that has not been closed.
- BEA-055180
- Cannot set the setClientID method on a JMSContext because the JMSContext is in an invalid state
- Category:
- JMSClientExceptions
- Cause:
- The setClientID method was called on a JMSContext when the JMSContext is in an invalid state. It only valid to call the setClientID method on a JMSContext immediately after the JMSContext has been created and before any other action on the JMSContext is taken. It is also only valid to call the setClientID method on a JMSContext if the client ID has not already been administratively configured.
- Action:
- Change the code to endure that the setClientID method on a JMSContext is only called immediately after the JMSContext has been created and before any other action on the JMSContext is taken, and only if the client ID has not already been administratively configured.
- BEA-055181
- Invalid client ID. Client ID may not be null.
- Category:
- JMSClientExceptions
- Cause:
- The setClientID method was called on a JMSContext but the specified client ID was null.
- Action:
- Change the code so that the specified client ID is neither null nor an empty string.
- BEA-055182
- Invalid client ID. Client ID may not be an empty string.
- Category:
- JMSClientExceptions
- Cause:
- The setClientID method was called on a JMSContext but the specified client ID was an empty string.
- Action:
- Change the code so that the specified client ID is neither null nor an empty string.
- BEA-055183
- JMSConsumer is closed
- Category:
- JMSClientExceptions
- Cause:
- The code called the close method on a JMSConsumer which had been previously closed.
- Action:
- Change the code so that it uses a JMSConsumer that has not been closed.
- BEA-055184
- Message is null
- Category:
- JMSClientExceptions
- Cause:
- The code called the send method on a JMSProducer with a null value for the message parameter.
- Action:
- Change the code so that the message parameter passed to the JMSProducer send method is not null
- BEA-055185
- An invalid value ({0}) for delivery mode was specified
- Category:
- JMSClientExceptions
- Cause:
- The setDeliveryMode method on JMSProducer was called with an invalid value of the deliveryMode parameter. The only valid values are DeliveryMode.NON_PERSISTENT, DeliveryMode.PERSISTENT.
- Action:
- Change the code so that it passes in a valid delivery mode. See the JMS API for more information.
- BEA-055186
- An invalid value ({0}) for message priority was specified
- Category:
- JMSClientExceptions
- Cause:
- The setPriority method on JMSProducer was called with an invalid value of the setPriority parameter. Priority must be a valie between 0 and 9.
- Action:
- Change the code so that it passes in a valid priority value. See the JMS API for more information.
- BEA-055187
- Message property name must not be null.
- Category:
- JMSClientExceptions
- Cause:
- The message property name parameter was null. This is not valid.
- Action:
- Change the code to pass a message property name which is not null.
- BEA-055188
- Message property name must not be an empty string
- Category:
- JMSClientExceptions
- Cause:
- The message property name parameter was an empty string. This is not valid.
- Action:
- Change the code to pass a message property name which is not an empty string.
- BEA-055189
- Message property value must not be of type ({0})
- Category:
- JMSClientExceptions
- Cause:
- The message property name was of an invalid type. A message property value must be of type Boolean, Byte, Short, Integer, Long, Float or Double.
- Action:
- Change the code to pass a message property value of a valid type. Valid types are Boolean, Byte, Short, Integer, Long, Float and Double.
- BEA-055190
- Message property name ({0}) must not be a reserved word
- Category:
- JMSClientExceptions
- Cause:
- The message property name is a reserved word. This is not valid. A message property name cannot be NOT, AND, OR, BETWEEN, LIKE, IN, IS, or ESCAPE.
- Action:
- Change the code to pass a message property name which is not a reserved word.
- BEA-055191
- Message property name ({0}) contains an invalid character.
- Category:
- JMSClientExceptions
- Cause:
- Message property name contains an invalid character. The first character must be a letter and subsequent characters must be either a letter or a digit. A letter is any character for which the method Character.isJavaLetter returns true. This includes '_' and '$'. A letter or digit is any character for which the method Character.isJavaLetterOrDigit returns true.
- Action:
- Change the code to pass a message property name which contains valid characters.
- BEA-055192
- Message property name ({0}) contains an invalid first character.
- Category:
- JMSClientExceptions
- Cause:
- Message property name contains an invalid start character. The first character must be a letter and subsequent characters must be either a letter or a digit. A letter is any character for which the method Character.isJavaLetter returns true. This includes '_' and '$'. A letter or digit is any character for which the method Character.isJavaLetterOrDigit returns true
- Action:
- Change the code to pass a message property name which contains valid characters.
- BEA-055193
- Message body is a {0} and cannot be assigned to the specified class {1}
- Category:
- JMSClientExceptions
- Cause:
- Message body is a {0} and cannot be assigned to the specified class {1}. The application called the getBody method on a Message object. This method returns the message body as an object of the specified type. The message body must be capable of being assigned to the specified type. This means that the specified class or interface must be either the same as, or a superclass or superinterface of, the class of the message body.
- Action:
- Specify a class which is suitable for the actual body type
- BEA-055194
- Message body is a StreamMessage and the getBody method cannot be used
- Category:
- JMSClientExceptions
- Cause:
- The application called the getBody method on a Message object. Message body is a StreamMessage and the getBody method cannot be used with this type of message.
- Action:
- Use the methods specific to StreamMessage to obtain the message body. Do not use the getBody method.
- BEA-055195
- Shared durable connection consumers are not supported.
- Category:
- JMSClientExceptions
- Cause:
- The system does not support shared durable connection consumers.
- Action:
- Do not attempt to create a shared durable connection consumer.
- BEA-055196
- Shared connection consumers are not supported.
- Category:
- JMSClientExceptions
- Cause:
- The system does not support shared connection consumers.
- Action:
- Do not attempt to create a shared connection consumer.
- BEA-055197
- Invalid deliveryDelay , must be >= 0.
- Category:
- JMSClientExceptions
- Cause:
- The deliveryDelay parameter passed to setDeliveryDelay was invalid.
- Action:
- Change the code to pass a deliveryDelay parameter that is >= 0 .
- BEA-055198
- The JMS specification does not permit a message listener to call {0} on its own {1}.
- Category:
- JMSClientExceptions
- Cause:
- A message listener attempted to call {0} on its own {1}. This is not permitted by the JMS specification.
- Action:
- To conform to the JMS specification, change the message listener code so that it does not call {0} on its own {1}. Alternatively enable the connection factory setting AllowCloseInOnMessage to specify that this non-JMS behavior is permitted.
- BEA-055199
- An injected JMSContext cannot be used when there is neither a transaction nor a valid request scope.
- Category:
- JMSClientExceptions
- Cause:
- The application attempted to use an injected JMSContext when there was neither a Java EE transaction nor a CDI request scope.
- Action:
- Change the code to ensure that methods on the injected JMSContext are only called when there is a Java EE transaction or a valid CDI request scope. Alternatively, use an application-managed JMSContext (one created explicitly from a Connectionfactory) instead of an injected JMSContext.
- BEA-055200
- Asynchronous message forward is not currently supported.
- Category:
- JMSClientExceptions
- Cause:
- The application called the JMSProducer method setAsync before calling the JMSProducer method forward on the same JMSProducer object.
- Action:
- Remove the call to the JMSProducer method setAsync and try again. This will perform a synchronmous forward instead.
- BEA-055201
- An invalid value ({0}) for message priority was specified
- Category:
- JMSClientExceptions
- Cause:
- The send method on MessageProducer was called with an invalid priority value. Priority must be a value between 0 and 9.
- Action:
- Pass a valid priority value. See the JMS API for more information.
- BEA-055202
- An invalid value ({0}) for delivery mode was specified.
- Category:
- JMSClientExceptions
- Cause:
- The send method on MessageProducer was called with invalid delivery mode value. The only valid values are DeliveryMode.NON_PERSISTENT, DeliveryMode.PERSISTENT.
- Action:
- Pass a valid delivery mode value. See the JMS API for more information.
- BEA-055203
- The same Message object ({0}) was previously sent asynchronously but is not complete yet.
- Category:
- JMSClientExceptions
- Cause:
- A send method is called for a Message object that was asynchronously sent but is not complete yet.
- Action:
- Create a new Message object to send or wait for the asynchronous send to complete.
- BEA-055204
- JMS asynchronous send is not supported in an XA transaction.
- Category:
- JMSClientExceptions
- Cause:
- A JMS asynchronous send was used in an XA transaction.
- Action:
- Do not attempt to use asynchronous send in an XA transaction.
- BEA-055205
- There is no message body.
- Category:
- JMSClientExceptions
- Cause:
- There is no message body in the message.
- Action:
- Do not attempt to get the message body from a message that has no message body.
- BEA-055206
- CompletionListener is null.
- Category:
- JMSClientExceptions
- Cause:
- A null CompletionListener was passed to the asynchronous send method.
- Action:
- Do not pass a null CompletionListener to the JMS asynchronous send method.
- BEA-055207
- The Security Policy setting for JMS Connection Factory ({0}) is ({1}) which is not compatible with a Thread Based InitialContext.
- Category:
- JMSClientExceptions
- Cause:
- The Security Policy setting for JMS Connection Factory ({0}) is ({1}) which is not compatible with a Thread Based InitialContext.
- Action:
- Use an Object Based InitialContext to lookup the connection factory instead of a Thread Based InitialContext, or set a different Security Policy.
- BEA-055208
- Object based InitialContext does not support to lookup type "{0}".
- Category:
- JMSClientExceptions
- Cause:
- Object based InitialContext only support to lookup three types: jndi context, WLJMS CF and WLJMS destinaton.
- Action:
- Use a WL standard InitialContext to lookup other types.
- BEA-055209
- Foreign Server is not supported by Object Based InitialContext.
- Category:
- JMSClientExceptions
- Cause:
- Foreign Server is not supported by Object Based InitialContext. Looking up the local JNDI name of the Foreign Server is not supported by Object Based InitialContext.
- Action:
- Do not use Object Based InitialContext to look up the local JNDI name of the Foreign Server.
- BEA-055210
- Object based InitialContext does not support the "{0}" method.
- Category:
- JMSClientExceptions
- Cause:
- Object based InitialContext does not support the "{0}" method.
- Action:
- Do not call this method with Object Based InitialContext or use a WL standard InitialContext instead.
- BEA-055211
- Object based InitialContext only support the "{0}" method on server side and install client.
- Category:
- JMSClientExceptions
- Cause:
- Object based InitialContext only support the "{0}" method on server side and install client, does not support it on other client.
- Action:
- Call this method on server side or install client, do not call it on other client.
- BEA-080001
- Error in dispatcher {0}
- Category:
- RMI
- Cause:
- A runtime error occurred while dispatching a request to the server.
- Action:
- If the error is not application related, contact My Oracle Support with the stack trace for further analysis.
- BEA-080002
- Unexport failed for: {0}.
- Category:
- RMI
- Cause:
- The remote object was unexported twice.
- Action:
- No action is required.
- BEA-080003
- A RuntimeException was generated by the RMI server: {0} {1}.
- Category:
- RMI
- Cause:
- A runtime exception occurred while dispatching the request to the server.
- Action:
- No action is required.
- BEA-080004
- An error was generated by the RMI server: {0} {1}.
- Category:
- RMI
- Cause:
- A runtime error occurred while dispatching a response to the client.
- Action:
- The associated stack trace contains information about the error. Check the server logs for more details.
- BEA-080005
- An exception was generated by the RMI server: {0} {1}.
- Category:
- RMI
- Cause:
- The error response could not be sent to the client. The underlying socket caused an IOException while dispatching the error response.
- Action:
- The associated stack trace contains information about the error.
- BEA-080006
- Failed to associate the transaction context with the response while marshalling an exception to the client: {0}.
- Category:
- RMI
- Cause:
- An IOException occurred while associating a transaction context with the response. This happened when marshalling an exception in the response. Most likely, the socket has been torn down or an error occurred in the stream.
- Action:
- Check the server logs for more details.
- BEA-080007
- RMI runtime is disabled, since it could not initialize the DGC {0}.
- Category:
- RMI
- Cause:
- RMI runtime could not be initialized.
- Action:
- Restart the server. If the problem continues, contact My Oracle Support with the stack trace information.
- BEA-080008
- Failed to send error reply to client {0}.
- Category:
- RMI
- Cause:
- An exception occurred while dispatching an error response to the client.
- Action:
- No action is required.
- BEA-080009
- An error was generated by the RMI server: {0} invoking: {1}.
- Category:
- RMI
- Cause:
- A java.lang.Error occurred while invoking method {1} on {0}. A ServerError occurred due to the server side RMI method call.
- Action:
- Check the nested exception in the ServerError for more details.
- BEA-080011
- Empty workingSet found while assembling the heartbeat for {0}.
- Category:
- RMI
- Cause:
- An empty set of references for {0} was found while assembling the deterministic garbage collector (DGC) heartbeats for all remote virtual machines that are referenced from this virtual machine.
- Action:
- If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support.
- BEA-080012
- No workingSet found for {0} residing in {1}.
- Category:
- RMI
- Cause:
- An empty working set for {0} was found while periodically scanning the list of finalized references and decrementing the count for any reference found. This is related to the deterministic garbage collector (DGC).
- Action:
- If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
- BEA-080013
- Reference for {0} not found in working set.
- Category:
- RMI
- Cause:
- Did not find {0} in the working set while attempting to decrement the reference count. This is related to the deterministic garbage collector (DGC).
- Action:
- If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
- BEA-080015
- Could not mark references {0}.
- Category:
- RMI
- Cause:
- An exception occurred during the execution of the DGC trigger.
- Action:
- If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
- BEA-080016
- No connection available to: {0}. References to objects hosted by it are in jeopardy.
- Category:
- RMI
- Cause:
- The client lost connection to the server {0}. If the server does not receive lease renewal messages on the server, RMI runtime removes the remote objects whose leases are not renewed.
- Action:
- If the server {0} has been shut down or crashed, no action is required. Otherwise, ensure that the network is healthy.
- BEA-080017
- Failed to renew lease for: {0} objects hosted by: {1}.
- Category:
- RMI
- Cause:
- This message is logged only in debug mode.
- Action:
- No action is required.
- BEA-080019
- Marked in: {0} milliseconds
- Category:
- RMI
- Cause:
- This message is logged only if the LogDGCStatistics debug flag is enabled.
- Action:
- No action is required.
- BEA-080020
- An exception occurred in the DGC server sweep {0}.
- Category:
- RMI
- Cause:
- A runtime error occurred while the DGC server (host of remote objects) requested a sweep to periodically clean up server references.
- Action:
- Provide the log files to My Oracle Support for further analysis of the problem.
- BEA-080021
- Sweep freed: {0} objects in: {1} milliseconds. {2} exported objects remain.
- Category:
- RMI
- Cause:
- This message is logged only if the LogDGCStatistics debug flag is enabled.
- Action:
- No action is required.
- BEA-080022
- Tried to enroll lost reference: {0}.
- Category:
- RMI
- Cause:
- This message is logged when an attempt is made to increment the reference count of a lost reference. The reference may have already been released.
- Action:
- If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
- BEA-080023
- Tried to unenroll a lost reference: {0}.
- Category:
- RMI
- Cause:
- This message is logged only if the DebugDGCEnrollment flag is enabled for debugging.
- Action:
- No action is required.
- BEA-080024
- Tried to renew the lease on the lost reference: {0}.
- Category:
- RMI
- Cause:
- This message is logged only if the DebugDGCEnrollment flag is enabled for debugging.
- Action:
- No action is required.
- BEA-080026
- Exporting remote object {0} with ID {1}.
- Category:
- RMI
- Cause:
- When a remote object is exported into RMI, RMI runtime assigns an object ID to it, thus setting up the environment for remote invocation.
- Action:
- This is an informational message. No action is required.
- BEA-080027
- A heartbeat was not sent due to probable client disconnect.
- Category:
- RMI
- Cause:
- A thin-client was disconnected from the server.
- Action:
- This is an informational message. No action is required.
- BEA-080028
- Failover attempt failed: {0} after {1} retries
- Category:
- RMI
- Cause:
- The cause was {0}
- Action:
- Please check the trace message.
- BEA-090058
- A Security Provider Exception occurred in a non-default AuditProvider {0}
- Category:
- Security
- Cause:
- A Security exception occurred during an audit write event.
- Action:
- Check errors or access permissions for the Auditing provider.
- BEA-090059
- The "{0}" AccessDecision class encountered an invalid Principal while attempting to check access to a WebLogic resource. Error: {1}
- Category:
- Security
- Cause:
- It is possible for this error to occur if a user has been deleted from a security realm while that user is still active.
- Action:
- If the user was mistakenly removed from the security realm, define them in the security realm again. Otherwise, no action is needed.
- BEA-090060
- The AccessDecision class "{0}" returned an error: {1}.
- Category:
- Security
- Cause:
- There are multiple possible causes.
- Action:
- Carefully read the returned error to determine if any action is required.
- BEA-090063
- The DeployableRoleMapper "{0}" returned an error: {1}.
- Category:
- Security
- Cause:
- There are multiple possible causes.
- Action:
- Carefully read the returned error to determine if any action is required.
- BEA-090064
- The DeployableAuthorizer "{0}" returned an error: {1}.
- Category:
- Security
- Cause:
- There are multiple possible causes.
- Action:
- Carefully read the returned error to determine if any action is required.
- BEA-090074
- Initializing {0} provider using LDIF template file {1}.
- Category:
- Security
- Cause:
- Either this is the first time this security provider has been initialized or the marker file indicating initialization (with a .initialized extension) has been removed from the system.
- Action:
- Look for a matching LoadedLDIFFForProvider message which indicates the successful loading the LDIF information for this security provider.
- BEA-090075
- The {0} provider has had its LDIF information loaded from: {1}
- Category:
- Security
- Cause:
- The provider was requested to import data.
- Action:
- No action is required.
- BEA-090076
- A failure occurred attempting to load LDIF for provider {0} from file {1}.
- Category:
- Security
- Cause:
- An exception occurred attempting to open a temporary file as part of the load process.
- Action:
- Examine the exception and correct the cause.
- BEA-090118
- LDIF template file {1} was empty. The WebLogic provider {0} has been bootstrapped but has not been initialized with any LDIF data.
- Category:
- Security
- Cause:
- A WebLogic provider LDIF template file may have been overwritten with an empty file.
- Action:
- If the server boots successfully, no action is needed. If the server does not boot successfully then an attempt should be made to recover non-empty LDIFT template file from the WebLogic Server kit.
- BEA-090119
- LDIF template file {1} not found. The WebLogic provider {0} has been bootstrapped but has not been initialized with any LDIF data.
- Category:
- Security
- Cause:
- A WebLogic provider LDIF template file may have been deleted by mistake.
- Action:
- If the server boots successfully, no action is needed. If the server does not boot successfully, an attempt should be made to recover the LDIFT template file from the WebLogic Server kit.
- BEA-090126
- Unable to read a valid version number for property {0} from file {1}. Received exception {2}.
- Category:
- Security
- Cause:
- The value for the {0} property may have been corrupted.
- Action:
- Shutdown the server. Attempt to determine what the proper value for the {0} property should be and edit the file so that it reflects that value. If it is not possible to determine the proper value for the {0} property, edit the file and reset the {0} value to 0. Reboot WebLogic Server.
- BEA-090127
- Encountered a {2} exception while attempting to read from file {1} for WebLogic {0} provider.
- Category:
- Security
- Cause:
- The {1} file may have been deleted while it was being accessed.
- Action:
- Shutdown the server. Attempt to restore the file from a backup. If no backup is available,reboot the server. Note that the default WebLogic provider might not be correctly initialized.
- BEA-090129
- Updating {0} provider to version {2} using LDIF update template file {1}.
- Category:
- Security
- Cause:
- This security provider has not yet been updated or the marker file indicating initialization (with a .initialized extension) has been removed.
- Action:
- Look for a matching LoadedLDIFFForProvider message in the log file which indicates success loading the LDIF information for this security provider.
- BEA-090130
- Failure {3} while attempting to update the LDIF to version {2} in file {1} for WebLogic {0} provider.
- Category:
- Security
- Cause:
- The directory into which the {1} is to be written may not be writable, the file may not be writable, or the file may not be a valid properties file.
- Action:
- Ensure both the directory and file are writable. If they are writable, restore the file from backup or open the file and see if the properties within it are corrupt and correct accordingly. The version for provider {0} needs to be set to {2} in the file.
- BEA-090131
- Could not create a {0} JDK keystore instance. Exception: {1}
- Category:
- Security
- Cause:
- {0} is not a valid JDK keystore type or the JDK keystore type is not properly configured.
- Action:
- Verify that the correct keystore type was specified and that the keystore type is correctly specified in the java.security file. Verify that the code for the JDK keystore is in the JDK extensions directory. Reboot the server. after correcting the problem.
- BEA-090132
- Could not open the keystore file {0} for read access. Exception: {1}
- Category:
- Security
- Cause:
- The file does not exist, the file is a directory rather than a regular file or the file cannot be opened for reading.
- Action:
- Verify that the correct path to the keystore file was specified and that the keystore file exists. Reboot the server after correcting the problem.
- BEA-090133
- Could not load a {1} keystore from the file {0}. Exception: {2}
- Category:
- Security
- Cause:
- There is an I/O or format problem with the keystore data.
- Action:
- Verify that the path to the keystore, the keystore type, and the password for the keystore were specified correctly. Note that some keystore types (for example, JKS) do not require a password for read-only access. Read the exception text for more help on diagnosing the problem. Reboot the server after correcting the problem.
- BEA-090134
- Could not load a {1} keystore from the file {0}. Exception: {2}
- Category:
- Security
- Cause:
- Some certificates in the keystore could not be loaded.
- Action:
- Verify that the crypto providers required by the certificates in the keystore are properly configured in the java.security file and that their code is in the JDK extensions directory. Look at the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
- BEA-090135
- Could not load a {1} keystore from the file {0}. Exception: {2}
- Category:
- Security
- Cause:
- The algorithm used to check the integrity of the keystore cannot be found.
- Action:
- Verify that the algorithm used to check the keystore integrity is properly configured in the java.security file and that the code is in the JDK extensions directory. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
- BEA-090161
- A failure occurred attempting to save LDIF for security provider {0} using file {1}.
- Category:
- Security
- Cause:
- An exception occurred attempting to open a temporary file as part of the export process.
- Action:
- Examine the exception and correct the cause.
- BEA-090162
- The {0} provider has had its LDIF information saved in: {1}
- Category:
- Security
- Cause:
- The security provider was requested to export data.
- Action:
- No action is required.
- BEA-090163
- The {0} provider did not import a duplicate entry: {1}
- Category:
- Security
- Cause:
- The security provider already contained the imported data.
- Action:
- Delete the existing data and import data into the security provider again.
- BEA-090234
- The Auditing Provider is not initialized.
- Category:
- Security
- Cause:
- The WebLogic Auditing provider was not initialized before the writeEvent method was called.
- Action:
- Ensure that the WebLogic Auditing provider has been initialized before events are written.
- BEA-090235
- Invalid Audit Severity
- Category:
- Security
- Cause:
- The Audit severity value is invalid or not supported.
- Action:
- Verify the Audit severity value passed to the setAuditSeverity method.
- BEA-090236
- DefaultAuthenticatorImpl constructor failed: {0}
- Category:
- Security
- Cause:
- An exception was thrown in the constructor of the WebLogic Authentication provider.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090237
- Validation of old password failed
- Category:
- Security
- Cause:
- The old password was not valid.
- Action:
- Pass in the correct old password to the changeUserPassword method.
- BEA-090239
- Identity Assertion type cannot be null
- Category:
- Security
- Cause:
- The token type was null.
- Action:
- The containers should not be passing a null token type. This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090240
- Identity Assertion token cannot be null
- Category:
- Security
- Cause:
- The identity assertion token was null.
- Action:
- The containers should not be passing a null token. This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090241
- Identity Assertion type of {0} is not a configured active type
- Category:
- Security
- Cause:
- The identity assertion token type was not configured in the WebLogic Identity Assertion provider.
- Action:
- Configure the identity assertion type {0} in the Active Types attribute of the WebLogic Identity Assertion provider.
- BEA-090248
- Unrecognized Callback
- Category:
- Security
- Cause:
- Callback type is not supported.
- Action:
- Verify that the LoginModule for the configured Authentication provider is only passing a NameCallback when calling the handle method.
- BEA-090249
- Cursor is null
- Category:
- Security
- Cause:
- A null cursor is not supported.
- Action:
- Modify the code to pass a non-null cursor.
- BEA-090250
- Cursor not found {0}
- Category:
- Security
- Cause:
- Cursor was not found in the list of valid cursors.
- Action:
- Verify that the cursor passed to the method is valid and was returned from a method that creates cursors. Examples of such methods are listUsers, listGroups and listRoles.
- BEA-090251
- haveCurrent error for cursor name {0}
- Category:
- Security
- Cause:
- LDAP exception during haveCurrent method.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090252
- advance error for cursor name {0}
- Category:
- Security
- Cause:
- an LDAP exception occurred while advancing the list.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090253
- close error for cursor name {0}
- Category:
- Security
- Cause:
- an LDAP exception occurred while closing this list cursor.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090254
- name cannot be null
- Category:
- Security
- Cause:
- The name cannot be null in the setUserDescription, setGroupDescription, getUserDescription, or getGroupDescription methods.
- Action:
- Pass in a non-null name to the method.
- BEA-090255
- User or Group {0}
- Category:
- Security
- Cause:
- The user or group cannot be found.
- Action:
- Pass in a user or group that exists.
- BEA-090256
- Error setting description for {0}
- Category:
- Security
- Cause:
- an exception occurred while calling to modify the description in the server.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090257
- group cannot be null
- Category:
- Security
- Cause:
- The group name cannot be null.
- Action:
- Pass in a non-null group name to the method.
- BEA-090258
- max cannot be < 0
- Category:
- Security
- Cause:
- The maximumToReturn value cannot be less than zero.
- Action:
- Pass in a maximumToReturn parameter value that is greater or equal to zero.
- BEA-090259
- Group {0} can not be found.
- Category:
- Security
- Cause:
- Group {0} does not exist in the server.
- Action:
- Pass in a group that exists.
- BEA-090260
- Error listing group members for {0}
- Category:
- Security
- Cause:
- an exception was thrown while searching for the group members in the store.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090261
- wildcard cannot be null
- Category:
- Security
- Cause:
- Wildcard parameter is null.
- Action:
- Pass a non-null wildcard parameter to the method.
- BEA-090262
- Error listing groups {0}
- Category:
- Security
- Cause:
- an exception was thrown while searching for the groups in the store.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090263
- parent group cannot be null
- Category:
- Security
- Cause:
- Parent group name is null.
- Action:
- Pass a non-null parent group name parameter to this method.
- BEA-090264
- member cannot be null
- Category:
- Security
- Cause:
- Member name is null.
- Action:
- Pass a non-null member name parameter to this method.
- BEA-090265
- member cannot be parent group
- Category:
- Security
- Cause:
- Member name and parent group name are the same value.
- Action:
- Change either the member name or parent group name parameters of this method.
- BEA-090266
- group name cannot be null
- Category:
- Security
- Cause:
- Group name cannot be null.
- Action:
- Pass a non-null group name to the method.
- BEA-090267
- Group {0}
- Category:
- Security
- Cause:
- Group {0} already exists in the LDAP server. Users and groups must have unique names.
- Action:
- Pass in a unique group name.
- BEA-090268
- Group {0}
- Category:
- Security
- Cause:
- User {0} already exists in the LDAP server. Users and groups must have unique names.
- Action:
- Pass in a unique user name.
- BEA-090269
- Error adding group {0}
- Category:
- Security
- Cause:
- an exception was thrown while adding the group in the store.
- Action:
- Users and groups must have unique names.
- BEA-090270
- group cannot be same as member
- Category:
- Security
- Cause:
- Member and group names must be unique.
- Action:
- Pass in a group and member name that are unique.
- BEA-090271
- Member {0} can not be found.
- Category:
- Security
- Cause:
- Member does not exist.
- Action:
- Pass in a member name that exists in the store.
- BEA-090272
- Error adding member {0} to {1}
- Category:
- Security
- Cause:
- an exception was thrown while adding the member to the group in the store.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090273
- member cannot be group
- Category:
- Security
- Cause:
- Member and group names must be unique.
- Action:
- Pass in a group and member name that are unique.
- BEA-090274
- Error removing member {0} from {1}
- Category:
- Security
- Cause:
- an exception was thrown when removing the member from the group in the store.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090275
- Error removing group {0}
- Category:
- Security
- Cause:
- an exception was thrown while removing the group from the store.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090276
- Error removing group {0} invalid cursor
- Category:
- Security
- Cause:
- An InvalidCursorException exception was thrown while removing the group from the store.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090277
- Error destroying provider:
- Category:
- Security
- Cause:
- an LDAP exception was thrown while removing all the users and groups from the LDAP server.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090278
- Error listing member groups {0}
- Category:
- Security
- Cause:
- an LDAP exception was thrown while listing the member groups in the LDAP server.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090279
- Error listing users {0}
- Category:
- Security
- Cause:
- an LDAP exception was thrown while listing the users in the LDAP server.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090280
- user cannot be null
- Category:
- Security
- Cause:
- User name cannot be null.
- Action:
- Pass a non-null user name to the method.
- BEA-090281
- user name cannot be null
- Category:
- Security
- Cause:
- The user name cannot be null.
- Action:
- Pass a non-null user name to the method.
- BEA-090282
- password cannot be null
- Category:
- Security
- Cause:
- The password cannot be null.
- Action:
- Pass a non-null password to the method.
- BEA-090283
- User {0}
- Category:
- Security
- Cause:
- User {0} already exists in the LDAP server.
- Action:
- Pass in another user name.
- BEA-090284
- Group {0}
- Category:
- Security
- Cause:
- Group {0} already exists in the LDAP server. Groups and users must have unique names.
- Action:
- Pass in an user name that is not already an existing group.
- BEA-090285
- password must be at least {0} characters long
- Category:
- Security
- Cause:
- Password is not long enough.
- Action:
- Enter a password that meets the specified minimum length requirement.
- BEA-090286
- Error adding user {0}
- Category:
- Security
- Cause:
- an LDAP exception was thrown while adding the user to the LDAP server.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090287
- User {0} can not be found.
- Category:
- Security
- Cause:
- User {0} does not exist in the server.
- Action:
- Pass a user name that exists.
- BEA-090288
- Invalid password for user {0}
- Category:
- Security
- Cause:
- The bind to the LDAP server using this user name and password failed.
- Action:
- Pass a valid password or use the resetPassword method which does not require the old password.
- BEA-090289
- Error changing password for {0}
- Category:
- Security
- Cause:
- an LDAP exception was thrown while modifying the password in the LDAP server.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090290
- Error removing user {0}
- Category:
- Security
- Cause:
- an LDAP exception was thrown while removing the user from the server.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090291
- {0} search scope ({1}) not recognized
- Category:
- Security
- Cause:
- Search scope {1} is not a valid value.
- Action:
- Change the User Search Scope attribute for the LDAP Authentication provider.
- BEA-090293
- Error creating provider
- Category:
- Security
- Cause:
- An LDAP exception was thrown when checking the LDAP hierarchy in the initialization of the provider.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090294
- could not get connection
- Category:
- Security
- Cause:
- an LDAP exception was thrown because an LDAP connection could not be obtained from the connection pool.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090295
- caught unexpected exception
- Category:
- Security
- Cause:
- An unexpected LDAP exception was thrown when calling LDAP methods.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090296
- invalid URL {0}
- Category:
- Security
- Cause:
- an LDAP exception was thrown because of an invalid dynamic group URL.
- Action:
- Verify the dynamic group definition. Read the exception text for more information on diagnosing the problem.
- BEA-090297
- No CallbackHandler Specified
- Category:
- Security
- Cause:
- The callback handler is null.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090298
- No Delegate Specified
- Category:
- Security
- Cause:
- The LDAP delegate is null.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090299
- Username Not Supplied
- Category:
- Security
- Cause:
- The user name returned from the NameCallback cannot be null.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090300
- Identity Assertion Failed: User {0} does not exist
- Category:
- Security
- Cause:
- User does not exist in the LDAP server.
- Action:
- Add the user to the LDAP server or configure the Identity Assertion provider to return a user that exists.
- BEA-090301
- Password Not Supplied
- Category:
- Security
- Cause:
- Password cannot be null.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090302
- Authentication Failed: User {0} denied
- Category:
- Security
- Cause:
- The username and password could not bind to the LDAP server.
- Action:
- Verify the username and password.
- BEA-090303
- Authentication Failed: User {0} {1}
- Category:
- Security
- Cause:
- an LDAP exception caused the authentication of the user to fail.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090304
- Authentication Failed: User {0} {1}
- Category:
- Security
- Cause:
- An unexpected exception caused the authentication of the user to fail.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090305
- Authentication Failed Getting Groups for User {0} {1}
- Category:
- Security
- Cause:
- A group to which the user belongs was not found.
- Action:
- Verify the groups to which the user belongs.
- BEA-090306
- Authentication Failed Getting Groups for User {0} {1}
- Category:
- Security
- Cause:
- A Invalid Cursor, Invalid Parameter, or LDAP exception was thrown when looking up the groups of which the user is a member.
- Action:
- Read the exception text in {1} for more information on diagnosing the problem.
- BEA-090307
- DefaultAuthenticatorImpl constructor failed: {0}
- Category:
- Security
- Cause:
- A exception was thrown in the constructor for the WebLogic Authentication provider.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090308
- Validation of old password failed
- Category:
- Security
- Cause:
- The old password was not valid.
- Action:
- Verify the old password. Optionally, use the resetPassword method to change the user password.
- BEA-090310
- Failed to create resource
- Category:
- Security
- Cause:
- An EnCreateException was thrown when creating the security policy.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090311
- Failed to set resource expression
- Category:
- Security
- Cause:
- An EnCreateException was thrown when setting the security policy expression.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090313
- policy removal error
- Category:
- Security
- Cause:
- A EnRemoveException was thrown during the deletion of security policies for the application.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090314
- Entitlement Engine unable to connect to the embedded LDAP server {0}
- Category:
- Security
- Cause:
- An exception was thrown when initializing the entitlement engine for the WebLogic Authorization provider.
- Action:
- Read the exception text in {0} for more information on diagnosing the problem.
- BEA-090315
- DefaultAuthorizerImpl init failed: {0}
- Category:
- Security
- Cause:
- An exception was thrown during the initialization of the WebLogic Authorization provider.
- Action:
- Read the exception text in {0} for more information on diagnosing the problem.
- BEA-090316
- null helper
- Category:
- Security
- Cause:
- The helper cannot be null.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090317
- bug in PredicateArgument
- Category:
- Security
- Cause:
- The arguments for the predicate are invalid.
- Action:
- Verify the definition of the condition expression of the security policy.
- BEA-090318
- DefaultRoleMapperImpl init failed: {0}
- Category:
- Security
- Cause:
- An exception was thrown in the initialization method of the WebLogic Role Mapping provider.
- Action:
- Read the exception text in {0} for more information on diagnosing the problem.
- BEA-090319
- Unknown resource type: {0}
- Category:
- Security
- Cause:
- The role id cannot be null.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090320
- Failed to create role
- Category:
- Security
- Cause:
- An exception was thrown during the createRole method.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090321
- Failed to set role expression
- Category:
- Security
- Cause:
- An exception was thrown during the setRole method.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090322
- role removal error
- Category:
- Security
- Cause:
- An EnRemoveException was thrown during the delete operation.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090324
- DefaultCredentialMapperImpl init failed: {0}
- Category:
- Security
- Cause:
- An exception was thrown during the initialization of the WebLogic Credential Mapping provider.
- Action:
- Read the exception text in {0} for more information on diagnosing the problem.
- BEA-090326
- DefaultCredentialMapperImpl.listCredentials got LDAP exception
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to get the list of credentials for this WebLogic resource.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090327
- DefaultCredentialMapperImpl.getCurrentCredentialRemoteUsername failed: No such credentials list cursor available
- Category:
- Security
- Cause:
- Cursor is invalid.
- Action:
- Verify that the cursor was returned from the listCredentials method.
- BEA-090329
- DefaultCredentialMapperImpl.listMappings got LDAP exception
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to get the list of credential mappings for this WebLogic resource.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090330
- DefaultCredentialMapperImpl.getCurrentMappingWLSUsername failed: No such resource maps list cursor available
- Category:
- Security
- Cause:
- Cursor is invalid.
- Action:
- Verify that the cursor was returned from the listMappings method.
- BEA-090331
- DefaultCredentialMapperImpl.getCurrentMappingRemoteUsername failed: No such resource maps list cursor available
- Category:
- Security
- Cause:
- Cursor is invalid.
- Action:
- Verify that the cursor was returned from the listMappings method.
- BEA-090332
- DefaultCredentialMapperImpl.getRemoteUserName got LDAP exception
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to get the credential map or the credential map principal.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090333
- DefaultCredentialMapperImpl.getRemotePassword got LDAP exception
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to get the password for the credential map.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090334
- DefaultCredentialMapperImpl.setUserPasswordCredential got LDAP exception
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to set the password for the credential map.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090335
- DefaultCredentialMapperImpl.setUserPasswordCredentialMapping got LDAP exception
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to set the credential resource map.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090336
- DefaultCredentialMapperImpl.removeUserPasswordCredential got LDAP exception
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to remove the user password credential.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090337
- DefaultCredentialMapperImpl.removeUserPasswordCredentialMapping got LDAP exception
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to remove the user password credential mapping.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090339
- Could not create file output stream {0}
- Category:
- Security
- Cause:
- An IO exception was thrown during the create of either the temporary file or the real file for the Audit log.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090367
- This method not yet implemented
- Category:
- Security
- Cause:
- Method is not implemented and should not be used.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090375
- Null TokenType Parameter
- Category:
- Security
- Cause:
- The token type is null.
- Action:
- The containers should not pass a null token types. This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090377
- Identity Assertion Failed, {0}
- Category:
- Security
- Cause:
- An IdentityAssertion exception was thrown in the assertIdentity or assertChallengeIdentity method of the Identity Assertion provider
- Action:
- Read the exception text in {0} for more information on diagnosing the problem.
- BEA-090380
- Identity Assertion Failed, Unsupported Token Type: {0}
- Category:
- Security
- Cause:
- Token type is not configured as an active type.
- Action:
- Define the token type {0} in the Active Types attribute of the configured Identity Assertion provider.
- BEA-090393
- Security service not yet initialized: {0}
- Category:
- Security
- Cause:
- The Security service must be initialized before it can be used.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090442
- location null or empty
- Category:
- Security
- Cause:
- A keystore filename must not be null or a zero length string.
- Action:
- Set the keystore location to a valid filename.
- BEA-090443
- null file
- Category:
- Security
- Cause:
- The load and store methods require a non-null filename.
- Action:
- Pass a valid filename to the keystore load or store method.
- BEA-090447
- invalid flag value {0}
- Category:
- Security
- Cause:
- The value specified for the LoginModule control flag is not supported.
- Action:
- Pass in a valid value for the LoginModule control flag. Valid values are REQUIRED, OPTIONAL, REQUISITE, or SUFFICIENT.
- BEA-090448
- Invalid Format: {0}
- Category:
- Security
- Cause:
- Import format is either null, zero length, or not supported by this provider.
- Action:
- Pass in a supported format.
- BEA-090449
- Invalid Constraints
- Category:
- Security
- Cause:
- Constraints are not supported.
- Action:
- Do not pass constraints to the provider.
- BEA-090450
- Invalid name supplied
- Category:
- Security
- Cause:
- The filename, domain name, or security realm name cannot be null.
- Action:
- Pass a non null filename, domain name, or security realm name.
- BEA-090451
- Unable to read file: {0}
- Category:
- Security
- Cause:
- Import file cannot be read.
- Action:
- Verify the import filename.
- BEA-090453
- Import File Error
- Category:
- Security
- Cause:
- An IO exception was thrown while importing from the file.
- Action:
- Verify the import filename. Read the exception text or the associated log message for more information on diagnosing the problem.
- BEA-090455
- Export File Error
- Category:
- Security
- Cause:
- An IO exception was thrown while exporting to the file.
- Action:
- Verify the export filename. Read the exception text or the associated log message for more information on diagnosing the problem.
- BEA-090469
- Invalid file format
- Category:
- Security
- Cause:
- LDIF template file did not contain any substitution entries and does not have the correct file format.
- Action:
- Verify that the file specified to the import operation is really a LDIF template file produced by an export operation.
- BEA-090473
- DefaultAuthorizerImpl search failed: {0}
- Category:
- Security
- Cause:
- An exception was thrown trying to access the data store.
- Action:
- Look at the exception text in {0} for more information on diagnosing the problem.
- BEA-090474
- Unable to create temporary file: {0}
- Category:
- Security
- Cause:
- The java.io.tmpdir system property is not set correctly or the temporary directory is not writeable.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090511
- The following exception has occurred:
- Category:
- Security
- Cause:
- An error condition has occurred.
- Action:
- Read the associated exception in the log or in application to determine the problem. In general, a stack trace can be used to debug an existing problem.
- BEA-090512
- The WebLogic Auditing provider failed to register to listen for AuditorMBean attribute change notifications
- Category:
- Security
- Cause:
- The installation of WebLogic Server is corrupt.
- Action:
- In order for a change in the auditing severity to take effect, the server needs to be rebooted.
- BEA-090516
- The {0} provider has preexisting LDAP data.
- Category:
- Security
- Cause:
- The provider was initialized during a previous boot of the WebLogic Server
- Action:
- No action necessary.
- BEA-090517
- Group {0} cannot be added to group {1} since group {0} is already ancestor of group {1}.
- Category:
- Security
- Cause:
- Group membership can not be circular..
- Action:
- Ensure that group membership is not circular. Add this group to a different group.
- BEA-090545
- DefaultRoleMapperImpl search failed: {0}
- Category:
- Security
- Cause:
- An exception was thrown trying to access the data store.
- Action:
- Look at the exception text in {0} for more information on diagnosing the problem.
- BEA-090553
- Invalid system property value: {0}={1}
- Category:
- Security
- Cause:
- Invalid system property value was passed on the command line.
- Action:
- Make sure the property value is valid and restart the server.
- BEA-090555
- The DefaultCredentialMapper could not get credentials. The requestor is {0}. The initiator is {1}. The resource is {2}. The exception is {3}.
- Category:
- Security
- Cause:
- An unexpected exception occurred when trying to get credentials.
- Action:
- Read the exception text from the log message for more information on diagnosing the problem.
- BEA-090583
- The EndCertificateSelector constructor was passed an illegal X509Certificate.
- Category:
- Security
- Cause:
- The X509Certificate must not be null.
- Action:
- Pass a valid X509Certificate to the EndCertificateSelector constructor.
- BEA-090584
- The IssuerDNSerialNumberSelector constructor was passed an illegal issuer DN.
- Category:
- Security
- Cause:
- The issuer DN must not be null or empty.
- Action:
- Pass a valid issuer DN to the IssuerDNSerialNumberSelector constructor.
- BEA-090585
- The IssuerDNSerialNumberSelector constructor was passed an illegal serial number.
- Category:
- Security
- Cause:
- The serial number must not be null.
- Action:
- Pass a valid serial number to the IssuerDNSerialNumberSelector constructor.
- BEA-090586
- The SubjectDNSelector constructor was passed an illegal subject DN.
- Category:
- Security
- Cause:
- The subject DN must not be null or empty.
- Action:
- Pass a valid subject DN to the SubjectDNSelector constructor.
- BEA-090587
- The SubjectKeyIdentifierSelector constructor was passed an illegal subject key identifier.
- Category:
- Security
- Cause:
- The subject key identifier must not be null or empty.
- Action:
- Pass a valid subject key identifier to the SubjectKeyIdentifierSelector constructor.
- BEA-090588
- The WLSCertPathBuilderResult constructor was passed an illegal Certpath.
- Category:
- Security
- Cause:
- The CertPath must not be null or empty.
- Action:
- Pass a valid CertPath to the WLSCertPathBuilderResult constructor. It must at least contain the end certificate of the cert chain."
- BEA-090593
- The realm {0} has an illegal cert path builder configured. To correct the problem, select one of the realm"s cert path providers as the realm"s cert path builder.
- Category:
- Security
- Cause:
- The realm {0} has an illegal cert path builder configured.
- Action:
- To correct the problem, select one of the realm"s cert path providers as the realm"s cert path builder.
- BEA-090594
- The {0} cert path security provider was passed an illegal CertPathParameters.
- Category:
- Security
- Cause:
- The CertPathParameters must be a weblogic.security.spi.CertPathBuilderParametersSpi.
- Action:
- The {0} cert path security provider must not be called directly by application code.
- BEA-090595
- The {0} cert path security provider was passed an illegal CertPathParameters.
- Category:
- Security
- Cause:
- The CertPathParameters must be a weblogic.security.spi.CertPathValidatorParametersSpi.
- Action:
- The {0} cert path security provider must not be called directly by application code.
- BEA-090596
- The WebLogicCertPathProvider was passed an unsupported CertPathSelector.
- Category:
- Security
- Cause:
- The CertPathSelector must be an EndCertificateSelector.
- Action:
- Pass an EndCertificateSelector to the WebLogicCertPathProvider.
- BEA-090597
- The CertificateRegistry was passed an unsupported CertPathSelector.
- Category:
- Security
- Cause:
- The CertPathSelector must be an EndCertificateSelector, IssuerDNSerialNumberSelector, SubjectDNSelector or SubjectKeyIdentifierSelector.
- Action:
- Pass an EndCertificateSelector, IssuerDNSerialNumberSelector, SubjectDNSelector or SubjectKeyIdentifierSelector to the CertificateRegistry.
- BEA-090603
- The certificate chain is invalid because it could not be completed. The trusted CAs did not include {0}.
- Category:
- Security
- Cause:
- The trusted CAs did not include {0}.
- Action:
- Add {0} to the chain or to the list of the trusted CAs if you want this chain to be validated.
- BEA-090604
- The certificate chain is invalid because none of its certificates is a trusted CA.
- Category:
- Security
- Cause:
- None of its certificates is a trusted CA.
- Action:
- Add one of the certificates in the chain to the list of of trusted CAs if you want this chain to be validated.
- BEA-090605
- The certificate chain is invalid because it contains the certificate {0} is either expired or is not currently valid.
- Category:
- Security
- Cause:
- The invalid certificate is {0}.
- Action:
- If this certificate is a trusted CA, and the certificate authority has issued a replacement certificate with the same subject DN and private key, and you want the certificate chain to be validated, then replace the trusted CA with the updated one. Otherwise, you must obtain a new certificate chain if you want the chain to be validated.
- BEA-090606
- The certificate chain is invalid because a certificate"s issuer DN "{0}" does not match it"s CA"s subject DN "{1}".
- Category:
- Security
- Cause:
- The certificate"s issuer DN is "{0}". The CA"s subject DN is "{1}".
- Action:
- You must obtain a new certificate chain if you want the chain to be validated.
- BEA-090607
- The certificate chain is invalid because of an encoding error for certificate {0}.
- Category:
- Security
- Cause:
- The invalid certificate is {0}.
- Action:
- Ensure that the certificate chain only contains certificates using RSA keys and that the JDK is configured to support RSA keys.
- BEA-090608
- The certificate chain is invalid because a certificate"s signature could not be validated by it"s CA"s public key. The invalid certificate is {0}. The CA is {1}.
- Category:
- Security
- Cause:
- Most likely, the wrong CA is in the chain for the certificate. The invalid certificate is {0}. The CA is {1}.
- Action:
- You must obtain a new certificate chain if you want the chain to be validated.
- BEA-090609
- The certificate chain is invalid because there is no JDK provider for certificate {0}.
- Category:
- Security
- Cause:
- The invalid certificate is {0}.
- Action:
- Ensure that the certificate chain only contains certificates using RSA keys and that the JDK is configured to support RSA keys.
- BEA-090610
- The certificate chain is invalid because there is no default JDK provider for certificate {0}.
- Category:
- Security
- Cause:
- The invalid certificate is {0}.
- Action:
- Ensure that the certificate chain only contains certificates using RSA keys and that the JDK is configured to support RSA keys.
- BEA-090611
- The certificate chain is invalid because a certificate"s signature could not be validated. The invalid certificate is {0}.
- Category:
- Security
- Cause:
- Most likely, the certificate has been tampered with. The invalid certificate is {0}.
- Action:
- You must obtain a new certificate chain if you want the chain to be validated.
- BEA-090612
- The certificate chain is invalid because it contains a certificate with an unsupported critical extension. The invalid certificate is {0}. The unsupported critical extension"s oid is {1}.
- Category:
- Security
- Cause:
- The invalid certificate is {0}. The unsupported critical extension"s oid is {1}.
- Action:
- You must obtain a new certificate chain if you want the chain to be validated.
- BEA-090613
- The certificate chain is invalid because it is longer than one of it"s CA"s allows. The CA is {0}. The chain length to that CA is {1}. The maximum chain length to that CA is {2}.
- Category:
- Security
- Cause:
- The CA is {0}. The chain length to that CA is {1}. The maximum chain length to that CA is {2}.
- Action:
- You must obtain a new certificate chain if you want the chain to be validated.
- BEA-090614
- The certificate chain is invalid because it contains a CA without basic constraints. The CA is {0}.
- Category:
- Security
- Cause:
- The CA is {0}.
- Action:
- You must obtain a new certificate chain if you want the chain to be validated.
- BEA-090615
- A CertPathBuilderParameters or CertPathValidatorParameters object was constructed with a list of trusted CAs that includes a null trusted CA.
- Category:
- Security
- Cause:
- A CertPathBuilderParameters or CertPathValidatorParameters object was constructed with a list of trusted CAs that includes a null trusted CA.
- Action:
- Ensure that the list of trusted CAs passed in does not include a null trusted CA.
- BEA-090616
- The configured CertPathBuilder provider returned an empty cert path.
- Category:
- Security
- Cause:
- The configured CertPathBuilder provider has a bug. It should never return an empty cert path.
- Action:
- Fix the bug in the configured CertPathBuilder.
- BEA-090618
- The WLS CertPathValidator was passed a null or empty cert path.
- Category:
- Security
- Cause:
- The WLS CertPathValidator was passed a null or empty cert path.
- Action:
- Pass a cert path containing at least one certificate to the WLS CertPathValidator.
- BEA-090620
- There is no JDK CertPathBuilder for algorithm {0}.
- Category:
- Security
- Cause:
- There is no JDK CertPathBuilder for algorithm {0}.
- Action:
- This is an internal WebLogic Server error in either the JDK or a WLS CertPathProvider.
- BEA-090621
- There is no JDK CertPathValidator for algorithm {0}.
- Category:
- Security
- Cause:
- There is no JDK CertPathValidator for algorithm {0}.
- Action:
- This is an internal WebLogic Server error in either the JDK or a WLS CertPathProvider.
- BEA-090623
- Failed to get the default trusted CAs for this server.
- Category:
- Security
- Cause:
- This exception is thrown when an exception occurs when finding this server"s trusted CAs.
- Action:
- Look at the exception text for more information on diagnosing the problem.
- BEA-090624
- Failed to create an X509 CertPath from an array of X509Certificates.
- Category:
- Security
- Cause:
- Failed to create an X509 CertPath from an array of X509Certificates.
- Action:
- Look at the exception text for more information on diagnosing the problem.
- BEA-090635
- No Results
- Category:
- Security
- Cause:
- There are no policies that match the search criteria.
- Action:
- No action necessary.
- BEA-090636
- No Results
- Category:
- Security
- Cause:
- There are no roles that match the search criteria.
- Action:
- No action necessary.
- BEA-090637
- No role name supplied
- Category:
- Security
- Cause:
- The role name is null or contains no data.
- Action:
- Specify a valid role name.
- BEA-090638
- No resource data
- Category:
- Security
- Cause:
- The resource data parameter was not supplied or is empty.
- Action:
- Specify valid resource data.
- BEA-090639
- No resource type
- Category:
- Security
- Cause:
- The resource type information was not supplied.
- Action:
- Specify a valid resource type.
- BEA-090640
- No resource identifier
- Category:
- Security
- Cause:
- The resource identifier parameter was not supplied or is empty.
- Action:
- Specify a valid resource identifier.
- BEA-090641
- No resource keys found
- Category:
- Security
- Cause:
- An invalid resource identifier was supplied.
- Action:
- Specify a valid resource identifier.
- BEA-090642
- Invalid data type for {0} resource key value
- Category:
- Security
- Cause:
- The data type of a resource key value is not valid.
- Action:
- Specify a valid resource key data type value.
- BEA-090643
- Invalid resource type: "{0}"
- Category:
- Security
- Cause:
- An invalid or unknown resource type was supplied.
- Action:
- Specify a valid resource type.
- BEA-090644
- Expected resource type: {0}
- Category:
- Security
- Cause:
- An invalid or unknown resource type was supplied.
- Action:
- Verify a valid resource type was supplied and contact BEA support.
- BEA-090645
- Expected resource key: {0}
- Category:
- Security
- Cause:
- An invalid resource identifier was supplied.
- Action:
- Specify a valid resource identifier.
- BEA-090646
- Unknown resource key: {0}
- Category:
- Security
- Cause:
- The resource key supplied in the resource data is unknown.
- Action:
- Specify only resource keys valid for a specific resource type.
- BEA-090647
- Invalid application name
- Category:
- Security
- Cause:
- The application name parameter was empty or contains invalid values.
- Action:
- Specify a valid application name.
- BEA-090648
- Invalid component name
- Category:
- Security
- Cause:
- The component name parameter was empty or contains invalid values.
- Action:
- Specify a valid component name.
- BEA-090649
- Illegal application search name
- Category:
- Security
- Cause:
- The application name was not a legal search string.
- Action:
- Specify a valid application name search string.
- BEA-090650
- Illegal component search name
- Category:
- Security
- Cause:
- The component name was not a legal search string.
- Action:
- Specify a valid component name search string.
- BEA-090651
- No component type
- Category:
- Security
- Cause:
- The component type parameter is empty.
- Action:
- Specify a valid component type of EJB, WebApp, Connector or WebService.
- BEA-090652
- Invalid component type: "{0}"
- Category:
- Security
- Cause:
- The component type parameter specified is not valid.
- Action:
- Specify a valid component type of EJB, WebApp, Connector or WebService.
- BEA-090653
- Empty array value found
- Category:
- Security
- Cause:
- An empty string was supplied for an array element of the resource key.
- Action:
- Specify a valid string.
- BEA-090654
- Unexpected resource identifier data: "{0}"
- Category:
- Security
- Cause:
- An invalid resource identifier was supplied.
- Action:
- Specify a valid resource identifier.
- BEA-090655
- Unexpected resource key array value: "{0}"
- Category:
- Security
- Cause:
- An invalid resource identifier was supplied.
- Action:
- Specify a valid resource identifier.
- BEA-090656
- Empty {0} resource {1} string
- Category:
- Security
- Cause:
- An empty string was supplied for an element of the resource.
- Action:
- Specify a valid string.
- BEA-090657
- Empty {0} resource {1} array string
- Category:
- Security
- Cause:
- An empty string was supplied for an array element of the resource.
- Action:
- Specify a valid string.
- BEA-090662
- The DeployableAuthorizer "{0}" implements the deprecated {1} interface.
- Category:
- Security
- Cause:
- At security provider initialization a deprecated security interface was detected.
- Action:
- No immediate action necessary. However, the security provider should be updated.
- BEA-090663
- The DeployableRoleMapper "{0}" implements the deprecated {1} interface.
- Category:
- Security
- Cause:
- At security provider initialization a deprecated security interface was detected.
- Action:
- No immediate action necessary. However, the security provider should be updated.
- BEA-090666
- Deploy handle not supplied
- Category:
- Security
- Cause:
- The deployment handle is null.
- Action:
- This exception is an internal WebLogic Server error. Contact BEA support.
- BEA-090667
- Application information not supplied
- Category:
- Security
- Cause:
- The application information is null.
- Action:
- This exception is an internal WebLogic Server error. Contact BEA support.
- BEA-090671
- Unable to get password digest for user name {0}
- Category:
- Security
- Cause:
- The user does not exist in the WebLogic authentication provider Embedded LDAP server or there is no password information available to calculate a digest.
- Action:
- Verify that the user exists in the WebLogic authentication provider, the authentication provider has the PasswordDigestEnabled attribute set to true, and the user entry has set the password since the attribute was set to true.
- BEA-090683
- The CertificateRegistry could not build a certificate path for end certificate {0}. This indicates that either someone is trying to access the server with an untrusted certificate or that the administrator has forgotten to register the certificate in the CertificateRegistry.
- Category:
- Security
- Cause:
- The CertificateRegistry does not contain the certificate {0}.
- Action:
- If you want to trust the end certificate {0}, then register it in the CertificateRegistry.
- BEA-090684
- The CertificateRegistry could not build a certificate path for the subject DN {0}. This indicates that either someone is trying to access the server with an untrusted subject DN or that the administrator has forgotten to register a certificate with this subject DN in the CertificateRegistry.
- Category:
- Security
- Cause:
- The CertificateRegistry does not contain a certificate whose subject DN is {0}.
- Action:
- If you want to trust the subject DN {0}, then register a certificate with this subject DN in the CertificateRegistry.
- BEA-090685
- The CertificateRegistry could not build a certificate path for the issuer DN {0} and serial number {1}. This indicates that either someone is trying to access the server with an untrusted issuer DN and serial number or that the administrator has forgotten to register a certificate with this issuer DN and serial number in the CertificateRegistry.
- Category:
- Security
- Cause:
- The CertificateRegistry does not contain a certificate whose issuer DN is {0} and whose serial number is {1}.
- Action:
- If you want to trust the issuer DN {0} and serial number {1}, then register a certificate with this issuer DN and serial number in the CertificateRegistry.
- BEA-090686
- The CertificateRegistry could not build a certificate path for the subject key identifier {0}. This indicates that either someone is trying to access the server with an untrusted subject key identifier or that the administrator has forgotten to register a certificate with this subject key identifier in the CertificateRegistry.
- Category:
- Security
- Cause:
- The CertificateRegistry does not contain a certificate whose subject key identifier is {0}.
- Action:
- If you want to trust the subject key identifier {0}, then register a certificate with this subject key identifier in the CertificateRegistry.
- BEA-090687
- The CertificateRegistry could not validate a certificate path whose end certificate is {0}. This indicates that either someone is trying to access the server with an untrusted certificate or that the administrator has forgotten to register the certificate in the CertificateRegistry.
- Category:
- Security
- Cause:
- The CertificateRegistry does not contain the certificate {0}.
- Action:
- If you want to trust the end certificate {0}, then register it in the CertificateRegistry.
- BEA-090688
- The maximum number of concurrent lists has been exceeded. The maximum is {0}. These lists are allocated by listing functions listAliases for the CertificateRegistry. Wait for some of the existing lists to either expire or be closed. Lists automatically expire if they have not been used for {1} milliseconds.
- Category:
- Security
- Cause:
- Either the server is under very heavy load, or someone is launching a denial service attack against the server or some application code (e.g. a client) is not closing lists after it finishes using them.
- Action:
- Wait for some of the existing lists to either time out or be closed.
- BEA-090689
- The certificate alias is null or empty.
- Category:
- Security
- Cause:
- An empty or null certificate alias is not supported.
- Action:
- Modify the code to pass a non-null and non-empty certificate alias.
- BEA-090690
- The file name is null or empty.
- Category:
- Security
- Cause:
- An empty or null file name is not supported.
- Action:
- Modify the code to pass a non-null and non-empty file name.
- BEA-090691
- The certificate alias wildcard is null or empty.
- Category:
- Security
- Cause:
- An empty or null certificate alias wildcard is not supported.
- Action:
- Modify the code to pass a non-null and non-empty certificate alias wildcard.
- BEA-090692
- max cannot be < 0
- Category:
- Security
- Cause:
- The maximumToReturn value cannot be less than zero.
- Action:
- Pass in a maximumToReturn parameter value that is greater or equal to zero.
- BEA-090693
- Certificate alias {0} not found.
- Category:
- Security
- Cause:
- The alias cannot be found.
- Action:
- Pass in a certificate alias that exists.
- BEA-090694
- The security provider already has a certificate registered under the alias {0}.
- Category:
- Security
- Cause:
- Certificate alias {0} already exists in the security provider.
- Action:
- Pass in another certificate alias.
- BEA-090695
- Subject DN {0} already registered under the alias {1}
- Category:
- Security
- Cause:
- A certificate with subject DN {0} already exists in the security provider under the alias {1}.
- Action:
- Either remove the previous certificate from the security provider or register a different certificate.
- BEA-090696
- Issuer DN {0} and serial number {1} already registered under the alias {2}
- Category:
- Security
- Cause:
- A certificate with issuer DN {0} and serial number {1} already exists in the security provider under the alias {2}.
- Action:
- Either remove the previous certificate from the security provider or register a different certificate.
- BEA-090697
- Subject key identifier {0} already registered under the alias {1}
- Category:
- Security
- Cause:
- A certificate with subject key identifier {0} already exists in the security provider under the alias {1}.
- Action:
- Either remove the previous certificate from the security provider or register a different certificate.
- BEA-090698
- Errors occurred while importing data into this security provider.
- Category:
- Security
- Cause:
- Some of the data could not be imported into this security provider.
- Action:
- The getExceptions method on the ErrorCollectionException thrown by this method may be used to get a list of the errors that occurred.
- BEA-090699
- Errors occurred while exporting data from this security provider.
- Category:
- Security
- Cause:
- Some of the data could not be exported from this security provider.
- Action:
- The getExceptions method on the ErrorCollectionException thrown by this method may be used to get a list of the errors that occurred.
- BEA-090710
- Unable to write the file {0}.
- Category:
- Security
- Cause:
- Examine the nested exception for more information in diagnosing the problem.
- Action:
- Verify that the file is not a directory or a read-only file.
- BEA-090711
- Unable to read the file {0}.
- Category:
- Security
- Cause:
- Examine the nested exception for more information in diagnosing the problem.
- Action:
- Verify that the file exists and is not a directory.
- BEA-090712
- Unable to read the JKS keystore {0}.
- Category:
- Security
- Cause:
- Examine the nested exception for more information in diagnosing the problem.
- Action:
- Verify that the file is a JKS keystore.
- BEA-090713
- Unable to read the certificate in the PEM or DER file {0}.
- Category:
- Security
- Cause:
- Examine the nested exception for more information in diagnosing the problem.
- Action:
- Verify that the file is a PEM or DER file containing a single certificate.
- BEA-090724
- Challenge identity assertion has not completed, subject is not available yet
- Category:
- Security
- Cause:
- The method to get the subject was called before the identity assertion has completed.
- Action:
- Call the hasChallengeIdentityCompleted method before calling the method to get the subject.
- BEA-090726
- Unexpected exception while reading credential attribute: {0}
- Category:
- Security
- Cause:
- LDAP connection failure, corrupted LDAP database, or invalid cursor.
- Action:
- Verify that LDAP is up and running.
- BEA-090728
- Failed to read credential of type {0} stored under alias {1}
- Category:
- Security
- Cause:
- LDAP connection failure, or the database is corrupted.
- Action:
- Verify that LDAP is up and running.
- BEA-090731
- Unable to retrieve query
- Category:
- Security
- Cause:
- The internal query structure was not able to be retrieved from the connection. This could potentially be caused by a misconfigured DBMS ATN provider, but is more likely caused by an internal coding error in the DBMS ATN provider.
- Action:
- Review JDBC connection pool configuration, and provider level SQL Query settings. If these appear valid, this exception may indicate an internal coding error in the DBMS ATN provider. Contact BEA support.
- BEA-090732
- Invalid data source name specified: {0}
- Category:
- Security
- Cause:
- The DBMS ATN provider was most likely configured with an invalid data source name
- Action:
- Review and correct the data source name in the DBMS ATN provider configuration
- BEA-090734
- The connection pool was not usable
- Category:
- Security
- Cause:
- The DBMS ATN provider or the connection pool it is configured to use may be misconfigured or unavailable.
- Action:
- Review the JDBC related configuration in the server and the DBMS ATN provider configuration, and test the JDBC connection pool.
- BEA-090735
- The DBMS connection was not usable
- Category:
- Security
- Cause:
- The DBMS ATN provider or the connection pool it is configured to use may be misconfigured or unavailable.
- Action:
- Review the JDBC related configuration in the server and the DBMS ATN provider configuration, and test the JDBC connection pool.
- BEA-090736
- An exception occurred while validating the {0} configuration settings
- Category:
- Security
- Cause:
- An unexpected exception was thrown while validating configuration settings. This may indicate a configuration problem, or it may be an internal coding error
- Action:
- Review the exception trace for details on the cause, if the cause and solution are not apparent, contact BEA support.
- BEA-090737
- An exception occurred while getting connection to validate the configuration settings
- Category:
- Security
- Cause:
- An exception was thrown while validating configuration settings. This may indicate a configuration problem, or it may be an internal coding error
- Action:
- Review the exception trace for details on the cause, if the cause and solution are not apparent, contact BEA support.
- BEA-090738
- The {0} password hash algorithm is not usable
- Category:
- Security
- Cause:
- The password algorithm name was not found to be supported by the JCE crypto configuration
- Action:
- Verify the password algorithm is specified correctly, and that the JCE configuration supports the algorithm.
- BEA-090739
- The SQL statement for {0} does not appear to be correct
- Category:
- Security
- Cause:
- The DBMS SQL providers attempt to validate the configured SQL statements are correct. The validation code detected something was wrong with the configured SQL.
- Action:
- Review and correct the SQL statement.
- BEA-090740
- An unexpected exception occurred while calling the {0} method of the user defined DBMS sub plugin
- Category:
- Security
- Cause:
- The DBMS pluggable runtime providers caught an unexpected exception while calling the user defined sub plugin. The cause likely resides in the user defined sub plugin.
- Action:
- Review the exception details and the user defined sub plugin code to determine the cause and action.
- BEA-090741
- A SQLException occurred while calling the {0} method of the user defined DBMS sub plugin
- Category:
- Security
- Cause:
- The DBMS pluggable runtime providers caught a SQLException while calling the user defined sub plugin. The cause could be a database connectivity issue, or it could reside in the user defined sub plugin.
- Action:
- Review the exception details and the user defined sub plugin code to determine the cause and action.
- BEA-090742
- The DBMS pluggable runtime sub plugin failed to load
- Category:
- Security
- Cause:
- The DBMS pluggable runtime provider was not able to load the user defined sub plugin.
- Action:
- Review the DBMS pluggable runtime provider configuration. Verify the name of the user defined sub plugin class is correct, and that it is present in the server classpath.
- BEA-090743
- An unexpected exception occurred while loading the {0} sub plugin class
- Category:
- Security
- Cause:
- The DBMS pluggable runtime provider was not able to load the user defined sub plugin class and the exception thrown was not expected.
- Action:
- Review the exception details and the sub plugin configuration.
- BEA-090744
- The DBMS sub plugin class {0} was not found
- Category:
- Security
- Cause:
- The user defined sub plugin class was not found
- Action:
- Verify the name of the user defined sub plugin class is correct, and that it is present in the server classpath.
- BEA-090745
- The DBMS sub plugin class {0} was not the correct type
- Category:
- Security
- Cause:
- The user defined sub plugin class was not the correct type. Either the wrong class was specified, or the sub plugin was not coded correctly
- Action:
- Verify the user defined sub plugin class name is correct and that it implements the correct interface.
- BEA-090746
- The DBMS sub plugin class {0} was not able to be accessed
- Category:
- Security
- Cause:
- The user defined sub plugin class was not able to be accessed. Either the wrong class was specified, or the sub plugin was not coded correctly
- Action:
- Verify the user defined sub plugin class name is correct, that it implements the correct interface, and that the class is publicly accessible.
- BEA-090747
- The DBMS sub plugin class {0} was not able to be instantiated
- Category:
- Security
- Cause:
- The user defined sub plugin class was not able to be instantiated. Either the wrong class was specified, or the sub plugin was not coded correctly
- Action:
- Verify the user defined sub plugin class name is correct, that it implements the correct interface, it is defined as a class, and it is not an abstract class.
- BEA-090748
- There was a failure closing the DBMS connection
- Category:
- Security
- Cause:
- The exception information should be reviewed to determine the cause.
- Action:
- Review the exception details to determine if action is required.
- BEA-090751
- Failed to retrieve the prepared statement for {0}
- Category:
- Security
- Cause:
- Failed to retrieve the prepared statement for {0}, this is potentially an internal coding error
- Action:
- Review the JDBC configuration, contact BEA support if the cause is not apparent
- BEA-090752
- The password type in the DBMS was not a supported type
- Category:
- Security
- Cause:
- It is most likely caused by the password field in the DBMS stored as an unexpected type, binary or char data is expected.
- Action:
- Review the type for the password field in the database to ensure it is either binary or char data
- BEA-090753
- Hash algorithm {0} was not found
- Category:
- Security
- Cause:
- The JCE configuration is most likely not setup to support the algorithm
- Action:
- Review the JCE configuration to ensure the hash algorithm is available for use.
- BEA-090754
- The DBMS authenticator provider login module was not properly initialized
- Category:
- Security
- Cause:
- The DBMS authentication provider configuration may be incorrect, or there could be an internal coding error.
- Action:
- Review the DBMS authentication provider configuration. If no cause is found, contact BEA support.
- BEA-090755
- A database connection was not available from pool. Try increasing Connection Pool Size or Timeout
- Category:
- Security
- Cause:
- The connection pool size or timeout settings may need to be increased
- Action:
- Review the JDBC connection pool related configuration in the server, and consider increasing the connection pool size or timeout
- BEA-090756
- The DBMS provider was unable to form a query to access the {0} information
- Category:
- Security
- Cause:
- For SQL based DBMS providers configuration is most likely incorrect. For sub pluggable DBMS providers the user defined sub-plugin code could also be the cause.
- Action:
- Review and correct the DBMS provider configuration. If a sub pluggable provider is being used, also review the user defined sub plugin code.
- BEA-090757
- The DBMS provider got an exception when formatting the user
- Category:
- Security
- Cause:
- If a user defined sub-plugin for formatting the user was supplied, it may have a coding error
- Action:
- Review and correct the user defined sub-plugin user format code.
- BEA-090758
- The DBMS provider got an exception when formatting the groups
- Category:
- Security
- Cause:
- If a user defined sub-plugin for formatting the groups was supplied, it may have a coding error
- Action:
- Review and correct the user defined sub-plugin group format code.
- BEA-090759
- A SQLException occurred while retrieving {0} information
- Category:
- Security
- Cause:
- A SQLException occurred while retrieving {0} information
- Action:
- Review the exception details to determine the cause and action.
- BEA-090760
- The user {0} was not unique in the DBMS
- Category:
- Security
- Cause:
- This is caused by multiple records for the username existing in the DBMS
- Action:
- Review the DBMS records for the username.
- BEA-090761
- Authentication failed for user {0}
- Category:
- Security
- Cause:
- The exception details need to be reviewed to determine the cause
- Action:
- Review the exception details to determine the cause and action to take.
- BEA-090762
- Exception occurred in login module
- Category:
- Security
- Cause:
- The exception details need to be reviewed to determine the cause
- Action:
- Review the exception details to determine the cause and action to take.
- BEA-090765
- Failed to create policies for application version {0}
- Category:
- Security
- Cause:
- An exception was thrown during the application version created method.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090766
- Failed to create roles for application version {0}
- Category:
- Security
- Cause:
- An exception was thrown during the application version created method.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090767
- Failed to create credential mappings for application version {0}
- Category:
- Security
- Cause:
- An exception was thrown during the application version created method.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090768
- credential mapping removal error
- Category:
- Security
- Cause:
- An unexpected exception occurred when trying to remove the credentials for a deleted application.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090769
- The Active Directory ATN provider could not access the tokenGroups attribute for userDN {0} with principal {1} to perform group membership lookup.
- Category:
- Security
- Cause:
- The tokenGroups attribute was not accessible in the user entry. This is most likely the a problem with the Active Directory schema, or an Active Directory permission problem with the principal that is configured to access Active Directory.
- Action:
- Have the Active Directory administrator verify that the tokenGroup attribute is present in the Active Directory schema, and that the {1} principal has permission to read the tokenGroups attribute in Active Directory
- BEA-090771
- The Negotiate Identity Asserter was not configured with enough active types to perform negotiation.
- Category:
- Security
- Cause:
- The Negotiate Identity Asserter needs to be configured with all of its supported types specified as active types in order to perform negotiation.
- Action:
- Update the Negotiate Identity Asserter configuration to add all supported types listed for the provider to be active types.
- BEA-090776
- Exception when trying to generate a SAML assertion: {0}
- Category:
- Security
- Cause:
- An exception during the generation of a SAML assertion.
- Action:
- Read the exception text from the log message for more information on diagnosing the problem.
- BEA-090777
- Exception when trying to sign a SAML assertion: {0}
- Category:
- Security
- Cause:
- An exception during the signing of a SAML assertion.
- Action:
- Read the exception text from the log message for more information on diagnosing the problem.
- BEA-090781
- The SAMLLoginModule expected to receive a SAMLNameCallback and instead received a {0}.
- Category:
- Security
- Cause:
- This likely a configuration problem, if a SAMLIALoginModule is configured without a corresponding SAMLIdentityAsserter being configured.
- Action:
- Check the configuration of Identity Asserters and Login Modules.
- BEA-090784
- While Trying to find the groups that {0} belongs to,A Duplicate member {1} was detected.
- Category:
- Security
- Cause:
- A duplicate Membership in the groups was detected.
- Action:
- It might be possible that a cycle exists in the group entries.
- BEA-090785
- The Negotiate Identity Asserter found no identity to assert and no continuation was indicated.
- Category:
- Security
- Cause:
- This likely a configuration problem.
- Action:
- Check the configuration for the negotiate identity asserter and kerberos.
- BEA-090786
- The Negotiate Identity Asserter encountered an unexpected error processing a token.
- Category:
- Security
- Cause:
- This should not happen. This could be due to an invalid or corrupt SPNEGO token, or possibly some unknown token format similar to SPNEGO.
- Action:
- This exception indicates an internal coding error in the server. Contact BEA support.
- BEA-090787
- A Null DataSource name specified
- Category:
- Security
- Cause:
- A configuration setting that required a DataSource name was null.
- Action:
- Check configuration settings that require DataSource names to verify they are correctly specified.
- BEA-090788
- "Problem with DataSource/ConnectionPool configuration, verify DataSource name {0} is correct and Pool configurations are correct"
- Category:
- Security
- Cause:
- A configuration setting that required a DataSource name was likely incorrect, or the pool settings associated with it are incorrect.
- Action:
- Check configuration settings to ensure the DataSource name is correct and the associated pool configuration settings are correct
- BEA-090789
- The DBMS authentication provider encountered an unexpected exception during authentication.
- Category:
- Security
- Cause:
- An unexpected exception occurred during authentication.
- Action:
- Review the exception stack trace. If the cause is not obvious, contact BEA support
- BEA-090790
- BINARY or VARBINARY Result type is not allowed for this SQL statement {0}
- Category:
- Security
- Cause:
- The SQL statement result was a type that is not allowed for that statement
- Action:
- Review the SQL statement in the configuration to ensure it returns an appropriate type
- BEA-090791
- Result type is not {0} for SQL statement {1}
- Category:
- Security
- Cause:
- The SQL statement requires a result type of {0}
- Action:
- Review the SQL statement in the configuration to ensure it returns an appropriate type
- BEA-090792
- Parameter {0} type is not CHAR or VARCHAR for SQL statement {1}
- Category:
- Security
- Cause:
- The SQL statement parameter {0} requires a type of CHAR or VARCHAR
- Action:
- Review the SQL statement in the configuration to ensure the parameter types are correct
- BEA-090793
- Unexpected exception caught accepting the kerberos context, verify the JCE configuration is correct in java.security and the sun.security.jgss.SunProvider is configured
- Category:
- Security
- Cause:
- The exception stack should be reviewed, but this could be due to the JCE configuration in java.security not having the sun.security.jgss.SunProvider configured
- Action:
- Verify the JCE configuration is correct. If it is correct, review the exception to determine the cause.
- BEA-090794
- Password hash algorithm was not specified
- Category:
- Security
- Cause:
- The configuration is most likely set with an empty password hash algorithm
- Action:
- Review the configuration to ensure the hash algorithm is specified correctly.
- BEA-090795
- No columns in SQL results, need 1 column for SQL statement {0}
- Category:
- Security
- Cause:
- The SQL statement requires a result
- Action:
- Review the SQL statement in the configuration to ensure it returns an appropriate number and type of result
- BEA-090796
- Number of parameters was expected to be {0} but was {1} for SQL statement {2}
- Category:
- Security
- Cause:
- The SQL statement requires a specific number of parameters, and the statement specified had a different number of parameters
- Action:
- Review the SQL statement in the configuration to ensure it has the expected number of parameters specified
- BEA-090798
- Invalid characters found in input {0}
- Category:
- Security
- Cause:
- Input was specified that had invalid characters in it
- Action:
- Review the rejected input to determine what invalid characters were specified and enter the input without them
- BEA-090799
- PKICredentialMapperImpl init failed: {0}
- Category:
- Security
- Cause:
- An exception was thrown during the initialization of the WebLogic PKI Credential Mapping provider.
- Action:
- Read the exception text in {0} for more information on diagnosing the problem.
- BEA-090800
- Value for argument {0} for the credential type {1} not found.
- Category:
- Security
- Cause:
- Value for {0} for credential type {1} does not exist in the LDAP server.
- Action:
- Pass a value that exists.
- BEA-090801
- Value for resource {0}, initiator name {1} representing user name {2} with credential action {3} for the credential type {4} not found.
- Category:
- Security
- Cause:
- Value for resource {0}, initiator name {1} representing user name {2} with credential action {3} for the credential type {4} does not exist in the LDAP server.
- Action:
- Pass the values that exists.
- BEA-090802
- PKI Credential Mapper has got an LDAP exception.
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to set the Key Pair mapping.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090803
- PKI Credential Mapper has got an LDAP exception.
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server to set the Public Certificate Mapping.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090804
- Credential of the type {0} could not be removed.
- Category:
- Security
- Cause:
- An LDAP exception was thrown while accessing the LDAP server.
- Action:
- Check if the LDAP serer is up and running.
- BEA-090805
- Failed to read credential for Resource {0}, initiator name {1} representing user name {2} with credential action {3} for the credential type {4}.
- Category:
- Security
- Cause:
- LDAP connection failure, or the database is corrupted.
- Action:
- Verify that LDAP is up and running.
- BEA-090806
- PKI Keystore at location {0} not found .
- Category:
- Security
- Cause:
- Keystore configured at location {0} for the PKI Credential Provider not found.
- Action:
- Please create the keystore that is configured for the PKI Credential Mapper.
- BEA-090807
- PKI Keystore at location {0} of the type {1} and of type {2} and could not be loaded with the password provided.
- Category:
- Security
- Cause:
- Either the keystore password provided was not correct or the keystore type and provider not correctly entered.
- Action:
- Configure the keystore properly.
- BEA-090808
- The keystore alias {0} provided does not exist in the keystore configured for the provider.
- Category:
- Security
- Cause:
- The alias provided does not exist in the keystore configured for the provider.
- Action:
- Configure the keystore with the alias provided.
- BEA-090809
- The key pair could not be retrieved from the keystore with the supplied alias {0} and its password.
- Category:
- Security
- Cause:
- Either the alias supplied does not represent a key pair or the password provided is incorrect.
- Action:
- Please configure the keystore with the key pair properly.
- BEA-090810
- The keystore alias {0} provided does not represent a certificate entry in the keystore.
- Category:
- Security
- Cause:
- The alias provided does not represent a certificate entry in the keystore.
- Action:
- Configure the keystore with the appropriate certificate entry.
- BEA-090812
- Could not create a {0} keystore instance for provider {1}. Exception: {2}
- Category:
- Security
- Cause:
- {0} is not a valid keystore type or keystore provider {1} was not properly configured.
- Action:
- Verify that the correct keystore type was specified and that the keystore provider is correctly specified in the java.security file.
- BEA-090813
- DefaultCredentialMapperImpl.getCurrentMappingResourceID failed: No such resource maps list cursor available
- Category:
- Security
- Cause:
- Cursor is invalid.
- Action:
- Verify that the cursor was returned from the listMappings method.
- BEA-090815
- The password provided for the keystore configured for the PKICredential Mapper was null.
- Category:
- Security
- Cause:
- The keystore password provided for the PKI Credential Mapper cannot be null.
- Action:
- Enter a valid password for the keystore configured for the PKI Credential Mapper.
- BEA-090816
- Error creating security configuration runtime: {0}
- Category:
- Security
- Cause:
- During initialization, the security runtime registers with the management infrastructure. If this process fails, a management exception is thrown.
- Action:
- Read the exception text for more information on diagnosing the problem.
- BEA-090817
- These configuration changes cannot be activated since the domain does not have a default realm configured.
- Category:
- Security
- Cause:
- The "DefaultRealm" is not set for the domain's SecurityConfiguration.
- Action:
- To correct the problem, set the "DefaultRealm" for the domain's SecurityConfiguration to one of its realms. If it does not have any realms, create and configure one.
- BEA-090820
- The internal variable {0} is null and it should not be.
- Category:
- Security
- Cause:
- Unknown.
- Action:
- This exception is an internal WebLogic Server error. Contact BEA support.
- BEA-090821
- The configured CertPathBuilder provider returned an unordered CertPath. {0} The CertPath is {1}
- Category:
- Security
- Cause:
- The configured CertPathBuilder provider has a bug. It should never return an unordered CertPath.
- Action:
- Fix the bug in the configured CertPathBuilder.
- BEA-090824
- Unable to generate SAML Assertion: {0}
- Category:
- Security
- Cause:
- The SAML assertion could not be generated due to incorrect SAML configuration or missing/incorrect parameters supplied to the assertion generator.
- Action:
- Check the SAML configuration.
- BEA-090827
- LDIF template file {1} was empty. The WebLogic provider {0} has been bootstrapped but has not been initialized with any LDIF data.
- Category:
- Security
- Cause:
- A WebLogic provider LDIF template file may have been overwritten with an empty file.
- Action:
- If the server boots successfully, no action is needed. If the server does not boot successfully then an attempt should be made to recover non-empty LDIFT template file from the WebLogic Server kit.
- BEA-090828
- Identity Assertion type cannot be null
- Category:
- Security
- Cause:
- The token type was null.
- Action:
- Null should not be passed as the token type.
- BEA-090829
- Identity Assertion token cannot be null
- Category:
- Security
- Cause:
- The identity assertion token was null.
- Action:
- Null should not be passed as the token.
- BEA-090830
- Identity Assertion type of {0} is not a valid token type for the LDAP X509 Identity Assertion provider.
- Category:
- Security
- Cause:
- The token type passed in did not match the LDAP X509 Identity Assertion token type.
- Action:
- Pass in the correct token type for the LDAP X509 Identity Assertion provider.
- BEA-090831
- Unrecognized Callback
- Category:
- Security
- Cause:
- Callback type is not supported.
- Action:
- Verify that the LoginModule for the configured Authentication provider is only passing a NameCallback when calling the handle method.
- BEA-090832
- No matching certificate found in the LDAP directory.
- Category:
- Security
- Cause:
- No matching certificate were found in the LDAP directory.
- Action:
- Verify that the appropriate certificates are present in the configured LDAP directory.
- BEA-090833
- No certificates found in the LDAP directory.
- Category:
- Security
- Cause:
- No certificates were found in the LDAP directory.
- Action:
- Verify that the appropriate certificates are present in the configured LDAP directory.
- BEA-090834
- No LDAP connection could be established.
- Category:
- Security
- Cause:
- The connection parameters provided were either not correct or the LDAP was offline.
- Action:
- Verify that the connection parameters provided are correct and the LDAP server is running.
- BEA-090835
- Required parameter not supplied when performing the management operation on the PKI Credential Provider.
- Category:
- Security
- Cause:
- A required parameter was null.
- Action:
- Please call the management operations with the appropriate parameters.
- BEA-090836
- The Keystore provider configured for PKICredential Mapper does not exist at location {0}.
- Category:
- Security
- Cause:
- The file {0} does not exist.
- Action:
- To use the PKICredentialProvider please point to an existing keystore. Reboot the server.
- BEA-090837
- The configured keystore location for the PKI Credential Mapper is either null or empty.
- Category:
- Security
- Cause:
- The PKI Credential provider location value was either set to null or empty.
- Action:
- Set the PKI Credential provider keystore location to a valid keystore location.
- BEA-090841
- SAMLServlet: Unexpected exception while handling {0} request.
- Category:
- Security
- Cause:
- SAML providers not configured correctly, internal server error, or malformed request.
- Action:
- Check SAML configuration and server status. If configuration is OK and server is operating normally, enable SAML debug logging for more information.
- BEA-090842
- SAMLServletAuthenticationFilter: Unexpected exception.
- Category:
- Security
- Cause:
- SAML providers not configured correctly, internal server error, or malformed request.
- Action:
- Check SAML configuration and server operation. If problem persists, enable SAML debug logging for more information.
- BEA-090843
- {0} provider initialization failed: {1} parameter is null.
- Category:
- Security
- Cause:
- Internal server error.
- Action:
- Try restarting server.
- BEA-090844
- {0} provider initialization failed: Invalid {1} property ''{2}'' for ''{3}''.
- Category:
- Security
- Cause:
- Incorrect provider configuration.
- Action:
- Check and update the indicated provider property.
- BEA-090845
- {0} provider initialization failed: Missing {1} property for "{2}".
- Category:
- Security
- Cause:
- Invalid provider configuration.
- Action:
- Check and update the indicated provider property.
- BEA-090846
- {0} provider initialization failed: Invalid {1} attribute ''{2}''.
- Category:
- Security
- Cause:
- Incorrect provider configuration.
- Action:
- Check and update the indicated provider attribute.
- BEA-090847
- {0} provider initialization failed: Missing {1} attribute.
- Category:
- Security
- Cause:
- Invalid provider configuration.
- Action:
- Check and update the indicated provider attribute.
- BEA-090848
- {0} provider initialization failed: Unexpected exception.
- Category:
- Security
- Cause:
- Internal server error.
- Action:
- Check server status.
- BEA-090849
- {0} provider initialization failed: Exception while initializing XML parsers.
- Category:
- Security
- Cause:
- Internal server error.
- Action:
- Check server.
- BEA-090851
- The {0} provider is initialized.
- Category:
- Security
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-090853
- SAMLIdentityAsserter initialization failed: Could not instantiate/initialize the used assertion cache class: {0}.
- Category:
- Security
- Cause:
- Invalid class name configured, class is not visible to the class loader, or initialization parameters are incorrect..
- Action:
- Check configuration of class name and initialization parameters. Check that class is installed in a valid location.
- BEA-090854
- {0} provider initialization failed: Could not retrieve credentials for {1}.
- Category:
- Security
- Cause:
- SSL identity not configured for server.
- Action:
- Check SSL configuration.
- BEA-090856
- {0} configuration update failed: Provider settings updated while not initialized.
- Category:
- Security
- Cause:
- Internal server error.
- Action:
- Check server.
- BEA-090857
- {0} provider initialization failed: Could not register MBean update listener.
- Category:
- Security
- Cause:
- Internal server error.
- Action:
- Check server.
- BEA-090863
- There was an error in the SAML CredentialMapper Cache subsystem. The exception is {0}.
- Category:
- Security
- Cause:
- The SAML Cache could have been misconfigured.
- Action:
- Please check the SAML Cache parameters and restart the server.
- BEA-090869
- The PolicyConsumer "{0}" returned an error: {1}.
- Category:
- Security
- Cause:
- There are multiple possible causes.
- Action:
- Carefully read the returned error to determine if any action is required.
- BEA-090871
- The RoleConsumer "{0}" returned an error: {1}.
- Category:
- Security
- Cause:
- There are multiple possible causes.
- Action:
- Carefully read the returned error to determine if any action is required.
- BEA-090872
- The {0} service can not be found for {1}
- Category:
- Security
- Cause:
- A null was returned when doing a service lookup
- Action:
- Check the configuration to see that the missing service was actually configured.
- BEA-090873
- Expected a {0} object but did not get one.
- Category:
- Security
- Cause:
- Possible configuration problem.
- Action:
- Check configuration.
- BEA-090874
- {0} returned a null {1}.
- Category:
- Security
- Cause:
- This should never happen.
- Action:
- Examine the specific objects referenced in the error message to see what may be the cause.
- BEA-090875
- Null parameter supplied to method {0}
- Category:
- Security
- Cause:
- A parameter was not correctly specified
- Action:
- This is most likely a coding error.
- BEA-090876
- {0}Consumer not configured
- Category:
- Security
- Cause:
- An attempt was made to reference a Consumer but none are configured
- Action:
- This is most likely a configuration error.
- BEA-090878
- Unknown token type: {0}
- Category:
- Security
- Cause:
- Likely caused by the token type not being properly configured.
- Action:
- This is most likely a configuration error.
- BEA-090879
- The certificate for the imported alias {0} is already in registry, certificate not imported
- Category:
- Security
- Cause:
- None
- Action:
- No action required.
- BEA-090881
- Management operation could not be performed
- Category:
- Security
- Cause:
- The administration server is not reachable.
- Action:
- Check that the administration server is running and available on the network.
- BEA-090883
- Resource name is null or empty.
- Category:
- Security
- Cause:
- Resource name should not be null or empty.
- Action:
- Check that the resource name is not null or empty.
- BEA-090884
- User name is null or empty.
- Category:
- Security
- Cause:
- User name should not be null or empty.
- Action:
- Check that the User name is not null or empty.
- BEA-090885
- Remote user name is null or empty.
- Category:
- Security
- Cause:
- Remote user name should not be null or empty.
- Action:
- Check that the Remote user name is not null or empty.
- BEA-090886
- List number should not be negative.
- Category:
- Security
- Cause:
- List number should not be negative.
- Action:
- Check that the list number is not negative.
- BEA-090887
- Can not find member {0} from group {1}.
- Category:
- Security
- Cause:
- Member {0} not exit in group {1}.
- Action:
- Check the group members.
- BEA-090897
- A failure occurred attempting to update XACML global policies for security provider {0}.
- Category:
- Security
- Cause:
- An exception occurred attempting to update XACML global policies.
- Action:
- Examine the exception and correct the cause.
- BEA-090899
- User attribute name cannot be null.
- Category:
- Security
- Cause:
- User attribute name is null for the request.
- Action:
- Please pass in user attribute name which is not null.
- BEA-090900
- User attribute name is not supported for specified operation.
- Category:
- Security
- Cause:
- User attribute name is not supported.
- Action:
- Please pass in user attribute name which is supported. Please refer to documentation for details.
- BEA-090901
- Invalid group name: {0}. Can not contain {1}.
- Category:
- Security
- Cause:
- Improper usage of {1}.
- Action:
- Never use a group name carrying {1}.
- BEA-090902
- The certificate chain received from {0} contained a V1 certificate which cannot be a CA.
- Category:
- Security
- Cause:
- The certificate chain received by the peer contained a V1 certificate which cannot be a CA. This is rejected by the basic constraints checking for strong and strict and not allowing V1 certificates as CAs, which protects against a specific certificate chain attack on SSL.
- Action:
- The peer certificate chain needs to be looked at carefully to determine which certificate is not correct. If the certificate chain really is from a valid peer, you should look at updating the peer certificate chain with valid CA certificates. If this is not possible, you can disable the basic constraints checking to allow the certificate chain to be accepted and allows this vulnerability to be exploited.
- BEA-090905
- Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -D{0}=true
- Category:
- Security
- Cause:
- CryptoJ JCE Provider self-integrity check incurs some performance penalty at server startup.
- Action:
- No action needed.
- BEA-090906
- Changing the default Random Number Generator in RSA CryptoJ from {1} to {2}. To disable this change, specify -D{0}=true
- Category:
- Security
- Cause:
- CryptoJ's default RNG ECDRBG causes certain cryptographic operations slower.
- Action:
- No action needed.
- BEA-090907
- Invalid user name: {0}. Can not contain {1}.
- Category:
- Security
- Cause:
- Improper usage of {1}.
- Action:
- Never use a user name carrying {1}.
- BEA-090908
- Using the default WebLogic SSL Hostname Verifier implementation.
- Category:
- Security
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-090909
- Using the configured custom SSL Hostname Verifier implementation: {0}.
- Category:
- Security
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-090910
- Grant statement has invalid syntax: {0}
- Category:
- Security
- Cause:
- There is an error in the syntax of the grant statement.
- Action:
- Verify that the grant statement syntax is correct.
- BEA-090911
- Permission found in grant statement has invalid syntax: {0}
- Category:
- Security
- Cause:
- There is an error in the syntax of the permission within the grant statement.
- Action:
- Verify that the grant statement permission syntax is correct.
- BEA-090912
- Attempting to check revocation status for certificate with subject: {0}
- Category:
- Security
- Cause:
- X.509 certificate revocation checking is enabled.
- Action:
- No action is required.
- BEA-090913
- Unknown revocation status not causing failure for certificate with subject: {0}
- Category:
- Security
- Cause:
- X.509 certificate revocation checking is enabled, however, certificate revocation status cannot be determined, and is configured not to fail on an unknown status.
- Action:
- If validation failure is required, configure certificate revocation status to fail on an unknown status. To determine why the status is unknown, enable debug logging.
- BEA-090914
- Certificate revocation status: {0}
- Category:
- Security
- Cause:
- X.509 certificate revocation checking is enabled.
- Action:
- No action is required.
- BEA-090915
- Nonce was ignored by the OCSP responder, forcing certificate revocation status to be ignored and considered unknown: {0}.
- Category:
- Security
- Cause:
- X.509 certificate revocation checking is enabled, and OCSP is configured with nonces enabled.
- Action:
- To enable use of the ignored status, configure to disable OCSP nonces.
- BEA-090916
- Unknown revocation status causing failure for certificate with subject: {0}.
- Category:
- Security
- Cause:
- X.509 certificate revocation checking is enabled, certificate revocation status cannot be determined, and is configured to fail on an unknown status.
- Action:
- If validation failure is not required, configure certificate revocation status to not fail on an unknown status. To determine why the status is unknown, enable debug logging.
- BEA-090917
- Revoked certificate causing validation failure, certificate with subject: {0}.
- Category:
- Security
- Cause:
- X.509 certificate revocation checking is enabled, and the checked certificate was reported revoked.
- Action:
- Contact the certificate presenter (for example, SSL peer) and request that the revoked certificate be updated.
- BEA-090918
- Non-revoked certificate with subject: {0}.
- Category:
- Security
- Cause:
- X.509 certificate revocation checking is enabled, and the checked certificate was reported NOT revoked.
- Action:
- No action is required.
- BEA-090919
- The configured SSL minimum protocol version {0} is invalid or not supported. The minimum has been changed to {1}.
- Category:
- Security
- Cause:
- The current SSL implementation does not support the configured SSL minimum protocol version.
- Action:
- No action is required.
- BEA-090920
- Certicom SSL is available, however JSSE is being used for SSL, since JSSE has been selected by system property {0}, either explicitly or by default.
- Category:
- Security
- Cause:
- The system property {0} is selecting JSSE either explicitly or by default.
- Action:
- To use Certicom for SSL, set the system property {0} to false.
- BEA-090921
- JSSE has not been selected by system property {0}, however Certicom SSL is not available, so JSSE is being used for SSL.
- Category:
- Security
- Cause:
- Certicom SSL is not available, so JSSE is being used for SSL, even though JSSE was not selected.
- Action:
- To use Certicom for SSL, install Certicom.
- BEA-090922
- Certicom SSL is available, however JSSE is being used for SSL, since JSSE has been selected by the SSLMBean.JSSEEnabled attribute, either explicitly or by default.
- Category:
- Security
- Cause:
- The attribute SSLMBean.JSSEEnabled is selecting JSSE either explicitly or by default.
- Action:
- To use Certicom for SSL, set the attribute SSLMBean.JSSEEnabled to false.
- BEA-090923
- JSSE has not been selected by the SSLMBean.JSSEEnabled attribute, however Certicom SSL is not available, so JSSE is being used for SSL.
- Category:
- Security
- Cause:
- Certicom SSL is not available, so JSSE is being used for SSL, even though JSSE was not selected.
- Action:
- To use Certicom for SSL, install Certicom.
- BEA-090924
- JSSE has been selected by default, since the SSLMBean is not available.
- Category:
- Security
- Cause:
- This usually occurs early in server startup, before Management Service runtime access is available.
- Action:
- No action is required. Eventually the Management Service will start and normal operation will commence.
- BEA-090925
- JSSE has been selected by default, since the system property {0} has the invalid value "{1}".
- Category:
- Security
- Cause:
- The system property {0} was not set to "true" or "false".
- Action:
- Change the system property {0} value to be either "true" or "false".
- BEA-090926
- Illegal key store source value [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]
- Category:
- Security
- Cause:
- The configured key store source value is not valid for the key store type.
- Action:
- Correct the key store source value, ensuring that the source is appropriate for the key store type. For example, the "jks" key store type requires that the source be a file path to an existing key store file.
- BEA-090927
- Illegal or unknown key store type value [keyStoreType="{0}", source="{1}"]
- Category:
- Security
- Cause:
- The configured key store type value is not recognized.
- Action:
- Correct the key store type value. For example, the "jks" key store type requires the type value to be "jks".
- BEA-090928
- Unable to instantiate key store [keyStoreType="{0}", provider="{1}", exception="{2}", message="{3}"]
- Category:
- Security
- Cause:
- Key store instantiation failure usually occurs because no appropriate specified or default provider is available. See the exception for details.
- Action:
- Verify that key store type is correct, and that a supporting Java Cryptography Architecture (JCA) provider is available in the Java Runtime Environment. A "jks" key store provider is usually available by default. An Oracle Key Store Service (type "kss") provider is only available if Oracle Java Required Files (JRF) is installed.
- BEA-090929
- Unable to load key store [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]
- Category:
- Security
- Cause:
- A key store could fail to load due to an invalid source or password. Since key store instantiation succeeded, the key store type is valid. See the exception for details.
- Action:
- Check the configured key store source and password values.
- BEA-090930
- One of the Custom Identity Key Store attributes is not set on the channel override (NetworkAccessPointMBean). If any of the following attributes are set, then all of these attributes must be set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.
- Category:
- Security
- Cause:
- One of the following Custom Identity Key Store attributes are not set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.
- Action:
- Ensure all of the following attributes are set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.
- BEA-090931
- When overriding Custom Identity Key Store attributes, ChannelIdentityCustomized must be enabled.
- Category:
- Security
- Cause:
- ChannelIdentityCustomized is not enabled, and must be when the following Custom Identity Key Store attributes are set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.
- Action:
- Enable ChannelIdentityCustomized.
- BEA-090932
- When overriding Custom Identity Key Store attributes, CustomPrivateKeyAlias must be set on the channel override (NetworkAccessPointMBean).
- Category:
- Security
- Cause:
- CustomPrivateKeyAlias is not set on the NetworkAccessPointMBean, and must be when the following Custom Identity Key Store attributes are set: CustomIdentityKeyStoreFileName, CustomIdentityKeyStoreType, and either CustomIdentityKeyStorePassPhrase or CustomIdentityKeyStorePassPhraseEncrypted.
- Action:
- Set the CustomPrivateKeyAlias attribute on the NetworkAccessPointMBean.
- BEA-090933
- Unable to obtain private key with alias {2} from {1} keystore file : {0}
- Category:
- Security
- Cause:
- Either KeyStoreFileName or KeyStorePassPhrase or KeyStoreAlias or KeyStore private key password is incorrect.
- Action:
- Verify that the path to the keystore, the keystore type, the password for the keystore, the alias for the keystore, and the password for the private key were specified correctly.
- BEA-090934
- Loading certificates and private key from {1} keystore file {0} caused an Exception :{2}
- Category:
- Security
- Cause:
- Either KeyStoreFileName or KeyStorePassPhrase or KeyStoreAlias or KeyStore private key password is incorrect.
- Action:
- Verify that the path to the keystore, the keystore type, the password for the keystore, the alias for the keystore, and the password for the private key were specified correctly.
- BEA-090935
- Could not load a {1} keystore from the file {0}. Exception: {2}
- Category:
- Security
- Cause:
- There is an I/O or format problem with the keystore data.
- Action:
- Verify that the path to the keystore, the keystore type, and the password for the keystore were specified correctly. Note that some keystore types (for example, JKS) do not require a password for read-only access. Read the exception text for more help on diagnosing the problem. Reboot the server after correcting the problem.
- BEA-090936
- Security restarting security realm: {0}
- Category:
- Security
- Cause:
- This message is for informational purposes.
- Action:
- Verify that the correct security realm is being restarted.
- BEA-090937
- Security completed restarting security realm: {0}
- Category:
- Security
- Cause:
- This message is for informational purposes.
- Action:
- Verify that the correct security realm is restarted.
- BEA-090938
- Authentication failure: The specified user failed to log in.
- Category:
- Security
- Cause:
- The specified username, password, or both are incorrect.
- Action:
- Verify the username and password.
- BEA-090939
- The JWTToken is invalid.
- Category:
- Security
- Cause:
- JWT token could not satisfy the rule.
- Action:
- See the log for detailed information and take appropriate action.
- BEA-090940
- JWTIdentityAsserter received unknown token data, data should by byte[].
- Category:
- Security
- Cause:
- An invalid JWT token was supplied.
- Action:
- Supply a valid JWT token.
- BEA-090941
- The JWT token cannot pass the sign validation.
- Category:
- Security
- Cause:
- An invalid JWT token was supplied.
- Action:
- Supply a valid JWT token.
- BEA-090942
- Partitions require a realm with updated default role mapper and authorizations policies. The realm {0} does not contain the correct default policies. Create a new realm and reapply any custom policies.
- Category:
- Security
- Cause:
- Partition support requires updated default role mapping and authorization policies.
- Action:
- Create a new realm with the same providers as the existing realm. Transfer the custom security policies from the old realm to the new realm and set the partition realm attribute to point to the new realm.
- BEA-090943
- The provider {1} in realm {0} does not support identity domains via the IdentityDomainAwareProviderMBean interface. If identity domains are configured in the domain, then all role mapper, authorization, credential mapper, and audit providers must support this interface.
- Category:
- Security
- Cause:
- The configured providers do not support identity domains.
- Action:
- Ensure that all configured role mapper, authorization, credential mapper, and audit providers support identity domains. Remove any providers that do not support identity domains.
- BEA-090944
- Inconsistent security configuration, the provider {1} in security realm {0} does not support identity domains via the IdentityDomainAwareProviderMBean interface. If identity domains are configured in the domain, then all role mapper, authorization, credential mapper, and audit providers must support this interface.
- Category:
- Security
- Cause:
- The configured providers do not support identity domains.
- Action:
- Ensure that all configured role mapper, authorization, credential mapper, and audit providers support identity domains. Remove any providers that do not support identity domains.
- BEA-090945
- Security shutting down retired instance of security realm: {0}
- Category:
- Security
- Cause:
- This message is for informational purposes.
- Action:
- No action is required.
- BEA-090946
- Security pre-initializing using security realm: {0}
- Category:
- Security
- Cause:
- This message is for informational purposes.
- Action:
- Verify that the correct security realm is configured.
- BEA-090947
- Security post-initializing using security realm: {0}
- Category:
- Security
- Cause:
- This message is for informational purposes.
- Action:
- Verify that the correct security realm is configured.
- BEA-090948
- Security starting security realm: {0}
- Category:
- Security
- Cause:
- This message is for informational purposes.
- Action:
- Verify that the correct security realm is being restarted.
- BEA-090949
- Security completed starting security realm: {0}
- Category:
- Security
- Cause:
- This message is for informational purposes.
- Action:
- Verify that the correct security realm is started.
- BEA-090950
- The realm "{0}" failed during shut down: {1}.
- Category:
- Security
- Cause:
- There are multiple possible causes.
- Action:
- Carefully read the returned error to determine if any action is required.
- BEA-090951
- Failed operation using security realm: {0}
- Category:
- Security
- Cause:
- There are multiple possible causes.
- Action:
- Carefully read the returned error to determine if any action is required.
- BEA-090952
- Provider configured for identity domain(s) "{0}" but login was supplied identity domain {1}
- Category:
- Security
- Cause:
- The partition or security configuration may be configured with a different identity domain than the provider.
- Action:
- None required if the realm handles multiple identity domains. Otherwise, the security configuration may have inconsistent identity domains.
- BEA-090953
- These configuration changes cannot be activated because the Administrative Identity Domain must be set on the Security Configuration when Identity Domains are in use.
- Category:
- Security
- Cause:
- The "Administrative Identity Domain" attribute is not set for the domain's SecurityConfiguration.
- Action:
- To correct the problem, set the "AdministrativeIdentityDomain" for the domain's SecurityConfiguration.
- BEA-090954
- These configuration changes cannot be activated because the Primary Identity Domain must be set on Partition {0} when Identity Domains are in use.
- Category:
- Security
- Cause:
- The "Primary Identity Domain" attribute is not set for the specified Partition.
- Action:
- To correct the problem, set the "PrimaryIdentityDomain" for the specified Partition.
- BEA-090955
- These configuration changes cannot be activated because there is no authenticator configured to support the "{0}" Identity Domain value.
- Category:
- Security
- Cause:
- No authenticator in this realm is configured to support the specified Identity Domain value.
- Action:
- To correct the problem, configure one of the authenticator providers to support the specified identity domain. This can either be a WebLogic Server provider or a custom provider.
- BEA-090956
- Both permissions.xml and a deployment descriptor grant were found.
- Category:
- Security
- Cause:
- Both permissions.xml and a deployment descriptor grant were used to declare permissions.
- Action:
- Use either permissions.xml or a deployment descriptor grant to declare permissions for the application. Use only one and remove the other before redeployment.
- BEA-090957
- One or more of the declared permissions in permissions.xml are not allowed.
- Category:
- Security
- Cause:
- The application's permissions.xml file contains one or more permissions which are not allowed.
- Action:
- Remove the prohibited permissions from the permissions.xml file before redeploying the application.
- BEA-090958
- Security permissions declared in the "{0}" deployment descriptor are not allowed due to the server''s configuration.
- Category:
- Security
- Cause:
- The server is configured to not allow Java security permissions to be declared in the Weblogic deployment descriptors.
- Action:
- Remove Java security permissions from the deployment descriptor or change the server's security configuration before redeployment.
- BEA-090959
- Java EE packaged permissions are not allowed due to the server''s configuration.
- Category:
- Security
- Cause:
- The server is configured to not allow Java EE packaged permissions in the application.
- Action:
- Remove permissions.xml or change the server's security configuration before redeployment.
- BEA-090960
- The serverr''s SSL configuration is not available. There will potentially be SSL handshake failures.
- Category:
- Security
- Cause:
- The server has not been able to load its SSL configuration. This usually occurs early in server startup, before Management Service runtime access is available.
- Action:
- Verify that the Administration Server is running. If the Administration Server non-secure port is disabled, verify that the Managed Server default SSL configuration is sufficient to handshake with the Administration Server over the SSL port.
- BEA-090961
- These configuration changes cannot be activated because the realm "{0}" already exists.
- Category:
- Security
- Cause:
- There is more than one realm named "{0}" configured for the domain's SecurityConfiguration.
- Action:
- To correct the problem, change the name of each realm configured for the domain's SecurityConfiguration to be a unique name.
- BEA-090962
- These configuration changes cannot be activated because the realm "{0}" is not valid.
- Category:
- Security
- Cause:
- The realm "{0}" is not properly configured for the domain's SecurityConfiguration. See the nested exceptions that accompany this error for details.
- Action:
- To correct the problem, review and address the nested exceptions that accompany this error.
- BEA-090963
- The {0} provider imports a modified entry: {1}
- Category:
- Security
- Cause:
- The security provider needs to be modified because of the overwrite flag is open.
- Action:
- Modified the imported data from the existing one.
- BEA-090964
- The connection to the datasource using "{0}" could not be established due to the following error: {1}.
- Category:
- Security
- Cause:
- There are multiple possible causes.
- Action:
- Read the returned exception to determine if any action is required.
- BEA-090965
- Unable to create policy with type {0}. Got exception {1}.
- Category:
- Security
- Cause:
- An internal WebLogic server error occurred when creating policy type {0}.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-090966
- A failure has occurred checking for WebLogic Kernel Permission: {0}
- Category:
- Security
- Cause:
- An attempt to perform an action that requires privileges has failed.
- Action:
- Read the returned exception to determine what action is required.
- BEA-090967
- LDAP test connection failed: {0} not configured.
- Category:
- Security
- Cause:
- The connection parameters provided were incomplete.
- Action:
- Verify that the connection parameters provided are complete.
- BEA-090968
- Error processing test connection parameters {0}: {1}
- Category:
- Security
- Cause:
- The connection parameters provided were incorrect.
- Action:
- Verify that the connection parameters provided are correct.
- BEA-090969
- Identity Assertion type cannot be null
- Category:
- Security
- Cause:
- The token type was null.
- Action:
- Null should not be passed as the token type.
- BEA-090970
- Identity Assertion token cannot be null
- Category:
- Security
- Cause:
- The identity assertion token was null.
- Action:
- Null should not be passed as the token.
- BEA-090971
- Identity Assertion type of {0} is not a valid token type for the OpenID Connect Identity Assertion provider.
- Category:
- Security
- Cause:
- The token type passed in did not match the OpenID Connect Identity Assertion token type.
- Action:
- Pass in the correct token type for the OpenID Connect Identity Assertion provider.
- BEA-090972
- Resource type already registered: "{0}"
- Category:
- Security
- Cause:
- The supplied resource type has already been registered.
- Action:
- Specify a valid resource type.
- BEA-090973
- Ldap request wait exceeds time limit {0} milliseconds, try number count {1}
- Category:
- Security
- Cause:
- Ldap request takes unexpected long time.
- Action:
- None required. Otherwise check if the Ldap authentication provider configuration is optimized or Ldap server issue.
- BEA-090974
- File does not exist {0}
- Category:
- Security
- Cause:
- SerializedSystemIni.dat does not exist in the specified location.
- Action:
- Create a SerializedSystemIni.dat in the specified location if needed.
- BEA-090975
- The connection between the WebLogic servers cannot be authorized since the nonce value has expired. Verify that clock skew has not occurred between the servers in the domain.
- Category:
- Security
- Cause:
- Clock skew between the two servers may cause the client nonce to be expired when it is validated on the server.
- Action:
- Verify that the clocks on the servers in the domain are in agreement. Optionally, enable the Network Time Protocol daemon on the servers in the domain.
- BEA-090976
- Secure Mode is enabled but no auditing provider is configured in realm: {0}.
- Category:
- Security
- Cause:
- Secure Mode is enabled but no auditing provider is configured.
- Action:
- None required otherwise set SecureModeMBean WarnOnAuditing to false to avoid this message.
- BEA-090977
- Secure Mode is enabled but the Default Auditor logging level does not include WARNING, ERROR, and FAILURE audit records in realm: {0}.
- Category:
- Security
- Cause:
- Secure Mode is enabled but the Default Auditor logging level does not include WARNING, ERROR, and FAILURE audit records.
- Action:
- None required otherwise set SecureModeMBean WarnOnAuditing to false to avoid this message.
- BEA-090978
- Secure Mode is enabled but user lockout settings are not secure in realm: {0}, i.e. LockoutThreshold should not be greater than 5, LockoutDuration should not be less than 30.
- Category:
- Security
- Cause:
- Secure Mode is enabled but user lockout is not enabled or lockout settings are less restrictive than default.
- Action:
- This is a warning message, no action is required.
- BEA-090979
- Secure Mode is enabled but unencrypted password is used in command line, i.e. system property weblogic.management.password is set.
- Category:
- Security
- Cause:
- Secure Mode is enabled but unencrypted password is used in command line.
- Action:
- This is a warning message, no action is required.
- BEA-090980
- Secure Mode is enabled but no password validator is configured in realm: {0}.
- Category:
- Security
- Cause:
- Secure Mode is enabled but no password validator is configured.
- Action:
- This is a warning message, no action is required.
- BEA-090981
- Secure Mode is enabled but the Security Manager is not enabled.
- Category:
- Security
- Cause:
- Secure Mode is enabled but the Security Manager is not enabled.
- Action:
- None required otherwise set SecureModeMBean WarnOnJavaSecurityManager to false to avoid this message.
- BEA-090982
- Secure Mode is enabled but PostBind is not enabled for machine : {0} when unix machine is configured and port {1} < 1024 is used.
- Category:
- Security
- Cause:
- Secure Mode is enabled but PostBind is not enabled when unix machine is configured and port < 1024 is used.
- Action:
- This is a warning message, no action is required.
- BEA-090983
- Secure Mode is enabled but the the administration port is not enabled.
- Category:
- Security
- Cause:
- Secure Mode is enabled but the the administration port is not enabled.
- Action:
- This is a warning message, no action is required.
- BEA-090984
- Secure Mode is enabled but the fie or directory {0} owner {1} does not match the domain directory owner {2}.
- Category:
- Security
- Cause:
- Secure Mode is enabled but the file or directory owner does not match the domain directory owner.
- Action:
- None required otherwise set SecureModeMBean WarnOnInsecureFileSystem to false to avoid this message.
- BEA-090985
- Secure Mode is enabled but the the file or directory {0} is insecure since its permission is not a minimum of umask 027.
- Category:
- Security
- Cause:
- Secure Mode is enabled but the the file or directory permission is insecure.
- Action:
- None required otherwise change the file or directory permission to be a minimum of umask 027, or set SecureModeMBean WarnOnInsecureFileSystem to false to avoid this message.
- BEA-090986
- Secure Mode requires a realm with updated default authorizations policies. The realm {0} does not contain the correct default policies. Create a new realm and reapply any custom policies.
- Category:
- Security
- Cause:
- Secure Mode support requires updated default authorization policies.
- Action:
- Create a new realm with the same providers as the existing realm. Transfer the custom security policies from the old realm to the new realm and set the realm attribute to point to the new realm.
- BEA-090987
- SSLv3 is enabled by the system property {0} in secure mode. SSLv3 is vulnerable and should not be enabled.
- Category:
- Security
- Cause:
- SSLv3 is enabled by the system property in secure mode.
- Action:
- Enable a secure TLS version such as TLSv1.2 or turn off warning on insecure SSL configuration in secure mode.
- BEA-090988
- Basic Constraints extension validation is turned off by the system property {0}=off in secure mode.
- Category:
- Security
- Cause:
- Basic Constraints extension validation is turned off by the system property {0}=off in secure mode.
- Action:
- Turn on Basic Constraints extension validation, {0}=strong or {0}=true or {0}=strict, or turn off warning on insecure SSL configuration in secure mode.
- BEA-090989
- SSL hostname verification is disabled by the system property {0} in secure mode.
- Category:
- Security
- Cause:
- SSL hostname verification is disabled by the system property {0} in secure mode.
- Action:
- Enable SSL host name verification or turn off warning on insecure SSL configuration in secure mode.
- BEA-090990
- SSL hostname verification is disabled by the SSL configuration of server {0} in secure mode.
- Category:
- Security
- Cause:
- SSL hostname verification is disabled by the SSL configuration of server {0} in secure mode.
- Action:
- Enable SSL host name verification or turn off warning on insecure SSL configuration in secure mode.
- BEA-090991
- SSL hostname verification is disabled by the SSL configuration of server channel {0} in secure mode.
- Category:
- Security
- Cause:
- SSL hostname verification is disabled by the SSL configuration of server channel {0} in secure mode.
- Action:
- Enable SSL host name verification or turn off warning on insecure SSL configuration in secure mode.
- BEA-090992
- SSLv3 is enabled as the minimum TLS protocol version by the system property {0} in secure mode.
- Category:
- Security
- Cause:
- SSLv3 is enabled as the minimum TLS protocol version by the system property {0} in secure mode.
- Action:
- Configure a secure TLS version such as TLSv1.2 as the minimum TLS protocol version or turn off warning on insecure SSL configuration in secure mode.
- BEA-090993
- SSLv3 is enabled as the minimum TLS protocol version by the SSL configuration of server {0} in secure mode.
- Category:
- Security
- Cause:
- SSLv3 is enabled as the minimum TLS protocol version by the SSL configuration of server {0} in secure mode.
- Action:
- Configure a secure TLS version such as TLSv1.2 as the minimum TLS protocol version or turn off warning on insecure SSL configuration in secure mode.
- BEA-090994
- SSLv3 is enabled as the minimum TLS protocol version by the SSL configuration of server channel {0} in secure mode.
- Category:
- Security
- Cause:
- SSLv3 is enabled as the minimum TLS protocol version by the SSL configuration of server channel {0} in secure mode.
- Action:
- Configure a secure TLS version such as TLSv1.2 as the minimum TLS protocol version or turn off warning on insecure SSL configuration in secure mode.
- BEA-090995
- Null cipher suites are allowed by the system property {0} in secure mode.
- Category:
- Security
- Cause:
- Null cipher suites are allowed by the system property {0} in secure mode.
- Action:
- Null cipher suites are not secure and should not be allowed or turn off warning on insecure SSL configuration in secure mode.
- BEA-090996
- Null cipher suites are allowed by the SSL configuration of server {0} in secure mode.
- Category:
- Security
- Cause:
- Null cipher suites are allowed by the SSL configuration of server {0} in secure mode.
- Action:
- Null cipher suites are not secure and should not be allowed or turn off warning on insecure SSL configuration in secure mode.
- BEA-090997
- Null cipher suites are allowed by the SSL configuration of server channel {0} in secure mode.
- Category:
- Security
- Cause:
- Null cipher suites are allowed by the SSL configuration of server channel {0} in secure mode.
- Action:
- Null cipher suites are not secure and should not be allowed or turn off warning on insecure SSL configuration in secure mode.
- BEA-090998
- Anonymous cipher suites are allowed by the system property {0} in secure mode.
- Category:
- Security
- Cause:
- Anonymous cipher suites are allowed by the system property {0} in secure mode.
- Action:
- Anonymous cipher suites are not secure and should not be allowed or turn off warning on insecure SSL configuration in secure mode.
- BEA-090999
- TLS client initiated secure renegotation is enabled by the SSL configuration of server {0} in secure mode.
- Category:
- Security
- Cause:
- TLS client initiated secure renegotation is enabled by the SSL configuration of server {0} in secure mode.
- Action:
- Disable TLS client initiated secure renegotation or turn off warning on insecure SSL configuration in secure mode.
- BEA-091000
- TLS client initiated secure renegotation is enabled by the SSL configuration of server channel {0} in secure mode.
- Category:
- Security
- Cause:
- TLS client initiated secure renegotation is enabled by the SSL configuration of server channel {0} in secure mode.
- Action:
- Disable TLS client initiated secure renegotation or turn off warning on insecure SSL configuration in secure mode.
- BEA-091001
- Insecure cipher suites are configured by the SSL configuration of server {0} in secure mode: {1}
- Category:
- Security
- Cause:
- Insecure cipher suites are configured for secure mode.
- Action:
- Remove the insecure cipher suites {1} or turn off warning on insecure SSL configuration in secure mode.
- BEA-091002
- Insecure cipher suites are configured by the SSL configuration of server channel {0} in secure mode: {1}.
- Category:
- Security
- Cause:
- Insecure cipher suites are configured for secure mode.
- Action:
- Remove the insecure cipher suites {1} or turn off warning on insecure SSL configuration in secure mode.
- BEA-091003
- Secure Mode requires that users in the Administrators group do not have obvious user names. Change the user name "{0}" so it is not a commonly used administrator name.
- Category:
- Security
- Cause:
- A user that is a member of the Administrators group has an obvious user name.
- Action:
- Change the user name to non-obvious name.
- BEA-091004
- Secure Mode requires that the samples are not installed in the WebLogic installation directory.
- Category:
- Security
- Cause:
- The WebLogic installation contains the samples directory
- Action:
- Reinstall WebLogic and do not include the samples when choosing the installation type.
- BEA-091005
- Boot authentication attempt failed. Retry attempt {0} of {1}
- Category:
- Security
- Cause:
- The authentication for the boot user failed.
- Action:
- Wait until the server fails to boot and determine if the authentication failure can be corrected. If so, then retry the boot after correcting the authentication failure.
- BEA-091006
- The WLS SSL-ALPN jars are not found in java.endorsed.dirs directory. The HTTP/2 over SSL (h2) protocol will not be supported.
- Category:
- Security
- Cause:
- WLS can't find SSL-ALPN related classes because WLS SSL-ALPN related jars are not found in java.endorsed.dirs directory.
- Action:
- Check the system property java.endorsed.dirs is configured and make sure WLS SSL-ALPN jars are in the directory.
- BEA-091007
- The Oracle Identity Cloud Service returned '{0}' 429 status code responses (Too Many Requests) in the last '{1}' seconds.
- Category:
- Security
- Cause:
- The Oracle Identity Cloud Service response indicating user has sent too many reqests in a given amount of time.
- Action:
- No action is required.
- BEA-091008
- The Oracle Identity Cloud Service returned '{0}' service unavailable or network timeout responses in the last '{1}' seconds.
- Category:
- Security
- Cause:
- The Oracle Identity Cloud Service unavailable or timeout caused by network issue or other issues.
- Action:
- Verify that the network or the Oracle Identity Cloud Service is not experiencing issues.
- BEA-096500
- Artifact of type SAML2 artifact-04 is not successfully constructed.
- Category:
- Security
- Cause:
- The passing parameter {0} was null or its length was not {1}.
- Action:
- Check the parameters being passed to the SAMLArtifact constructor.
- BEA-096501
- SAML message returned in samlp:ArtifactResponse is not the right type. It should be of {0} type.
- Category:
- Security
- Cause:
- The SAML message that was returned in samlp:ArtifactResponse was not the one that samlp:ArtifactRequest requested.
- Action:
- Check the remote ARS storage to see if there is a {0} corresponding to the artifact.
- BEA-096502
- There is no SAML message in returned samlp:ArtifactResponse.
- Category:
- Security
- Cause:
- The SAML message may have been deleted because of expiration, or the client has no authority to access it.
- Action:
- Check the remote ARS storage to see if there is an item corresponding to the artifact.
- BEA-096503
- The artifact in the HTTP request is null. It should be {0} parameter in the HTTP request.
- Category:
- Security
- Cause:
- The artifact in the HTTP request was null. It should be {0} parameter in the HTTP request.
- Action:
- Check the HTTP request to see if there is a {0} parameter with a non-null value.
- BEA-096504
- Could not get binding handler of {0} type.
- Category:
- Security
- Cause:
- An internal WebLogic Server error occurred while getting the binding handler.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-096505
- Could not get SAML response, it should be of {0} type.
- Category:
- Security
- Cause:
- The remote service may be down or the message exchange timed out.
- Action:
- Check the remote service status.
- BEA-096506
- The SAML response is invalid in the field {0}, expected value is {1}, actual value is {2}.
- Category:
- Security
- Cause:
- The SAML response was not the one that the SAML request expected.
- Action:
- Check the remote service configuration.
- BEA-096507
- Could not get end point, the entityID is {0}, service type is {1}, end point index is {2}.
- Category:
- Security
- Cause:
- The end point was not registered.
- Action:
- Check the register storage to see if there is such an endpoint.
- BEA-096508
- Cannot get the key to sign {0}.
- Category:
- Security
- Cause:
- There may not be a key to sign {0}.
- Action:
- Check the local configuration to see if there is a key for signing {0}.
- BEA-096509
- Cannot get the key to verify the signature of {0}.
- Category:
- Security
- Cause:
- There may not be a key to verify the signature of {0}.
- Action:
- Check the partner registration information to see if there is key for verifying {0}.
- BEA-096510
- There is no SAML message in the HTTP request, it should be a value of {0} parameter.
- Category:
- Security
- Cause:
- There was no message in the HTTP request with a value of {0}.
- Action:
- Check the HTTP request to confirm that there is a parameter with a non-null value.
- BEA-096511
- The certificate chain sent by the SSL server is null or empty.
- Category:
- Security
- Cause:
- The remote partner acting as an SSL server did not send a certificate to authenticate itself.
- Action:
- Check the remote partner to see if it has an SSL certificate to authenticate itself.
- BEA-096512
- The SSL server cannot be trusted for {0}.
- Category:
- Security
- Cause:
- The remote partner acting as an SSL server cannot be trusted.
- Action:
- Check the SSL certificate that the remote partner uses to authenticate itself.
- BEA-096513
- Could not get partner, the entityID(or SHA-1 hash value) is {0}.
- Category:
- Security
- Cause:
- The partner is not registered.
- Action:
- Check the register storage to see if there is such a partner.
- BEA-096514
- Could not get Transport Layer Certificate from partner whose entityId is {0}.
- Category:
- Security
- Cause:
- The partner did not register its Transport Layer Certificate information.
- Action:
- Check the register storage to see if this partner has a Transport Layer Certificate.
- BEA-096515
- The SSL client is expected to authenticate, but cannot get the key and certificate.
- Category:
- Security
- Cause:
- The SSL key and certificate could not be retrieved.
- Action:
- Check the metadata to see if there is a Transport Layer Certificate and key.
- BEA-096516
- Could not get SAML signature from the HTTP request, it should be a {0} parameter.
- Category:
- Security
- Cause:
- If there is no SAML signature in the HTTP request, there should also be no signature algorithm in the HTTP request.
- Action:
- Check the HTTP request. The signature and signature algorithm should appear at the same time.
- BEA-096517
- The SAML message was signed but could not get a signature from it.
- Category:
- Security
- Cause:
- The SAML message was signed but there was no signature to retrieve.
- Action:
- Check the SAML message for the signature.
- BEA-096518
- The signature is invalid.
- Category:
- Security
- Cause:
- The signature was verified but was not valid.
- Action:
- Provide a valid signature.
- BEA-096519
- Could not get artifact when storing the SAML message, have no idea whether the SAML message was stored successfully.
- Category:
- Security
- Cause:
- There may have been an error when generating the artifact.
- Action:
- Check the log files for an error.
- BEA-096520
- Could not receive a valid SAML request of type "{0}" from HTTP request.
- Category:
- Security
- Cause:
- A valid SAML request of type "{0}" was not received from the HTTP request.
- Action:
- Check whether the configuration of the corresponding partner is correct.
- BEA-096521
- Could not receive a valid SAML response of type "{0}" from HTTP request.
- Category:
- Security
- Cause:
- A valid SAML response of type "{0}" was not retrieved from the HTTP request.
- Action:
- Check whether the configuration of the corresponding partner is correct.
- BEA-096522
- Error occurs when signing {0}.
- Category:
- Security
- Cause:
- Error occurs when signing {0}.
- Action:
- Error occurs when signing {0}.
- BEA-096523
- Authentication failed.
- Category:
- Security
- Cause:
- Authentication failed due to an invalid certificate or an invalid username or password.
- Action:
- Ensure that your certificate or your username and password are correct.
- BEA-096524
- Invalid Identity Assertion token object for specified token type.
- Category:
- Security
- Cause:
- An internal WebLogic server error occurred while determining the token type.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-096525
- Signature required but assertion is not signed.
- Category:
- Security
- Cause:
- An unsigned SAML assertion was received where the SAML configuration required a signed assertion.
- Action:
- Check the SAML partner configuration or contact the SAML Identity Provider.
- BEA-096526
- There must be a subject in assertion.
- Category:
- Security
- Cause:
- A SAML assertion was received in which the SAML Subject was not provided.
- Action:
- Contact the SAML Identity Provider for information on how to correct the problem.
- BEA-096527
- No SubjectConfirmation in assertion.
- Category:
- Security
- Cause:
- A SAML assertion was received in which the SAML Subject Confirmation was not provided.
- Action:
- Contact the SAML Identity Provider for information on how to correct the problem.
- BEA-096528
- Unsupported assertion type: {0}.
- Category:
- Security
- Cause:
- A SAML assertion was received in which the SAML Subject Confirmation is not supported.
- Action:
- Contact the SAML Identity Provider for information on how to correct the problem.
- BEA-096529
- Signature required but no valid certificate in the specified partner configuration.
- Category:
- Security
- Cause:
- A signature was required but the certificate has expired, is not yet valid or is undefined in the specified partner configuration.
- Action:
- Provide a valid certificate for the partner.
- BEA-096530
- Cannot get the key to verify the signature.
- Category:
- Security
- Cause:
- An improper key was provided.
- Action:
- Provide a proper key to verify the signature.
- BEA-096531
- The signature is invalid.
- Category:
- Security
- Cause:
- The signature was verified but was not valid.
- Action:
- Provide a valid signature.
- BEA-096532
- Invalid version found in the {0} document: {1}.
- Category:
- Security
- Cause:
- The sender sent a document that is not version 2.0.
- Action:
- Fix the SAML sender.
- BEA-096533
- Certificate in assertion''s keyinfo does not match configured signing certificate.
- Category:
- Security
- Cause:
- A SAML assertion was received where the SAML KeyInfo does not match the SAML partner entry.
- Action:
- Check the SAML partner configuration or contact the SAML Identity Provider.
- BEA-096534
- No issuer in the assertion.
- Category:
- Security
- Cause:
- A SAML assertion was received where the SAML Issuer is not supplied or the SAML Issuer is empty.
- Action:
- Contact the SAML Identity Provider for information on how to correct the problem.
- BEA-096535
- The Issuer in {0} is invalid: {1}.
- Category:
- Security
- Cause:
- The sender sent an invalid SAML document that contains an invalid Issuer URI.
- Action:
- Ask the SAML requester to fix this problem.
- BEA-096536
- Invalid issuer format: {0}.
- Category:
- Security
- Cause:
- The sender sent a document that contains an invalid issuer format attribute.
- Action:
- Ask the SAML requester to send a correct document.
- BEA-096537
- Assertion is not yet valid ({0} condition).
- Category:
- Security
- Cause:
- The received SAML assertion is not yet valid.
- Action:
- Check the SAML configuration, the system clock or contact the SAML Identity Provider.
- BEA-096538
- Assertion has expired ({0} condition).
- Category:
- Security
- Cause:
- The received SAML assertion has expired.
- Action:
- Check the SAML configuration, the system clock or contact the SAML Identity Provider.
- BEA-096539
- AudienceRestriction condition not satisfied (no matching audience).
- Category:
- Security
- Cause:
- The received SAML assertion audience restrictions where not satisfied.
- Action:
- Check the SAML partner configuration or contact the SAML Identity Provider.
- BEA-096540
- The assertion: {0} cannot be used again.
- Category:
- Security
- Cause:
- The received SAML assertion has already been consumed and cannot be used again.
- Action:
- Contact the SAML Identity Provider for information on how to correct the problem.
- BEA-096541
- Web SSO profile must be bearer confirmation method.
- Category:
- Security
- Cause:
- A SAML assertion was received where the SAML Subject Confirmation must be of Bearer type.
- Action:
- Contact the SAML Identity Provider for information on how to correct the problem.
- BEA-096542
- No NameID in assertion.
- Category:
- Security
- Cause:
- A SAML assertion was received in which the SAML Issuer is not supplied or the SAML Issuer is empty.
- Action:
- Contact the SAML Identity Provider for information on how to correct the problem.
- BEA-096543
- The partner: {0} does not exist or is disabled.
- Category:
- Security
- Cause:
- The partner: {0} does not exist or is disabled.
- Action:
- Register or enable the specified partner.
- BEA-096544
- Cannot find identity provider partner, partnerName: {0}, request URI: {1}.
- Category:
- Security
- Cause:
- Cannot find identity provider partner, partnerName: {0}, request URI: {1}.
- Action:
- Check the identity provider partner setting.
- BEA-096545
- Cannot find single sign-on services for partner: {0}.
- Category:
- Security
- Cause:
- No single sign-on services are defined for partner: {0}.
- Action:
- Define single sign-on services for partner: {0}.
- BEA-096546
- Cannot get the single sign-on sign key to sign the {0} in the key store.
- Category:
- Security
- Cause:
- Either no single sign-on sign key is defined in the local configuration or the key/keystore is invalid.
- Action:
- Correct the key configuration for SAML services.
- BEA-096547
- The status code of SAML2 response indicates that the request failed: {0}.
- Category:
- Security
- Cause:
- The SAML2 response from the identity provider partner indicates that the request failed.
- Action:
- Contact the identity provider partner to get the reason.
- BEA-096548
- Cannot find identity provider partner for issuer URI: {0}.
- Category:
- Security
- Cause:
- The identity provider partner for issuer URI: {0} is not defined.
- Action:
- Define the identity provider partner for issuer URI: {0}.
- BEA-096549
- Cannot get a valid certificate in partner registry to verify {0} for partner {1}.
- Category:
- Security
- Cause:
- The certificate has expired, is not yet valid or is undefined for the specified partner.
- Action:
- Provide a valid certificate for the partner.
- BEA-096550
- Failed to create session for identity: {0}.
- Category:
- Security
- Cause:
- This usually is caused by one of the LoginSessionListeners failing to create a session.
- Action:
- Ensure that all the listeners work properly or try to re-install.
- BEA-096551
- {0} binding of local configuration is not enabled.
- Category:
- Security
- Cause:
- The binding: {0} of the local configuration is not enabled.
- Action:
- Enable the binding: {0} for the local configuration.
- BEA-096552
- Illegal destination: {0} of assertion response.
- Category:
- Security
- Cause:
- The SAML2 response received from the identity provider partner is illegal.
- Action:
- Contact the identity provider partner to ensure that the generated response is correct.
- BEA-096554
- Cannot find request for InResponseTo: {0} in response.
- Category:
- Security
- Cause:
- The SAML2 response received from the identity provider partner is illegal.
- Action:
- Contact the identity provider partner to ensure that the generated response is correct.
- BEA-096555
- Attribute: {0} should not be empty.
- Category:
- Security
- Cause:
- The SAML2 response received from the identity provider partner is illegal.
- Action:
- Contact the identity provider partner to ensure that the generated response is correct.
- BEA-096556
- Attribute: {0} should be omitted.
- Category:
- Security
- Cause:
- The SAML2 response received from the identity provider partner is illegal.
- Action:
- Contact the identity provider partner to ensure that the generated response is correct.
- BEA-096557
- Illegal confirmation method: {0}.
- Category:
- Security
- Cause:
- The SAML2 response received from the identity provider partner is illegal.
- Action:
- Contact the identity provider partner to ensure that the generated response is correct.
- BEA-096558
- Illegal Recipient: {0} for the subject confirmation data.
- Category:
- Security
- Cause:
- The SAML2 response received from the identity provider partner is illegal.
- Action:
- Contact the identity provider partner to ensure that the generated response is correct.
- BEA-096559
- Illegal InResponseTo: {0} for the subject confirmation.
- Category:
- Security
- Cause:
- The SAML2 response received from the identity provider partner is illegal.
- Action:
- Contact the identity provider partner to ensure that the generated response is correct.
- BEA-096560
- The Issuer element cannot have NameQualifier, SPNameQualifer and SPProviderID.
- Category:
- Security
- Cause:
- The SAML requester sent a document that contains an invalid <Issuer>.
- Action:
- Ask the SAML Requester to fix this.
- BEA-096561
- Identity provider partner: {0} is not enabled.
- Category:
- Security
- Cause:
- The specified identity provider partner is not enabled.
- Action:
- Enable the identity provider partner.
- BEA-096562
- Errors occurred when sending {0}.
- Category:
- Security
- Cause:
- An internal WebLogic server error occurred when sending A SAML assertion.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-096563
- Errors occurred when receiving {0}.
- Category:
- Security
- Cause:
- An internal WebLogic Server error occurred when A SAML assertion was requested.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-096565
- Artifact requester authentication failed.
- Category:
- Security
- Cause:
- There was an invalid basic auth/certificate.
- Action:
- Check the log for more details and take appropriate action.
- BEA-096566
- The SAML2 identity provider service is disabled.
- Category:
- Security
- Cause:
- The SAML2 identity provider service is disabled in the local configuration, but a request was sent to this service.
- Action:
- Enable the identity provider in the local configuration.
- BEA-096567
- Cannot find service provider partner with the specified URI {0}.
- Category:
- Security
- Cause:
- The partner may be misconfigured in the partner registry, or this issuer is not enabled/configured in the registry.
- Action:
- Configure the partner correctly in the partner registry, or just ignore it if this issuer should not be served. It could also be errors in the service provider that issues this request.
- BEA-096568
- The service provider partner {0} is disabled.
- Category:
- Security
- Cause:
- The specified service provider partner is disabled in the partner registry.
- Action:
- Enable the partner in the partner registry.
- BEA-096569
- Cannot authenticate user in passive mode.
- Category:
- Security
- Cause:
- The AuthnRequest wants the user to be authenticated in passive mode, but the Identity Provider is not able to do this.
- Action:
- Ensure that the service provider does not send passive requests, or just ignore this error.
- BEA-096570
- The user is accessing the login return URL of SAML2 service, however, this user is not authenticated.
- Category:
- Security
- Cause:
- A user accidentally accessed this page or bookmarked it, or the login application is behaving incorrectly.
- Action:
- Fix the login application.
- BEA-096571
- There is no <AuthnRequest> object in user''s session.
- Category:
- Security
- Cause:
- The user's session may have expired. The user must do the single sign-on process from the very beginning. This could also be caused by an incorrect login application.
- Action:
- Start the single sign-on process from the beginning, or fix the login application.
- BEA-096572
- The user is accessing the Identity Provider initiator service, but is not authenticated yet.
- Category:
- Security
- Cause:
- The user accidentally accessed this page or bookmarked it, or the login application is behaving incorrectly.
- Action:
- Fix the login application or the page links to this URL.
- BEA-096573
- The Identity provider-initiated single sign-on requires a parameter {0}, but the request does not have one.
- Category:
- Security
- Cause:
- The user or the link did not append the parameter.
- Action:
- Append the parameter in the request.
- BEA-096574
- Cannot find partner with name: {0}
- Category:
- Security
- Cause:
- The partner with name {0} does not exist in the partner registry.
- Action:
- Add a partner with the indicated name, or rename a partner to this name.
- BEA-096575
- The URL for relay state is too long.
- Category:
- Security
- Cause:
- The service provider-initiated single sign-on requester sent a request URL longer than 80 bytes.
- Action:
- If the URL for the service provider is too long, do not send it.
- BEA-096576
- Received a SAML document that is not a AuthnRequest document, but {0}.
- Category:
- Security
- Cause:
- The SAML requester sent an invalid document to the identity provider single sign-on service.
- Action:
- Ask the requester to send a valid document.
- BEA-096577
- Failed to receive {0} document from the requester.
- Category:
- Security
- Cause:
- Review other messages in the log for the cause.
- Action:
- Fix the error in the document or network.
- BEA-096578
- Cannot generate assertion for the user.
- Category:
- Security
- Cause:
- There may be an error in the credential mapper, or the SAML2 credential mapper is not configured correctly.
- Action:
- Configure the SAML2 credential mapper correctly.
- BEA-096579
- Failed to unmarshal the assertion from the credential mapper.
- Category:
- Security
- Cause:
- An internal WebLogic Server error occurred during unmarshaling.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-096580
- No assertion consumer services configured in the {0} partner.
- Category:
- Security
- Cause:
- No assertion consumer services are configured in the partner.
- Action:
- Configure the ACS service for this partner.
- BEA-096581
- The destination attribute of <AuthnRequest> does not match local configuration.
- Category:
- Security
- Cause:
- Either the request was sent to the wrong place, or the request document is wrong.
- Action:
- Fix the SAML requester to match the destination attribute.
- BEA-096582
- <SubjectConfirmation> cannot exist in the <Subject> element of <AuthnRequest>
- Category:
- Security
- Cause:
- The SAML requester sent an <AuthnRequest>, its <subject> contains a <SubjectConfirmation>, which is not allowed by the SAML specification.
- Action:
- Fix the SAML requester.
- BEA-096583
- Requested NameId format not supported, only urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified is supported.
- Category:
- Security
- Cause:
- The SAML requester sent a request that is not supported yet.
- Action:
- Fix the SAML requester to send a request without the name id format, or set the format to "unspecified".
- BEA-096584
- <RequestedAuthnContext> is not currently supported.
- Category:
- Security
- Cause:
- The SAML requester sent an invalid <AuthnRequest> document.
- Action:
- Fix the SAML requester to send a request without <RequestedAuthnContext>.
- BEA-096585
- The SPNameQualifier is not supported in <AuthnRequest>.
- Category:
- Security
- Cause:
- The SAML requester sent a request that is not supported yet.
- Action:
- Fix the SAML requester to not send such a document.
- BEA-096586
- Find service provider partner by issuer URI {0} error.
- Category:
- Security
- Cause:
- The exception was caused while searching for the service provider partner from the store by the issuer uri.
- Action:
- Check the store service.
- BEA-096587
- Find service provider partner by name {0} error.
- Category:
- Security
- Cause:
- This exception was caused while searching for the service provider partner from the store by name.
- Action:
- Check the store service.
- BEA-096588
- Find identity provider partner by name {0} error.
- Category:
- Security
- Cause:
- This exception was caused while searching for the identity provider partner from the store by name.
- Action:
- Check the store service.
- BEA-096589
- Find partner by name {0} error.
- Category:
- Security
- Cause:
- This exception was caused while searching for the partner from the store by name.
- Action:
- Check the store service.
- BEA-096590
- Could not get local entity ID for checking audience in assertion.
- Category:
- Security
- Cause:
- The service provider has no entity ID.
- Action:
- Check the service provider local configuration to see whether it has an entity ID.
- BEA-096591
- Could not get partner from partner registry by name.
- Category:
- Security
- Cause:
- There is no such partner in the partner registry.
- Action:
- Check the partner registry to see whether this partner exists.
- BEA-096592
- Partner is not enabled in partner registry.
- Category:
- Security
- Cause:
- This partner is in the partner registry, but the partner is not enabled.
- Action:
- Check the partner registry to see whether the partner is enabled.
- BEA-096593
- Audience cannot be empty.
- Category:
- Security
- Cause:
- The assertion contains an empty audience.
- Action:
- Check the CredentialMapper.
- BEA-096594
- Web single sign-on service provider partner entity ID is empty, could not create assertion.
- Category:
- Security
- Cause:
- The SAML partner entry does not have an Entity ID or the Entity ID is empty.
- Action:
- Check and import the SAML service provider metadata file or contact the SAML service provider to obtain the Entity ID.
- BEA-096595
- Confirmation method should not be empty.
- Category:
- Security
- Cause:
- The provider partner has no confirmation method.
- Action:
- Check the partner information to make sure it has a confirmation method.
- BEA-096596
- Assertion signing certificate should not be empty while wantAssertionSigned is TRUE.
- Category:
- Security
- Cause:
- The provider partner has no assertion signing certificate while wantAssertionSigned is TRUE.
- Action:
- Check the partner information to make sure it has an assertion signing certificate.
- BEA-096597
- Artifact POST form should not be empty while isArtifactUsePost is TRUE.
- Category:
- Security
- Cause:
- The provider partner has no artifact POST form while isArtifactUsePost is TRUE.
- Action:
- Check the partner information to make sure it has an artifact POST form.
- BEA-096598
- Single sign-on signing certificate should not be empty while assertion/artifact request/authn request wants to be signed.
- Category:
- Security
- Cause:
- The provider partner has no single sign-on signing certificate while the assertion/artifact request/authn request wants to be signed.
- Action:
- Check the partner information to make sure it has a single sign-on signing certificate.
- BEA-096599
- Issuer URI should not be empty.
- Category:
- Security
- Cause:
- The provider partner has no issuer URI.
- Action:
- Check the partner information to make sure it has an issuer URI.
- BEA-096600
- No SAML2 service entity ID configured.
- Category:
- Security
- Cause:
- The SAML2 service entity ID is not configured.
- Action:
- Configure the SAML2 service entity ID.
- BEA-096601
- No SAML2 service published site URL configured.
- Category:
- Security
- Cause:
- The SAML2 service published site URL is not configured.
- Action:
- Configure the SAML2 service published site URL.
- BEA-096602
- No SAML2 service single sign-on signing key alias configured.
- Category:
- Security
- Cause:
- The SAML2 service single sign-on signing key alias is not configured.
- Action:
- Configure a SAML2 service single sign-on signing key alias.
- BEA-096603
- No SAML2 service single sign-on signing key pass phrase configured.
- Category:
- Security
- Cause:
- The SAML2 service single sign-on signing key pass phrase is not configured.
- Action:
- Configure the SAML2 service single sign-on signing key pass phrase.
- BEA-096604
- No SAML2 service login return query parameter are configured.
- Category:
- Security
- Cause:
- The SAML2 service login return query parameter is not configured.
- Action:
- Configure the SAML2 service login return query parameter.
- BEA-096605
- Entity ID should not be empty.
- Category:
- Security
- Cause:
- The provider partner has no entity ID.
- Action:
- Check the partner information to make sure it has an entity ID.
- BEA-096606
- Name should not be empty.
- Category:
- Security
- Cause:
- The provider partner has no name.
- Action:
- Check the partner information to make sure it has a name.
- BEA-096607
- Single sign-on services should not be empty.
- Category:
- Security
- Cause:
- Provider partner has no single sign-on services.
- Action:
- Check the partner information to make sure it has single sign-on services.
- BEA-096608
- Assertion consumer services should not be empty.
- Category:
- Security
- Cause:
- The provider partner has no assertion consumer services.
- Action:
- Check the partner information to make sure it has assertion consumer services.
- BEA-096609
- Illegal published site url: {0}.
- Category:
- Security
- Cause:
- The published site url is illegal.
- Action:
- Check the partner information to make sure it has a legal published site url.
- BEA-096610
- Cannot resolve IssuerURI for SAML Assertion.
- Category:
- Security
- Cause:
- The system could not resolve the IssuerURI for the SAML Assertion from the context and credential mapper MBean.
- Action:
- Check the context and credential mapper MBean to make sure that the issuerURI is not empty.
- BEA-096611
- Cannot get key info for key {0} from key service.
- Category:
- Security
- Cause:
- The key info got from key service for key {0} is empty.
- Action:
- Check the key store service for key {0}.
- BEA-096612
- Decrypt password {0} error.
- Category:
- Security
- Cause:
- The password {0} could not be decrypted, causing an exception.
- Action:
- Check the key and the password.
- BEA-096613
- Clearing cache {0}.
- Category:
- Security
- Cause:
- The SAML cache is being cleared.
- Action:
- No action is required.
- BEA-096614
- Cache {0} cleared.
- Category:
- Security
- Cause:
- The SAML cache has been cleared.
- Action:
- No action is required.
- BEA-096615
- The SAML credential cache item''s ttl value {0} is smaller than the minimum viable ttl {1} in milliseconds and will not be cached.
- Category:
- Security
- Cause:
- The SAML credential cache is unable to retain the item due to the length of the timeout.
- Action:
- No action is required.
- BEA-096616
- The value of max to return is negative.
- Category:
- Security
- Cause:
- The value of max to return cannot be negative.
- Action:
- Check the value of max to return and make sure that the value is not negative.
- BEA-096617
- The value for contact person type is illegal.
- Category:
- Security
- Cause:
- The value for the contact person type is not legal. The legal value must be in one of "technical", "support", "administrative", "billing" or "other".
- Action:
- Choose one of the legal values and try again.
- BEA-096618
- Invalid keystore configuration.
- Category:
- Security
- Cause:
- The keystore configuration is not correct.
- Action:
- Configure a valid value and try again.
- BEA-096619
- Key name is null or empty.
- Category:
- Security
- Cause:
- The key name is null or empty when updating/retrieving key information.
- Action:
- Choose a valid key name and try again.
- BEA-096620
- Invalid key information.
- Category:
- Security
- Cause:
- At least one of key name, alias or passphrase is not correct.
- Action:
- Choose a valid value and try again.
- BEA-096621
- SAML2 Service cannot be initialized:{0}
- Category:
- Security
- Cause:
- Errors occurred while initializing the SAML2 service.
- Action:
- Check and change the SAML2 configuration and try again.
- BEA-096622
- ForceAuthn and IsPassive cannot both be true.
- Category:
- Security
- Cause:
- ForceAuthn wants to authenticate the user freshly, but IsPassive requests that the identity provider not do this.
- Action:
- Change one of the values to false.
- BEA-096623
- Item has already expired on {0}, it will not be cached.
- Category:
- Security
- Cause:
- The configured timeout may be too short.
- Action:
- Check the timeout configuration.
- BEA-096624
- The "{1}" parameter passed to "{0}" must not be null.
- Category:
- Security
- Cause:
- A null "{1}" parameter was passed to "{0}".
- Action:
- Ensure that a valid reference is passed.
- BEA-096625
- The parameter MaxCacheSize or timeout must not be a negative number.
- Category:
- Security
- Cause:
- The parameter MaxCacheSize or timeout cannot be a negative number.
- Action:
- Change the MaxCacheSize parameter or timeout to zero or a positive number.
- BEA-096626
- The partner name cannot be changed at partner update operation.
- Category:
- Security
- Cause:
- The user tried to change the read-only partner name.
- Action:
- Set the partner name back to the original name.
- BEA-096627
- There is no login URL configured in Identity Provider Site.
- Category:
- Security
- Cause:
- No login URL was configured in the Identity Provider Site.
- Action:
- Configure a valid login URL in SingleSignOnServicesMBean.
- BEA-096628
- The value configured for NameMapper attribute: {0} is not valid.
- Category:
- Security
- Cause:
- The name mapper class {0} is not in the classpath or it does not implement a name mapper interface.
- Action:
- Ensure that the name mapper class {0} is in the classpath and implements a name mapper interface.
- BEA-096629
- The confirmation method passed through Context handler: {0} is not valid.
- Category:
- Security
- Cause:
- An invalid confirmation method was passed through the Context handler.
- Action:
- Make sure the confirmation method passed through Context handler {0} has a valid value.
- BEA-096630
- Using expired certificate at alias {0} for signing.
- Category:
- Security
- Cause:
- An attempt was made to use an expired certificate at alias {0} for signing, but allow expired cert is false.
- Action:
- Use a valid certificate for signing.
- BEA-096631
- Using not yet valid certificate at alias {0} for signing.
- Category:
- Security
- Cause:
- A not yet valid certificate was used at alias {0} for signing, but allow expired cert is false.
- Action:
- Use a valid certificate for signing.
- BEA-096632
- Binding type {0} is unsupported, endpoint with this binding is filtered out from partner.
- Category:
- Security
- Cause:
- The binding type that was used is not supported.
- Action:
- Use a binding type that is supported.
- BEA-096633
- The partner metadata file does not contain an XML root element of <EntityDescriptor>.
- Category:
- Security
- Cause:
- The partner metadata file content is not supported.
- Action:
- Update the partner metadata content or obtain a new partner metadata file.
- BEA-096634
- Cannot get the single sign-on sign certificate to sign the {0} in the key store.
- Category:
- Security
- Cause:
- Either no single sign-on sign certificate is defined in the local configuration or the key/keystore is invalid.
- Action:
- Correct the key configuration for SAML services.
- BEA-096635
- Error occurs when encrypting {0}.
- Category:
- Security
- Cause:
- Error occurs when encrypting {0}.
- Action:
- Check debug log for specific encryption error on {0}.
- BEA-097000
- Service info was not found for service to shut it down, {0}
- Category:
- Engine
- Cause:
- Service info was not found when shutting down a service.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097001
- Configuration problems detected.
- Category:
- Engine
- Cause:
- A bad configuration was supplied.
- Action:
- Check and fix the configuration.
- BEA-097002
- Configuration canno be modified after the engine has been started.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine configuration was modified after the engine was started.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097004
- Engine has already been started.
- Category:
- Engine
- Cause:
- An attempt was made to start the engine after it had been started.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097005
- Unable to find ServiceConfig.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine cannot be configured.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097006
- Duplicate service name {0}.
- Category:
- Engine
- Cause:
- The service engine was configured with a duplicate service name.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097007
- Logger not found.
- Category:
- Engine
- Cause:
- The service engine could not find the logger.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097008
- An attempt was made to access the ServiceEngine after it had already been shut down.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine was accessed after being shut down.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097009
- Engine already shut down.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine has already been shut down.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097010
- Service {0} not found.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine cannot find the service.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097011
- Service {0} not exposed.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine looked up a service that it cannot expose.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097012
- Service {0} does not implement ServiceLifecycleSpi.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine was configured with a service that it cannot use.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097013
- Null service {0} loaded.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine was configured with a null service.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097014
- Classloader not found for service {0}.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine was configured with a service but the service's classloader could not be found.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097015
- Failure loading service {0} using class {1}.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine could not load a service.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097016
- Service {0} is dependent upon {1} which does not exist.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine could not find a dependent service.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097017
- Service name not specified.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine could not find a service.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097018
- Attempt to remove lifecycle impl for {0} when {1} dependencies still exist.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine attempted to remove a service that still has dependencies.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097019
- Attempt to remove dependencies for {0} when no dependencies still exist.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error indicating that the service engine attempted to remove dependencies for a service when no dependencies exist.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097020
- Internal consistency failure in {0}
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097021
- Manageable Service {0} not found.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server error. An attempt was made to look up a manageable service but it was not found.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097022
- Service {0} is not manageable.
- Category:
- Engine
- Cause:
- This is an internal WebLogic Server Error. An attempt was made to look up a manageable service and a service with the requested name was found, but it was not a manageable service.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097500
- {0} requires a {1} to be supplied for configuration but it was not supplied.
- Category:
- Security
- Cause:
- The configuration supplied to {0} was incorrect.
- Action:
- Ensure that the configuration supplied for {0} is correct.
- BEA-097501
- {1} supplied to {0} is missing {2}
- Category:
- Security
- Cause:
- The configuration supplied to {0} was incorrect.
- Action:
- Ensure that the configuration supplied for {0} is correct.
- BEA-097502
- MaxIdentitiesInCache value for the IdentityCacheService is invalid {0}
- Category:
- Security
- Cause:
- The value supplied for MaxIdentitiesInCache for the IdentityCacheService was invalid.
- Action:
- Change MaxIdentitiesInCache to a valid value.
- BEA-097503
- The configured CertPathBuilder service returned a non X.509 certificate path.
- Category:
- Security
- Cause:
- The CertPathBuilder was configured with an incorrect certificate path for an X.509 certificate.
- Action:
- Correct the configured CertPathBuilder service.
- BEA-097504
- AdjudicationService does not have an AdjudicatorV2Name but has multiple AccessDecision providers.
- Category:
- Security
- Cause:
- The AdjudicationService has multiple AccessDecision providers, but there are no providers that implement the AdjudicatorV2 interface.
- Action:
- Configure an adjudicator that implements the AdjudicatorV2 interface.
- BEA-097505
- None of the configured {0} support JAAS login.
- Category:
- Security
- Cause:
- There are no authentication providers configured to support JAAS login.
- Action:
- Configure at least one authentication provider that supports JAAS login.
- BEA-097506
- An AuthorizationProvider returned a null AccessDecision.
- Category:
- Security
- Cause:
- An AuthorizatonProvider was not able to return an AccessDecision.
- Action:
- Examine the AuthorizationProvider.
- BEA-097507
- {0} may only be called if hasChallengeIdentityCompleted returns false.
- Category:
- Security
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Contact My Oracle Support.
- BEA-097508
- {0} may only be called if hasChallengeIdentityCompleted returns true.
- Category:
- Security
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Contact My Oracle Support.
- BEA-097509
- {0} returned a null {1}.
- Category:
- Security
- Cause:
- There is a configuration problem because a null object was returned.
- Action:
- Examine the specific objects referenced in the error message to see what may be the cause.
- BEA-097510
- Got back a null {0} object.
- Category:
- Security
- Cause:
- There is a configuration problem because a null object was returned.
- Action:
- Examine the specific object referenced in the error message to see what may be the cause.
- BEA-097511
- Expected a {0} object but did not get one.
- Category:
- Security
- Cause:
- There is a configuration problem because an object was expected and a different object was returned.
- Action:
- Check the configuration.
- BEA-097512
- Multiple challenges not supported.
- Category:
- Security
- Cause:
- An attempt has made to handle multiple challenges with a provider that does not support it.
- Action:
- Correct the code or configure a ChallengeIdentityAsserter that supports multiple challenges.
- BEA-097513
- Incorrect Cert Path type, expecting a {0} type.
- Category:
- Security
- Cause:
- The wrong type of Cert Path was passed due to incorrect configuration.
- Action:
- Correct the configured CertPathBuilder service.
- BEA-097514
- Multiple {0} support the token type {1}.
- Category:
- Security
- Cause:
- The configuration is not correct.
- Action:
- Remove one of the objects supporting this token token type from the configuration.
- BEA-097515
- Unsupported token type {0}
- Category:
- Security
- Cause:
- No objects are configured to support the specified token type.
- Action:
- Configure an object that supports this token type.
- BEA-097516
- Unable to validate a non X.509 certificate path.
- Category:
- Security
- Cause:
- Not all certificate paths are of type X.509.
- Action:
- Correct the configured CertPathBuilder service to ensure that all certificate paths are of type X.509.
- BEA-097517
- A certificate is self signed but it is not the last certificate in the chain, see {0}
- Category:
- Security
- Cause:
- There is a certificate chain but one of the certificates is self signed.
- Action:
- Ensure that the certificate chain is correct.
- BEA-097518
- Issue DN mismatch error. Issued: {0} does not match issuer: {1}.
- Category:
- Security
- Cause:
- There is an inconsistent certificate chain. The issuer DN of a certificate did not match the subject DN of the next certificate in the chain.
- Action:
- Ensure that the the certificates in the chain correctly refer to each other.
- BEA-097519
- Certificate not signed by issuer. Certificate: {0} not signed by issuer: {1}.
- Category:
- Security
- Cause:
- There is an inconsistent certificate chain. A certificate was not signed by the next certificate in the chain.
- Action:
- Ensure that the the certificates in the chain correctly refer to each other.
- BEA-097520
- Capacity {0} greater than maximum {1}
- Category:
- Security
- Cause:
- The specified queue capacity is too large.
- Action:
- Reduce the specified queue capacity.
- BEA-097521
- Maximum capacity {0} is greater than the allowed {1}
- Category:
- Security
- Cause:
- The specified maximum queue capacity is larger than allowed.
- Action:
- Reduce the specified maximum capacity.
- BEA-097522
- Initial specified capacity of {0} is illegal.
- Category:
- Security
- Cause:
- The specified capacity is illegal.
- Action:
- Specify a correct capacity.
- BEA-097523
- Illegal load factor.
- Category:
- Security
- Cause:
- An illegal load factor was specified.
- Action:
- Specify a load factor greater than 0 and less than 1.
- BEA-097524
- No appropriate registered configuration to handle the AppConfigurationEntry named: {0}
- Category:
- Security
- Cause:
- No appropriate JAASConfiguration has been registered.
- Action:
- Register the appropriate JAASConfiguration
- BEA-097525
- Null JAASConfiguration.
- Category:
- Security
- Cause:
- An attempt was made to register a null JAASConfiguration.
- Action:
- Register a non-null JAASConfiguration.
- BEA-097526
- Duplicate JAASConfiguration.
- Category:
- Security
- Cause:
- An attempt was made to register a JAASConfiguration twice.
- Action:
- Do not attempt to register the JAASConfiguration twice.
- BEA-097527
- JAASConfiguration not registered.
- Category:
- Security
- Cause:
- An attempt was made to unregister a JAASConfiguration that is not registered.
- Action:
- Do not attempt to unregister an unregistered JAASConfiguration.
- BEA-097528
- A null {0} was specified.
- Category:
- Security
- Cause:
- This method cannot accept a null argument.
- Action:
- Do not pass in a null argument.
- BEA-097529
- The principal validators {0} and {1} both validate the same principal types.
- Category:
- Security
- Cause:
- There can only be one principal validator for each principal type.
- Action:
- Correct the configuration.
- BEA-097530
- No {1} found in method {0}
- Category:
- Security
- Cause:
- Objects should have been configured but were not.
- Action:
- Correct the configuration.
- BEA-097531
- Method {0} was unable to sign a principal.
- Category:
- Security
- Cause:
- Something was wrong with the principal or the principal validator was incorrect.
- Action:
- Correct the configuration.
- BEA-097532
- Null parameter supplied to method {0}.
- Category:
- Security
- Cause:
- A parameter was not correctly specified. This is most likely a coding error.
- Action:
- Check the code for an incorrectly specified parameter.
- BEA-097533
- SecurityProvider service class name for {0} is not specified.
- Category:
- Security
- Cause:
- The SecurityProviderConfig does not contain a SecurityProvider service class name.
- Action:
- Examine the specific objects referenced in the error message to see what may be the cause, and take appropriate action.
- BEA-097534
- Failed to obtain an instance of class {0}.
- Category:
- Security
- Cause:
- There is a possible configuration problem. A {0} class name is invalid, or is not in the class path. It does not have a public no argument constructor, or has the constructor which failed to execute.
- Action:
- Check the configuration.
- BEA-097535
- The configuration does not define a store, but providers that require a store are in use.
- Category:
- Security
- Cause:
- There is no store servoce defined in the configuration.
- Action:
- Configure a store service.
- BEA-097536
- The {0} service can not be found for {1}.
- Category:
- Security
- Cause:
- A null was returned when doing a service lookup.
- Action:
- Check the configuration to see if the missing service was actually configured.
- BEA-097537
- The {2} setting supplied in the {1} configuration to {0} is invalid.
- Category:
- Security
- Cause:
- The configuration setting {2} supplied in {1} to {0} is incorrect.
- Action:
- Ensure that the configuration supplied for {0} is correct.
- BEA-097538
- The keystore {0} of type {1} could not be accessed.
- Category:
- Security
- Cause:
- The keystore {0} of type {1} could not be accessed and the configuration may be incorrect.
- Action:
- Ensure that the keystore {0} of type {1} can be accessed.
- BEA-097539
- Connection to the database is currently unavailable.
- Category:
- Security
- Cause:
- The database configuration may be incorrect or the database was not available.
- Action:
- Ensure that the database configuration is correct and that the database is available.
- BEA-097540
- Property could not be parsed and will be skipped. Format must be name=value. Format found: {0}
- Category:
- Security
- Cause:
- The properties configured for the database pool could not be parsed and will be skipped.
- Action:
- Check the format of the properties supplied to the configuration
- BEA-097541
- {0} requires a {1}, this was not available.
- Category:
- Security
- Cause:
- This may be a coding error or a configuration error.
- Action:
- Check for configuration errors. If the configuration appears valid, contact My Oracle Support.
- BEA-097542
- Connection was not found by name {0}.
- Category:
- Security
- Cause:
- The named SQL connection was not found.
- Action:
- Check the log to see whether there is a connection pool checkout failure and determine the cause.
- BEA-097543
- Store service properties must not be null.
- Category:
- Security
- Cause:
- This may be a store service configuration error.
- Action:
- Check the store service configuration.
- BEA-097544
- Get a null {0} value in store service properties.
- Category:
- Security
- Cause:
- A data store connection was not specified in the store service properties.
- Action:
- Check the store service configuration.
- BEA-097545
- The internal state of the token is not consistent, possibly due to a failure during encoding/decoding the token.
- Category:
- Security
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097546
- Timestamp is not of the correct length: {0}.
- Category:
- Security
- Cause:
- The timestamp format was not correct.
- Action:
- Fix the timestamp format.
- BEA-097547
- Timestamp contains illegal non-digit characters: {0}.
- Category:
- Security
- Cause:
- The timestamp format is not correct.
- Action:
- Fix the timestamp format.
- BEA-097548
- Timestamp has invalid timezone designator: {0}.
- Category:
- Security
- Cause:
- The timestamp format is not correct.
- Action:
- Fix the timestamp format.
- BEA-097549
- Timestamp is missing timezone designator: {0}.
- Category:
- Security
- Cause:
- The timestamp format is not correct.
- Action:
- Fix the timestamp format.
- BEA-097550
- Month value is out-of-range for given year: {0}.
- Category:
- Security
- Cause:
- The timestamp format is not correct.
- Action:
- Fix the timestamp format.
- BEA-097551
- Day of month value is out-of-range for given month and year: {0}.
- Category:
- Security
- Cause:
- The timestamp format is not correct.
- Action:
- Fix the timestamp format.
- BEA-097552
- SPNEGO token trying to be constructed with invalid parsed information.
- Category:
- Security
- Cause:
- The parsed information is invalid.
- Action:
- This is likely an internal WebLogic Server error. If this occurs again, contact My Oracle Support.
- BEA-097553
- SAMLSourceSite: Error while generating {0}: {1}.
- Category:
- Security
- Cause:
- {0} Could not be generated.
- Action:
- This is likely an internal WebLogic Server error. If this occurs again, contact My Oracle Support.
- BEA-097554
- Queries that test at least one scope primary key must test all primary keys with a lower index.
- Category:
- Security
- Cause:
- Not all primary keys with a lower index were tested.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097555
- This store does not support nested containers (that is, collections of collections).
- Category:
- Security
- Cause:
- You are using nested containers for a store that does not support them.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-097556
- Primary key field must not be null: {0}.
- Category:
- Security
- Cause:
- There was no value found for the primary key.
- Action:
- Check the query to see if the primary key is not null or empty.
- BEA-097558
- FederationServicesMBean configuration Protocol Signing Key {0} is invalid.
- Category:
- Security
- Cause:
- The FederationServicesMBean Protocol Signing Key was configured with an invalid value.
- Action:
- Check the key information to see if it is valid.
- BEA-097559
- FederationServicesMBean configuration SSL Client Key {0} is invalid.
- Category:
- Security
- Cause:
- The FederationServicesMBean SSL Client Key was configured with an invalid value.
- Action:
- Check the key information to see if it is valid.
- BEA-097560
- Invalid Source Site configuration, {0} must not be null or empty.
- Category:
- Security
- Cause:
- The Source Site configuration is missing.
- Action:
- Check the configuration to see if there is a null or empty field.
- BEA-097561
- Store service is not initialized properly.
- Category:
- Security
- Cause:
- The store service was configured incorrectly.
- Action:
- Check the Store service configuration.
- BEA-097562
- Cannot forward to custom post form, please check if the post form configuration is valid.
- Category:
- Security
- Cause:
- The post form configuration was invalid.
- Action:
- Fix the post form configuration.
- BEA-097563
- Connection was not found by name {0}.
- Category:
- Security
- Cause:
- There was a configuration error or an internal WebLogic Server error.
- Action:
- Ensure that the specified data source is configured. In addition, check the log to see whether there is a connection pool checkout failure and find the cause.
- BEA-097564
- The JDBC Connection Service initialization failed.
- Category:
- Security
- Cause:
- The configuration is incorrect.
- Action:
- Check that the SQL configuration has been specified properly.
- BEA-098500
- Decimal is too short.
- Category:
- Security
- Cause:
- The value length is less than or equal to 0.
- Action:
- Pass in a correct value.
- BEA-098501
- Decimal contains incorrect characters.
- Category:
- Security
- Cause:
- The specified decimal value contains incorrect characters.
- Action:
- Pass in a correct value.
- BEA-098502
- Hex binary data bad length.
- Category:
- Security
- Cause:
- The length of hex binary data is uneven.
- Action:
- Pass in a correct value.
- BEA-098503
- Invalid hex digit.
- Category:
- Security
- Cause:
- An invalid hexadecimal digit was encountered.
- Action:
- Pass in a correct value.
- BEA-098504
- Invalid RFC822 name: {0}
- Category:
- Security
- Cause:
- An invalid RFC822 name attribute value was passed.
- Action:
- Pass in a valid RFC822 name attribute value.
- BEA-098505
- Illegal X500 value: {0}
- Category:
- Security
- Cause:
- An illegal X500 value was passed.
- Action:
- Pass in a valid X500 name attribute value.
- BEA-098506
- Not enough BASE64 bytes
- Category:
- Security
- Cause:
- The atom cannot be decoded because not enough bytes were available.
- Action:
- Correct the BASE64 value.
- BEA-098507
- Incorrect XPathVersion
- Category:
- Security
- Cause:
- An unsupported XPathVersion was specified.
- Action:
- Use a supported XPathVersion
- BEA-098508
- Negative month with non-zero year
- Category:
- Security
- Cause:
- The month cannot be negative if the year is a non-zero value.
- Action:
- Correct the month or year value.
- BEA-098509
- Month and year are zero.
- Category:
- Security
- Cause:
- Both the month and the year are zero. At least one of the month and year must be non-zero.
- Action:
- Correct the month or year value.
- BEA-098510
- Method {0} had an internal WebLogic Server error.
- Category:
- Security
- Cause:
- This is an internal WebLogic Server error
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-098511
- Illegal explicit to non-explicit time zone comparison
- Category:
- Security
- Cause:
- It is illegal to compare time values when one has an explicit time zone and the other does not.
- Action:
- Correct the time-zone specification mismatch.
- BEA-098512
- Could not schedule Audit log rotate trigger
- Category:
- Security
- Cause:
- There is an issue with the parameters configured on the Audit provider.
- Action:
- Correct the parameters configured on the Audit provider.
- BEA-098513
- Service Initialization when getting service with {0} service name.
- Category:
- Security
- Cause:
- The service with {0} service name was not correctly initialized in the service engine.
- Action:
- Correctly initialize the service in the service engine.
- BEA-098514
- Failed to generate a certificate thumbprint: {0}.
- Category:
- Security
- Cause:
- The thumbprint algorithm cannot be found or a certificate encoding error occurred.
- Action:
- Examine the error message to determine the exact cause and take appropriate action.
- BEA-098515
- {1} cannot be {2}.
- Category:
- Security
- Cause:
- This is most likely a coding error.
- Action:
- Pass a valid {1} to the method {0}.
- BEA-098516
- The CertificateRegistry could not build a certificate path for the thumbprint {0}. This indicates that either someone is trying to access the server with an untrusted thumbprint or that the administrator has forgotten to register a certificate with this thumbprint in the CertificateRegistry.
- Category:
- Security
- Cause:
- The CertificateRegistry does not contain a certificate whose thumbprint is {0}.
- Action:
- If you want to trust the thumbprint {0}, then register a certificate with this thumbprint in the CertificateRegistry.
- BEA-098517
- Failed to get SAML assertion info: {0}.
- Category:
- Security
- Cause:
- A SAML assertion document parsing error occurred.
- Action:
- Examine the error message to determine the cause and take appropriate action.
- BEA-098518
- The environment does not support anonymous, please log in.
- Category:
- Security
- Cause:
- The method getAnonymousIdentity of IdentityService returned null.
- Action:
- Check the environment configuration.
- BEA-098519
- Invalid file store password or the file has been invalidly changed.
- Category:
- Security
- Cause:
- The password for the file store is illegal or the file is modified.
- Action:
- Ensure that the store password is not changed and the file is not modified either.
- BEA-098520
- Unable to instantiate the CSSDelegate implementation.
- Category:
- Security
- Cause:
- The CSS Delegate implementation is not in the classpath.
- Action:
- Check the CSS classpath.
- BEA-098521
- Invalid principal class name {0} is entered to the PrincipalFactory create() API.
- Category:
- Security
- Cause:
- An invalid principal class name was entered to the PrincipalFactory create() API.
- Action:
- Ensure that the principal class derives from WLSPrincipal.
- BEA-098522
- Unable to instantiate the principal instance for principal class {0}.
- Category:
- Security
- Cause:
- The principal class {0} is not in the classpath.
- Action:
- Ensure that the class {0} is in the classpath.
- BEA-098523
- Unable to instantiate the PrincipalConfigurationDelegate instance.
- Category:
- Security
- Cause:
- The related class, either WLSPrincipalConfigurationDelegateImpl or OPPrincipalConfigurationDelegateImpl, is not in the classpath.
- Action:
- Ensure that WLSPrincipalConfigurationDelegateImpl and OPPrincipalConfigurationDelegateImpl are in the classpath.
- BEA-099000
- Null {0} parameter supplied to method {1}.
- Category:
- Security
- Cause:
- A parameter was not correctly specified. This is most likely a coding error.
- Action:
- Check for a coding error.
- BEA-099001
- Invalid ContextHandler value for {0} type: expect to {1} type.
- Category:
- Security
- Cause:
- This most likely was caused by an environment error.
- Action:
- Check and update the indicated context element.
- BEA-099002
- Null or empty certificate chain
- Category:
- Security
- Cause:
- This was most likely caused by an environment error.
- Action:
- Check and update the indicated context element.
- BEA-099003
- SAMLBeanUpdateListener {0}: {1} failed with exception: {2}
- Category:
- Security
- Cause:
- This was most likely caused by an environment error.
- Action:
- Check and update the environment.
- BEA-099004
- SAMLCreateAssertion: Exception while creating authentication statement.: {0}
- Category:
- Security
- Cause:
- This was most likely caused by an environment error.
- Action:
- Check and update the environment.
- BEA-099005
- SAMLCreateAssertion: can't map confirmation method
- Category:
- Security
- Cause:
- This was most likely caused by an environment error.
- Action:
- Check and update the environment.
- BEA-099006
- provider {0}: SAML Key Manage failed to validate key (Assertions signing) configuration in the FederationServicesMBean, key alias: {1}
- Category:
- Security
- Cause:
- This was most likely caused by an environment error.
- Action:
- Check and update the environment.
- BEA-099007
- Provider {0} not initialized: method {1} could not be called.
- Category:
- Security
- Cause:
- An internal WebLogic Server error occurred when the SAML provider was initialized.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-099008
- Store service properties must not be null.
- Category:
- Security
- Cause:
- This was most likely caused by a configuration error.
- Action:
- Check the Store service configuration.
- BEA-099009
- Get a null {0} value in store service properties.
- Category:
- Security
- Cause:
- This was most likely caused by a configuration error.
- Action:
- Check the Store service configuration.
- BEA-099010
- Unable to derive key.
- Category:
- Security
- Cause:
- The input {0} is null or empty.
- Action:
- Verify that the input parameter {0} is not null or empty.
- BEA-099011
- Unable to get digest value for a password.
- Category:
- Security
- Cause:
- The input {0} is null or empty.
- Action:
- Verify that the input parameter {0} is not null or empty.
- BEA-099012
- Unable to create password digest - UTF-8 encoding required but unavailable:{0}.
- Category:
- Security
- Cause:
- An internal WebLogic Server error occurred while performing a message digest.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-099013
- Invalid token type {0} received by the LDAP X509 certificate identity asserter.
- Category:
- Security
- Cause:
- This was likely caused by the provider not being properly configured.
- Action:
- Check the provider configuration.
- BEA-099014
- {0}: {1} is null
- Category:
- Security
- Cause:
- A parameter was not correctly specified.
- Action:
- Check for a coding error.
- BEA-099015
- The format for import or export is invalid.
- Category:
- Security
- Cause:
- The format for import or export was invalid.
- Action:
- Check the string used for import or export.
- BEA-099016
- Could not get partner by partner id: {0}.
- Category:
- Security
- Cause:
- The partner could not be retrieved using the partner id: {0}.
- Action:
- Check the registry to see if the partner exists.
- BEA-099017
- Could not add partner with null partner id.
- Category:
- Security
- Cause:
- The partner id is null.
- Action:
- Check the partner information.
- BEA-099018
- Update business object failed, could not determine the object to update.
- Category:
- Security
- Cause:
- The object for updating could not be found.
- Action:
- Check the registry to find the correct partner for updating.
- BEA-099019
- Could not parse assertion: {0}.
- Category:
- Security
- Cause:
- An assertion was received that could not be properly parsed.
- Action:
- Check the SAML assertion or contact My Oracle Support.
- BEA-099020
- Assertion validity check failed: {0}.
- Category:
- Security
- Cause:
- An assertion was received that did not pass validation.
- Action:
- Check the SAML assertion or contact My Oracle Support.
- BEA-099021
- Signature required but assertion is not signed.
- Category:
- Security
- Cause:
- The assertion is not signed.
- Action:
- Check the SAML assertion.
- BEA-099022
- Signature is required but no signing certificate alias configured.
- Category:
- Security
- Cause:
- No signing certificate alias is configured.
- Action:
- Check the SAML configuration.
- BEA-099023
- Unable to find trusted certificate for alias: {0}.
- Category:
- Security
- Cause:
- The trusted certificate was not available from the certificate registry.
- Action:
- Check the SAML configuration.
- BEA-099024
- Signature verified but no certificate found to check trust.
- Category:
- Security
- Cause:
- No certificate was found to check the trust.
- Action:
- Check the signature for the certificate.
- BEA-099025
- Certificate in signature does not match configured signing cert.
- Category:
- Security
- Cause:
- The certificate in the signature does not match the configured signing cert.
- Action:
- Check the certificate information in the partner registry.
- BEA-099026
- Certificate is not trusted.
- Category:
- Security
- Cause:
- An assertion was received for which the signing certificate is not trusted.
- Action:
- Check the SAML configuration and add the certificate to the registry.
- BEA-099027
- Could not create name mapper: {0}.
- Category:
- Security
- Cause:
- An error occurred while creating an instance of the configured SAML name mapper.
- Action:
- Check the details of the error message to determine the proper handling.
- BEA-099028
- Mapping name error: {0}.
- Category:
- Security
- Cause:
- An error occurred while invoking an instance of the configured SAML name mapper.
- Action:
- Check the details of the error message to determine the proper handling.
- BEA-099029
- Mapping group error: {0}.
- Category:
- Security
- Cause:
- An error occurred while invoking an instance of the configured SAML name mapper.
- Action:
- Check the details of the error message to determine the proper handling.
- BEA-099030
- NameMapper returned no username mapping.
- Category:
- Security
- Cause:
- An instance of the configured SAML name mapper returned no user or group information.
- Action:
- Check the SAML assertion or contact My Oracle Support.
- BEA-099031
- Assertion is invalid before {0}.
- Category:
- Security
- Cause:
- The received SAML assertion is not yet valid.
- Action:
- Check the SAML configuration, the system clock or contact the SAML Identity Provider.
- BEA-099032
- Assertion is invalid on or after {0}.
- Category:
- Security
- Cause:
- The received SAML assertion has expired.
- Action:
- Check the SAML configuration, the system clock or contact the SAML Identity Provider.
- BEA-099033
- No matching audience.
- Category:
- Security
- Cause:
- The received SAML assertion audience conditions was not satisfied.
- Action:
- Check the SAML configuration or contact the SAML Identity Provider.
- BEA-099034
- Unrecognized assertion condition (schema extension).
- Category:
- Security
- Cause:
- The received SAML assertion contained an unknown condition.
- Action:
- Contact the SAML Identity Provider for information on how to correct the problem.
- BEA-099035
- No target in context handler.
- Category:
- Security
- Cause:
- An internal WebLogic Server error occurred while determining the SAML target.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-099036
- Could not map Confirmation Method URN: {0}.
- Category:
- Security
- Cause:
- The received SAML assertion contained an unknown confirmation method.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-099037
- Could not find asserting party matching assertion and context.
- Category:
- Security
- Cause:
- The SAML partner could not be determined from the received SAML assertion.
- Action:
- Check the SAML assertion or contact My Oracle Support.
- BEA-099038
- Could not verify signature: {0}.
- Category:
- Security
- Cause:
- The signature from the received SAML assertion could not be verified.
- Action:
- Check the SAML assertion or contact My Oracle Support.
- BEA-099039
- No issuer URI configured for asserting party.
- Category:
- Security
- Cause:
- The SAML asserting party was not configured with an issuer URI.
- Action:
- Check the SAML configuration.
- BEA-099040
- Assertion issuer does not match issuer configured for asserting party.
- Category:
- Security
- Cause:
- The issuer from the received SAML assertion could not be verified.
- Action:
- Check the SAML assertion against the SAML configuration.
- BEA-099041
- Assertion subject confirmation method does not match asserting party configuration.
- Category:
- Security
- Cause:
- The subject confirmation from the received SAML assertion could not be verified.
- Action:
- Check the SAML assertion against the SAML configuration.
- BEA-099046
- Illegal value for {0}: {1}.
- Category:
- Security
- Cause:
- This error has multiple possible causes. When using the PasswordHashUtility, an invalid command line argument was passed. For SAML, it means that there is an invalid SAML provider configuration.
- Action:
- Check the command line argument for the parameter specified in the message or check the SAML provider configuration.
- BEA-099047
- Missing parameter {0}.
- Category:
- Security
- Cause:
- The SAML provider configuration is invalid.
- Action:
- Check the SAML provider configuration.
- BEA-099048
- Invalid {0} value {1} for {2}.
- Category:
- Security
- Cause:
- An invalid configuration was supplied for the SAML provider.
- Action:
- Check the SAML provider configuration based on the configuration parameter from the error message.
- BEA-099049
- Could not load SAML partner registry schema file {0}.
- Category:
- Security
- Cause:
- An internal WebLogic Server error occurred while loading the SAML partner registry.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-099050
- Could not generate XML Schema from SAML partner registry schema file: {0}.
- Category:
- Security
- Cause:
- An internal WebLogic Server error occurred while loading the SAML partner registry.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-099051
- ImportMode = fail, partnerID {0} exists, import operation terminated.
- Category:
- Security
- Cause:
- The SAML partner could not be imported because the partner entry already exists.
- Action:
- Check the SAML configuration or select a different SAML partner import mode.
- BEA-099052
- Could not locate {0} {1} in the import XML document, import operation abort.
- Category:
- Security
- Cause:
- The SAML partner could not be imported because the partner or certificate could not be found.
- Action:
- Check the SAML partner registry file based on the information from the error message.
- BEA-099053
- {0} {1} already exists, Import operation fail.
- Category:
- Security
- Cause:
- The SAML partner could not be imported because the partner or certificate already exists.
- Action:
- Check the SAML configuration based on the information from the error message.
- BEA-099054
- Error getting {0} {1} from registry, Import operation fail.
- Category:
- Security
- Cause:
- The SAML partner could not be imported because the partner or certificate could not be located.
- Action:
- Check the SAML configuration based on the information from the error message.
- BEA-099055
- Could locate {0} {1} from registry.
- Category:
- Security
- Cause:
- The SAML partner could not be imported because the partner or certificate could not be located.
- Action:
- Check the SAML configuration based on the information from the error message.
- BEA-099056
- Could not export partner registry data ldift: {0}.
- Category:
- Security
- Cause:
- An internal WebLogic Server error occurred while exporting a SAML partner.
- Action:
- Contact My Oracle Support and provide them with the log files.
- BEA-099057
- Could not decrypt password: {0}.
- Category:
- Security
- Cause:
- The supplied password could not be read.
- Action:
- Check that the password value is correct or contact My Oracle Support.
- BEA-099058
- No sender certificate is provided for checking trust.
- Category:
- Security
- Cause:
- The received SAML assertion could not be trusted because no certificate was provided.
- Action:
- Check the SAML configuration, the SSL configuration or contact My Oracle Support.
- BEA-099059
- There is no {0} in {1}.
- Category:
- Security
- Cause:
- The received SAML assertion could not be validated.
- Action:
- Check the details of the error message to determine the proper handling.
- BEA-099060
- The URL specified for the data store connection is invalid: {0},please check all host configuration parameters.
- Category:
- Security
- Cause:
- This was most likely caused by a configuration error.
- Action:
- Check all host configuration.
- BEA-099061
- Hash algorithm {0} was not found
- Category:
- Security
- Cause:
- The JCE configuration is most likely not set up to support the algorithm.
- Action:
- Review the JCE configuration to ensure the hash algorithm is available for use.
- BEA-099062
- The {0} password hash algorithm is not usable.
- Category:
- Security
- Cause:
- The password algorithm name was not found to be supported by the JCE crypto configuration.
- Action:
- Verify that the password algorithm is specified correctly, and that the JCE configuration supports the algorithm.
- BEA-099063
- Plaintext password usage was rejected.
- Category:
- Security
- Cause:
- Plaintext passwords are configured to not be allowed, but a Plaintext password was either found or was attempted to be saved.
- Action:
- If the failure occurred during authentication, review the plaintext passwords and correct them. If the failure occurred while changing a password, review the password style settings to ensure that they specify a non-plaintext style.
- BEA-099064
- Plaintext password is not allowed and unable to parse the stored hashed password.
- Category:
- Security
- Cause:
- Plaintext passwords are configured to not be allowed, but the hashed password could not be parsed.
- Action:
- If the failure occurred during authentication, review the plaintext passwords and correct them. If the failure occurred while changing a password, review the password style settings to ensure that they specify a non-plaintext style.
- BEA-099065
- Password ("quit" to end)
- Category:
- Security
- Cause:
- The password hash utility internally uses this prompt for a password.
- Action:
- This is the prompt that will be used by the password hash utility.
- BEA-099066
- Usage: Java com.bea.security.utils.authentication.PasswordHashUtility [-a algorithm] [-s size] password* "algorithm" is the name of the hash algorithm "size" is the length of the salt characters "passwords" are the plain text passwords to be hashed. None for interactive mode.
- Category:
- Security
- Cause:
- The is the text the password hash utility displays for usage of the utility.
- Action:
- This is the usage text that will be used by the password hash utility.
- BEA-099067
- The minimum length of password must not be greater than the maximum length of password.
- Category:
- Security
- Cause:
- System password validation was configured with an invalid password length.
- Action:
- Change the value for minimum or maximum length of a password.
- BEA-099068
- The user name cannot be empty.
- Category:
- Security
- Cause:
- The user name is null.
- Action:
- Input correct user name information.
- BEA-099069
- The password length cannot be less than {0}.
- Category:
- Security
- Cause:
- The current password length is less than {0}.
- Action:
- Change your password, and try again.
- BEA-099070
- The password length cannot be greater than {0}.
- Category:
- Security
- Cause:
- The current password length is greater than {0}.
- Action:
- Change your password, and try again.
- BEA-099071
- The password cannot contain or be equal to your username.
- Category:
- Security
- Cause:
- The password contains or is the same as your username.
- Action:
- Change your password, and try again.
- BEA-099072
- The password cannot contain or be equal to the reverse of your username.
- Category:
- Security
- Cause:
- The password contains or is equal to the reverse of your username.
- Action:
- Change your password, and try again.
- BEA-099073
- The maximum instances of a character in a password cannot be greater than {0}.
- Category:
- Security
- Cause:
- The maximum occurrences of a character in the password is greater than what is allowed by the configuration of system password validation.
- Action:
- Change your password, and try again.
- BEA-099074
- The maximum repeating consecutive characters in a password cannot be greater than {0}.
- Category:
- Security
- Cause:
- The repetition of a character in the password is greater than what is allowed by the configuration of system password validation.
- Action:
- Reduce the repeating consecutive characters in your password, and try again.
- BEA-099075
- The number of alphabetic characters in a password cannot be less than {0}.
- Category:
- Security
- Cause:
- The number of alphabetic characters in the password is less than what is required by the configuration of system password validation.
- Action:
- Add more alphabetic characters in your password.
- BEA-099076
- The number of numeric characters in a password cannot be less than {0}.
- Category:
- Security
- Cause:
- The number of numeric characters in the password is less than {0}.
- Action:
- Add more numeric characters in your password.
- BEA-099077
- The number of lowercase characters in a password cannot be less than {0}.
- Category:
- Security
- Cause:
- The number of lowercase characters in the password is less than {0}.
- Action:
- Add more lowercase characters in your password.
- BEA-099078
- The number of uppercase characters in a password cannot be less than {0}.
- Category:
- Security
- Cause:
- The number of uppercase characters in the password is less than {0}.
- Action:
- Add more uppercase characters in your password.
- BEA-099079
- The number of non-alphanumeric characters in a password cannot be less than {0}.
- Category:
- Security
- Cause:
- The number of non-alphanumeric characters in the password is less than {0}.
- Action:
- Add more non-alphanumeric characters in your password.
- BEA-099080
- The user password cannot be null.
- Category:
- Security
- Cause:
- The user password is null.
- Action:
- Input your password, and try again.
- BEA-099081
- Illegal command line.
- Category:
- Security
- Cause:
- Command line syntax is not correct.
- Action:
- Retype the command line and try again.
- BEA-099082
- Could not configure attribute {0} in MBean {1}.
- Category:
- Security
- Cause:
- The method to configure this attribute could not be found or the parameter for this method could not be created.
- Action:
- Refer to the MBean javadoc to verify whether the MBean attribute name is correct.
- BEA-099083
- The key {0} in property file is in the wrong format.
- Category:
- Security
- Cause:
- The key {0} in property file is in the wrong format.
- Action:
- Modify the property file and use a valid format for the key.
- BEA-099084
- Could not create MBean.
- Category:
- Security
- Cause:
- The MBean type or MBean class in property file may not be correct.
- Action:
- Check the MBean type or MBean class in the property file.
- BEA-099085
- Unknown MBeanResource ActionType {0}.
- Category:
- Security
- Cause:
- The MBean resource method that a caller is attempting to access is unknown.
- Action:
- Modify your entitlement policy and try again.
- BEA-099086
- Get null or empty encrypted value. An encrypted value must not be null or empty.
- Category:
- Security
- Cause:
- The encrypted value is null or empty.
- Action:
- Check the encrypted value.
- BEA-099087
- The MaxPasswordLength must not be less than MinAlphabeticCharacters+MinNumericCharacters+MinNonAlphanumericCharacters.
- Category:
- Security
- Cause:
- System password validation was configured with an invalid password length.
- Action:
- Change the system password validation configuration lengths.
- BEA-099088
- The MaxPasswordLength must not be less than MinLowercaseCharacters+MinUppercaseCharacters+MinNumericCharacters+MinNonAlphanumericCharacters.
- Category:
- Security
- Cause:
- System password validation was configured with an invalid password length.
- Action:
- Change the system password validation configuration lengths.
- BEA-099089
- The NegotiateCredentialMapper could not get credentials. The requestor is {0}. The initiator is {1}. The resource is {2}. The exception is {3}.
- Category:
- Security
- Cause:
- An unexpected exception occurred when trying to get the credentials.
- Action:
- Read the exception text from the log message for more information on diagnosing the problem.
- BEA-099090
- The NegotiateCredentialMapper could not get credentials for initiator with String type. The requestor is {0}. The initiator is {1}. The resource is {2}.
- Category:
- Security
- Cause:
- The initiator should not be a String while acquiring credentials with NegotiateCredentialMapperProvider.
- Action:
- Try the getCredentials() method with a Subject as the initiator.
- BEA-099091
- Illegal parameter type.
- Category:
- Security
- Cause:
- An initiator with String type is not supported by NegotaiteCredentialMapper for method getCredential().
- Action:
- Try the method getCredentials() with Subject as the initiator type.
- BEA-099092
- Trust group {0} not found.
- Category:
- Security
- Cause:
- The group could not be found as the group parameter that was passed to the method is not registered in the security provider.
- Action:
- Pass in a trust group that exists.
- BEA-099093
- The security provider already has a trust group registered with {0}.
- Category:
- Security
- Cause:
- The trust group {0} already exists in the security provider.
- Action:
- Pass in another trust group name.
- BEA-099094
- The trust group is null or empty.
- Category:
- Security
- Cause:
- An empty or null trust group was passed but this is not supported.
- Action:
- Modify the code to pass a non-null and non-empty trust group.
- BEA-099095
- The trust group wildcard is null or empty.
- Category:
- Security
- Cause:
- An empty or null trust group wildcard was passed, but this is not supported.
- Action:
- Modify the code to pass a non-null and non-empty trust group wildcard.
- BEA-099096
- An invalid entry {1} found in the group JKS keystore {0}.
- Category:
- Security
- Cause:
- Examine the nested exception for more information in diagnosing the problem.
- Action:
- Verify that the file is a group JKS keystore.
- BEA-099097
- The group {0} is not in the specified file {1}.
- Category:
- Security
- Cause:
- The group is not contained in a group JKS keystore.
- Action:
- Verify that the group is contained in a group JKS keystore.
- BEA-099098
- The security provider already has a certificate registered for trust group {0} under the alias {1}.
- Category:
- Security
- Cause:
- The certificate alias {0} already exists in the trust group {0}.
- Action:
- Pass in another certificate alias.
- BEA-099099
- Errors occurred when register certificate into groups {0}, please see nested message for details.
- Category:
- Security
- Cause:
- Errors occurred when trying to register certificates into trust groups.
- Action:
- Remove the trust group from the passed in trust group list.
- BEA-099100
- The trust group is null or empty.
- Category:
- Security
- Cause:
- An empty or null trust group was used, but this is not supported.
- Action:
- Modify the code to pass a non-null and non-empty trust group.
- BEA-099101
- The trust group name {0} is reserved for internal use, please choose another trust group name.
- Category:
- Security
- Cause:
- The trust group name is reserved.
- Action:
- Modify the code to pass another trust group name.
- BEA-099102
- Subject DN {1} already registered under the alias {2} trust group {0}.
- Category:
- Security
- Cause:
- A certificate with subject DN {1} already exists in the trust group {0} under the alias {2}.
- Action:
- Either remove the previous certificate from the trust group {0} or register a different certificate.
- BEA-099103
- Issuer DN {1} and serial number {2} already registered under the alias {3} in the trust group {0}
- Category:
- Security
- Cause:
- A certificate with issuer DN {1} and serial number {2} already exists in the trust group {0} under the alias {3}.
- Action:
- Either remove the previous certificate from the trust group {0} or register a different certificate.
- BEA-099104
- Subject key identifier {1} already registered under the alias {2} in the trust group {0}.
- Category:
- Security
- Cause:
- A certificate with subject key identifier {1} already exists in the trust group {0} under the alias {2}.
- Action:
- Either remove the previous certificate from the security provider or register a different certificate.
- BEA-099105
- The file path {0} does not exist.
- Category:
- Security
- Cause:
- The specified file path does not exist.
- Action:
- Create the file path {0} or use another existing file path.
- BEA-099106
- The password is a null or empty string.
- Category:
- Security
- Cause:
- The password is a null or empty string.
- Action:
- Supply a new password which is neither null nor empty.
- BEA-099107
- The algorithm {0} used to encrypt the file is invalid.
- Category:
- Security
- Cause:
- The algorithm {0} used to encrypt the file is invalid.
- Action:
- Supply a new algorithm.
- BEA-099108
- Invalid Property file: property "{0}" is required but is not configured.
- Category:
- Security
- Cause:
- Invalid Property file: property "{0}" is required but is not configured.
- Action:
- Add configuration of property "{0}" to your property file.
- BEA-099109
- Had problem attempting to get CallbackHandler for debugging in {0}: {1}
- Category:
- Security
- Cause:
- The system property weblogic.security.DumpContextHandler was set to true, but no CallbackHandler is available to handle the callback.
- Action:
- If using programmatic authentication, check if the passed CallbackHandler supports handling weblogic.security.auth.callback.ContextHandlerCallback. Otherwise, contact My Oracle Support.
- BEA-099110
- The value configured for NameMapper attribute: {0} is not valid.
- Category:
- Security
- Cause:
- The name mapper class {0} is not in the classpath or it does not implement thename mapper interface.
- Action:
- Ensure that the name mapper class {0} is in the classpath and implements the name mapper interface.
- BEA-099111
- The KerberosCredentialMapper could not get credentials. The requestor is {0}. The initiator is {1}. The resource is {2}. The exception is {3}.
- Category:
- Security
- Cause:
- An unexpected exception occurred when trying to get the credentials.
- Action:
- Read the exception text from the log message for more information on diagnosing the problem.
- BEA-099112
- The KerberosCredentialMapper could not get credentials for initiator with String type. The requestor is {0}. The initiator is {1}. The resource is {2}.
- Category:
- Security
- Cause:
- The initiator should not be a String while acquiring credentials with KerberosCredentialMapperProvider.
- Action:
- Try the getCredentials() method with a Subject as the initiator.
- BEA-099113
- Illegal parameter type.
- Category:
- Security
- Cause:
- An initiator with String type is not supported by NegotaiteCredentialMapper for method getCredential().
- Action:
- Try the method getCredentials() with Subject as the initiator type.
- BEA-099114
- The MaxPasswordLength must not be less than MinAlphaCharacters+MinNumericOrSpecialCharacters.
- Category:
- Security
- Cause:
- The MaxPasswordLength is less than MinAlphaCharacters+MinNumericOrSpecialCharacters.
- Action:
- Change the value and try again.
- BEA-099115
- The MaxPasswordLength must not be less than MinLowercaseCharacters+MinUppercaseCharacters+MinNumericOrSpecialCharacters.
- Category:
- Security
- Cause:
- The MaxPasswordLength is less than MinLowercaseCharacters+MinUppercaseCharacters+MinNumericOrSpecialCharacters.
- Action:
- Change the value and try again.
- BEA-099116
- The number of numeric or special characters in a password cannot be less than {0}.
- Category:
- Security
- Cause:
- The number of numeric or special characters in the password is less than {0}.
- Action:
- Add more numeric or special characters into your password.
- BEA-099117
- The LDAP authentication provider named "{0}" failed to make a connection to LDAP server at {1}://{2}:{3}, the error cause is: {4}.
- Category:
- Security
- Cause:
- Exception in making connection to LDAP server by the LDAP authentication provider.
- Action:
- Check the configured host name and port of the LDAP server for the failed LDAP authentication provider; also check SSL configuration details if SSL is enabled. If the failed provider is not used anymore in the domain, remove it to avoid the warning message. To change the default log interval (600 seconds), use the system property "weblogic.security.providers.authentication.connWarningLogIntervalSeconds". Note: If multiple LDAP providers are configured, the failover mechanism may tolerate failures for some providers.
- BEA-099118
- The special character "{0}" cannot be the first character of a password.
- Category:
- Security
- Cause:
- The special character "{0}" cannot be the first character of a password.
- Action:
- Change the value and try again.
- BEA-099500
- Invalid property value: {0}={1}
- Category:
- Security
- Cause:
- An exception occurred while processing the value for the specified property.
- Action:
- Correct the property and restart. This exception should not normally occur as the properties are only used internally.
- BEA-099501
- Caught exception while evaluating policy expression: {0} associated with: {1}
- Category:
- Security
- Cause:
- The evaluate method of the predicate used by the policy failed with a RuntimeException.
- Action:
- Ensure that parameters which are passed to the predicates in the expression or context are valid.
- BEA-099502
- An invalid predicate {0} was retrieved from the database. Ensure that the predicate class is in the server classpath.
- Category:
- Security
- Cause:
- The class file belonging to the condition was not in the server classpath.
- Action:
- Update the classpath and restart the server.
- BEA-099503
- Evaluation of policy associated with role {0} failed because the policy expression contains unregistered predicate: {1}.
- Category:
- Security
- Cause:
- The predicate that is specified in the log message is not registered, or the policy is out of date.
- Action:
- Register the predicate or remove its reference from the policy.
- BEA-099504
- Evaluation of policy associated with resource {0} failed because the policy expression contains unregistered predicate: {1}.
- Category:
- Security
- Cause:
- The predicate that is specified in the log message is not registered, or the policy is out of date.
- Action:
- Register the predicate, or remove its reference from the policy.
- BEA-100000
- Invalid call to the deprecated method {0}.
- Category:
- HTTP Session
- Cause:
- The method was deprecated in the latest servlet specification.
- Action:
- Check the specification for an alternative. If not corrected, unpredictable behavior might occur.
- BEA-100005
- Could not remove session: "{0}".
- Category:
- HTTP Session
- Cause:
- An unexpected error occurred while removing the session.
- Action:
- Check the exception text for the exact error message.
- BEA-100006
- HTTP session file persistence: storing sessions in directory: {0}.
- Category:
- HTTP Session
- Cause:
- This is an informational message.
- Action:
- Ensure that the directory stores the sessions per the PeristentStoreDir session parameter (weblogic.xml).
- BEA-100007
- Erasing the directory tree for persistent HTTP sessions: {0}.
- Category:
- HTTP Session
- Cause:
- The storage directory is being deleted as a result of session invalidation.
- Action:
- Ensure that deletion is occurring while removing sessions.
- BEA-100008
- Cannot delete "{0}".
- Category:
- HTTP Session
- Cause:
- The storage directory failed to be deleted.
- Action:
- Ensure that the permissions on this directory are correct and that the file and directory are not in use by another process.
- BEA-100011
- An error occurred while serializing session data. Deleting this session.
- Category:
- HTTP Session
- Cause:
- This might be due to a change in the class definition or serialVersionUID.
- Action:
- Check the exception text for the exact error message and take appropriate action.
- BEA-100013
- {0} not invalidated. The session that was serialized into the file system does not exist.
- Category:
- HTTP Session
- Cause:
- The session was not found and does not exist.
- Action:
- This session might have been deleted by a trigger in another server, which is pointing to the same storage location.
- BEA-100015
- Deleted file-based session persistent store file: {0}.
- Category:
- HTTP Session
- Cause:
- This is an informational message indicating that the storage file is being deleted.
- Action:
- Ensure that the deletion is consistent with the path defined in the PersistentStoreDir (weblogic.xml)
- BEA-100016
- Session expiration check failed for: {0}. Invalidating the session expiration check.
- Category:
- HTTP Session
- Cause:
- An unexpected error occurred while checking the session for expiration.
- Action:
- The session will be removed from the persistent store. Check the exception text for the exact error message.
- BEA-100018
- An error occurred while loading the serialized session data for session {0}.
- Category:
- HTTP Session
- Cause:
- An unexpected error occurred.
- Action:
- Check the exception text for the exact error message. The file could be corrupted.
- BEA-100019
- The file-based persistent session ID: "{0}" was stored in file: "{1}". File exists: {2}.
- Category:
- HTTP Session
- Cause:
- This is an informational message indicating that the session was stored in this path.
- Action:
- Ensure that the file-based persistent session storage is consistent with the PersistentStoreDir (weblogic.xml).
- BEA-100020
- Received malformed cookie ID: {0}.
- Category:
- HTTP Session
- Cause:
- The cookie could not be parsed properly.
- Action:
- Check the cookie format and the exception text for the exact problem.
- BEA-100022
- Session invalidation interval: {0}
- Category:
- HTTP Session
- Cause:
- The session invalidation trigger is being created.
- Action:
- Ensure that the session invalidation interval is consistent with the InvalidationIntervalSecs (weblogic.xml).
- BEA-100025
- An unexpected error occurred in the HTTP session timeout callback while deleting sessions.
- Category:
- HTTP Session
- Cause:
- The invalidation trigger failed unexpectedly while deleting sessions.
- Action:
- Check the exception message for the probable cause.
- BEA-100026
- An unexpected error occurred in the HTTP session timeout callback while checking session expiration.
- Category:
- HTTP Session
- Cause:
- An unexpected error occurred while checking the sessions for expiration.
- Action:
- Check the exception text for the exact error message.
- BEA-100028
- The session data could not be deserialized.
- Category:
- HTTP Session
- Cause:
- The session data could not be deserialized.
- Action:
- Ensure that the object being put into the session is serializable and that the non-transient objects it aggregates are also serializable. If any of the non-transient objects in the entire object graph are not serializable, this error message will occur.
- BEA-100030
- HTTP session expired. Session ID: {0}
- Category:
- HTTP Session
- Cause:
- This is an informational message indicating that the session with ID {0} has expired.
- Action:
- If the session expired sooner than expected, check the SessionTimeout parameter in the weblogic.xml file.
- BEA-100031
- An error occurred while unregistering the servlet session runtime MBean: {0}.
- Category:
- HTTP Session
- Cause:
- This MBean could not be removed.
- Action:
- Check the exception text for the exact error message.
- BEA-100032
- An error occurred while creating a servlet session runtime MBean.
- Category:
- HTTP Session
- Cause:
- This MBean could not be created.
- Action:
- Check the exception text for the exact error message.
- BEA-100033
- The license for replicated sessions is invalid: {0}. Downgrading sessions to memory, which are not replicated.
- Category:
- HTTP Session
- Cause:
- The license was not valid to support replicated sessions.
- Action:
- Check the license. An upgrade to a clustering and replication license may be desired. Alternatively, file and JDBC persistence can be used for session store reliability.
- BEA-100035
- The timer invalidated session ID: {0}, Web application: {1}, because it expired.
- Category:
- HTTP Session
- Cause:
- This message was logged by the Web application level timer, which periodically checks the sessions for expiration. The session expired.
- Action:
- If the session expired too soon, check the SessionTimeout in the weblogic.xml file.
- BEA-100038
- Unknown persistent type: {0} for Web application: {1}. Valid types are: memory, file, replicated, JDBC, cookie, and replicated_if_clustered.
- Category:
- HTTP Session
- Cause:
- The specified persistent store type for this Web application was not recognized.
- Action:
- Check the PersistentStoreType parameter in the weblogic.xml file. The valid values are: memory, file, replicated, cookie, JDBC, and replicated_if_clustered.
- BEA-100039
- Replicated HTTP sessions were specified for the Web application: {0}, but clustering was not enabled.
- Category:
- HTTP Session
- Cause:
- The session replication mechanism relies on clustering, which was not been configured.
- Action:
- Set up clustering or change the PersistentStoreType in the weblogic.xml file to either memory, file, JDBC, or cookie.
- BEA-100040
- The getAttribute(): {0} was a handle. Reconstructing the EJB object.
- Category:
- HTTP Session
- Cause:
- This is an informational message indicating that the container is storing only the handle for the EJB object placed into the session.
- Action:
- No action is required.
- BEA-100041
- The setAttribute(): {0} was an EJB object. Storing the handle into the session.
- Category:
- HTTP Session
- Cause:
- The container found an EJB handle stored in the session. It will reconstruct the EJB object before returning it.
- Action:
- No action is required.
- BEA-100042
- An error occurred while reconstructing the EJB object: {0}, which was put into the session.
- Category:
- HTTP Session
- Cause:
- The container found an EJB handle stored in the session. However, it failed to reconstruct the EJB object using that handle.
- Action:
- Ensure that the handle is still valid. Check the exception text for the exact error message.
- BEA-100043
- An error occurred while finding the handle for the EJB object: {0}.
- Category:
- HTTP Session
- Cause:
- The container stores only the handle for an EJB object put into the session. However, in this case, it failed to find the handle.
- Action:
- Check the RemoteException for the exact error message details.
- BEA-100044
- Found WLCookie cookie {0}={1}.
- Category:
- HTTP Session
- Cause:
- The cookie persistence mechanism relies on setting the cookie header.
- Action:
- No action is required.
- BEA-100045
- Malformed WLCookie. Value: {0} will be ignored.
- Category:
- HTTP Session
- Cause:
- The cookie persistence mechanism relies on setting the cookie header.
- Action:
- The cookie was found to be malformed. Only strings are supported for cookie-based persistence. Ensure that there are no characters in the attribute names and values, which can break the cookie syntax.
- BEA-100046
- Creating new session with ID: {0} for Web application: {1}.
- Category:
- HTTP Session
- Cause:
- A new session was created.
- Action:
- Ensure that the length is equal to the IDLen parameter in the weblogic.xml file.
- BEA-100047
- Performing the database operation: {0} with ID: {1} and Web application: {2}.
- Category:
- HTTP Session
- Cause:
- This is an informational message for JDBC-based persistence. It is meant for debugging purposes only.
- Action:
- No action is required.
- BEA-100048
- Looked up ROID: {0} from host {1}:{2} for ID: {3}.
- Category:
- HTTP Session
- Cause:
- The replicated session ID was not found in the current server, perhaps because this server is not the primary or secondary server. Another attempt to retrieve the session from the assigned secondary server will be made if it is alive.
- Action:
- No action is required.
- BEA-100050
- The current server is becoming the primary server for replicated session ID: {0}.
- Category:
- HTTP Session
- Cause:
- The current server is taking the role of the primary server for the given session.
- Action:
- No action is required.
- BEA-100051
- The current server is becoming the secondary server for replicated session ID: {0}.
- Category:
- HTTP Session
- Cause:
- The current server is taking the role of the secondary server for the given session.
- Action:
- No action is required.
- BEA-100052
- Unregistering replicated session ID: {0}.
- Category:
- HTTP Session
- Cause:
- The current server will unregister the given session.
- Action:
- The session was invalidated. No action is required.
- BEA-100053
- Failed to update the secondary server for HTTP session ID: {0}.
- Category:
- HTTP Session
- Cause:
- Failed to update the secondary server for the modification that occurred in the current request.
- Action:
- Verify that the secondary server is alive, and ensure that the objects put into the session are all serializable. Also, check the exception text for the exact error message.
- BEA-100054
- Failed to find the secondary server for HTTP session ID: {0}.
- Category:
- HTTP Session
- Cause:
- The secondary server could not be found for the replicated session.
- Action:
- Verify that the clustering is configured properly and that there is more than one server in the cluster.
- BEA-100055
- The generated session ID: {0} contains a reserved keyword and is regenerating.
- Category:
- HTTP Session
- Cause:
- On Windows 32-bit systems, if the session ID contains a reserved keyword, the file-based persistence fails. This is because it relies upon successful creation of subdirectories. The reserved keywords are: "CON", "PRN", "AUX", "NUL" "COM1", "COM2", "COM3", " COM4", "COM5", "COM6", "COM7", " COM8", "COM9", "LPT1", "LPT2", " LPT3", "LPT4", "LPT5", "LPT6", " LPT7", "LPT8", "LPT9", "CLOCK$"
- Action:
- No action is required. The session ID will be regenerated.
- BEA-100056
- For {0}: The session with ID: {1} was invalidated before the session creation and registration could complete.
- Category:
- HTTP Session
- Cause:
- This is a past-release problem.
- Action:
- Contact My Oracle Support.
- BEA-100057
- This server does not have deployment for the Web application with context path: {0}. The callback: {1} failed while replicating the session. Check the configuration; only uniform configurations in a cluster are supported.
- Category:
- HTTP Session
- Cause:
- WebLogic Server clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers.
- Action:
- Redeploy the Web application, and ensure that it targets the cluster and all members in the cluster.
- BEA-100058
- The PersistentStoreType for the Web application with context path: {0} is not replicated. The callback: {1} failed while replicating the session. Check the configuration; only uniform configurations in a cluster are supported.
- Category:
- HTTP Session
- Cause:
- WebLogic Server clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers with uniform configuration.
- Action:
- Redeploy the Web application, and ensure that it targets the cluster and all members in the cluster. Also, the PersistentStoreType should be set to "replicated" for all cluster members.
- BEA-100059
- An unexpected error occurred while cleaning up sessions during undeployment of Web application: {0}.
- Category:
- HTTP Session
- Cause:
- The trigger failed to clean up the expired session.
- Action:
- Check the exception text for the exact error message. When using JDBC-based HTTP session persistence, ensure that the database is set up properly. For file-based persistence, ensure that the permissions on the storage directory are appropriately set.
- BEA-100060
- An unexpected error occurred while retrieving the session for Web application: {0}.
- Category:
- HTTP Session
- Cause:
- The session from persistent store could not be retrieved.
- Action:
- Check the configuration, and check the exception text for the exact error message. Also, check the WebLogic Server documentation for more details about how to configure session persistence for Web applications.
- BEA-100061
- Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment. This message is logged only once per session.
- Category:
- HTTP Session
- Cause:
- The session.setAttribute(name, value) was invoked with a non-serializable value for memory-based sessions.
- Action:
- If the session data should survive redeployment, ensure that all attributes are serializable. Otherwise, the non-serializable data will be lost upon redeployment.
- BEA-100062
- Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be replicated to the secondary server. This message is logged only once per session.
- Category:
- HTTP Session
- Cause:
- The session.setAttribute(name, value) was invoked with a non-serializable value for a replicated session.
- Action:
- If the session data should survive redeployment and session failovers, ensure that all attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
- BEA-100063
- Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the disk. This message is logged only once per session.
- Category:
- HTTP Session
- Cause:
- The session.setAttribute(name, value) was invoked with a non-serializable value for a file-based persistent session.
- Action:
- If the session data should survive redeployment and session failovers, ensure that all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
- BEA-100064
- Web application: {0} tried to place a non-serializable attribute: {1} into the session: {2}. The attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the database. This message is logged only once per session.
- Category:
- HTTP Session
- Cause:
- The session.setAttribute(name, value) attribute was invoked with a non-serializable value for a JDBC-based persistent session.
- Action:
- If the session data should survive redeployment and session failovers, ensure that all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover and redeployment.
- BEA-100065
- {0}. Failed to remove attributes for HTTP session ID: {1}.
- Category:
- HTTP Session
- Cause:
- An unexpected error occurred during HTTP session invalidation.
- Action:
- Check the error message for the exact cause.
- BEA-100066
- Failed to look up the replicated session object for Web application: {0}, session ID: {1}.
- Category:
- HTTP Session
- Cause:
- The ReplicationManager returned the NotFoundException.
- Action:
- This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front end can cause unnecessary session failovers in the back end, which could result in this error in certain situations. Check the error message for more information.
- BEA-100067
- Failed to look up the secondary information for Web application: {0} session ID: {1}.
- Category:
- HTTP Session
- Cause:
- The ReplicationManager returned the NotFoundException. This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front end can cause unnecessary session failovers in the back end, which could result in this error in certain situations.
- Action:
- Check the error message for more information.
- BEA-100068
- Failed to look up the secondary information for Web application: {0} session ID: {1}.
- Category:
- HTTP Session
- Cause:
- The ReplicationManager failed to look up the secondary information for a valid session.
- Action:
- This is an unexpected error. Check the error message for details.
- BEA-100069
- The getAttribute(): {0} was a HomeHandle, reconstructing the EJBHome.
- Category:
- HTTP Session
- Cause:
- This is an informational message indicating that the container is storing only the handle for the EJBHome placed into the session.
- Action:
- No action is required.
- BEA-100070
- Error reconstructing the EJBHome put into session for name: {0}
- Category:
- HTTP Session
- Cause:
- The container found an EJBHome handle stored in the session. However, it failed to reconstruct the EJBHome using that EJBHome handle.
- Action:
- Ensure that the HomeHandle is still valid. Check the exception text for the exact error message.
- BEA-100071
- The setAttribute(): {0} was an EJBHome, storing the HomeHandle into the session.
- Category:
- HTTP Session
- Cause:
- The container found an EJBHome handle stored in the session. It will reconstruct the EJBHome object before returning.
- Action:
- No action is required.
- BEA-100072
- Error in finding the HomeHandle for the EJBHome: {0}.
- Category:
- HTTP Session
- Cause:
- The container stores only the handle for an EJBHome put into the session. However, in this case, it failed to find the HomeHandle.
- Action:
- Check the RemoteException for the exact error message details.
- BEA-100073
- Exception while serializing session object: {0}.
- Category:
- HTTP Session
- Cause:
- The session object failed to serialize.
- Action:
- Check the exception text for the exact error message details.
- BEA-100079
- WAN failover configuration missing.
- Category:
- HTTP Session
- Cause:
- The JDBCTxDataSource or the backup cluster address was not properly configured.
- Action:
- Set the JDBCTxDataSource or the backup cluster address to store session state.
- BEA-100081
- Persistent store settings cannot be changed between versions. The persistent store settings for application {0} is different from the settings for previous versions.
- Category:
- HTTP Session
- Cause:
- The persistent store settings of the new version were different from previous versions.
- Action:
- Ensure that the persistent store settings are not changed when deploying a new version of an application.
- BEA-100082
- Failed to deploy {0} because the JDBC data source was missing. Target a JDBC data source to the cluster.
- Category:
- HTTP Session
- Cause:
- The configuration was incomplete.
- Action:
- Target a JDBC data source to the cluster. Refer to the cluster documentation for more information.
- BEA-100083
- The Web application: {0} in application: {1} has its PersistenceStoreType set to: {2} for HTTP sessions. However, the target list does not contain all members of cluster: {3}. Non-homogeneous deployment for replicated sessions is not allowed.
- Category:
- HTTP Session
- Cause:
- Non-homogeneous deployment for replicated sessions is not allowed. The target list must be a cluster or a virtual host which is targeted to a cluster.
- Action:
- Fix the targets for this Web application. Specify a cluster or virtual host as the target.
- BEA-100084
- The Web application: {0} in application: {1} has its PersistenceStoreType set to: {2} for HTTP sessions. However, the target list contains virtual host: {3}, for which the target list does not contain all members of cluster: {4}. Non-homogeneous deployment for replicated sessions is not allowed.
- Category:
- HTTP Session
- Cause:
- Non-homogeneous deployment for replicated sessions is not allowed. The target list must be a cluster or a virtual host which is targeted to a cluster.
- Action:
- Fix the targets for this Web application.Specify a cluster or virtual host as the target.
- BEA-100087
- The JDBC session data for session ID: {0} has been modified by another server in the cluster.
- Category:
- HTTP Session
- Cause:
- The front-end Web server failed to maintain server affinity.
- Action:
- Ensure that the front-end Web server or load balancer has been properly configured.
- BEA-100089
- The session ID: {0} has been accessed from {1}, a server that is neither the primary ({2}) nor the secondary ({3}). The request URL was: {4}
- Category:
- HTTP Session
- Cause:
- The most likely cause is a configuration error on a front end hardware loadbalancer or webserver plugin. They should be configured to respect the values of primary/secondary in the cookie (i.e., stickiness), when possible.
- Action:
- Please ensure that the front end webserver or load-balancer has been properly configured.
- BEA-100090
- An unexpected error occurred during a batched update of the last accessed time attribute of the updated sessions in application {0}.
- Category:
- HTTP Session
- Cause:
- Check the exception message for details.
- Action:
- Check the exception message for details.
- BEA-100094
- The session ID: {0} has been accessed from {1}, a server that is not the primary ({2}). The request URL was: {3}.
- Category:
- HTTP Session
- Cause:
- The most likely cause is a configuration error on a front-end hardware load balancer or Web server plug-in. These should be configured to respect the values of the primary or secondary in the cookie (for example, stickiness), when possible.
- Action:
- Ensure that the front-end Web server or load balancer has been properly configured.
- BEA-100095
- persistent-data-source-jndi-name is required for an async-jdbc session.
- Category:
- HTTP Session
- Cause:
- persistent-data-source-jndi-name was not used to specify the data source JNDI name for the JDBC connection, but persistent-store-type is async-jdbc.
- Action:
- Use persistent-data-source-jndi-name to specify the data source JNDI name for the JDBC connection.
- BEA-100096
- persistent-data-source-jndi-name will take effect and persistent-store-pool will be ignored for async-jdbc session in application {0}.
- Category:
- HTTP Session
- Cause:
- This is debug information.
- Action:
- No action is required.
- BEA-100097
- The IDLength {0} is too short. It is not secure. WebLogic Server will increase the length to {1}.
- Category:
- HTTP Session
- Cause:
- The IDLength of Session Descriptor is smaller than {1}.
- Action:
- Mofify the Weblgoic deployment descriptor. Ensure that the IDLength of Session Descriptor is equal to or greater than {1}.
- BEA-100098
- persistent-data-source-jndi-name or persistent-store-pool is required when persistent-store-type is jdbc.
- Category:
- HTTP Session
- Cause:
- persistent-data-source-jndi-name or persistent-store-pool was not used to configure the database connection, but persistent-store-type is jdbc.
- Action:
- Use persistent-data-source-jndi-name or persistent-store-pool to configure the database connection.
- BEA-100099
- An error occurred while looking up the session with ID:{0} from primary server:{1} and secondary server:{2}.
- Category:
- HTTP Session
- Cause:
- A RemoteException occurred when looking up the session from the secondary server.
- Action:
- Check if the secondary server is down. Note that it is not recommended to stop both the primary and secondary server at the same time. Because replication happens lazily, upon request, if the secondary server needs to end, give sufficient time so that the active end users hit their sessions and get replicated.
- BEA-100100
- Replication services could not be found for remote object {1} in application context {0}.
- Category:
- HTTP Session
- Cause:
- This error can occur during clustered application undeployment or redeployment, particularly when the server where it occurs is configured for managed server independent deployment (MSI-D). It is typically transient in those situations, and should only occur during redeployment in those scenarios.
- Action:
- If the error persists, check the server log files for more details. Contact Oracle support if necessary.
- BEA-101002
- [{0}] Could not deserialize the context attribute.
- Category:
- HTTP
- Cause:
- The classloader changed. When this happens, the old attributes are deserialized using the new classloader.
- Action:
- Ensure that the attribute class is available to the Web application scope and is serializable.
- BEA-101003
- [{0}] {1} called with a null document root.
- Category:
- HTTP
- Cause:
- The Web application did not initialize correctly.
- Action:
- Check the log file for error messages about this Web application.
- BEA-101005
- [{0}] {1} called with unsafe path: "{2}".
- Category:
- HTTP
- Cause:
- The virtual path that was passed in points to a resource outside of the Web application scope.
- Action:
- Check the virtual path being passed to the method and rectify the problem accordingly.
- BEA-101008
- [{0}] Cannot get InputStream of resource "{1}".
- Category:
- HTTP
- Cause:
- The getResourceAsStream() method failed to get an InputSteam for the resource.
- Action:
- Ensure that the resource exists.
- BEA-101017
- [{0}] Root cause of ServletException.
- Category:
- HTTP
- Cause:
- The Web application container caught an unexpected exception.
- Action:
- Check the exception for the exact error message.
- BEA-101019
- [{0}] Servlet failed with an IOException.
- Category:
- HTTP
- Cause:
- An unexpected IOException was caught while processing the request.
- Action:
- Check the exception for the exact error message.
- BEA-101020
- [{0}] Servlet failed with an Exception
- Category:
- HTTP
- Cause:
- An unexpected error occurred.
- Action:
- Check the exception for the exact error message.
- BEA-101024
- [{0}] Unsupported error status code for the error-page element in web.xml.
- Category:
- HTTP
- Cause:
- The format of the error status code was invalid.
- Action:
- Check the web.xml and fix the error-page element error status code.
- BEA-101025
- [{0}] Document root is null.
- Category:
- HTTP
- Cause:
- This should never happen. The initialization failed.
- Action:
- Check the log file for error messages during the Web application initialization phase.
- BEA-101027
- [{0}] Document root: "{1}" does not exist.
- Category:
- HTTP
- Cause:
- This is an unexpected error message.
- Action:
- Ensure that the directory exists.
- BEA-101029
- [{0}] cannot make temporary directory "{1}". Will not be able to compile JSPs.
- Category:
- HTTP
- Cause:
- The creation of the temporary directory failed.
- Action:
- Check the write permissions.
- BEA-101040
- [{0}] Error occurred while trying to set "{1}{2}".
- Category:
- HTTP
- Cause:
- A NumberFormatException occurred while parsing the value assigned to the reloadCheckSecs parameter in web.xml.
- Action:
- Ensure that the value was entered correctly.
- BEA-101045
- [{0}] {1}
- Category:
- HTTP
- Cause:
- This is a general purpose error message.
- Action:
- Check the message for the exact cause and take proper action.
- BEA-101046
- [{0}] {1}
- Category:
- HTTP
- Cause:
- This is a general purpose error message.
- Action:
- Check the exception for exact cause and take proper action.
- BEA-101047
- [{0}] {1}
- Category:
- HTTP
- Cause:
- This is a general purpose informational message for debug purposes only.
- Action:
- This is a debug message. No action is required.
- BEA-101051
- [{0}] started
- Category:
- HTTP
- Cause:
- This is an informational message indicating that the Web server has been started.
- Action:
- This is a debug message. No action is required.
- BEA-101052
- [{0}] Initialized
- Category:
- HTTP
- Cause:
- This is an informational message indicating that the Web server has been initialized.
- Action:
- This is a debug message. No action is required.
- BEA-101053
- [{0}] Loading Web application: {1}
- Category:
- HTTP
- Cause:
- The Web application is being deployed.
- Action:
- This is a debug message. No action is required.
- BEA-101054
- [{0}] {1} is the default Web application for {2}.
- Category:
- HTTP
- Cause:
- The given Web application is being registered as a default Web application.
- Action:
- This is a debug message. No action is required.
- BEA-101060
- [{0}] Loading "{1}" from directory: "{2}"
- Category:
- HTTP
- Cause:
- The Web application was deployed using an exploded directory structure.
- Action:
- This is a debug message. No action is required.
- BEA-101061
- [{0}] Could not find Web application "{1}".
- Category:
- HTTP
- Cause:
- The descriptor for the Web application with the name given could not be loaded.
- Action:
- Check the error message for details and ensure that the Web application was configured properly.
- BEA-101062
- [{0}] Error reading Web application "{1}".
- Category:
- HTTP
- Cause:
- An IOException occurred while reading the descriptors for the Web application.
- Action:
- Ensure that the web.xml and weblogic.xml descriptors exist in the right place.
- BEA-101064
- [{0}] Error parsing descriptor in Web appplication "{1}"
- Category:
- HTTP
- Cause:
- An unexpected error occurred while reading the descriptors for the Web application.
- Action:
- Ensure that web.xml and weblogic.xml exist in the right place
- BEA-101066
- [{0}] Cannot initialize HTTP URL resources. Could not get JNDI context: {1}.
- Category:
- HTTP
- Cause:
- The URL contexts could not be registered because the JNDI context was not found.
- Action:
- Ensure that the JNDI resources were properly configured.
- BEA-101067
- [{0}] Disregarding null URL resource value for property {1}
- Category:
- HTTP
- Cause:
- The URL for the JNDI resource specified in URLResource was null.
- Action:
- Correct the configuration (WebServerMBean). The URLs cannot be null.
- BEA-101068
- [{0}] Could not parse URL resource value {1}.
- Category:
- HTTP
- Cause:
- The URL for the JNDI resource specified in the URL resource was malformed.
- Action:
- Correct the configuration (WebServerMBean). Specify a valid URL.
- BEA-101069
- [{0}] Could not bind URL {1} to JNDI name {2} error message: {3}.
- Category:
- HTTP
- Cause:
- The URL failed to bind with the JNDI name.
- Action:
- Correct the configuration (WebServerMBean).
- BEA-101070
- [{0}] Bound URL resource "{1}" to JNDI name "{2}".
- Category:
- HTTP
- Cause:
- This is an informational message only.
- Action:
- No action is required.
- BEA-101075
- [{0}] HttpServer is shutting down.
- Category:
- HTTP
- Cause:
- The Web server is shutting down.
- Action:
- This is a debug message. No action is required.
- BEA-101083
- Connection failure.
- Category:
- HTTP
- Cause:
- The connection failed while writing data into the stream.
- Action:
- Check the exception for the exact cause and take appropriate action.
- BEA-101086
- No host in HTTP header. Dispatching to default HTTP server.
- Category:
- HTTP
- Cause:
- Host header missing.
- Action:
- Ensure that the requests are accompanied with a host header in order for virtual hosting to work. Also, proper HTTP redirects must have a host header.
- BEA-101087
- {0} is not a virtual host. Dispatching to default HTTP server.
- Category:
- HTTP
- Cause:
- The host header is missing from the HTTP request.
- Action:
- Make sure the requests are accompanied with a host header in order for Virtual Hosting to work. Also, proper HTTP redirects must have a host header.
- BEA-101088
- Dispatching request to {0}.
- Category:
- HTTP
- Cause:
- Dispatching the request to the Web server (Virtual Host) defined by the host header.
- Action:
- Check the configuration.
- BEA-101093
- A problem occurred while dispatching the servlet request.
- Category:
- HTTP
- Cause:
- The request could not be dispatched into the execute queue.
- Action:
- The request could be malformed. Check the exception for the exact cause.
- BEA-101095
- POST time exceeded the configured MaxPostTimeSecs of {0,number}.
- Category:
- HTTP
- Cause:
- The parameter makes sure that a malicious user does not send slow POSTs to cause a denial of service attack.
- Action:
- If you think the time was too short, try increasing the value of MaxPostTimeSecs using the Administration Console.
- BEA-101096
- POST size exceeded the MaxPostSize={0,number}.
- Category:
- HTTP
- Cause:
- The parameter makes sure that a malicious user does not send huge POSTs to cause a denial of service attack.
- Action:
- If you think the post size is unreasonable, try increasing MaxPostSize using the Administration Console.
- BEA-101100
- [{0}] Got bad cookie header: {1} from User-Agent: {2}
- Category:
- HTTP
- Cause:
- A cookie was malformed.
- Action:
- Refer to the cookie specifications for the correct format: http://www.ietf.org/rfc/rfc2965.txt (Oct 2000; Obsoletes: 2109) http://www.ietf.org/rfc/rfc2109.txt (Feb 1997) http://www.ietf.org/rfc/rfc2616.txt (Jun 1999; Obsoletes: 2068) http://www.ietf.org/rfc/rfc2068.txt (Jan 1997)
- BEA-101101
- [{0}] Unable to create new session.
- Category:
- HTTP
- Cause:
- A new session could not be created.
- Action:
- Ensure that the persistent store has been properly configured.
- BEA-101104
- Servlet execution in servlet context "{0}" failed, {1}.
- Category:
- HTTP
- Cause:
- An unexpected error occurred while serving the request. This is not a simple client connection reset error.
- Action:
- Check the error message for the exact cause.
- BEA-101105
- [{0}] error-page location: "{1}" for the error-code: "{2,number}" does not exist. Serving the default error page.
- Category:
- HTTP
- Cause:
- The error-page you configured in web.xml does not exist. A configuration error has occurred.
- Action:
- Correct the web.xml descriptor, or make the resource available.
- BEA-101106
- [{0}] Could not serve custom error page: "{1}" for the error code: "{2,number}"
- Category:
- HTTP
- Cause:
- The error-page configured in web.xml does not exist. A configuration error has occurred.
- Action:
- Correct the web.xml descriptor or make the resource available.
- BEA-101107
- [{0}] Problem occurred while serving the error page.
- Category:
- HTTP
- Cause:
- The error-page configured in web.xml could not be served.
- Action:
- Check the configuration in web.xml.
- BEA-101108
- [{0}] Unsupported encoding: "{1}" specified.
- Category:
- HTTP
- Cause:
- The specified encoding is not supported by the underlying virtual machine(VM).
- Action:
- Ensure that the specified encoding is valid or install the additional encoding classes.
- BEA-101122
- [{0}] Servlet: "{1}" is permanently unavailable.
- Category:
- HTTP
- Cause:
- The Web application is not currently available.
- Action:
- Ensure that the Web application has been deactivated. Check to see if redeployment is in progress.
- BEA-101123
- [{0}] Servlet: "{1}" will be unavailable for the next: "{2,number}" seconds.
- Category:
- HTTP
- Cause:
- The servlet has been marked as unavailable.
- Action:
- Make the request again after the specified time.
- BEA-101125
- [{0}] Error occurred while instantiating servlet: "{1}".
- Category:
- HTTP
- Cause:
- The servlet failed to instantiate.
- Action:
- Ensure that the servlet has been configured properly in web.xml. Also, check the exception for the exact cause.
- BEA-101126
- [{0}] Error casting servlet: "{1}" to javax.servlet.Servlet
- Category:
- HTTP
- Cause:
- The servlet class that has been configured does not implement javax.servlet.Servlet.
- Action:
- Fix the definition of the class.
- BEA-101128
- Initializing HTTP services.
- Category:
- HTTP
- Cause:
- This is an informational message.
- Action:
- Ensure that the resources are available now.
- BEA-101129
- Initializing the Web application container.
- Category:
- HTTP
- Cause:
- This is an informational message.
- Action:
- This is an informational message. No action is required.
- BEA-101133
- Initializing Web server {0}.
- Category:
- HTTP
- Cause:
- The Web server was just initialized.
- Action:
- No action is required.
- BEA-101135
- {0} is the default Web server.
- Category:
- HTTP
- Cause:
- The default Web server name is being logged.
- Action:
- This is an informational message for debug purposes only. No action is required.
- BEA-101136
- Registering virtual host: {0}.
- Category:
- HTTP
- Cause:
- A Virtual Host (non-default Web server) has been registered.
- Action:
- This is an informational message for debug purposes only. No action is required.
- BEA-101138
- {0} One of the getParameter family of methods was called after reading from the ServletInputStream. Not merging post parameters.
- Category:
- HTTP
- Cause:
- If the servlet reads the data from the input stream directly, then the request data will not be available for the getParameter family of methods.
- Action:
- If the code relies on post parameters being available through the getParameter method, fix the code.
- BEA-101140
- An error occurred while creating servlet {1} (class: {2}, initArgs: {3}) for Web application {0}.
- Category:
- HTTP
- Cause:
- The servlet instance failed to initialize.
- Action:
- Check the configuration and the exception for the exact error message.
- BEA-101142
- There was an error unregistering servlet runtime {0}.
- Category:
- HTTP
- Cause:
- The servlet runtime MBean that is used for monitoring could not be destroyed.
- Action:
- Report this problem to My Oracle Support.
- BEA-101143
- An error occurred while unregistering Web application component runtime {0}.
- Category:
- HTTP
- Cause:
- The Web application runtime MBean that is used for monitoring could not be destroyed.
- Action:
- Report this problem to My Oracle Support.
- BEA-101159
- [{0}] Received IllegalAccessException while instantiating servlet: "{1}". Ensure that the servlet implementation is a public class.
- Category:
- HTTP
- Cause:
- This occurs if WebLogic Server attempts to instantiate a servlet class that is not declared public.
- Action:
- Ensure that the servlet implementation is a public class.
- BEA-101160
- Deployment descriptor is malformed; check against the DTD: {0}.
- Category:
- HTTP
- Cause:
- The web.xml file is not in strict conformance to the DTD. There may be deployment problems if this is not corrected.
- Action:
- Check the web.xml file against the DTD to ensure conformance. Remember that the ordering of elements is important.
- BEA-101162
- User defined listener {0} failed: {1}.
- Category:
- HTTP
- Cause:
- The listener failed while processing the event fired by the container.
- Action:
- Check the exception for the exact error message and fix the listener code.
- BEA-101163
- Could not load user defined listener: {0}
- Category:
- HTTP
- Cause:
- The listener class could not be loaded or instantiated.
- Action:
- Check the exception for the exact error message and fix the listener code.
- BEA-101164
- User defined class {0} is not a listener, as it does not implement the correct interface(s).
- Category:
- HTTP
- Cause:
- The class is invalid.
- Action:
- Fix the listener code to implement the appropriate interfaces.
- BEA-101165
- Could not load user defined filter in web.xml: {0}.
- Category:
- HTTP
- Cause:
- The filter class could not be loaded.
- Action:
- Check the configuration and ensure that the class is available to the context classloader.
- BEA-101168
- The security-role-assignment references an invalid security-role: {0}.
- Category:
- HTTP
- Cause:
- The security-role-assignment specified in weblogic.xml is not valid.
- Action:
- Ensure that the role-name defined in web.xml is valid. Also, check the DTD and examples for the correct syntax.
- BEA-101169
- The servlet {0} is referenced but not defined in web.xml.
- Category:
- HTTP
- Cause:
- The servlet-mapping element in web.xml refers to a servlet name that was not defined.
- Action:
- Ensure that the servlet-name that is used for the mapping is defined. Check the DTD for the correct syntax.
- BEA-101170
- The servlet {0} is referenced in servlet-mapping {1} but not defined in web.xml.
- Category:
- HTTP
- Cause:
- The servlet-mapping element in web.xml refers to a servlet name that was not defined.
- Action:
- Ensure that the servlet-name that is used for the mapping is defined. Check the DTD for the correct syntax.
- BEA-101171
- The web.xml descriptor has no resource-ref entries for the reference-descriptor defined in weblogic.xml.
- Category:
- HTTP
- Cause:
- The resource-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.
- Action:
- Ensure that the resource-ref-name matches a resource-ref-name defined in web.xml.
- BEA-101172
- The web.xml descriptor has no ejb-ref entries.
- Category:
- HTTP
- Cause:
- The ejb-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.
- Action:
- Ensure that the ejb-ref-name matches a ejb-ref-name defined in web.xml.
- BEA-101173
- Did not find resource-ref in web.xml matching {0}.
- Category:
- HTTP
- Cause:
- The resource-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.
- Action:
- Ensure that the resource-ref-name matches a resource-ref-name defined in web.xml.
- BEA-101174
- Did not find ejb-ref in web.xml matching {0}.
- Category:
- HTTP
- Cause:
- The ejb-ref-name referred to by the reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.
- Action:
- Ensure that the ejb-ref-name matches a ejb-ref-name defined in web.xml.
- BEA-101175
- [{0}] Exception occurred while closing zip file {1}.
- Category:
- HTTP
- Cause:
- A zip file failed to close while undeploying a Web application.
- Action:
- Report this problem to My Oracle Support.
- BEA-101180
- The auth-constraint references security-role: {0}, which is not defined in web.xml.
- Category:
- HTTP
- Cause:
- The auth-constraint should refer to roles that have been defined in web.xml.
- Action:
- Add the definition of this role in the security-role element of web.xml.
- BEA-101188
- A bad exception-type exists in web.xml: {0}.
- Category:
- HTTP
- Cause:
- An invalid class can cause this exception while registering the Web application.
- Action:
- Check the classpath.
- BEA-101189
- Could not load the url-match-map class defined in weblogic.xml: {0}.
- Category:
- HTTP
- Cause:
- An invalid classname will cause this exception while registering the Web application.
- Action:
- Check the classpath.
- BEA-101194
- The preprocessor {0} is referenced but not defined in weblogic.xml.
- Category:
- HTTP
- Cause:
- The preprocessor element is not defined in weblogic.xml.
- Action:
- Check the weblogic.xml descriptor.
- BEA-101196
- [{0}]: Error while parsing the Tag Library Descriptor at "{1}".
- Category:
- HTTP
- Cause:
- A TLD parsing exception occurred.
- Action:
- Check the exception for the exact cause.
- BEA-101198
- Could not deploy role: {0} for Web application: {1} application: {2}.
- Category:
- HTTP
- Cause:
- The Web application could not deploy the role defined in web.xml.
- Action:
- Ensure that security is configured properly in the server. Also, check the stack trace for the exact cause.
- BEA-101199
- Could not deploy policy for resource: {0}.
- Category:
- HTTP
- Cause:
- The Web application failed to deploy the policy for the security-constraint defined in web.xml.
- Action:
- Ensure that security is configured properly in the server. Also, check the stack trace for the exact cause.
- BEA-101200
- CacheFilter not caching the response for URI: {0} reason: {1}
- Category:
- HTTP
- Cause:
- The CacheFilter does not cache responses unless the status is 200.
- Action:
- Check the message for information on how to fix the problem.
- BEA-101212
- {0}:{1} Failure while precompiling JSPs: {2}.
- Category:
- HTTP
- Cause:
- The JSPs failed to precompile at startup.
- Action:
- Check the exception for the exact cause.
- BEA-101214
- Included resource or file "{0}" not found from requested resource "{1}".
- Category:
- HTTP
- Cause:
- The included resource or file is missing.
- Action:
- Add the missing resource or file.
- BEA-101215
- Malformed request "{0}". Request parsing failed, Code: {1}
- Category:
- HTTP
- Cause:
- The request does not follow the pattern specified by the HTTP 1.0/1.1 specification(s).
- Action:
- Fix the client that sent the invalid request.
- BEA-101216
- Servlet: "{0}" failed to preload on startup in Web application: "{1}".
- Category:
- HTTP
- Cause:
- The servlet that was marked as load-on-startup failed to preload on startup.
- Action:
- Check the exception for the exact cause.
- BEA-101217
- Cannot deploy {0} from {1} on {2}, because there is already a Web application named {3} loaded from {4}, using the context path {5}.
- Category:
- HTTP
- Cause:
- The Web application that is being deployed has been assigned a context path that is already in use.
- Action:
- Choose a different context path.
- BEA-101218
- An error exists in web.xml for servlet "{0}". Neither servlet-class nor jsp-file is defined.
- Category:
- HTTP
- Cause:
- The servlet element should contain either servlet-class or jsp-file. Both are missing.
- Action:
- Update the web.xml descriptor.
- BEA-101220
- An error occurred while setting the document root for "{0}" to "{1}".
- Category:
- HTTP
- Cause:
- Setting the document root for the Web application failed. The Web application will not be deployed.
- Action:
- Check the IOException message for exact cause of the problem.
- BEA-101221
- The url-pattern is empty or null for url-pattern {0} in {1}.
- Category:
- HTTP
- Cause:
- Not a valid url-pattern for the servlet.
- Action:
- If the servlet is intended to be a default servlet, then specify / or /*.
- BEA-101223
- {0}: The server {1} is temporarily suspended.
- Category:
- HTTP
- Cause:
- The server has been suspended by the administrator.
- Action:
- Wait until it comes back up again.
- BEA-101226
- AuthFilter: {0} invocation failed in: {1} phase for URI: {2}
- Category:
- HTTP
- Cause:
- The authentication filter that acts before and after the authentication phase failed to execute.
- Action:
- Check the exception for the exact cause of the problem.
- BEA-101228
- Failed to undeploy security policy for resource: {0} while undeploying Web application.
- Category:
- HTTP
- Cause:
- The security policy defined in web.xml failed to undeploy upon Web application undeployment.
- Action:
- Check the exception for the exact cause of the problem.
- BEA-101229
- Failed to undeploy security policy for resource: {0} while undeploying the Web application.
- Category:
- HTTP
- Cause:
- The security role defined in web.xml failed to undeploy upon Web application undeployment.
- Action:
- Check the exception for the exact cause of the problem.
- BEA-101231
- The HTTP log file does not use version 1.0 of the Extended Log File format.
- Category:
- HTTP
- Cause:
- The ELF headers in the existing log file specify a version other than 1.0.
- Action:
- Only version 1.0 is supported. Delete the existing log file and start over again.
- BEA-101232
- An exception occurred while reading headers of HTTP log file.
- Category:
- HTTP
- Cause:
- An IOException was received while reading the headers.
- Action:
- Check the exception for the exact cause of the problem.
- BEA-101234
- Attempting to initialize ExtendedLogFormat application specific header: {0}. However, initialization failed due to an exception.
- Category:
- HTTP
- Cause:
- An unexpected error occurred while initializing the log file format.
- Action:
- Check the exception for the exact error message.
- BEA-101235
- Attempting to initialize ExtendedLogFormat application specific header: {0}. However, initialization failed because class: {1} is not an instance of weblogic.servlet.logging.CustomELFLogger.
- Category:
- HTTP
- Cause:
- An unexpected error occurred while initializing the ExtendedLogFormat.
- Action:
- Check the exception for the exact error message.
- BEA-101236
- The format of log field {0} is incorrect.
- Category:
- HTTP
- Cause:
- The format of the log field is invalid.
- Action:
- Check the log field and fix the format.
- BEA-101237
- HTTP logging has been disabled for the Web server: {0}.
- Category:
- HTTP
- Cause:
- This is a debug message.
- Action:
- No action is required.
- BEA-101242
- Failed to roll the HTTP log file for the Web server: {0}.
- Category:
- HTTP
- Cause:
- An unexpected error occurred.
- Action:
- Check the exception message for the exact cause.
- BEA-101247
- {0}: Public ID references the old version of the Servlet DTD. Change the public ID in web.xml file to "{1}".
- Category:
- HTTP
- Cause:
- The public ID in WEB-INF/web.xml references the old version of servlet DTD.
- Action:
- Generally, this will not cause any problems with the application unless the DTD has changed in a way such that the web.xml cannot be parsed. To avoid the message, change the public ID in the web.xml file to the current version of the servlet DTD.
- BEA-101248
- [{0}]: Deployment descriptor "{1}" is malformed. Check against the DTD: {4} (line {2}, column {3}).
- Category:
- HTTP
- Cause:
- The descriptor file is not in strict conformance to its DTD. There may be deployment problems if this is not corrected.
- Action:
- Check the descriptor file against the DTD to ensure conformance. Remember that the ordering of elements is important.
- BEA-101249
- [{0}]: Servlet class {2} for servlet {1} could not be loaded because the requested class was not found in the classpath {3}. {4}.
- Category:
- HTTP
- Cause:
- The servlet class was not recognized by the Web application classloader.
- Action:
- Ensure that the servlet class is available either in WEB-INF/classes or WEB-INF/lib or the system classpath.
- BEA-101250
- [{0}]: Servlet class {2} for servlet {1} could not be loaded because a class on which it depends was not found in the classpath {3}. {4}.
- Category:
- HTTP
- Cause:
- One of the classes the servlet class uses was not recognized by the Web application classloader.
- Action:
- Make sure the class is available either in WEB-INF/classes or WEB-INF/lib or system classpath.
- BEA-101251
- [{0}]: Could not load servlet class {2} for servlet {1} because a resource on which it depends was not found in the classpath {3}. {4}.
- Category:
- HTTP
- Cause:
- This exception occurs if the Java Virtual Machine (JVM) cannot find an appropriate native-language definition of a method that is declared native.
- Action:
- This could be due to a problem with path/LD_LIBRARY_PATH. Check if the resource it complains about exists.
- BEA-101252
- [{0}]: Servlet class {2} for servlet {1} could not be verified. {3}.
- Category:
- HTTP
- Cause:
- This exception occurs when the "verifier" detects that a class file, though well formed, contains some sort of internal inconsistency or security problem.
- Action:
- Verify the servlet class.
- BEA-101253
- [{0}]: Servlet class {2} for servlet {1} could not be defined. The class file could be corrupt. {3}.
- Category:
- HTTP
- Cause:
- This exception occurs when the Java Virtual Machine (JVM) attempts to read a class file and determines that the file is malformed or otherwise cannot be interpreted as a class file.
- Action:
- Check to see if the class file is corrupt.
- BEA-101254
- [{0}]: Servlet class {2} for servlet {1} could not be handled by the classloader with classpath {3}. {4}.
- Category:
- HTTP
- Cause:
- Subclasses of LinkageError indicate that a class has some dependency on another class; however, the latter class has incompatibly changed after the compilation of the former class.
- Action:
- Check the class and its dependencies.
- BEA-101256
- The run-as user: {0} for the servlet: {1} for Web application: {2} could not be resolved to a valid user in the system. Verify that the user exists.
- Category:
- HTTP
- Cause:
- The run-as element in weblogic.xml refers to an invalid user.
- Action:
- Check to see if the user exists.
- BEA-101257
- Failed to parse the client certificate in header: {0}. Ignoring this certificate.
- Category:
- HTTP
- Cause:
- The format of the client certificate was invalid.
- Action:
- Check the exception for more details.
- BEA-101258
- Invalid JSP parameter in weblogic.xml with name: {0}.
- Category:
- HTTP
- Cause:
- The JSP parameter was not recognized.
- Action:
- Check the weblogic.xml descriptor and refer to the DTD for the correct syntax and element information.
- BEA-101260
- The JSP parameter name in weblogic.xml is empty.
- Category:
- HTTP
- Cause:
- One of the mandatory elements in weblogic.xml was found to be empty.
- Action:
- Check the weblogic.xml descriptor.
- BEA-101261
- Invalid session parameter name in weblogic.xml: {0}.
- Category:
- HTTP
- Cause:
- One of the session parameters configured in weblogic.xml was invalid.
- Action:
- Check the weblogic.xml and correct the session parameter.
- BEA-101262
- The session parameter name "{0}" in weblogic.xml is deprecated.
- Category:
- HTTP
- Cause:
- This parameter has been deprecated.
- Action:
- See the WebLogic Server documentation for an alternative. This parameter might be removed from future releases.
- BEA-101263
- The session parameter name in weblogic.xml is empty.
- Category:
- HTTP
- Cause:
- The param-name element is a mandatory element.
- Action:
- Check the weblogic.xml descriptor.
- BEA-101264
- {0}: CLIENT-CERT-based authentication failed.
- Category:
- HTTP
- Cause:
- Authentication failed.
- Action:
- Either the certificate was missing or the user the certificate resolves to is not a valid user in the system.
- BEA-101267
- Failed while destroying filter: {0}.
- Category:
- HTTP
- Cause:
- Destroying the filter on the Web application undeploy failed.
- Action:
- There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
- BEA-101268
- {0}: Failed while destroying servlet: {1}.
- Category:
- HTTP
- Cause:
- Destroying a servlet on the Web application undeploy failed.
- Action:
- There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
- BEA-101271
- The url-pattern element is not specified for the web-resource-collection/web-resource-name: {0} in the web.xml descriptor.
- Category:
- HTTP
- Cause:
- The url-pattern element is a mandatory element.
- Action:
- If you want the security constraint to apply for all requests, specify url-pattern=/*.
- BEA-101275
- Server has detected non-replicated sessions while SUSPENDING. Server will wait for non-replicated sessions to either become invalidated or timed out or will wait until a secondary is chosen using the lazy process (meaning if a session does not have a secondary, the server waits until the next request to create the secondary). The current timeout value is {0} seconds. To terminate non-replicated sessions immediately, use the FORCESHUTDOWN option.
- Category:
- HTTP
- Cause:
- During graceful shutdown, the server waits for inflight work to complete. This includes non-replicated sessions.
- Action:
- No action is required. Use FORCESHUTDOWN to ignore inflight work and force shutdown of the server.
- BEA-101276
- Web application(s) {1} still have non-replicated sessions after {0} minutes of initiating SUSPEND. Waiting for non-replicated sessions to finish.
- Category:
- HTTP
- Cause:
- The server is waiting for sessions to finish before gracefully shutting down.
- Action:
- No action is required. Use FORCESHUTDOWN to ignore inflight work and shutdown the server.
- BEA-101277
- Web application(s) {0} has {1} non-replicated session(s) respectively.
- Category:
- HTTP
- Cause:
- The server has detected non-replicated sessions while gracefully shutting down.
- Action:
- No action is required. Use FORCESHUTDOWN to ignore inflight work and shut down the server.
- BEA-101278
- There are no active sessions. The Web service is ready to suspend.
- Category:
- HTTP
- Cause:
- All active sessions have completed. The Web service is ready to gracefully shut down.
- Action:
- No action is required.
- BEA-101280
- Failed to create WebServerRuntimeMBean for the Web server: {0}.
- Category:
- HTTP
- Cause:
- The Web server creates a runtime MBean during the initialization phase for monitoring.
- Action:
- Check the exception for the exact cause.
- BEA-101282
- {0}: jspServlet "{1}" defined in weblogic.xml could not be registered. It should be a subclass of javax.servlet.http.HttpServlet.
- Category:
- HTTP
- Cause:
- The user-defined class should be a subclass of javax.servlet.http.HttpServlet.
- Action:
- The jspServlet class must be a subclass of javax.servlet.http.HttpServlet.
- BEA-101283
- {0}: jspServlet "{1}" defined in weblogic.xml could not be loaded.
- Category:
- HTTP
- Cause:
- The user-defined class was unable to load.
- Action:
- Ensure that the class appears in the webapp-classpath.
- BEA-101287
- {0}. The servlet: {1} received an exception during servlet destroy. Ensure that the super.init(config) is called in the init() method.
- Category:
- HTTP
- Cause:
- This is due to a bug in javax.servlet.GenericServlet.
- Action:
- Ensure that the super.init(config) is called in the init() method for the servlet.
- BEA-101288
- Application:{0} WebAppModule: {1} failed to set contextPath: {2}.
- Category:
- HTTP
- Cause:
- The set context path call failed for the MBean.
- Action:
- Check that the context path assigned to this Web application module is valid.
- BEA-101291
- The webAppModule: {1} in application: {0} is unable to reload classes because it shares a classloader with other modules.
- Category:
- HTTP
- Cause:
- An attempt to reload a class was made when the classloader was shared by other modules.
- Action:
- Ensure that the module has its own classloader or reload all modules that share the classloader at once.
- BEA-101292
- Validation failed for the descriptor: {0} param: {1}.
- Category:
- HTTP
- Cause:
- The container found an illegal value assigned to this parameter.
- Action:
- Check the error message for the exact cause.
- BEA-101295
- Recompiling JSP [{0}], resource [{1}], because it is stale. It was previously compiled using a different version of WebLogic Server. JSP build version: {2} WebLogic Server build version: {3}.
- Category:
- HTTP
- Cause:
- A JSP was compiled using a different version of WebLogic Server or JSPC.
- Action:
- To precompile JSPs, ensure that you precompile them using the same version, service pack, rolling patches, and temporary-patches in your classpath for WebLogic Server or JSPC. This will ensure the same version string and compatibility at runtime.
- BEA-101296
- Unable to load the default compiler class "{0}". Using the default javac compiler to compile JSPs.
- Category:
- HTTP
- Cause:
- The compiler class was not found and hence could not be loaded.
- Action:
- Ensure that the class exists in the classpath.
- BEA-101297
- The value assigned to the container-descriptor parameter: index-directory-sort-by in weblogic.xml is invalid: {0}. The valid values are "NAME", "LAST_MODIFIED", or "SIZE".
- Category:
- HTTP
- Cause:
- An invalid value is specified in weblogic.xml for the container-descriptor parameter: index-directory-sort-by.
- Action:
- Fix the values in the weblogic.xml descriptor. Valid values are "NAME", "LAST_MODIFIED", or "SIZE".
- BEA-101299
- The servlet-mapping for servlet-name "{0}" will override the default mapping for *.jsp. This can lead to a show code vulnerability.
- Category:
- HTTP
- Cause:
- The url-pattern *.jsp is being overriden in the web.xml by a user-defined servlet.
- Action:
- Since the default JSP servlet will be overriden, care must be taken to ensure that JSP source code does not appear directly on the browser.
- BEA-101302
- Web application: {0}, the {1} role: {2} defined in the descriptor: {3} has not been mapped to a principal name in weblogic.xml. Will use the first principal-name: {4} specified in security-role-assignment as the run-as-identity. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
- Category:
- HTTP
- Cause:
- No mapping was found for the run-as role in weblogic.xml.
- Action:
- Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
- BEA-101303
- Web application: {0}, the {1} role: {2} defined in the descriptor: {3} has not been mapped to a principal name in weblogic.xml. Also there is no security-role-assignment defined for this role. Will use the rolename itself as a principal-name for {1} for the servlet. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
- Category:
- HTTP
- Cause:
- No mapping was found for the run-as role in weblogic.xml.
- Action:
- Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either the run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
- BEA-101304
- Web application: {0}, the {1}: {3} defined in web.xml {2} not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.
- Category:
- HTTP
- Cause:
- Did not find a mapping for the roles which were supposed to be mapped to a principal in security-role-assignment in weblogic.xml.
- Action:
- Since the server has decided to use the implicit map, ensure that this is the principal-name you intended to use.
- BEA-101305
- [{0}] Error-page location: "{1}" for the error code: "{2,number}" causes an infinite loop condition as it throws the same code for which it has been mapped.
- Category:
- HTTP
- Cause:
- The servlet for the error-page, which maps to the given error code, throws the same error code. This causes an infinite loop condition.
- Action:
- Fix the error page.
- BEA-101306
- Could not resolve entity "{0}" for the webapp at: "{1}". Check the DTD reference in the corresponding descriptor (web.xml/weblogic.xml).
- Category:
- HTTP
- Cause:
- The descriptor validation failed.
- Action:
- Check the DTD and ensure that the descriptors comply with that. Check the exception message for more details. Also, ensure that there are no typos in the DOCTYPE header.
- BEA-101307
- Got an error while resolving entity "{0}" for the Web application at: "{1}". Check the DTD reference in the corresponding descriptor (web.xml/weblogic.xml).
- Category:
- HTTP
- Cause:
- The descriptor validation failed.
- Action:
- Check the DTD and ensure that the descriptors comply with that. Check the exception message for more details. Also, ensure that there are no typos in the DOCTYPE header.
- BEA-101310
- Web server: {0}, failed to perform batched update for replicated sessions against jndiname: {1} on the secondary server: {2} http-port: {3} https-port: {4}
- Category:
- HTTP
- Cause:
- The Remote Management Interface (RMI) call from the trigger, which was intended to periodically update the read-only replicated sessions on the secondary server, failed.
- Action:
- Check the exception for the exact cause.
- BEA-101317
- The Web application: {0} has specified DIGEST as the auth-method in web.xml, which is not implemented. Will default to BASIC.
- Category:
- HTTP
- Cause:
- DIGEST authentication is not yet implemented. The Web application will fallback to BASIC authentication.
- Action:
- Choose either BASIC, FORM, or CLIENT-CERT.
- BEA-101318
- The Web application: {0} has specified: {1} as the auth-method in web.xml, which is not valid. Valid values are BASIC (default), FORM, and CLIENT-CERT.
- Category:
- HTTP
- Cause:
- An invalid authentication method was specified in web.xml.
- Action:
- The valid values are BASIC, FORM, and CLIENT-CERT. Fix the web.xml file for the Web application.
- BEA-101319
- The Web application: {0} has "FORM" based authentication specified but the mandatory element: {1} is left blank.
- Category:
- HTTP
- Cause:
- The form-login-page and form-error-page are mandatory elements when auth-method is "FORM."
- Action:
- Fix the web.xml for the specified Web application.
- BEA-101325
- The local-path: {1} specified for the virtual-directory-mapping specified in weblogic.xml for the Web application: {0} (docroot={2}), is not valid.
- Category:
- HTTP
- Cause:
- A relative path was possibly assigned to the local-path. If so, the container makes the path relative to the document root.
- Action:
- Ensure that the relative path exists with respect to the document root.
- BEA-101326
- The element: {1} contains an undefined security-role: {0}
- Category:
- HTTP
- Cause:
- The security-role definition is mandatory.
- Action:
- Ensure that the security role-name is defined in web.xml. Also check the DTD and examples for the correct syntax.
- BEA-101327
- The element: {0} is not allowed to appear more than once in the descriptor: {1}
- Category:
- HTTP
- Cause:
- The parser found more than one occurrence for the element.
- Action:
- Ensure that than the element appears only once (check the schema).
- BEA-101328
- {0}: invalid dispatcher: {2} for filter-mapping: {1}
- Category:
- HTTP
- Cause:
- An invalid value was found for the filter mapping dispatcher.
- Action:
- Valid values are: "REQUEST," "FORWARD," "INCLUDE," or "ERROR."
- BEA-101331
- Cannot deploy {0} from {1} on {2}, because there is already a non-versioned Web application named {3} loaded from {4}, using the context path {5}.
- Category:
- HTTP
- Cause:
- The Web application version that is being deployed has been assigned a context path that is already in use by a non-versioned Web application.
- Action:
- Choose a different context path or undeploy the conflicting Web application.
- BEA-101332
- Failed to register JACC policy context handlers for the Web application container.
- Category:
- HTTP
- Cause:
- This is an unexpected error.
- Action:
- See the error message for more information.
- BEA-101337
- Received a SecurityException during: {0}, for : {1}, Web application: {2}
- Category:
- HTTP
- Cause:
- The user does not have enough privileges.
- Action:
- See the error message for more information.
- BEA-101338
- The context parameter "weblogic.httpd.defaultServlet" has been deprecated. Instead, use the servletMapping = "/" to define the default servlet.
- Category:
- HTTP
- Cause:
- A deprecated context parameter was used.
- Action:
- The servlet weblogic.servlet.FileServlet is the default servlet. If you want to override the default, define a new servlet-mapping in web.xml with url-pattern = "/".
- BEA-101339
- The context parameter: {0} has been deprecated. Instead, use the element: {1} in weblogic.xml.
- Category:
- HTTP
- Cause:
- A deprecated context parameter was used.
- Action:
- Replace it with the suggested alternative in weblogic.xml.
- BEA-101340
- The context parameter "weblogic.httpd.servlet.classpath" has been deprecated. Instead use manifest classpath or WEB-INF/lib or WEB-INF/classes or virtual-directories in weblogic.xml
- Category:
- HTTP
- Cause:
- A deprecated context parameter was used.
- Action:
- There are better ways to extend the classpath exposed to the Web application classloader, including virtual-directories and a manifest classpath.
- BEA-101341
- {0}: Class file up-to-date for JSP: {1}
- Category:
- HTTP
- Cause:
- This message indicates that the class file associated with the JSP is up-to-date.
- Action:
- No action is required.
- BEA-101342
- {0}: Error(s) encountered while precompiling JSP {1} {2}
- Category:
- HTTP
- Cause:
- The JSP file shown by the error message had errors and could not be precompiled.
- Action:
- Correct the errors shown by the message so that it gets precompiled without errors.
- BEA-101343
- {0}: Attempting to precompile {1}, since the class file associated with it was found to be out-of-date.
- Category:
- HTTP
- Cause:
- This message indicates that the class file associated with the given JSP was out of date and needs recompilation.
- Action:
- No action is required.
- BEA-101344
- {0}: Attempting to precompile {1}, since the class file associated with it was not found in the Web application classpath.
- Category:
- HTTP
- Cause:
- This message indicates that the class file associated with the given JSP was not found in the Web application classpath and thus needs to be compiled.
- Action:
- No action is required.
- BEA-101345
- A change in value was detected for the "Fields" directive in access.log for webserver: {0}. Rotating the access.log. The value defined for the WebServerMBean will take precedence. Default being "time cs-method cs-uri sc-status". Old value: "{1}" and new value: "{2}".
- Category:
- HTTP
- Cause:
- This message indicates that the value from WebServerMBean.getELFFields() was different that the value in the "Fields" directive on the top of access.log.
- Action:
- Changing the ELF fields by hand editing access.log is no longer supported. Change the access.log "Fields" using the Administration Console.
- BEA-101346
- The virtual host name: {0} being used by the Virtual Host: {1} is already in use by: {2}
- Category:
- HTTP
- Cause:
- There is duplicate name usage for VirtualHostNames.
- Action:
- Fix the VirtualHostNames fields for the Virtual Host and choose a unique name.
- BEA-101347
- The server channel name (NetworkAccessPoint): {0} being used by the Virtual Host: {1} is already in use by: {2}
- Category:
- HTTP
- Cause:
- There is uplicate name usage for ServerChannelName for Virtual Hosts.
- Action:
- Fix the ServerChannelName field for the Virtual Host and choose a unique name.
- BEA-101348
- The server channel name (NetworkAccessPoint): {0} being used by the Virtual Host: {1} is not defined. This virtual host will not be deployed.
- Category:
- HTTP
- Cause:
- The NetworkAccessPoint is not yet defined.
- Action:
- Choose a different NetworkAccessPoint name or define a new one using the Administration Console.
- BEA-101349
- Failed to save the WorkContexts into the session or cache for the request: {0}
- Category:
- HTTP
- Cause:
- An unexpected exception occurred.
- Action:
- At the end of the request, the Web application container saves the WorkContexts into the session and the local cache in order to propagate them between successive HTTP requests. Contact My Oracle Support and report this problem.
- BEA-101350
- Web application(s) {2} of module {1} of application {0} has {3} pending session(s) respectively.
- Category:
- HTTP
- Cause:
- The server has detected pending sessions for the Web application module while the application is gracefully transitioning from running to administration mode.
- Action:
- No action is required. Use the -force option to ignore inflight work and bring the application to administration mode.
- BEA-101351
- Server has detected pending sessions while gracefully transitioning webapp module {1} of application {0} from running to administration mode. Server will wait for pending sessions to either become invalidated or timed out. The current timeout value is {2} seconds. To terminate sessions immediately, use the -force option.
- Category:
- HTTP
- Cause:
- During graceful transition of the application from running to administration mode, the server waits for inflight work to complete. This includes pending sessions.
- Action:
- No action is required. Use the -force to ignore inflight work and force transition of the application from running to administration mode.
- BEA-101352
- There are no active sessions. The Web application module {1} of application {0} is ready to go into administration mode.
- Category:
- HTTP
- Cause:
- All active sessions have completed. The Web service is ready to gracefully transition to administration mode.
- Action:
- No action is required.
- BEA-101354
- Web application(s) {3} of module {1} of application {0} still have pending sessions after {2} minutes of initiating transition from running to administration mode. Waiting for pending sessions to finish.
- Category:
- HTTP
- Cause:
- The server is waiting for the application sessions to finish before gracefully shutting down.
- Action:
- No action is required. Use the -force option to ignore inflight work and force transition of the application into administration mode.
- BEA-101355
- [{0}] Version {2} is specified for Web Services {1}, but versioning of Web Services is not supported.
- Category:
- HTTP
- Cause:
- An attempt was made to deploy Web Services with versioning.
- Action:
- Deploy the Web Services (or the application containing the Web Services) without versioning.
- BEA-101356
- Web application: {0} failed to load the shared library (fastfile) for using native I/O in the FileServlet, falling back to the standard I/O.
- Category:
- HTTP
- Cause:
- An unexpected error occurred while attempting to load the native library (fastfile) for using native I/O in the FileServlet.
- Action:
- Ensure that the shared library (fastfile) exists in a directory that is in the LD_LIBRARY_PATH or PATH. Also, note that native I/O is supported on Windows, Linux, and Solaris. If problem persists, contact My Oracle Support.
- BEA-101357
- A force graceful production to administration mode transition was initiated. The Web application module {1} of application {0} is ready to go into administration mode.
- Category:
- HTTP
- Cause:
- A force graceful production to administration mode transition was initiated. The Web service is ready to transition to administration mode.
- Action:
- No action is required.
- BEA-101359
- The servlet {0} initilization method failed while it was run in the background. The exception was: {1}.
- Category:
- HTTP
- Cause:
- The servlet initilization method caused an exception.
- Action:
- The cause of the exception must be corrected and then the application should be redeployed.
- BEA-101360
- Recompiling JSP [{0}], resource [{1}], because it is stale.
- Category:
- HTTP
- Cause:
- The JSP was changed from the last time it was compiled.
- Action:
- The JSP will be always recompiled if it is different from the last compiled version.
- BEA-101361
- [{0}] A library reference in weblogic.xml has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1.
- Category:
- HTTP
- Cause:
- The Specification-Version of a library reference in weblogic.xml cannot be parsed.
- Action:
- Fix the library's Specification-Version in weblogic.xml to conform to the required version string syntax.
- BEA-101362
- [{0}] could not deserialize the {1} scoped attribute with name: "{2}"
- Category:
- HTTP
- Cause:
- Classloader changed. When this happens, the old attributes will be deserialized using the new classloader. The classloader can change either as the result of a dynamic reload of classes (controlled by weblogic.xml parameter "reload-check-secs" or upon across webapp dispatch (include or forward).
- Action:
- Ensure that the attribute class is available to the Web application scope and that the attribute class and all the references it holds are serializable.
- BEA-101363
- Application: {0}, Web application: {1} has context-root specified in application.xml: "{2}". The context-root specified in weblogic.xml: "{3}" will be ignored.
- Category:
- HTTP
- Cause:
- The context-root specified in application.xml takes higher precedence than the one in weblogic.xml.
- Action:
- This is an informational message. Ensure that this is what you intended to do.
- BEA-101364
- {0}:{1} Failure while precompiling JSP: {2}.
- Category:
- HTTP
- Cause:
- The JSP failed to precompile on a partial update.
- Action:
- Check the exception for the exact cause.
- BEA-101366
- The server could not send the HTTP message during the configured timeout value. The socket has been closed.
- Category:
- HTTP
- Cause:
- This is an informational message.
- Action:
- Bump up the value of CompleteMessageTimeout. The default is 60 seconds. If you have slow clients that cannot complete the messsage transfer and are getting timed out, raise the value.
- BEA-101367
- An error occurred while extracting archived file for "{0}", located at "{1}".
- Category:
- HTTP
- Cause:
- An error occurred while extracting the archived WAR file, due to path length limitations on some OS's.
- Action:
- Some OS's only allow a certain number of characters in the file name. This limitation can be noticed when extracting an archive in a deeply nested directory. Since the default temporary directory for extracting all archives is relative to the server root directory, it is recommended that one use the system property weblogic.j2ee.application.tmpDir and set it to a shorter file path, or one could ensure that the server is started in a directory with a shorted file path.
- BEA-101369
- {0}: The encoding jsp-descriptor parameter has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.
- Category:
- HTTP
- Cause:
- {0}: The encoding jsp-descriptor parameter has been deprecated.
- Action:
- Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.
- BEA-101370
- There was a failure when merging library descriptors into the application descriptors for application {0}. Ensure that the descriptors are valid. The error is {1}
- Category:
- HTTP
- Cause:
- The library or the application descriptors are invalid.
- Action:
- Fix the descriptors in the application or the library.
- BEA-101371
- There was a failure when processing annotations for application {0}. Ensure that the annotations are valid. The error is {1}
- Category:
- HTTP
- Cause:
- The descriptor has an invalid servlet-class, filter-class, or listener-class.
- Action:
- Fix the descriptors in the application or the library.
- BEA-101372
- There was a failure in application {0} when attempting to inject dependencies into {1}. Dependencies will not be injected into this class.
- Category:
- HTTP
- Cause:
- The annotations defined in the class may be invalid or the descriptor may have conflicting entries.
- Action:
- Check the annotations defined in this class. Also, verify that the descriptor has valid entries.
- BEA-101373
- Reloading classes in application {0} failed due to change of annotations on a refreshed class. Modified or new annotations will not be processed during servlet reload as they involve a non-dynamic change. Redeploy the application for these annotations to be processed.
- Category:
- HTTP
- Cause:
- New or modified annotations will not be processed in application {0} due to a servlet refresh.
- Action:
- Redeploy the application for reloading classes when annotations are modified.
- BEA-101374
- The Web container failed to look up the transaction associated with the current thread for Web application: ${0}.
- Category:
- HTTP
- Cause:
- After the response is sent, the container needs to check if there is any active transaction associated with the thread so that it can abort the transaction. See the exception message for more details.
- Action:
- See the exception message for more details.
- BEA-101375
- [{0}]: Error while parsing the JSF Configuration Descriptor at "{1}".
- Category:
- HTTP
- Cause:
- A JSF Configuration Descriptor parsing exception occurred.
- Action:
- Check the exception for the exact cause.
- BEA-101376
- Unable to purge cache of Bean classes from BeanELResolver, error occurs at "{0}".
- Category:
- HTTP
- Cause:
- Unable to get the cache property of BeanELResolver.
- Action:
- Contact My Oracle Support and report this problem.
- BEA-101377
- Filtering class loader configuration ignored for web module {1} of application {0}.
- Category:
- HTTP
- Cause:
- Filtering class loader configuration is only supported in descriptors at the main level of the deployment (for example, in enterprise applications or standalone web applications). This configuration is not supported in Web modules of an enteprise application.
- Action:
- Remove the filtering class loader configuration from the deployment descriptor of web module {1} of application {0}.
- BEA-101378
- The version of OpenJPA shipped with WebLogic Server does not support JPA 2.0. Recompile the application with the JPA 1.0 API JAR available at http://www.jcp.org/en/jsr/summary?id=220.
- Category:
- HTTP
- Cause:
- The Kodo-OpenJPA persistence provider that ships with WebLogic Server does not support JPA 2.0.
- Action:
- Recompile the application with the JPA 1.0 API jar available at http://www.jcp.org/en/jsr/summary?id=220 or use TopLink if you wish to use a JPA 2.0 persistence provider.
- BEA-101379
- Starting with WebLogic Server 10.3.4.0, some methods changed in the OpenJPA interfaces that ship with WebLogic Server. Recompile the application with the OpenJPA JAR in your WebLogic Server installation.
- Category:
- HTTP
- Cause:
- Some methods in the OpenJPA interfaces that ship with WebLogic Server have changed.
- Action:
- Recompile the application with the OpenJPA JAR in your WebLogic Server installation.
- BEA-101380
- There is more than one Web fragment with the same name: "{0}".
- Category:
- HTTP
- Cause:
- There is more than one Web fragment with the same name.
- Action:
- Change the duplicate Web fragment names to avoid the conflict.
- BEA-101381
- Both before others and after others found in Web fragment: "{0}".
- Category:
- HTTP
- Cause:
- Both before others and after others was found in the Web fragment.
- Action:
- Ensure that the Others element appears only in before or after.
- BEA-101382
- WLServlet annotation cannot be used with WebServlet together.
- Category:
- HTTP
- Cause:
- WLServlet annotation cannot be used with WebServlet together.
- Action:
- Oracle recommends that you use only servlet 3.0 annotations.
- BEA-101383
- WLFilter annotation can't be used with WebFilter together
- Category:
- HTTP
- Cause:
- WLFilter annotation can't be used with WebFilter together.
- Action:
- Suggest to use servlet 3.0 annotations only
- BEA-101384
- {0} annotation is deprecated, please use servlet 3.0 annotation instead. App:{1}, Class:{2}
- Category:
- HTTP
- Cause:
- The older WL annotations are deprecated, and replaced by servlet 3.0 annotations, for example WLServlet is replaced by WebServlet, WLFilter is replaced by WebFilter.
- Action:
- Suggest to use servlet 3.0 annotations instead if WL annotations
- BEA-101385
- WebListener annotation is used illegally, the class annotated by WebListener must implement listener interface
- Category:
- HTTP
- Cause:
- WebListener annotation is used illegally, the class annotated by WebListener must implement listener interface, for example: javax.servlet.ServletContextListener and so on, please check the servlet 3.0 specification.
- Action:
- The class annotated by WebListener must implement listener interface, for example: javax.servlet.ServletContextListener and so on, suggest to check the servlet 3.0 specification.
- BEA-101386
- The ServletSecurity Annotation is illegal, the root is {0}
- Category:
- HTTP
- Cause:
- The ServletSecurity Annotation is illegal, the root is {0}.
- Action:
- Suggest not to correct ServletSecurity Annotation accroding to the Servlet 3.0 Specification.
- BEA-101387
- ServletContext has already been initialized, cannot call method {0} any longer.
- Category:
- HTTP
- Cause:
- ServletContext has already been initialized, cannot call method {0} any longer.
- Action:
- Check Servlet 3.0 Specification and the corresponding javadoc.
- BEA-101388
- The ServletContext was passed to the ServletContextListener.contextInitialized method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.
- Category:
- HTTP
- Cause:
- The ServletContext was passed to the ServletContextListener.contextInitialized method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.
- Action:
- Check Servlet 3.0 Specification and the corresponding javadoc.
- BEA-101389
- Cannot add this ServletContextListener
- Category:
- HTTP
- Cause:
- Because this ServletContext was passed to the ServletContextListener's contextInitialized() method of a ServletContextListener that was neither declared in web.xml or web-fragment.xml, nor annotated with javax.servlet.annotation.WebListener.
- Action:
- Check Servlet 3.0 Specification and the corresponding javadoc.
- BEA-101390
- It is illegal to use both value and urlPatterns attributes together in the same WebServlet/WebFilter annotation: {0}.
- Category:
- HTTP
- Cause:
- As per the Servlet 3.0 specification, section 8.1, both the value attribute and urlPatterns attribute were detected in the identical WebServlet/WebFilter annotation.
- Action:
- Use either the value attribute or urlPatterns attribute, but not both at the same time in the same annotation.
- BEA-101391
- Circular references found in web fragments relative ordering.
- Category:
- HTTP
- Cause:
- Circular references found in web fragments relative ordering.
- Action:
- Use absolute ordering to overwrite relative ordering or change relative ordering config.
- BEA-101392
- Glassfish Descriptor element <{0}> was successfully parsed and applied.
- Category:
- HTTP
- Cause:
- This is an information message.
- Action:
- No action is required if the element parsing was successful.
- BEA-101393
- Glassfish Descriptor element <{0}> is not supported by WebLogic.
- Category:
- HTTP
- Cause:
- This is an informational message.
- Action:
- No action is required. Note that the element is ignored by the descriptor parser.
- BEA-101394
- The exception "{0}" occurred when processing getParameter or getParameterValues from a multipart value of a ServletRequest.
- Category:
- HTTP
- Cause:
- The exception "{0}" occurred when processing getPart or getParts from a ServletRequest.
- Action:
- Check whether the size of the uploaded file exceeds the size limit. Check that the content of the post-multipart form data is correct.
- BEA-101395
- Application or module {0} is deployed as a web application.
- Category:
- HTTP
- Cause:
- The spplication or module {0} was deployed as a web application because there was no hint (descriptors or classes annotated by component annotations) detected. WebLogic Server deploys applications without deployment descriptors or classes annotated by component annotations as web application.
- Action:
- No action is required if the application is a web application or a web module. Otherwise, add the corresponding deployment descriptors so that WebLogic Server can detect the application type correctly.
- BEA-101396
- Either the urlPatterns or the value attribute in the WebServlet annotation MUST be present: {0}.
- Category:
- HTTP
- Cause:
- As per the Servlet 3.0 specification, section 8.1.1, neither the value attribute nor the urlPatterns attribute was detected in the WebServlet annotation.
- Action:
- Use either the value attribute or urlPatterns attribute, but not both at a same time in the same annotation.
- BEA-101397
- The urlPatterns attribute, servletNames attribute, or value attribute of the WebFilter annotation MUST be specified: {0}.
- Category:
- HTTP
- Cause:
- As per the Servlet 3.0 specification, section 8.1.2, neither the urlPatterns attribute, servletNames attribute, nor value attribute was detected in the WebFilter annotation.
- Action:
- Use either the urlPatterns, servletNames, or value attribute in the annotation. Do not use both the urlPatterns and value attributes at a same time in the same annotation.
- BEA-101398
- Exception : [{0}][{1}] during request upgrade.
- Category:
- HTTP
- Cause:
- An error occurred while creating an instance of HttpUpgradeHandler. [{0}][{1}]
- Action:
- Check whether the Implement of HttpUpgradeHandler exists or the class has been put under the correct classpath.
- BEA-101399
- The Web application: {0} has specified DIGEST as the auth-method in web.xml, which is not implemented.
- Category:
- HTTP
- Cause:
- DIGEST authentication is not yet implemented.
- Action:
- Choose either BASIC, FORM, or CLIENT-CERT.
- BEA-101400
- The value of {0} attribute {1} can not be serialized and will be removed when reloading the application, the class of the value object is {2}.
- Category:
- HTTP
- Cause:
- An exception occurred when serializing the attribute value.
- Action:
- Either correct the serialization issue of the attribute value class or ignore this warning if it is harmless for application reloading.
- BEA-101401
- The url-pattern {0} in web application {1} is mapped to multiple Servlets.
- Category:
- HTTP
- Cause:
- The effective web.xml, after merging information from fragments and annotations, contains url-patterns that are mapped to multiple servlets.
- Action:
- Check the web.xml, fragment.xml, and annotations to remove the multiple url-patterns mapping issue of the servlets.
- BEA-101402
- Cannot get Request or Response when the current state is completed or dispatched.
- Category:
- HTTP
- Cause:
- Try to get Request or Response from a completed or dispatched AsyncContext.
- Action:
- Try to call AsyncContext.getRequest and AsyncContext.getResponse after the asynchronous request is completed or dispatched.
- BEA-101403
- For security constraint with url-pattern {0} in web application {1}, only the http methods "{2}" are covered.
- Category:
- HTTP
- Cause:
- During application deployment, the container must inform the deployer of any uncovered http methods that are present in the application security constraint configuration resulting from the combination of the constraints defined for the application.
- Action:
- Check the security constraint in the web application. Remove the uncovered http methods.
- BEA-101404
- For security constraint with url-pattern {0} in web application {1}, the http methods "{2}" are uncovered.
- Category:
- HTTP
- Cause:
- During application deployment, the container must inform the deployer of any uncovered HTTP methods that are present in the application security constraint configuration resulting from the combination of the constraints defined for the application.
- Action:
- Check the security constraint in the web application. Remove the uncovered http omitted methods.
- BEA-101405
- The preliminary servlet {0} defined in web.xml or web-fragment.xml has not been completed through the ServletContext.addServlet() API by any ServletContextListener or ServletContainerInitializer.
- Category:
- HTTP
- Cause:
- The servlet does not have any servlet-class or jsp-file configured in web.xml or web-fragment.xml. Therefore it does not get completed by by ServletContextListener or ServletContainerInitializer with the programmatically servlet adding API of ServletContext.
- Action:
- Ensure that the servlet is completed in web.xml or web-fragment.xml, or can be completed by ServletContextListener or ServletContainerInitializer with the programmatically servlet adding API of ServletContext.
- BEA-101406
- Filter Name cannot be a Null or Empty string.
- Category:
- HTTP
- Cause:
- The filter name is a Null or Empty string when calling ServletContext.addFilter().
- Action:
- Check the application. Add a 'not null' string type name for ServletContext.addFilter().
- BEA-101407
- Servlet Name cannot be a Null or Empty string.
- Category:
- HTTP
- Cause:
- The Servlet name is a Null or Empty string when calling ServletContext.addServlet().
- Action:
- Check the application. Add a 'not null' string type name for ServletContext.addServlet().
- BEA-101408
- [{0}] An error occurred while removing WLDFDataAccessRuntimeMBean.
- Category:
- HTTP
- Cause:
- The WLDFDataAccessRuntimeMBean associated with Web application {0} could not be removed.
- Action:
- Check the exception for the exact error message.
- BEA-101409
- The referenced shared library {0} {1} will be ignored and the {0} library in system class path will be used.
- Category:
- HTTP
- Cause:
- Since WebLogic Server 12c, application is unnecessary to reference shared library to use JSF/JSTL feature. Since WebLogic Server 12.2.1, the referenced JSTL 1.2 and JSF 2.x shared library in application will be ignored. The JSF/JSTL shared library in system classpath will be used.
- Action:
- The JSF 2.x/JSTL 1.2 library-ref in deployment descriptor should be removed.
- BEA-101410
- Secure mode is enabled in WLS domain, the servlet {0} uses weblogic.servlet.ServletServlet which should not be used in WLS secure mode.
- Category:
- HTTP
- Cause:
- The servlet weblogic.servlet.ServletServlet is recommended to be not used in WLS secure mode.
- Action:
- Please remove weblogic.servlet.ServletServlet and existing mappings in web.xml of your application. Please refer to document Oracle® Fusion Middleware Securing a Production Environment for Oracle WebLogic Server, Chapter 3 "Ensuring the Security of Your Production Environment" for more details.
- BEA-101411
- There's IOException thrown when web application [{0}] sends error response to client. The IOException is {1}
- Category:
- HTTP
- Cause:
- An unexpected IOException was thrown when sending error message to client.
- Action:
- Check the exception for the exact cause of the problem.
- BEA-110000
- Transaction log record class name encoding error [{0}]: {1}
- Category:
- JTA
- Cause:
- An error occurred while writing a record to the transaction log.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110001
- Transaction log record encoding error [{0}]: {1}
- Category:
- JTA
- Cause:
- An error occurred while writing a record to the transaction log. See the reported exception for more details.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110003
- onError() callback exception: {0}
- Category:
- JTA
- Cause:
- An error occurred while writing a record to the transaction log.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110004
- Unable to read transaction log record checksum.
- Category:
- JTA
- Cause:
- The transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system reboot, a crash caused the transaction being logged at that time to be rolled back.
- Action:
- No action is required. Recovery is automatic.
- BEA-110005
- Transaction log record checksum failure [{0}].
- Category:
- JTA
- Cause:
- A record in the transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system re-boot, a crash caused the transaction being logged at that time to be rolled back.
- Action:
- No action is required. Recovery is automatic.
- BEA-110007
- Log record class instantiation problem [{0}]: {1}
- Category:
- JTA
- Cause:
- An error occurred while reading a record from the transaction log. This may have also occurred due to crash recovery processing of a new transaction log file performed by an older WebLogic Server software version.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110008
- Log record class readExternal problem [{0}]: {1}
- Category:
- JTA
- Cause:
- An error occurred while reading externalized state information for a record from the transaction log. This may have also occurred due to crash recovery processing of a new transaction log file performed by an older WebLogic Server software version.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110011
- onRecovery() callback exception: {0}.
- Category:
- JTA
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110013
- An error occurred while writing transaction log: {0}.
- Category:
- JTA
- Cause:
- The file system is full or permission problems exist.
- Action:
- Verify the transaction log file location and locate any file system problems.
- BEA-110015
- A version error occurred while reading the transaction log header file.
- Category:
- JTA
- Cause:
- File corruption exists. A new transaction log file may have been given to an older version of WebLogic Server.
- Action:
- The system will automatically create an empty transaction log.
- BEA-110020
- Error reading transaction log file [{0}]: {1}
- Category:
- JTA
- Cause:
- There are file system or permission problems, or possible corruption of the transaction log.
- Action:
- Verify the transaction log file location and check for file system problems. Crash recovery processing continues as best it can.
- BEA-110021
- Format error [{0}] occurred while reading transaction log file [{1}]
- Category:
- JTA
- Cause:
- The transaction log file was possibly corrupted.
- Action:
- Contact My Oracle Support.
- BEA-110022
- Format error [{0}] occurred while reading transaction log file [{1}]: {2}
- Category:
- JTA
- Cause:
- The transaction log file is possibly corrupted.
- Action:
- Contact My Oracle Support.
- BEA-110023
- Transaction log record checksum failure [{0}]: {1}.
- Category:
- JTA
- Cause:
- A record in the transaction log file is corrupted, possibly due to a crash or file system error. If this error occurs only once per system reboot, a crash caused the transaction being logged at that time to be rolled back.
- Action:
- No action is required. Recovery is automatic.
- BEA-110026
- Missing transaction log file [{0}]
- Category:
- JTA
- Cause:
- File system or permission problems exist, or the transaction log might be corrupted. The file might also have been manually deleted.
- Action:
- Verify the transaction log file location and check for file system problems. Crash recovery processing will continue.
- BEA-110028
- The transaction manager did not call XA.forget() for transaction [{1}] on resource [{0}], which reported a heuristic decision during commit.
- Category:
- JTA
- Cause:
- See the message details for probable cause.
- Action:
- After correcting any data inconsistencies due to the heuristic outcome, use the resource manager administrative commands to instruct the resource to ignore the transaction.
- BEA-110029
- The transaction manager did not call XA.forget() for transaction [{1}] on resource [{0}], which reported a heuristic decision during rollback.
- Category:
- JTA
- Cause:
- See the message details for the probable cause.
- Action:
- After correcting any data inconsistencies due to the heuristic outcome, use the resource manager administrative commands to instruct the resource to ignore the transaction.
- BEA-110030
- XA resource [{0}] has not responded in the last {1} second(s).
- Category:
- JTA
- Cause:
- The resource is unavailable (possibly the resource is down, or network problems exist).
- Action:
- Check the resource manager and network condition. When the resource is available again, take the following actions to inform the Transaction Manager: For JDBC connection pools, refresh the connection pool. You can also enable the auto-refresh feature of the connection pool to do this automatically. For other third-party XA resources, the resource provider should re-register the resource by calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().
- BEA-110033
- Recovered transaction log header file from backup location [{0}].
- Category:
- JTA
- Cause:
- This error is probably caused by a crash that occurred when the the transaction log header file was being rewritten.
- Action:
- No action is required. Recovery is automatic.
- BEA-110101
- No license exists for two-phase commit (2PC) processing.
- Category:
- JTA
- Cause:
- The 2PC license is not present.
- Action:
- Contact an Oracle sales representative to obtain a 2PC license.
- BEA-110102
- A transaction with multiple resources was rolled back due to an invalid two-phase commit (2PC) license.
- Category:
- JTA
- Cause:
- The 2PC license is not present.
- Action:
- Contact an Oracle sales representative to obtain a 2PC license.
- BEA-110200
- User [{0}] is not authorized to invoke startCommit on a transaction branch.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternately, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110201
- User [{0}] is not authorized to invoke startRollback on a transaction branch.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that client software is not directly invoking an internal WebLogic system object.
- BEA-110202
- User [{0}] is not authorized to invoke rollback on a transaction branch.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.
- Action:
- Verify that client software is not directly invoking an internal WebLogic system object.
- BEA-110204
- XA resource [{0}] returns XAER_RMFAIL and is unavailable.
- Category:
- JTA
- Cause:
- The resource is unavailable because is down or network problems exist.
- Action:
- Check the resource manager and network conditions. When the resource is available again, take the following actions to inform the Transaction Manager: For JDBC connection pools, refresh the connection pool. You can also enable the auto-refresh feature of the connection pool to do this automatically. For other third-party XA resources, the resource provider should re-register the resource by calling weblogic.transaction.TransactionManager.unregisterResource(), followed by weblogic.transaction.TransactionManager.registerStaticResource() or weblogic.transaction.TransactionManager.registerDynamicResource().
- BEA-110207
- A previously unavailable XA resource [{0}] is now available.
- Category:
- JTA
- Cause:
- The previously unavailable resource is now available. It is possible that the resource has recovered from earlier failures or that previous network problems were cleared.
- Action:
- No action is required.
- BEA-110208
- Unregistration of Transaction Recovery Service for server [{0}] failed.
- Category:
- JTA
- Cause:
- An attempt to unregister the Transaction Recovery Service for server [{0}] from the migratable service framework failed.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110209
- Registration of Transaction Recovery Service for server [{0}] failed.
- Category:
- JTA
- Cause:
- An attempt to register the Transaction Recovery Service for server [{0}] from the migratable service framework failed.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110210
- Failback of Transaction Recovery Service for server [{0}] failed.
- Category:
- JTA
- Cause:
- Transaction recovery actions are performed for the Transaction Recovery Service for server [{0}]. An attempt to failback the Transaction Recovery Service failed.
- Action:
- Examine the migration errors and perform manual migration of the Transaction Recovery Service back to server [{0}].
- BEA-110211
- Failback retry of Transaction Recovery Service for server [{0}] failed.
- Category:
- JTA
- Cause:
- Transaction recovery actions are performed for the Transaction Recovery Service for server [{0}]. Both the first and second attempt to failback the Transaction Recovery Service failed. JTA is going to give up implicitly failing back the Transaction Recovery Service for server [{0}].
- Action:
- Examine the migration errors and perform manual migration of the Transaction Recovery Service back to server [{0}].
- BEA-110212
- An attempt was made to manually migrate the Transaction Recovery Service of the current server away from the server while it is still active.
- Category:
- JTA
- Cause:
- An attempt was made to manually migrate the current Transaction Recovery Service away from the server while it is still active.
- Action:
- For controlled migration, suspend or shut down the current server first before manually migrating it to a backup server.
- BEA-110213
- The activation of Transaction Recovery Service for server [{0}] failed.
- Category:
- JTA
- Cause:
- The activation of Transaction Recovery Service for server [{0}] failed.
- Action:
- Examine the error details, correct the error conditions, and perform the necessary manual migration again if possible. If unsuccessful, My Oracle Support.
- BEA-110400
- An error occurred while unregistering Resource Runtime MBean: {0}
- Category:
- JTA
- Cause:
- The MBean may have been unregistered previously or there may be an issue with the JMX Administration Server.
- Action:
- No action is required.
- BEA-110401
- Ignoring error in afterCompletion. Object={0}, Exception={1}
- Category:
- JTA
- Cause:
- The application-defined javax.transaction.Synchronization callback may have caused an exception.
- Action:
- No action is required.
- BEA-110402
- Unknown state in getStatus(): {0}.
- Category:
- JTA
- Cause:
- The Transaction.getStatus() method was called and the transaction status is not a valid value.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110403
- An unexpected exception occurred while processing a transaction during a transaction manager timer event. Exception={0}.
- Category:
- JTA
- Cause:
- Refer to the exception information found in the error message.
- Action:
- No action is required.
- BEA-110405
- Resource {0} was not assigned to any of these servers: {1}
- Category:
- JTA
- Cause:
- The transaction coordinator maintains information regarding where resources are registered among all the servers that are known to the coordinator. The participating resource may have been unregistered or became unavailable prior to attempting the operation. This condition may also occur if the cache belonging to the coordinator was out of date or has not completed initialization at the time the operation was invoked.
- Action:
- Verify the state of resource managers participating in the transaction and retry the operation.
- BEA-110406
- Internal error interpreting heuristic status. Expected={0}, Actual={1}
- Category:
- JTA
- Cause:
- The heuristic completion status of a transaction is calculated based on the expected and actual completion states of all participants. The logic to determine the heuristic outcome did not account for the combination of the actual and expected completion states.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110407
- Unknown state in getStatus(): {0}
- Category:
- JTA
- Cause:
- The Transaction.getStatus() method did not recognize the transaction state as a valid state.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110408
- An attempt to add a duplicate transaction to the transaction manager list was ignored.
- Category:
- JTA
- Cause:
- The internal transaction table of the server already contains the transaction instance being added. This event is innocuous.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110409
- Unable to advertise resource {0}: {1}
- Category:
- JTA
- Cause:
- A problem may exist with the JNDI provider, or another object is already bound to this context.
- Action:
- Contact My Oracle Support.
- BEA-110410
- Unable to create resource runtime MBean for resource {0}: {1}
- Category:
- JTA
- Cause:
- There may be a problem with the JMX Administration Server, or another MBean with this name is already registered with the Administration Server.
- Action:
- Contact My Oracle Support.
- BEA-110411
- Failed to construct local ServerCoordinatorDescriptor: {0}.
- Category:
- JTA
- Cause:
- During server initialization, information about the local server could not be obtained from the local JNDI context.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110412
- {0} completed heuristically: {1}.
- Category:
- JTA
- Cause:
- The resource manager may have failed, timed out, or detected locking conflicts that prompted it to commit or roll back work for the transaction branch. If the heuristic error was due to a resource manager failure, the resource may not be able to determine if work for the transaction branch was committed, aborted, or both. In this case, the condition is considered a HAZARD or MIXED heuristic.
- Action:
- Check the participants of the transaction should be checked for possible data corruption. The resource manager reporting the heuristic may maintain state information related to the updates involved in the heuristic error. If the JTA ForgetHeuristics configuration parameter is set to false, this information may be preserved in the resource manager. This information might be useful in correcting any data inconsistencies.
- BEA-110414
- Illegal State (expected: Prepared or Committing): {0}
- Category:
- JTA
- Cause:
- While attempting to retry the commit phase of a transaction, it was detected that the state of the transaction is not valid. To be in the commit phase, a transaction can only be in the prepared or committing states.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110415
- Illegal state. Proceeding with rollback anyway. {0}
- Category:
- JTA
- Cause:
- While attempting to retry the rollback of a prepared transaction, it was detected that the state of the transaction is not valid.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-110419
- An attempt was made to add an incompatible object as a transaction property: keys must be strings and values must be serializable.
- Category:
- JTA
- Cause:
- An attempt was made to add an incompatible object as a transaction property (the class of the key object must be a string and the class of the value object must be serializable).
- Action:
- Change the application to assign the transaction property using a String key and a serializable value.
- BEA-110420
- An attempt was made to add an incompatible object as a local transaction property: keys must be String.
- Category:
- JTA
- Cause:
- An attempt was made to add an incompatible object as a local transaction property (the key object must be of the class String).
- Action:
- Change the application to add the local property with a String key.
- BEA-110421
- Timer method was called on committed transaction {0}.
- Category:
- JTA
- Cause:
- The transaction manager invoked a timer method on a transaction that has already completed. The transaction manager periodically checks for transactions that should be aborted due to timeout. This transaction should have been removed from the internal transaction table.
- Action:
- Check for other log messages that give more information about the failure. No action required.
- BEA-110422
- Forcibly aborting a transaction found in an unexpected internal state. Details={0}
- Category:
- JTA
- Cause:
- While processing a transaction, the transaction manager detected that the transaction is in an illegal state. The only course of action for the coordinator is to attempt to force a rollback of all participants.
- Action:
- Check for any data inconsistencies among participating resources. Contact My Oracle Support.
- BEA-110423
- Abandoning transaction after {0} seconds: {1}
- Category:
- JTA
- Cause:
- A resource or participating server may have been unavailable for the duration of the AbandonTimeoutSeconds period.
- Action:
- Check participating resources for heuristic completions and correct any data inconsistencies.
- BEA-110424
- An unexpected exception was caught during begin: {0}
- Category:
- JTA
- Cause:
- Check the exception detail portion of the log message.
- Action:
- Correct the condition described in the exception detail portion of the log message.
- BEA-110425
- Error advertising TransactionManager object: {0}
- Category:
- JTA
- Cause:
- There may be a problem with the JNDI provider or another object is already bound to this context.
- Action:
- Contact My Oracle Support.
- BEA-110426
- An error occurred while advertising UserTransaction object: {0}
- Category:
- JTA
- Cause:
- There may be a problem with the JNDI provider, or another object is already bound to this context.
- Action:
- Contact My Oracle Support.
- BEA-110427
- An error occurred while advertising Coordinator object: {0}
- Category:
- JTA
- Cause:
- There may be a problem with the JNDI provider, or another object is already bound to this context.
- Action:
- Contact My Oracle Support.
- BEA-110428
- An error occurred while exporting Coordinator object ID: {0}
- Category:
- JTA
- Cause:
- Another remote object may be bound to this object ID.
- Action:
- Contact My Oracle Support.
- BEA-110429
- Error advertising SubCoordinator object: {0}.
- Category:
- JTA
- Cause:
- There may be a problem with the JNDI provider, or another object is already bound to this context.
- Action:
- Contact My Oracle Support.
- BEA-110433
- Unable to obtain ownership of the transaction log.
- Category:
- JTA
- Cause:
- The Transaction Recovery Service associated with the current server is currently owned by other servers.
- Action:
- Migrate the Transaction Recovery Migratable Service back to the current server before restarting it.
- BEA-110442
- An administrative request was made to locally roll back the transaction associated with Xid {0}
- Category:
- JTA
- Cause:
- The forced local rollback operation was initiated by an administrative application.
- Action:
- No action is required.
- BEA-110443
- An administrative request was made to locally commit the transaction associated with Xid {0}
- Category:
- JTA
- Cause:
- The forced local commit operation was initiated by an administrative application.
- Action:
- No action is required.
- BEA-110444
- An administrative request was made to globally commit the transaction associated with Xid {0}.
- Category:
- JTA
- Cause:
- A forced global rollback operation was initiated by an administrative application.
- Action:
- No action is required.
- BEA-110445
- An administrative request was made to globally commit the transaction associated with Xid {0}.
- Category:
- JTA
- Cause:
- A forced global commit operation was initiated by an administrative application.
- Action:
- No action is required.
- BEA-110446
- The administrative request to locally roll back the transaction associated with Xid {0} failed because the transaction does not exist.
- Category:
- JTA
- Cause:
- The transaction may have completed before the administrative request was made.
- Action:
- No action is required.
- BEA-110447
- The administrative request to locally commit the transaction associated with Xid {0} failed because the transaction does not exist.
- Category:
- JTA
- Cause:
- The transaction may have completed before the administrative request was made.
- Action:
- No action is required.
- BEA-110448
- The administrative request to globally roll back the transaction associated with Xid {0} failed because the transaction does not exist.
- Category:
- JTA
- Cause:
- The transaction may have completed before the administrative request was made.
- Action:
- No action is required.
- BEA-110449
- The administrative request to globally commit the transaction associated with Xid {0} failed because the transaction does not exist
- Category:
- JTA
- Cause:
- The transaction may have completed before the administrative request was made.
- Action:
- No action is required.
- BEA-110450
- The administrative request to locally roll back the transaction {0} encountered an error {1}.
- Category:
- JTA
- Cause:
- Refer to the exception information in the error message.
- Action:
- Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
- BEA-110451
- The administrative request to globally roll back the transaction {0} encountered an error {1}.
- Category:
- JTA
- Cause:
- Refer to the exception information in the error message.
- Action:
- Check to see if the transaction still exists; the operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
- BEA-110452
- The administrative request to locally commit the transaction {0} encountered an error {1}.
- Category:
- JTA
- Cause:
- Refer to the exception information in the error message.
- Action:
- Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
- BEA-110453
- The administrative request to globally commit the transaction {0} encountered an error {1}.
- Category:
- JTA
- Cause:
- Refer to the exception information in the error message.
- Action:
- Check to see if the transaction still exists. The operation may have resolved the transaction. If the problem persists, contact My Oracle Support.
- BEA-110454
- The administrative request to locally roll back the transaction {0} failed because the transaction is in an invalid state. {1}
- Category:
- JTA
- Cause:
- The administrative request is invalid.
- Action:
- Issue a forced commit operation instead to resolve the transaction.
- BEA-110455
- The administrative request to globally roll back the transaction {0} failed because the transaction is in an invalid state. {1}
- Category:
- JTA
- Cause:
- The administrative request is invalid.
- Action:
- Issue a forced commit operation instead to resolve the transaction.
- BEA-110456
- The administrative request to locally commit the transaction {0} failed because the transaction is in an invalid state. {1}
- Category:
- JTA
- Cause:
- The administrative request is invalid.
- Action:
- Issue a forced rollback operation instead to resolve the transaction.
- BEA-110458
- The administrative request to globally roll back the transaction {0} failed, because the coordinator {1} could not be contacted. {2}
- Category:
- JTA
- Cause:
- The coordinating server for the transaction is either not running or is unreachable.
- Action:
- Verify that the coordinating server is available and retry the operation. Alternatively, perform local operations to resolve the transaction.
- BEA-110459
- The administrative request to globally commit the transaction {0} failed, because the coordinator at {1} could not be contacted. {2}
- Category:
- JTA
- Cause:
- The coordinating server for the transaction is either not running or is unreachable.
- Action:
- Verify that the coordinating server is available and retry the operation. Alternatively, perform local operations to resolve the transaction.
- BEA-110460
- The administrative request to globally rollback the transaction {0} failed, because the coordinator does not support manual transaction resolution.
- Category:
- JTA
- Cause:
- The coordinating server is an older version of WebLogic Server that does not support manual transaction resolution.
- Action:
- Perform local commit operations on all participants that support manual transaction resolution.
- BEA-110462
- The administrative request to locally commit the transaction {0} failed, because the transaction has been marked for rollback.
- Category:
- JTA
- Cause:
- The transaction has been marked for rollback by an application component.
- Action:
- Attempt to resolve the transaction by using a forced rollback operation instead.
- BEA-110464
- The forced commit operation for transaction {0} on resource {1} was not performed, because the resource is busy.
- Category:
- JTA
- Cause:
- There may be a blocked resource operation for this transaction. The resource may be experiencing problems or it may be slow to respond.
- Action:
- Attempt to retry the commit operation. The associated resource changes for the transaction may need to be manually resolved using a resource-specific utility.
- BEA-110465
- The forced rollback operation for transaction {0} on resource {1} was not performed, because the resource is busy
- Category:
- JTA
- Cause:
- There may be a blocked resource operation for this transaction. The resource may be experiencing problems or it may be slow to respond.
- Action:
- Attempt to retry the commit operation. The associated resource changes for the transaction may need to be manually resolved using a resource-specific utility.
- BEA-110466
- The forced commit operation for transaction {0} on resource {1} was not performed because the resource has already been committed.
- Category:
- JTA
- Cause:
- The transaction may have completed before the administrative client invoked the commit operation.
- Action:
- No action is required. The transaction has been resolved.
- BEA-110467
- The forced rollback operation for transaction {0} on resource {1} was not performed because the resource has already been rolled back.
- Category:
- JTA
- Cause:
- The transaction may have completed before the administrative client invoked the rollback operation.
- Action:
- No action is required. The transaction has been resolved.
- BEA-110468
- The forced commit operation for transaction {0} on resource {1} encountered an error. {2}
- Category:
- JTA
- Cause:
- Refer to the resource exception in the error message and any appropriate resource-specific error logs.
- Action:
- Determine if administrative operations are required in the resource to resolve the transaction branch.
- BEA-110469
- The forced rollback operation for transaction {0} on resource {1} encountered an error. {2}
- Category:
- JTA
- Cause:
- Refer to the resource exception in the error message and any appropriate resource-specific error logs.
- Action:
- Determine if administrative operations are required in the resource to resolve the transaction branch.
- BEA-110470
- User [{0}] is not authorized to invoke a forced global rollback.
- Category:
- JTA
- Cause:
- The authenticated principal making the request does not have adequate privileges to perform a forced rollback operation on the transaction.
- Action:
- Authenticate using an identity with adequate privileges prior to invoking the operation.
- BEA-110471
- User [{0}] is not authorized to invoke a forced global commit.
- Category:
- JTA
- Cause:
- The authenticated principal making the request does not have adequate privileges to perform a forced commit operation on the transaction.
- Action:
- Authenticate using an identity with adequate privileges prior to invoking the operation.
- BEA-110472
- User [{0}] is not authorized to invoke a forced local rollback.
- Category:
- JTA
- Cause:
- The authenticated principal making the request does not have adequate privileges to perform a forced rollback operation on the transaction.
- Action:
- Authenticate using an identity with adequate privileges prior to invoking the operation.
- BEA-110473
- User [{0}] is not authorized to invoke a forced local commit.
- Category:
- JTA
- Cause:
- The authenticated principal making the request does not have adequate privileges to perform a forced commit operation on the transaction.
- Action:
- Authenticate using an identity with adequate privileges prior to invoking the operation.
- BEA-110474
- Unable to advertise non-XA resource {0}: {1}
- Category:
- JTA
- Cause:
- There may be a problem with the JNDI provider, or another object is already bound to this context.
- Action:
- Contact My Oracle Support.
- BEA-110475
- User [{0}] is not authorized to invoke commit on a non-XA resource transaction branch.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that client software is not directly invoking an internal WebLogic Server system object.
- BEA-110476
- The server has detected pending transactions during graceful shutdown. The server will wait for the pending transactions to complete before suspending the RMI service. A forced shutdown command can be issued to shut down the server immediately.
- Category:
- JTA
- Cause:
- The server has detected pending transactions during graceful shutdown.
- Action:
- No action is required. Use a forced shutdown command to ignore inflight work and shut down the server immediately.
- BEA-110477
- The unregisterResource operation for resource {0} timed out after {1} seconds.
- Category:
- JTA
- Cause:
- It was requested that the specified resource be unregistered from the transaction manager and transactions that refer to the resource still exist on the server.
- Action:
- Monitor inflight transactions to determine if there are still active transactions that depend on the unregistered resource. Options include using the Administration Console to manually resolve dependent transactions, or the resource may be redeployed for a sufficient period to allow the dependent transactions to complete.
- BEA-110478
- One-phase transaction [{1}] is in an unknown state for logging resource [{0}]. The transaction operations either all rolled back, or all committed, or are blocked. Transaction detail: [{2}]. Root cause: [{3}].
- Category:
- JTA
- Cause:
- If the logging last resource is a database, there are a number of possible root causes. Among them are: the database may have shut down or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potential deadlock condition introduced by application operations within the local commit.
- Action:
- Examine the exception caused by the LLR resource to determine the root cause of the problem.
- BEA-110479
- Two-phase transaction [{1}], with logging resource [{0}], is an unknown state. The transaction manager will periodically retry determining the state of the transaction every [{3}] seconds. When the state is determined, the remaining resources in the transaction will be either rolled back or committed accordingly. Transaction detail: [{2}]. Root cause: [{4}].
- Category:
- JTA
- Cause:
- If the logging last resource is a database, there are a number of possible root causes. Among them are: the database may have shutdown or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potention dead-lock condition introduced by application operations within the local commit.
- Action:
- Examine the exception caused by the LLR resource to determine the root cause of the problem. Note that no action may be required as the transaction manager will periodically retry the transaction until it can automatically rollback or commit accordingly.
- BEA-110480
- The transaction manager is completing logging resource [{0}] transaction [{1}]. The transaction, which was previously in an unknown state, is now resolved and in the [{2,choice,0#rollback|1#commit}] state.
- Category:
- JTA
- Cause:
- See previous log messages for the same transaction to determine the root cause.
- Action:
- See previous log messages for the same transaction to determine the root cause.
- BEA-110482
- A logging last resource (LLR) failed during initialization. The server cannot boot unless all configured LLRs initialize. Failing reason: {0}
- Category:
- JTA
- Cause:
- If the logging last resource is a JDBC LLR connection, there are a number of possible root causes. Among them are: the database may have shut down or crashed, the database connection may have failed during boot, or the database connection may have incorrect database permissions.
- Action:
- Examine the root exception thrown by the LLR to determine the root cause of the problem.
- BEA-110483
- The JTA health state has changed from {0} to {1}.
- Category:
- JTA
- Cause:
- An internal event has caused the JTA health state to transition to the normal state. Refer to previous health log entries for the conditions that have been corrected to trigger the state change.
- Action:
- No action is required.
- BEA-110484
- The JTA health state has changed from {0} to {1} with reason codes: {2}.
- Category:
- JTA
- Cause:
- Refer to the message body for information regarding the events that caused the health change.
- Action:
- Refer to the message body for the cause of the JTA state change and take the appropriate action to correct the exception condition.
- BEA-110485
- The JTA health state has changed from {0} to {1} with reason codes: {2}.
- Category:
- JTA
- Cause:
- Refer to the message body for information regarding the events that caused the health change.
- Action:
- Refer to the message body for the cause of the JTA state change and take the appropriate action to correct the exception condition.
- BEA-110486
- Transaction {0} cannot complete commit processing because resource [{1}] is unavailable. The transaction will be abandoned after {2} seconds unless all resources acknowledge the commit decision.
- Category:
- JTA
- Cause:
- The resource may have been undeployed or is unresponsive and declared unavailable.
- Action:
- Check for related server log messages that may provide additional details regarding the state of the resource. If the resource is undeployed, deploy the resource or the application module if the resource is application scoped. If a problem exists with the resource manager, correct the problem and redeploy the resource.
- BEA-110487
- Transaction {0} cannot complete rollback processing because the pending resource [{1}] is unavailable. The transaction will be abandoned after {2} seconds unless all resources acknowledge the rollback decision.
- Category:
- JTA
- Cause:
- The resource may have been undeployed or is unresponsive and declared unavailable.
- Action:
- Check for related server log messages that may provide additional detail regarding the state of the resource. If the resource is undeployed, deploy the resource or the application module if the resource is application scoped. If a problem exists with the resource manager, correct the problem and redeploy the resource.
- BEA-110488
- The LLR resource(s) {0} are not available and may contain transaction commit records required for recovery processing. Recovery of XA resources will not occur until these resources are deployed.
- Category:
- JTA
- Cause:
- Prior to server restart, one or more global transactions were processed that had a LLR participant and may not have completed before the server was restarted. This potentially left a commit record in a LLR resource and prepared resource transaction branches that are awaiting a commit or rollback decision from the coordinator.
- Action:
- Redeploy the specified LLR resources, wait for all in progress transactions to complete, and shut down the server gracefully.
- BEA-110490
- User [{0}] is not authorized to invoke Commit on a Coordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack, or alternately, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110491
- User [{0}] is not authorized to invoke AckPrePrepare on a Coordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110492
- User [{0}] is not authorized to invoke CheckStatus on a Coordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110493
- User [{0}] is not authorized to invoke AckCommit on a Coordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110494
- User [{0}] is not authorized to invoke NakCommit on a Coordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110495
- User [{0}] is not authorized to invoke AckRollback on a Coordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110496
- User [{0}] is not authorized to invoke NakRollback on a Coordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110500
- User [{0}] is not authorized to invoke GetSubCoordinatorInfo on a SubCoordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110501
- User [{0}] is not authorized to invoke GetProperties on a SubCoordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110502
- User [{0}] is not authorized to invoke Recover on a SubCoordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-110503
- The migrator (the Administration Server for manual JTA migration policy or the Singleton Master for automatic JTA migration policy) is not available. Will skip JTA TRS failback because isStrictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if the TRS of {0} has been migrated to a backup server and the backup server is accessing the TLOG of {0}. More safety can be achieved by setting isStrictOwnershipCheck to [true].
- Category:
- JTA
- Cause:
- The Administration Server or Singleton Master is not running or cannot be reached.
- Action:
- Start Administration Server or Singleton Master before starting any Managed Server in the cluster.
- BEA-110504
- There was an error advertising TransactionSynchronizationRegistry object: {0}.
- Category:
- JTA
- Cause:
- There may be a problem with the JNDI provider or another object is already bound to this context.
- Action:
- Contact My Oracle Support.
- BEA-110505
- An attempt was made to set an invalid TRANSACTION_COMPLETION_TIMEOUT_SECONDS_PROPERTY_KEY for transaction property: keys must be number and values must be between -1 and max value of integer.
- Category:
- JTA
- Cause:
- See the message detail.
- Action:
- Change the application to assign the proper TRANSACTION_COMPLETION_TIMEOUT_SECONDS_PROPERTY_KEY property value.
- BEA-111001
- The Transaction Manager is being started in standalone mode and will not be able to participate in distributed transactions.
- Category:
- JTA
- Cause:
- There are no suitable RMI or JNDI providers configured.
- Action:
- Configure the appropriate RMI and JNDI context providers.
- BEA-111002
- The Transaction Manager is being started in distributed mode.
- Category:
- JTA
- Cause:
- The Transaction Manager is in distributed mode and can participate in distributed transactions.
- Action:
- No action is required.
- BEA-111003
- An error occurred while creating the transaction log persistent store: {1}.
- Category:
- JTA
- Cause:
- Refer to the associated exception for the cause.
- Action:
- No action is required.
- BEA-111004
- Transaction could not set CoordinatorURL to use AdminChannel downgrading {0}.
- Category:
- JTA
- Cause:
- An error occurred while trying to set CoordinatorURL to use AdminChannel.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-111005
- An in-progress XA operation for transaction {0} on resource {1} could not complete within {2} seconds, or was interrupted. Allowing subsequent calls to proceed.
- Category:
- JTA
- Cause:
- The call to the resource manager may have been affected by a server or network problem and could have been interrupted.
- Action:
- Verify that the resource manager is functioning properly and is accessible.
- BEA-111006
- Transaction could not set CoordinatorURL to use SSL URL downgrading {0}
- Category:
- JTA
- Cause:
- An error occurred while trying to set CoordinatorURL to use the SSL port.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-111007
- The commit operation for one-phase transaction {0} on resource {1} encountered an error. {2}
- Category:
- JTA
- Cause:
- Refer to the resource exception in the error message and any appropriate resource-specific error logs.
- Action:
- Determine if administrative operations are required in the resource to resolve the transaction branch.
- BEA-111008
- Transaction Log failed during initialization. The server cannot boot unless Transaction Log initialize. Failing reason: {0}
- Category:
- JTA
- Cause:
- The transaction log may contain transaction records for committed two-phase transactions that have not completed committing all resources involved in the transaction..
- Action:
- Check for other log messages that give more information about the failure.
- BEA-111009
- activateDeployments failed during initialization. Failing reason: {0}
- Category:
- JTA
- Cause:
- During WLS start up, an exception was caught at activateDeployemts.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-111010
- SetPrimaryStore failed. Failing reason: {0}
- Category:
- JTA
- Cause:
- An exception was caught at setPrimaryStore.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-111011
- A Transaction Log PrimaryStore failed during initialization. The server cannot boot unless configured Transaction Log Primary Store initialize. Failing reason: {0}
- Category:
- JTA
- Cause:
- The Transaction Log Primary Store may contain transaction records for committed two-phase transactions that have not completed committing all resources involved in the transaction.
- Action:
- Examine the root exception thrown by the Transaction Log Primary Store to determine the root cause of the problem.
- BEA-111012
- SetPrimaryStore close failed when retry. Failing reason: {0}
- Category:
- JTA
- Cause:
- An exception was caught at close store in retrying setPrimaryStore .
- Action:
- Check for other log messages that give more information about the failure.
- BEA-111013
- Recover JDBCStore init store exception: {0}
- Category:
- JTA
- Cause:
- An exception occurred when init store.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-111014
- There is a naming conflict for resource = [{0}]. This resource is being registered by this server and has already been registered in: [{1}].
- Category:
- JTA
- Cause:
- This resource is trying to be registered as a NonXAResource but was already registered as an XAResource.
- Action:
- Correct the configuration either by making the resource name unique or by making the resource consistently either an XAResource or a NonXAResource.
- BEA-111015
- The commit operation for transaction {0} timed out after {1} seconds.
- Category:
- JTA
- Cause:
- The application may take longer than the time that is specified in timeout-seconds in the JTA parameter before issuing the commit.
- Action:
- Increase the transaction timeout-seconds in the JTA parameter or tuning application.
- BEA-111016
- Recovery is not possible as determiner resource can not be obtained {0}.
- Category:
- JTA
- Cause:
- Determiner resource may have been removed or is otherwise unobtainable.
- Action:
- Insure determiner resource can be obtained and has not been removed.
- BEA-111017
- Encountered an exception while attempting to acquire a transaction manager for transactional annotation interceptors {0}.
- Category:
- JTA
- Cause:
- Examine the root exception to determine the cause of the problem.
- Action:
- Take appropriate action based on the cause.
- BEA-111018
- No ComponentInvocation is present for @Transactional annotation processing. The restriction on use of UserTransaction will not be enforced.
- Category:
- JTA
- Cause:
- No ComponentInvocation is present for @Transactional annotation processing.
- Action:
- No action is required.
- BEA-111019
- The server has detected pending transactions after graceful shutdown in ClientInitiatexTxShutdownService.stop. Continue to work.
- Category:
- JTA
- Cause:
- The server has detected pending transactions after graceful shutdown in ClientInitiatexTxShutdownService.stop. Continue to work.
- Action:
- No action is required. Use a forced shutdown command to ignore inflight work and shut down the server immediately.
- BEA-111020
- An issue occurred during cross-site recovery processing: {0}.
- Category:
- JTA
- Cause:
- A lease store connection or other failures has occurred.
- Action:
- Refer to logs for information on the cause of failure.
- BEA-111021
- The JTA Security Interoperability Mode value "compatibility" is deprecated. Use "default" or "performance" instead.
- Category:
- JTA
- Cause:
- The domain JTA configuration specifies a value of "compatibility" for Security Interoperability Mode.
- Action:
- Modify the domain JTA configuration to specify a value of "default" or "performance" for Security Interoperability Mode.
- BEA-114089
- User [{0}] is not authorized to invoke ackPrepare on a Coordinator.
- Category:
- JTA
- Cause:
- This might be a symptom of a potential security attack or, alternatively, a problem with the "system" security identity of the server.
- Action:
- Verify that the client software is not directly invoking an internal WebLogic Server system object.
- BEA-119000
- One-phase transaction [{1}] for logging last resource [{0}] is in an unknown state.
- Category:
- JTAExceptions
- Cause:
- If the LLR is a database, there are a number of possible root causes. Among them are: the database may have shut down or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potential deadlock condition introduced by application operations within the local commit.
- Action:
- Examine the root exception generated by the LLR to determine the root cause of the problem.
- BEA-119001
- Two-phase transaction [{1}] for logging last resource [{0}] is in an unknown state.
- Category:
- JTAExceptions
- Cause:
- If the LLR is a database, there are a number of possible root causes. Among them are: the database may have shut down or crashed during the call to local commit, the database connection may have failed, the database local transaction may have timed out, or the database may have detected a potential deadlock condition introduced by application operations within the local commit.
- Action:
- Examine the root exception generated by the LLR resource to determine the root cause of the problem.
- BEA-119002
- A LLR failed during initialization. The server cannot boot unless all configured LLRs initialize. Failing reason: {0}
- Category:
- JTAExceptions
- Cause:
- If the LLR is a JDBC LLR connection, there are a number of possible root causes. Among them are: the database may have shut down or crashed, the database connection may have failed during boot, or the database connection may have incorrect database permissions.
- Action:
- Examine the root exception generated by the LLR resource to determine the root cause of the problem.
- BEA-119003
- LLR [{0}] failed during initialization, as one of its records is corrupted. Failure reason: {1}
- Category:
- JTAExceptions
- Cause:
- The cause is unknown, but could be possible disk corruption.
- Action:
- Examine the root exception generated by the LLR to determine the root cause of the problem. Possible solutions are: restore LLR resource tables from backup, delete the failing LLR table (which risks producing heuristic hazards), or contact My Oracle Support.
- BEA-119004
- The user-preferred server of JTAMigratableTargetMBean [{0}] cannot be set to [{1}].
- Category:
- JTAExceptions
- Cause:
- The value of the user-preferred server is invalid. It must be [{0}].
- Action:
- Change the value of the user-preferred server of JTAMigratableTargetMBean [{0}] from [{1}] to [{0}].
- BEA-119005
- JTA subsystem failed. A forced shutdown of the server was done because the server is in automatic JTA migration mode.
- Category:
- JTAExceptions
- Cause:
- The JTA subsystem failed.
- Action:
- JTA Transaction Recovery Service will be automatically migrated to back up the server.
- BEA-119006
- A Transaction Log Primary Store failed during initialization. The server cannot boot unless the configured Transaction Log Primary Store initialize. Failing reason: {0}
- Category:
- JTAExceptions
- Cause:
- See the message detail.
- Action:
- Examine the root exception generated by the Transaction Log Primary Store to determine the root cause of the problem.
- BEA-130000
- Insertion of {0} into XML entity cache rejected. Entity size, {1}, exceeded cache size, {2}.
- Category:
- XML
- Cause:
- The cache may be too small or a specific item might be very large. The worst case is that this indicates a denial of service attack.
- Action:
- No action is required. However, performance will be best if items are cached.
- BEA-130001
- Entity cache appears to be broken. This impacts the performance of XML parsing.
- Category:
- XML
- Cause:
- Unknown
- Action:
- No action is required. However, performance will increase if items are cached. Also the cache provides a backup in the case of a network failure. While the cache is not operating, this backup is not in effect.
- BEA-130002
- The entity that was just put in the cache cannot be retrieved: "{0}". Timeout may be too short.
- Category:
- XML
- Cause:
- Usually this indicates that the entity timeout was set to a very small value. Otherwise, there is some unknown problem with the cache module itself.
- Action:
- No action is required, but XML parse performance will be impacted. Also, there is no cached copy to act as a backup in the event of a network failure.
- BEA-130003
- Could not instantiate the specified factory class. {0}.
- Category:
- XML
- Cause:
- The class name of the factory was not correct or it was not in the CLASSPATH.
- Action:
- Check the CLASSPATH or verify the Administration Console entry or MBean value.
- BEA-130006
- XML cache warning for registry {0}: entry rejection due to entry being larger than the cache memory size. entry: {1} Entry memory size: {2}
- Category:
- XML
- Cause:
- The entry is larger than the cache.
- Action:
- No action is required unless the item should be cached next time. If so, increase the cache memory size.
- BEA-130007
- XML cache event: memory purge of {0} entries of combined size {1}. Current memory usage is {2} bytes.
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130008
- XML cache event: disk purge of {0} entries of combined size {1}. Current disk usage is {2} bytes.
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130009
- XML cache warning for registry {0}: entry persist attempt rejected due to entry being larger than the cache disk size. Status changed to transient. entry: {1} entry disk size: {2}
- Category:
- XML
- Cause:
- The size of the entry on the disk exceeds the allocated disk space.
- Action:
- No action is required. If the entry should be persisted next time, increase the disk size of the cache.
- BEA-130010
- XML cache event for registry {0}: entry added. entry: {1}, entry memory size: {2}, storage type: {3}, current memory usage (bytes): {4}
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130011
- XML cache event for registry {0}: entry deleted. entry: {1}, entry memory size: {2}, entry disk size: {3}, current memory usage (bytes): {4}, current disk usage (bytes): {5}
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130012
- XML cache event for registry {0}: entry persisted. entry: {1}, entry disk size: {2}, current disk usage (bytes): {3}
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130013
- XML cache event for registry {0}: entry loaded. entry: {1}, entry memory size: {2}, current memory usage (bytes): {3}
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130014
- XML cache event: statistics checkpointed.
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130015
- XML cache event: cache created. current memory usage (bytes): {0}, current disk usage (bytes): {1}
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130016
- XML cache event: cache loaded. Current memory usage (bytes): {0}, current disk usage (bytes): {1}
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130017
- XML cache event: cache closed. current disk usage (bytes): {0}
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130018
- XML cache error: cache file {0} is corrupted. Creating new cache from scratch.
- Category:
- XML
- Cause:
- The cache file was corrupted. This normally does not occur.
- Action:
- The server should be restarted. If a backup of the cache files exists, restore the cache files, and then restart the server.
- BEA-130019
- XML cache error for registry {0}: entry file {1} is corrupted. Removing from cache. entry: {2}
- Category:
- XML
- Cause:
- The cache file was corrupted. This normally does not occur.
- Action:
- The server should be restarted. The entry will be re-cached on the next access of the server.
- BEA-130020
- XML cache error: statistics file {0} is corrupted, reinitializing. Previous statistics are lost.
- Category:
- XML
- Cause:
- The cache file was corrupted. This normally does not occur.
- Action:
- The server should be restarted.
- BEA-130021
- XML cache error for registry {0}: entry file {1} cannot be written. Status changed to transient. entry: {2}
- Category:
- XML
- Cause:
- This is often a file protection issue.
- Action:
- Determine why the file cannot be saved and make the appropriate adjustments.
- BEA-130022
- XML cache error: cache file {0} cannot be written.
- Category:
- XML
- Cause:
- This is often a file protection issue.
- Action:
- Determine why the file cannot be saved and make the appropriate adjustments.
- BEA-130023
- XML cache error: statistics file {0} cannot be written. There are no futher cache statistics for this session.
- Category:
- XML
- Cause:
- This is often a file protection issue.
- Action:
- Determine why the file cannot be saved and make the appropriate adjustments.
- BEA-130024
- XML cache error for registry {0}: out of memory loading entry. Entry removed from cache. entry: {1}, file: {2}
- Category:
- XML
- Cause:
- The entry might be unusually large or perhaps the JVM heap size is too small.
- Action:
- Check the size of the rejected entry. If entries of that size need to be handled, increase the heap size.
- BEA-130025
- XML cache error: out of memory loading cache. Cache not opened. file: {0}
- Category:
- XML
- Cause:
- The cache file is not large, so memory usage is almost full.
- Action:
- Increase the JVM heap size.
- BEA-130026
- XML cache error: out of memory loading statistics. File: {0}
- Category:
- XML
- Cause:
- The cache file is not large, so memory usage is almost full.
- Action:
- Increase the JVM heap size.
- BEA-130027
- XML cache warning: the requested memory size of the XML cache, {0}, exceeds the available memory, {1}.
- Category:
- XML
- Cause:
- Either the provided parameters are not in sync with the usage, or a lot of the available memory is being used.
- Action:
- Reduce the cache size or increase the JVM heap size. If there should be more available memory, determine what is using all of the available memory.
- BEA-130028
- XML cache warning: the requested memory size of the XML cache, {0}, is a large percentage of the available memory, {1}.
- Category:
- XML
- Cause:
- Either the provided parameters are not in sync with the usage, or something is using a lot of the available memory.
- Action:
- Reduce the cache size or increase the JVM heap size. If there should be more available memory, determine what is using all of the available memory.
- BEA-130029
- XML cache error: an unexpected error occurred in the XML cache. {0}
- Category:
- XML
- Cause:
- The cause is unknown.
- Action:
- Refer to the associated text at the end of the message and contact My Oracle Support for help resolving the error.
- BEA-130030
- XML cache error for registry {0}: the file, {1}, representing entry {2} cannot be read.
- Category:
- XML
- Cause:
- The file is read-protected.
- Action:
- Check the access rights of the file and make the appropriate changes.
- BEA-130031
- XML cache error: the cache file, {0}, cannot be read.
- Category:
- XML
- Cause:
- The file is read-protected.
- Action:
- Check the access rights of the file and make the appropriate changes.
- BEA-130032
- XML cache error: statistics file {0} cannot be read.
- Category:
- XML
- Cause:
- The file is read-protected.
- Action:
- Check the access rights of the file and make the appropriate changes.
- BEA-130033
- Parser or DocumentBuilder cannot be created to satisfy the configuration requested. {0}
- Category:
- XML
- Cause:
- The configuration was invalid.
- Action:
- Verify that the factory that creates the parser and the properties or features set on this parser are configured properly.
- BEA-130034
- Failed to parse the given XML document. {0}
- Category:
- XML
- Cause:
- An error occurred in the structure of the XML document.
- Action:
- Verify the XML syntax of the document.
- BEA-130035
- Failed to open XML document. {0}
- Category:
- XML
- Cause:
- The file does not exist.
- Action:
- Check the file name, the file location and its associated permissions.
- BEA-130036
- Initializing XMLRegistry
- Category:
- XML
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-130037
- The stack trace associated with message {0} follows:
- Category:
- XML
- Cause:
- An error condition was reported.
- Action:
- No action is required.
- BEA-130039
- The warning message:
- Category:
- XML
- Cause:
- An warning condition was reported.
- Action:
- No action is required.
- BEA-140008
- Internal error. Failed to save configuration changes to the configuration repository - {0}.
- Category:
- Management
- Cause:
- The config.xml file is either write-protected, or the user that started the server is not authorized to write to this file or directory.
- Action:
- Ensure that the operating system user who starts the server has authorization to write to the config.xml file and that the config.xml file is not write-protected.
- BEA-140013
- {0}
- Category:
- Management
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-141009
- Error occurred in the file distribution servlet while processing the request type "{0}", {1}.
- Category:
- Management
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Take action based upon the provided exception details.
- BEA-141010
- Error occurred in the file distribution servlet and received an unacceptable request of type "{0}".
- Category:
- Management
- Cause:
- An invalid request was made to the file distribution servlet.
- Action:
- This is an internal WebLogic Server error. No action is required.
- BEA-141011
- The file distribution servlet failed to distribute the security properties file, because the file was not found at the configured location: {0}.
- Category:
- Management
- Cause:
- The identified file was not available to the Administration Server.
- Action:
- Verify the configuration of this file.
- BEA-141021
- The cluster property {0} was ignored because the server is not part of a cluster.
- Category:
- Management
- Cause:
- A non-applicable cluster property was specified at server startup.
- Action:
- Modify the configuration to identify that this Managed Server is, in fact, a member of a cluster, or eliminate the specification of the cluster property from the start command.
- BEA-141023
- An error occurred while setting the attribute value in the MBean proxy {0}, method {1} with value {2} ({3}).
- Category:
- Management
- Cause:
- An invalid attribute value was specified.
- Action:
- Verify that the provided attribute value (specified either in the configuration or through a dynamic setting) is correct.
- BEA-141051
- The operation failed with message: {0}.
- Category:
- Management
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Take action based upon the details of the provided error message.
- BEA-141052
- The auto deployment poller has started.
- Category:
- Management
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-141053
- The auto deployment poller has not started for the production server.
- Category:
- Management
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-141062
- The user does not have permission to perform {1} operation on MBean {0}. Method = {3}, attribute = {2}
- Category:
- Management
- Cause:
- No access control list (ACL) permissions are defined for the user to complete this operation.
- Action:
- The system administrator must add ACL permissions in order for the user to perform this operation.
- BEA-141063
- The user does not have permission to perform {1} operation on MBean {0}. Method: {2}.
- Category:
- Management
- Cause:
- The user has no defined access control list (ACL) to perform this MBean operation.
- Action:
- The system administrator must define permissions in order for the user to perform this MBean operation.
- BEA-141071
- The file distribution servlet failed to distribute the embedded LDAP initial replica data file because the file was not found at the configured location: {0}.
- Category:
- Management
- Cause:
- This is an internal WebLogic Server error that should not occur during normal operation.
- Action:
- Contact My Oracle Support.
- BEA-141073
- Migration task ({0}) - {1}
- Category:
- Management
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-141076
- No module with URI ({1}) was found in ({0}).
- Category:
- Management
- Cause:
- The application is potentially misconfigured relative to this module.
- Action:
- Verify that the application archive and its descriptors are correctly configured.
- BEA-141077
- An error occurred during the parsing of descriptors for {0}. Exception {1} occurred.
- Category:
- Management
- Cause:
- Refer to the exception details for the exact cause of this parsing error.
- Action:
- Take action based upon provided exception details to either correct the identified component or its descriptors.
- BEA-141078
- A descriptor initialization error occurred for module {0} in EAR file {1}. Creation of the temporary file {2} failed.
- Category:
- Management
- Cause:
- The extraction of the EAR file failed due to an I/O error. See the logged for details.
- Action:
- Ensure that the file referred to in the exception can be created, and there is no directory by the same name.
- BEA-141081
- The file distribution servlet failed to distribute the embedded LDAP initial replica data file due to the following error: {0}.
- Category:
- Management
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Take action based upon the provided exception details.
- BEA-141086
- An error occurred while setting a value for {0}.
- Category:
- Management
- Cause:
- The specified command line property provided an invalid value for attribute {0}.
- Action:
- Verify that the specified command line property provides a valid attribute value.
- BEA-141087
- Property: {0} is not a recognized MBean attribute or special property used for management. It is most likely being used by subsystems and will continue to work as expected if it is a supported option.
- Category:
- Management
- Cause:
- An unrecognized property has been specified on the start command.
- Action:
- Eliminate the invalid properties from the start command.
- BEA-141089
- Starting the server based on the WebLogic Server 6.x configuration directory structure.
- Category:
- Management
- Cause:
- The startup directory does not contain the config.xml configuration file. The file was located in the config/domain directory.
- Action:
- Start the server from the directory that contains the domain configuration file.
- BEA-141102
- Subject: {0} does not have access to perform {1} actions.
- Category:
- Management
- Cause:
- Either the named subject is not allowed to perform this action and is appropriately being denied this access, or the named subject should be allowed to perform this action and the role membership of the subject is not properly configured.
- Action:
- Contact the system administrator to modify role definitions.
- BEA-141107
- Version: {0}
- Category:
- Management
- Cause:
- This is normal system initialization processing.
- Action:
- No action is required.
- BEA-141124
- An invalid system property was specified while booting the server {0}.
- Category:
- Management
- Cause:
- The server might have been started using an invalid system property. For example, starting the server using java -D weblogic.Server will generate this exception.
- Action:
- Correct the invalid system property.
- BEA-141126
- The configuration file {0} is read-only.
- Category:
- Management
- Cause:
- This occurs when the write permissions on the file are not set to allow the user that booted the server to write to the config.xml file. Write access is often intentionally denied in production environments.
- Action:
- In many cases, write access is intentionally denied. In such cases, this is just an informational message. If the file needs to be writable, change the permissions on the file or ask the system administrator to do so.
- BEA-141133
- The Name attribute cannot be modified after the MBean {0} has been created.
- Category:
- Management
- Cause:
- The Name attribute is being modified by a setName operation.
- Action:
- Specify the name of the MBean during creation.
- BEA-141145
- An attempt was made to connect to the Administration Server without credentials.
- Category:
- Management
- Cause:
- The requirement to supply credentials on all requests was added in version 8.1 of the product. It is most likely that an old version of a utility is being used that is not properly supplying these credentials. It is also possible that this represents an attempt to compromise the server.
- Action:
- Determine the source of the request. If it is a legitimate request, ensure that updated software is being used which properly supplies the credentials. It is also important to restrict access to the Administration Server. Refer to the WebLogic Server documentation to ensure that all of the proper security precautions have been taken.
- BEA-141146
- An attempt was made to connect to the Administration Server by the user {0} and a password which does not match.
- Category:
- Management
- Cause:
- The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the password is not valid for the specified user. This may be the result of supplying an improper user name and password when using the deployment utilities.
- Action:
- Determine the source of the request. If it is a legitimate request, ensure that updated software which properly supplies the credentials is in use. It is also important to restrict access to the Administration Server. Refer to the WebLogic Server documentation to ensure that all of the proper security precautions have been taken.
- BEA-141147
- An attempt was made to upload a file to the Administration Server by the unauthorized user {0}.
- Category:
- Management
- Cause:
- The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the user specified is not configured with the authorization to upload files.
- Action:
- To enable the user to upload files to the Administration Server, it is necessary that the user be added to the administrator or deployer role. Alternatively, it is possible to authorize a user specifically for "FileUpload". Consult the WebLogic Server documentation for instructions on how to do this.
- BEA-141148
- An invalid attempt was made to download a {1} resource from the Administration Server by the unauthorized user {0}.
- Category:
- Management
- Cause:
- The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the credentials of the user that is being used to boot the Managed Server are used to authorize the request. That user is not authorized to access files of the type {1}.
- Action:
- Ensure that the proper credentials are being used to initiate the connection. In most cases, this involves ensuring that the credentials being used to boot the Managed Server are properly authorized on the Administration Server.
- BEA-141149
- An invalid attempt was made to connect to the Administration Server with a salt of {0} and a signature of {1}, likely due to private key mismatch or clock skew between servers.
- Category:
- Management
- Cause:
- The requirement to supply credentials on all requests was added in version 8.1 of the product. In this case, the password is not valid for the specified user or the nonce has expired. This may be the result of supplying an improper user name and password when using the deployment utilities.
- Action:
- Determine the source of the request and ensure that the Managed Server and the Administration Server share the same security credential. That credential is stored in the domain configuration and distributed at server startup. In this case, where the Managed Server is booted using a configuration that is different from that of the Administration Server, perhaps in Managed Server independence mode. Refer to the WebLogic Server documentation to ensure that all of the proper security precautions have been taken. Verify that clock skew has not occurred between the servers in the domain.
- BEA-141151
- The Administration Server could not be reached at {0}.
- Category:
- Management
- Cause:
- The Administration Server is not available at the specified URL or the URL is not specified in the correct format, such as http://myhost:7001.
- Action:
- Ensure that the Administration Server is running at the specified host and port. Check that the URL is specified in the correct format. The URL is specified by the protocol://host:port, for example http://myhost:7001.
- BEA-141187
- Java system properties are defined as follows: {0}.
- Category:
- Management
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-141190
- The commit phase of the configuration update failed with an exception.
- Category:
- Management
- Cause:
- An exception occurred during the commit of the update.
- Action:
- Retry the activate. Take action based upon the provided exception details.
- BEA-141191
- The prepare phase of the configuration update failed with an exception.
- Category:
- Management
- Cause:
- An exception occurred during the prepare of the update.
- Action:
- Ensure that the update is valid. Take action based upon the provided exception details, make any required changes, change the changes, and retry the activate.
- BEA-141192
- The read of the edit lock file failed with an exception.
- Category:
- Management
- Cause:
- An exception occurred during the read of the edit lock file.
- Action:
- Take action based upon the provided exception details. Try to get the edit lock again.
- BEA-141193
- The write of the edit lock file failed with an exception.
- Category:
- Management
- Cause:
- An exception occurred during the write of the edit lock file.
- Action:
- Take action based upon the provided exception details. Try to get the edit lock again.
- BEA-141194
- The registration of the configuration subsystem with the deployment subsystem failed with an exception.
- Category:
- Management
- Cause:
- An exception occurred during the registration of the configuration subsystem.
- Action:
- Take action based upon the provided exception details. Restart the server.
- BEA-141196
- The Managed Server could not update the configuration files during the registration with the deployment service. The update failed due to an exception.
- Category:
- Management
- Cause:
- An exception occurred during the update of configuration files.
- Action:
- Take action based upon the provided exception details, make any required changes, and try to restart the Managed Server.
- BEA-141197
- The deployment of {0} failed.
- Category:
- Management
- Cause:
- An exception occurred during a resource deployment.
- Action:
- Take action based upon the provided exception details, make any required changes, and try to restart the Managed Server.
- BEA-141198
- The undeployment of {0} failed.
- Category:
- Management
- Cause:
- An exception occurred during a resource undeployment.
- Action:
- Take action based upon the provided exception details, make any required changes, and try to restart the Managed Server.
- BEA-141199
- In the compatibility MBean server, the operation {1} on the MBean {0} modified the configuration without starting an edit session and activating the changes.
- Category:
- Management
- Cause:
- The impact information was incorrect for the MBean operation.
- Action:
- Contact My Oracle Support as this is an internal coding error that should not occur.
- BEA-141200
- Detected a domain that was created from an earlier release of WebLogic Server. The domain will be upgraded to the current {0} release.
- Category:
- Management
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-141201
- Unable to modify the configuration using the compatibility MBean server, as other changes are pending. Activate the pending changes before modifying the configuration with the compatibility MBean server.
- Category:
- Management
- Cause:
- The configuration was not modified because pending changes were present.
- Action:
- Activate the changes before using the compatibility server.
- BEA-141202
- The addition of the bean {0} failed during the activate phase because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141203
- The addition of the bean {0} failed during the activate phase because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141204
- The addition of the bean {0} failed during the activate phase because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141205
- The removal of the bean {0} failed during the activate phase because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141206
- The removal of the bean {0} failed during the activate phase because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141207
- The removal of the bean {0} failed during the activate phase because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141208
- The modification of the property {0} failed during the activate phase because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141209
- The modification of the property {0} failed during the activate phase because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141210
- The modification of the property {0} failed during the activate phase because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141211
- An attempt to initialize the property {0} failed because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information on the cause of this error.
- Action:
- The exception message may have more information about the action to take.
- BEA-141212
- An attempt to initialize the property {0} failed because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information on the cause of this error.
- Action:
- The exception message may have more information about the action to take.
- BEA-141213
- An attempt to initialize the property {0} failed because of {1}
- Category:
- Management
- Cause:
- See the exception message for more information on the cause of this error.
- Action:
- The exception message may have more information about the action to take.
- BEA-141214
- The add of the bean {0} failed. The encountered exception was {1}
- Category:
- Management
- Cause:
- See the exception message for more information on the cause of this error.
- Action:
- The exception message may have more information about the action to take.
- BEA-141215
- The add of the bean {0} failed. The encountered exception was {1}
- Category:
- Management
- Cause:
- See the exception message for more information on the cause of this error.
- Action:
- The exception message may have more information about the action to take.
- BEA-141216
- The add of the bean {0} failed. The encountered exception was {1}
- Category:
- Management
- Cause:
- See the exception message for more information on the cause of this error.
- Action:
- The exception message may have more information about the action to take.
- BEA-141217
- The removal of the bean {0} failed. The encountered exception was {1}
- Category:
- Management
- Cause:
- See the exception message for more information on the cause of this error.
- Action:
- The exception message may have more information about the action to take.
- BEA-141218
- The removal of the bean {0} failed. The encountered exception was {1}
- Category:
- Management
- Cause:
- See the exception message for more information on the cause of this error.
- Action:
- The exception message may have more information about the action to take.
- BEA-141219
- The removal of the bean {0} failed. The encountered exception was {1}
- Category:
- Management
- Cause:
- See the exception message for more information on the cause of this error.
- Action:
- The exception message may have more information about the action to take.
- BEA-141220
- A required class was not found while upgrading the domain. This could be possible if the security provider JAR files were not upgraded to conform with WebLogic Server version 9.0. Upgrade these providers using java weblogic.Upgrade -type securityproviders.
- Category:
- Management
- Cause:
- The security provider JAR files were not upgraded to conform with new WebLogic Server 9.0 classes.
- Action:
- Run the upgrade tool to upgrade the provider.
- BEA-141221
- An error occurred while performing an undo of unactivated changes in the compatibility MBean server: {0}.
- Category:
- Management
- Cause:
- See the exception message for more information.
- Action:
- Check the exception message for more detail.
- BEA-141223
- The server name {0} specified with -Dweblogic.Name does not exist. The configuration includes the following servers {1}.
- Category:
- Management
- Cause:
- The -Dweblogic.Name command line property specifies a server that does not exist in the configuration.
- Action:
- Check the configuration for the list of configured servers.
- BEA-141224
- The Administration Server is not reachable.
- Category:
- Management
- Cause:
- This could be a network issue.
- Action:
- Check the status of the Administration Server.
- BEA-141225
- The delete of pending directory file {0} failed.
- Category:
- Management
- Cause:
- An error occurred while deleting the file.
- Action:
- Ensure that no processes have the file open for write.
- BEA-141226
- An invalid deployment service prepare callback with ID {0} was received.
- Category:
- Management
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-141227
- Making a backup copy of the configuration at {0}.
- Category:
- Management
- Cause:
- This happens during certain server lifecycle transitions and during configuration changes.
- Action:
- No action is required.
- BEA-141228
- An attempt to back up the configuration to {0} failed with {1}.
- Category:
- Management
- Cause:
- See the message text for the exception message.
- Action:
- Check the exception information included in the message text.
- BEA-141229
- The upgrade process has been canceled by the user. The server process will not be started.
- Category:
- Management
- Cause:
- The server startup cannot proceed without upgrading the domain.
- Action:
- Upgrade the domain, and then start the server.
- BEA-141230
- Could not locate the descriptor file for System Resource: {0}.
- Category:
- Management
- Cause:
- The descriptor file could not be located in the specified path.
- Action:
- Ensure that the descriptor file is in the appropriate location.
- BEA-141231
- Could not register the JSR object: {0}.
- Category:
- Management
- Cause:
- There are many possible causes for this warning.
- Action:
- Look at the stack trace and take appropriate action.
- BEA-141232
- Could not decrypt the {1} attribute value of {2} from the file {0}. The edit session has been canceled. The decryption failed with the exception {3}.
- Category:
- Management
- Cause:
- An invalid encrypted value was found in the edit lock file.
- Action:
- Start a new edit session.
- BEA-141233
- Could not decrypt the edit lock file {0}. The edit session has been canceled. The decryption failed with the exception {1}.
- Category:
- Management
- Cause:
- An exception occurred when decrypting the edit lock file.
- Action:
- Start a new edit session.
- BEA-141234
- A rollback of a dynamic change failed. The message for the failure is "{0}". The cause of the exception is "{1}".
- Category:
- Management
- Cause:
- See the message body for the cause.
- Action:
- Look at the possible causes of this error. The cause may give some indication of the possible actions to take.
- BEA-141237
- Extraneous text found in the config.xml file: {0}.
- Category:
- Management
- Cause:
- This is generally caused by mistakes in hand-edited config.xml files. The config.xml file is a valid XML document, however, the extraneous text is not related to any MBean attributes.
- Action:
- Review the config.xml file for mistakes, such as extra delimeters near the text listed in the error message.
- BEA-141238
- A non-dynamic change has been made which affects the server {0}. This server must be rebooted in order to consume this change.
- Category:
- Management
- Cause:
- This happens when one or more of the changes made to the configuration affect non-dynamic settings. When this occurs, the affected Managed Servers are determined, and those servers are not updated when the change is activated. In order to consume the change, these servers must be rebooted.
- Action:
- Reboot the named server.
- BEA-141239
- The non-dynamic attribute {1} on {0} has been changed. This may require redeploying or rebooting configured entities.
- Category:
- Management
- Cause:
- This happens when one or more of the changes made to the configuration affect non-dynamic settings.
- Action:
- The required action, if any, will be indicated in a later log message.
- BEA-141240
- Found a version {0} config.cml file, but expected a version 9 or higher config.xml file. This could happen if an attempt to boot was made from the config directory rather than the domain root.
- Category:
- Management
- Cause:
- This could happen if an attempt was made to boot from the config directory rather than the domain root. Otherwise, the configuration could be corrupted.
- Action:
- Ensure that the config.xml file is not corrupted and that the boot is attempted from the domain root.
- BEA-141241
- Found a version {0} config.xml file, but expected a pre-version 9 config.xml file. This could happen if an attempt was made to boot from the config directory rather than the domain root.
- Category:
- Management
- Cause:
- This could happen if a 9.x config.xml file was put in the top level, rather than in the config directory.
- Action:
- Ensure that the config.xml file is in the correct location in the domain.
- BEA-141242
- Invalid configuration version found at {1} version = {0}.
- Category:
- Management
- Cause:
- WebLogic Server found a config.xml file with a version that does not match any known version of the product.
- Action:
- Ensure that the version string in the config.xml file is valid.
- BEA-141243
- The property {0} in element {1} has been deprecated in version {2} - {3}.
- Category:
- Management
- Cause:
- The config.xml file contained elements that have been deprecated.
- Action:
- Replace or remove the deprecated configuration artifacts.
- BEA-141244
- Schema validation errors while parsing {0} - {1}.
- Category:
- Management
- Cause:
- The WebLogic Server configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal, depending on the setting of the system property weblogic.configuration.schemaValidationEnabled.
- Action:
- See the error details for more information on the validation problem.
- BEA-141245
- Schema validation error in {0}. See the log for details. Schema validation can be disabled by starting the server with the command line option: {1}.
- Category:
- Management
- Cause:
- The WebLogic Server configuration files are defined by a schema. When parsing these files, they are validated against the schema. This warning indicates that there were problems found during validation. The problems may or may not be fatal, depending on the setting of the system property weblogic.configuration.schemaValidationEnabled.
- Action:
- See the error details for more information on the validation problem.
- BEA-141246
- The configuration directory {0} does not exist.
- Category:
- Management
- Cause:
- The server was booted from a directory that does not contain a configuration directory.
- Action:
- Ensure that the server is booted from a valid domain directory.
- BEA-141247
- The configuration directory {0} does not exist, and the Administration Server is not available.
- Category:
- Management
- Cause:
- The configuration directory is missing and the Administration Server is not available to download a copy. In this case, the Managed Server cannot boot.
- Action:
- Ensure that either the server is booted from a valid domain directory or that the Administration Server is available.
- BEA-141248
- The configuration directory {0} is missing the file {1}.
- Category:
- Management
- Cause:
- The server was booted from a directory that does not contain a valid domain configuration.
- Action:
- Ensure that the server is booted from a valid domain directory.
- BEA-141249
- The configuration directory {0} is missing the file {1}, and the Administration Server is not available to download it.
- Category:
- Management
- Cause:
- The server was booted from a directory that does not contain a valid configuration, and the Administration Server is unavailable to download the current configuration files.
- Action:
- Ensure that either the server is booted from a valid domain directory or that the Administration Server is available.
- BEA-141251
- The attribute {1} from the element {0} was introduced in version 9.0.0.0 or later and is not valid in a pre-9.0 config.xml file.
- Category:
- Management
- Cause:
- An attribute that was introduced in release 9.0 or later was found in a pre-9.0 config.xml file.
- Action:
- Verify that the upgrade process correctly handles the named elements by reviewing the upgraded configuration files.
- BEA-141252
- The domain version {0} is greater than the release version {1} of this server.
- Category:
- Management
- Cause:
- The DomainVersion in the configuration used by the Administration Server is not compatible with the release version of this Managed Server.
- Action:
- Update the WebLogic Server installation for this server.
- BEA-141253
- An error occurred while loading the configuration translator {0} : {1}.
- Category:
- Management
- Cause:
- The message includes the specific cause.
- Action:
- Repair or remove the configuration translator.
- BEA-141254
- Generating new domain directory in {0}.
- Category:
- Management
- Cause:
- There was no domain directory at the specified location. Either a command line option or user input specified creation of the domain, so generation of the domain is commencing.
- Action:
- No action is required. The domain directory will be generated, and the server will continue to boot normally.
- BEA-141255
- Domain generation completed in {0} milliseconds.
- Category:
- Management
- Cause:
- A new domain has been generated.
- Action:
- No action is required. The server will continue to boot normally.
- BEA-141256
- A RuntimeException occurred while adding or removing a configuration element: {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review this message to determine the appropriate action.
- BEA-141257
- An exception occurred while translating a configuration file: {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review this message to determine the appropriate action.
- BEA-141258
- An exception occurred while constructing an ObjectName: {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review this message to determine the appropriate action.
- BEA-141259
- An exception occurred while sending a Notification: {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review this message to determine the appropriate action.
- BEA-141260
- An exception occurred while removing a Notification: {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review this message to determine the appropriate action.
- BEA-141261
- An exception occurred while unregistering a Notification: {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review this message to determine the appropriate action.
- BEA-141262
- An exception occurred while adding a Filter: {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review this message to determine the appropriate action.
- BEA-141263
- An exception occurred in an MBean customizer: {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review this message to determine the appropriate action.
- BEA-141264
- An exception occurred in an MBeanProxy: {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review this message to determine the appropriate action.
- BEA-141265
- Could not get the configuration lock used to serialize access to the configuration files.
- Category:
- Management
- Cause:
- The lock could not be obtained before the specified timeout period had elasped.
- Action:
- Verify the configuration files and ensure that no server has hung, thereby not releasing the lock.
- BEA-141266
- Parsing failure in {0}: {1}.
- Category:
- Management
- Cause:
- This error occurs when the configuration file has invalid XML syntax or other errors.
- Action:
- Validate the contents of the configuration file.
- BEA-141267
- Parsing failure in {0} on line {1}: {2}.
- Category:
- Management
- Cause:
- This error occurs when the configuration file has invalid XML syntax or other errors.
- Action:
- Validate the contents of the configuration file.
- BEA-141268
- Parsing failure in {0} on line {1}, column {2}: {3}.
- Category:
- Management
- Cause:
- This error occurs when the configuration file has invalid XML syntax or other errors.
- Action:
- Validate the contents of the configuration file.
- BEA-141269
- The temporary bean tree {0} was allocated for an undo, get, or activate operation, but has not been garbage collected.
- Category:
- Management
- Cause:
- The temporary bean tree has not been garbage collected.
- Action:
- Repeat the specified operation and determine if memory usage in the server is increasing.
- BEA-141270
- Could not get the configuration lock used to serialize access to configuration files. Retrying for another {0} seconds.
- Category:
- Management
- Cause:
- Another server was reading or writing to the configuration files, and the lock could not be obtained before the specified timeout period had elasped.
- Action:
- No action is required. If the configuration subsystem fails to get the lock, and the number of retries is exhausted, a different message with error severity will be displayed.
- BEA-141271
- An IOException occurred while recording setAttribute {1} on MBean {0}. Exception: {2}.
- Category:
- Management
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Take action based upon the provided exception details.
- BEA-141272
- An IOException occurred while recording invoke {1} on MBean {0}. Exception: {2}.
- Category:
- Management
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Take action based upon the provided exception details.
- BEA-141273
- An upgrade framework class was not found. Exception: {0}. The configuration and upgrade framework component may not have been installed.
- Category:
- Management
- Cause:
- The configuration and upgrade framwork component may not have been installed.
- Action:
- Install the Configuration Wizard and pgrade framework component by running the installer again.
- BEA-141274
- Production mode has been specified at the command line using the the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in the config.xml file. However, the Administration Console and WLST show the attribute values and defaults that correspond to the development mode specified in the config.xml file.
- Category:
- Management
- Cause:
- The command line overrides are not persisted to the config.xml file.
- Action:
- If the Administration Console or WLST should display production mode defaults for attributes, then enable production mode in the Administration Console or WLST and activate the changes.
- BEA-141275
- Development mode has been specified at the command line by setting the weblogic.ProductionModeEnabled system property to false. This system property overrides the production mode setting contained in the config.xml file. However, the Administration Console and WLST show the attribute values and defaults that correspond to the production mode specified in the config.xml file.
- Category:
- Management
- Cause:
- The command line overrides are not persisted to the config.xml file.
- Action:
- If the Administration Console or WLST should display development mode defaults for attributes, then enable development mode in the Administration Console or WLST and activate the changes.
- BEA-141276
- An exception occurred while obtaining the class for interface {0}. The exception is: {1}
- Category:
- Management
- Cause:
- A resource or classloader issue caused the class lookup to fail.
- Action:
- See the underlying exception to troubleshoot further.
- BEA-141277
- The JMX MBean PlatformMBeanServerUsed attribute is true, but the Platform MBeanServer was created without the hooks for the WebLogic Server security infrastructure. The Platform MBeanServer will not be used and Platform MBeans will not be available using the WebLogic Server Runtime or Domain Runtime MBeanServers. This can occur if Platform MBeanServer system properties or JVM options (-Dcom.sun.management.jmxremote or JRockit -XManagement) were defined. To allow the Platform MBeanServer to be used, either remove the system properties and JVM options or start WebLogic Server with the following system property: -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder To eliminate this log error if Platform MBeans do not need to be available when using WebLogic Server, set the PlatformMBeanUsed attribute in the JMXMBean to false.
- Category:
- Management
- Cause:
- A system property was specified that caused the Platform MBeanServer to be created before the WebLogic Server Runtime MBeanServer.
- Action:
- Remove the system properties or start WebLogic Server with the following system property: -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder.
- BEA-141278
- Java entropy configuration is: {0}.
- Category:
- Management
- Cause:
- This message is informational and is printed every time WebLogic Server starts.
- Action:
- Change your jave entropy configuration, if needed.
- BEA-141279
- Detected BLOCKING java entropy configuration. This is the most secure setting, but may cause performance issues on machines with few sources of entropy.
- Category:
- Management
- Cause:
- This message is informational and is printed every time WebLogic Server starts.
- Action:
- Change your jave entropy configuration, if needed.
- BEA-141280
- Detected NON-BLOCKING java entropy configuration. This setting will provide the best performance on machines with few sources of entropy, but is less secure than a blocking entropy configuration.
- Category:
- Management
- Cause:
- This message is informational and is printed every time WebLogic Server starts.
- Action:
- Change your jave entropy configuration, if needed.
- BEA-141281
- A ForeignJNDIProvider named {0} has two child ForeignJNDILinks named {1} and {2}, which both have the same LocalJNDIName {3}. This duplication of LocalJNDIName is invalid.
- Category:
- Management
- Cause:
- Two links cannot share the same LocalJNDIName because it would be unclear as to which remote JNDI name to link to.
- Action:
- Change the LocalJNDIName of one of the ForeignJNDILinks.
- BEA-141282
- Server name {0} not found in domain {1}.
- Category:
- Management
- Cause:
- A managed server is started with -Dweblogic.Name with a value that is not configured in the domain.
- Action:
- Specify the correct value of the param -Dweblogic.Name.
- BEA-141283
- Server name could not be determined.
- Category:
- Management
- Cause:
- Either the name is not specified or the specified name does not exist in the config.xml file.
- Action:
- Specify the correct value of the -Dweblogic.Name parameter.
- BEA-141284
- A deprecated MBean for {0} has been removed from the current version of WebLogic Server but still exists in an application configuration file.
- Category:
- Management
- Cause:
- A deprecated MBean for {0} has been removed from the current version of WebLogic Server but still exists in an application configuration file.
- Action:
- Update the configuration file to remove the deprecated MBean.
- BEA-141285
- The network access point property {0} was ignored because the specified network access point name was not found.
- Category:
- Management
- Cause:
- The specified network access point does not exist in the configuration.
- Action:
- Modify the system property, and specify a valid network access point name.
- BEA-141286
- The creation of the dynamic server failed with an exception.
- Category:
- Management
- Cause:
- An exception occurred during the creation of the dynamic server.
- Action:
- Take action based upon the provided exception details, make any required changes, and retry the operation.
- BEA-141287
- No matching machines were found based on the MachineNameMatchPrefix property. No machine has been calculated for servers from dynamic servers {0}.
- Category:
- Management
- Cause:
- The MachineNameMatchPrefix did not match any of the existing machines in the domain.
- Action:
- Set the MachineNameMatchPrefix property so it matches the machine names in the domain.
- BEA-141288
- Unable to obtain file lock but will retry.
- Category:
- Management
- Cause:
- This is an informational message only.
- Action:
- If WebLogic Server fails to start because it was unable to obtain the file lock, then the lock files need to be removed manually before restarting WebLogic Server.
- BEA-141289
- Upgrade of 8.1 or prior domains is no longer supported. Convert the {1} from version {0} to 10.x format using weblogic.Upgrade.
- Category:
- Management
- Cause:
- WebLogic Server found a config.xml file with a version that is no longer supported.
- Action:
- Upgrade the config.xml file to a newer version using weblogic.Upgrade from a 10.3 or lower version of the product.
- BEA-141290
- Configuration plug-in not found for component type "{0}" in location "{1}"
- Category:
- Management
- Cause:
- The plug-in JAR file was not found.
- Action:
- Verify the installation to ensure that the plug-in was installed correctly.
- BEA-141291
- A system component for component type "{0}" was not defined in config.xml. The file "{1}" will not be distributed to the external server.
- Category:
- Management
- Cause:
- The system component is not defined in config.xml
- Action:
- Define the corresponding system component in config.xml.
- BEA-141292
- A machine was not specified in the system component "{0}" in config.xml. The file "{1}" will not be distributed to the external server.
- Category:
- Management
- Cause:
- The machine for the system component is not defined in config.xml
- Action:
- Define the corresponding machine in the system component in config.xml.
- BEA-141293
- Bad CAM replication exclusive file {0} : {1}.
- Category:
- Management
- Cause:
- See the error message for details.
- Action:
- Correct the error in the CAM replication exclusive file.
- BEA-141294
- Found invalid entries in CAM replication exclusive file {0}: {1}.
- Category:
- Management
- Cause:
- There are invalid entries in the file.
- Action:
- Correct the invalid entries in the file.
- BEA-141295
- Unable to contact Node Manager on "{1}". Activation for system component "{0}" is deferred until "{1}" becomes available.
- Category:
- Management
- Cause:
- Contact with Node Manager on "{1}" could not be made.
- Action:
- No action is required.
- BEA-141296
- Unable to contact Node Manager on "{1}". Activation for system component "{0}" is deferred until "{1}" becomes available.
- Category:
- Management
- Cause:
- Contact with Node Manager on "{1}" could not be made.
- Action:
- No action is required.
- BEA-141297
- Could not get the server file lock. Ensure that another server is not running in the same directory. Retrying for another {0} seconds.
- Category:
- Management
- Cause:
- Another server is running and still has the server lock.
- Action:
- Check to see if another server is running.
- BEA-141298
- Could not register with the Administration Server: {0}
- Category:
- Management
- Cause:
- A network connection failed or an I/O exception occurred.
- Action:
- Check the underlying exception and determine why the Managed Server could not connect to the Administration Server.
- BEA-141299
- An exception occurred during the registration of MBeans in the MBeanServer : {0}.
- Category:
- Management
- Cause:
- See the exception text for details.
- Action:
- The message includes information on the root cause. Review the message to determine the appropriate action.
- BEA-141300
- The activate changes operation for request "{0}" could not be completed because the activate timed out. Detailed state info is: {1}
- Category:
- Management
- Cause:
- The activate changes operation timed out.
- Action:
- Try increasing the activate changes timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-141301
- Access not allowed for ObjectName: {0}, on action: {1}, target {2} in partition {3}.
- Category:
- Management
- Cause:
- The user does not have enough access to the MBean in the partition.
- Action:
- Check WebLogic Server JMX policies to determine which role is required to access MBeans.
- BEA-141302
- Access not allowed for Subject: {0}, on resource {1}, action: {2}, target {3}.
- Category:
- Management
- Cause:
- The Subject role for the user does not have enough access to the MBean.
- Action:
- Check WebLogic Server JMX policies to determine which role is required to access MBeans.
- BEA-141303
- The internal method that you have invoked is not available unless you are running as Kernel. You are running as: {0}
- Category:
- Management
- Cause:
- The Subject role for the user does not have enough access to the MBean.
- Action:
- Check WebLogic Server JMX policies to determine which role is required to access MBeans.
- BEA-141304
- Access not allowed for Subject roles: {0} on ObjectName {1}: Resource Type: {2}, Action: {3}, Target: {4} in partition {5}
- Category:
- Management
- Cause:
- The person with the specified Subject role does not have enough access to the MBean.
- Action:
- Check WebLogic Server JMX policies to determine which role is required to access MBeans.
- BEA-141305
- An error occurred while firing an edit DomainMBean reload event: {0}
- Category:
- Management
- Cause:
- EditAccess fires an event when the edit DomainMBean is reloaded but one listener throws an exception.
- Action:
- Check the JMX client.
- BEA-141306
- JMS configuration error --- {0} ---.If you need to delay fixing this problem, you can force a log message to occur instead of a configuration exception by configuring the "{1}" system property to false. This system property will be removed in a future 12.2.1 stage.
- Category:
- Management
- Cause:
- JMS resource MBean validations failed.
- Action:
- Check the cross MBean relationships of JMS resources.
- BEA-141307
- Unable to connect to the Administration Server. Waiting {1} second(s) to retry (attempt number {0} of {2}).
- Category:
- Management
- Cause:
- The Administration Server is not available.
- Action:
- Start the Administration Server.
- BEA-141308
- New
- Category:
- Management
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-141309
- Initialized
- Category:
- Management
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-141310
- Prepared
- Category:
- Management
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-141311
- Activated
- Category:
- Management
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-141312
- Suspended
- Category:
- Management
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-141313
- Automatic resolve operation during startEdit fails. {0}
- Category:
- Management
- Cause:
- {0}
- Action:
- It is recommended to call resolve() manually.
- BEA-141314
- Use of the GlobalMBeansVisibleToPartitions system property is temporary. It serves only as a transitional aid to the new MBean visibility model. This warning is generated when it is detected that the old MBean visibility model is in use. Switch to the new model by eliminating the use of the -DGlobalMBeansVisibleToPartitions property. This property will be removed prior to August 2015.
- Category:
- Management
- Cause:
- The system property -DGlobalMBeansVisibleToPartitions=true was included in the server startup command.
- Action:
- Remove the system property -DGlobalMBeansVisibleToPartitions=true or use -DGlobalMBeansVisibleToPartitions=false when starting the server.
- BEA-141315
- Canceling the configuration update failed with an exception. {0}
- Category:
- Management
- Cause:
- An exception occurred during an attempt to cancel an update. {0}
- Action:
- Ensure that the config is valid. Take action based upon the provided exception details, make any required changes, and retry the activate.
- BEA-141316
- An exception was received during the prepare phase of configuration, the system is attempting to recover. {0}
- Category:
- Management
- Cause:
- An exception occurred during an attempt to prepare an update. {0}
- Action:
- If the system is unable to automatically recover, ensure that the config is valid. Take action based upon the provided exception details, make any required changes, and retry the activate.
- BEA-141317
- Auto-halting partition "{0}" due to config change; no active targeted admin resource groups
- Category:
- Management
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-141318
- Auto-booting partition "{0}" due to config change; active targeted admin resource groups
- Category:
- Management
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-141319
- The file distribution servlet failed to initialize JMX default security policies due to the following error: {0}.
- Category:
- Management
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- No action is required if REST management support is not required. Otherwise, configure an authorization security provider in the security configuration that implements weblogic.security.spi.PolicyConsumer such as the XACML Authorization provider.
- BEA-141320
- The JMX invocation timed out for request "{0}" for activate changes operation. Detailed state info is: {1}
- Category:
- Management
- Cause:
- The JMX invocation timed out for activate changes operation.
- Action:
- Compare the JMX invocation timeout value and activate timeout values. If using WLST, specify timeout in connect() command. If JMX API is used, specify the value of jmx.remote.x.request.waiting.timeout in the JMX client while creating the JMX connection.
- BEA-141321
- Property {0} was overrloaded via situational properties to {1}
- Category:
- Management
- Cause:
- Situational Properties are in effect. {0} = {1}
- Action:
- If the property setting is incorrect, update the situational properties file.
- BEA-141322
- The situational config file has an invalid format, it is being ignored: {0}
- Category:
- Management
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Update the situational config file.
- BEA-141323
- The situational config file has an invalid format, it is being ignored: {0} because {1}
- Category:
- Management
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Update the situational config file.
- BEA-141324
- Unable to obtain file lock {0} due to {1}, but will retry.
- Category:
- Management
- Cause:
- This is an informational message only.
- Action:
- If WebLogic Server fails to start because it was unable to obtain the file lock, then the lock file needs to be removed manually before restarting WebLogic Server.
- BEA-141325
- There was an exception while acquiring the configuration lock. The exception was {0}
- Category:
- Management
- Cause:
- Refer to the exception information for more details as to the probable cause of this error
- Action:
- The action taken will depend on the exception that was thrown
- BEA-141326
- There was an exception while releasing the configuration lock. The exception was {0}
- Category:
- Management
- Cause:
- Refer to the exception information for more details as to the probable cause of this error
- Action:
- The action taken will depend on the exception that was thrown
- BEA-141327
- The SitConfigRequired configuration element is set to true, but no situational config files were found.
- Category:
- Management
- Cause:
- No situational config files were found.
- Action:
- Either change the SitConfigRequired configuration element for the server to false, or ensure that situational config files are present during startup.
- BEA-141328
- The non-dynamic attribute {1} on {0} was attempted to be changed via a situational configuration file. This change may require redeploying or rebooting configured entities before it takes effect.
- Category:
- Management
- Cause:
- This happens when one or more of the changes made to the configuration via situational configuration files affect non-dynamic settings.
- Action:
- Restart the server or redeploy the entity to ensure the change takes effect.
- BEA-141329
- Error loading the situational config files: {0}
- Category:
- Management
- Cause:
- Refer to the embedded error message information for more details as to the probable cause of this error.
- Action:
- Update the situational config file to correct the error.
- BEA-141330
- Loading situational config file: {0}
- Category:
- Management
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-141331
- Canceling Edit Lock without discarding or activating the pending changes. Unactivated changes have been saved to the domain directory.
- Category:
- Management
- Cause:
- The user has cancelled the edit lock without either activating or undo the saved pending changes. This is not an error, but unactivated changes will impact later in case one performs WLST offline changes.
- Action:
- Either activate or undo the unactivated changes.
- BEA-149000
- Unable to create DeployerRuntimeMBean.
- Category:
- Deployer
- Cause:
- This may occur if an error at the JMX level exists.
- Action:
- Report this problem to My Oracle Support.
- BEA-149001
- No application named "{0}" exists for operation "{1}".
- Category:
- Deployer
- Cause:
- The application name was likely misspelled.
- Action:
- Verify that the application is correctly named.
- BEA-149002
- The source file was not provided for activation of application: "{0}".
- Category:
- Deployer
- Cause:
- Source files do not exist for the application to be deployed.
- Action:
- Make source files available for the application to be deployed in the said path.
- BEA-149003
- Unable to access application source information in "{0}" for application "{1}". The specific error is: {2}.
- Category:
- Deployer
- Cause:
- Source files for the application to be deployed are not accessible.
- Action:
- Ensure that no other process is using the source file(s).
- BEA-149004
- Failures were detected while initiating {1} task for application "{0}".
- Category:
- Deployer
- Cause:
- Task creation can fail for many reasons.
- Action:
- Check the error message and take appropriate action.
- BEA-149011
- Some of the targets in the deployment request are not configured in this domain. The named targets are: "{0}".
- Category:
- Deployer
- Cause:
- This error occurs when a deployment request is made to a target that is not configured.
- Action:
- Ensure that the target list in the request is correct.
- BEA-149013
- Application "{0}" does not define the module, "{1}". {2} are the known valid module(s) for this application.
- Category:
- Deployer
- Cause:
- Incorrect deployment information was provided in the activate request.
- Action:
- Ensure that the module information in the request is accurate. If adding modules, ensure that the source file is specified again so that it is reloaded and any new modules are deployed.
- BEA-149014
- Target "{0}" is not defined.
- Category:
- Deployer
- Cause:
- Incorrect deployment information was provided in the activate request.
- Action:
- Ensure that the target information in the request is accurate.
- BEA-149015
- Unable to add "{0}" to component "{1}".
- Category:
- Deployer
- Cause:
- The component is already targeted to the server, cluster, or virtual host.
- Action:
- Check the target list.
- BEA-149021
- Rejecting {2} request for application "{1}". The specified ID, {0}, is already being used.
- Category:
- Deployer
- Cause:
- A {1} request included an ID provided by a user that is already assigned to another task.
- Action:
- Choose a different ID or allow the system to allocate an ID for the request.
- BEA-149025
- An invalid attempt was made to target a non-Web application component, "{1}", in application "{0}" to a virtual host, "{2}".
- Category:
- Deployer
- Cause:
- An invalid attempt was made to target a non-Web application to virtual hosts.
- Action:
- Correct the target list.
- BEA-149026
- {2} application {0} on {1}.
- Category:
- Deployer
- Cause:
- This is an informational message about the task description.
- Action:
- This is an informational message about the task description.
- BEA-149027
- Unable to activate the application "{1}" from source "{0}". Reason: {2}
- Category:
- Deployer
- Cause:
- The application was improperly defined.
- Action:
- Define the application properly.
- BEA-149028
- An invalid path, "{1}", was specified for the application "{0}".
- Category:
- Deployer
- Cause:
- The configured path for this application does not exist.
- Action:
- Provide the application files in the specified location.
- BEA-149031
- The staging mode of "{0}" is invalid. The legal values are "stage" or "nostage".
- Category:
- Deployer
- Cause:
- An invalid staging mode has been specified.
- Action:
- Specify a valid staging mode for the deployment request.
- BEA-149032
- An attempt to restart a task has been rejected. The task has already been started.
- Category:
- Deployer
- Cause:
- This error results if start is called on a task that has already been started.
- Action:
- Do not call start on a task that has already been started.
- BEA-149033
- {2} application {0} on {1}.
- Category:
- Deployer
- Cause:
- An application-level deployment notification has been reported.
- Action:
- No action is required. This is an informational log message.
- BEA-149034
- An exception occurred for task {0}: {1}.
- Category:
- Deployer
- Cause:
- An error occurred while reporting the application status.
- Action:
- The error may be due to server instability. Check the health of the server.
- BEA-149035
- Module {0} reported error: {1}.
- Category:
- Deployer
- Cause:
- The deployment request failed.
- Action:
- Check the exception log and take appropriate action.
- BEA-149038
- Initiating task for {1} : {0}.
- Category:
- Deployer
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-149040
- An attempt to change the staging mode for the application "{0}" has been rejected.
- Category:
- Deployer
- Cause:
- An attempt was made to change the staging mode for the application.
- Action:
- The staging mode cannot be changed once it is set. Try deploying again without changing the staging mode.
- BEA-149045
- An attempt to add cluster target "{0}" was rejected, since cluster member "{1}" is also targeted by module "{2}". Targeting to a cluster member results in different behaviors than targeting to the entire cluster.
- Category:
- Deployer
- Cause:
- A cluster member is already in the target list of the module.
- Action:
- Remove the cluster member from the target list, or re-target the cluster member rather than the cluster itself.
- BEA-149048
- An attempt to add server target "{1}" to module "{2}" has been rejected. This is because its parent cluster, "{0}", is also targeted by the module.
- Category:
- Deployer
- Cause:
- The module is already targeted to a cluster that contains the server.
- Action:
- Remove the cluster from the target list or remove the cluster member from the target list.
- BEA-149054
- An attempt to add a virtual host target "{0}" to a non-Web application module "{1}" has been rejected.
- Category:
- Deployer
- Cause:
- An EJB or connector was attempting to target a virtual host.
- Action:
- Remove the host from target list.
- BEA-149055
- Adding server {1} of cluster {0} as a target for module {3}. This module also includes server {2} that belongs to this cluster as one of its additional targets. Having multiple individual servers of a cluster as targets instead of having the entire cluster as the target can result in non-optimal load balancing and scalability. Therefore, this is not usually recommended.
- Category:
- Deployer
- Cause:
- The module is already targeted to a different cluster member.
- Action:
- Target the entire cluster to the module.
- BEA-149058
- Distribute can only have stage as its staging mode. Application "{0}" has {1} as its staging mode.
- Category:
- Deployer
- Cause:
- This is an unexpected error.
- Action:
- Specify a valid staging name.
- BEA-149059
- Module {1} of application {0} is transitioning from {2} to {3} on server {4}.
- Category:
- Deployer
- Cause:
- A module is being deployed.
- Action:
- No action is required.
- BEA-149060
- Module {1} of application {0} successfully transitioned from {2} to {3} on server {4}.
- Category:
- Deployer
- Cause:
- A module is being deployed.
- Action:
- No action is required.
- BEA-149061
- Module {1} of application {0} failed to transition from {2} to {3} on server {4}.
- Category:
- Deployer
- Cause:
- An error was encountered during a module deployment.
- Action:
- Details of the specific failure are documented in the associated log entries. Take appropriate action.
- BEA-149062
- The task containing ID {0} cannot be canceled, since it has already completed execution.
- Category:
- Deployer
- Cause:
- An attempt has been made to cancel a deployment task that has completed execution.
- Action:
- Do not attempt this operation on a completed task.
- BEA-149066
- Unable to deploy application "{0}", because module "{1}" does not provide a valid URI.
- Category:
- Deployer
- Cause:
- The application is incorrectly configured.
- Action:
- Provide a URI for the module, or remove the application from the configuration.
- BEA-149068
- This is an unexpected exception.
- Category:
- Deployer
- Cause:
- An unexpected exception occurred.
- Action:
- No action is required.
- BEA-149069
- Deploying {0} using a deprecated protocol.
- Category:
- Deployer
- Cause:
- The application is configured with TwoPhase=false or is not a recognized type of application. For example, an application that is not an EAR file (no application.xml) but has multiple modules will not be deployed with the two-phase protocol.
- Action:
- No action is required.
- BEA-149073
- The application "{0}" has no configured modules.
- Category:
- Deployer
- Cause:
- The application is improperly configured.
- Action:
- The application will be marked as undeployable. After resolving configuration issues with the application, the administrator can retry the deployment.
- BEA-149074
- Successfully completed deployment task: {0}.
- Category:
- Deployer
- Cause:
- A deployment operation was requested.
- Action:
- No action is required.
- BEA-149078
- Stack trace for message {0}
- Category:
- Deployer
- Cause:
- A deployment failure occurred.
- Action:
- No action is required.
- BEA-149080
- A partial update of an archived application is not allowed. Application "{0}" cannot be redeployed.
- Category:
- Deployer
- Cause:
- There was an attempt to partially redeploy an archived application.
- Action:
- Try deploying the entire application.
- BEA-149081
- Cannot {2} application, "{0}", with version "{1}". The application was previously deployed without a version.
- Category:
- Deployer
- Cause:
- An attempt was made to {2} a versioned application when it was previously deployed without a version.
- Action:
- Try {2} without a version.
- BEA-149082
- Cannot {2} application "{0}" without a version. The application was previously deployed with version "{1}".
- Category:
- Deployer
- Cause:
- An attempt was made to {2} an application without a version when it was previously deployed with a version.
- Action:
- Try {2} with a version.
- BEA-149083
- An attempt was made to activate the application "{0}" when stop was in progress.
- Category:
- Deployer
- Cause:
- An attempt was made to activate the application "{0}" when stop was in progress.
- Action:
- Try to activate the application "{0}" again after the stop is done. If it is a graceful stop, stop the application forcefully to end the graceful stop immediately.
- BEA-149085
- No application version was specified for application "{0}". The {2} operation will be performed against the currently active version "{1}".
- Category:
- Deployer
- Cause:
- No application version was specified for the operation.
- Action:
- Verify that the currently active version is the desired version for the operation. If not, perform the operation again with the -app_version operation to specify a particular version.
- BEA-149086
- The application {0} is being retired gracefully.
- Category:
- Deployer
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-149087
- The application {0} will be retired after {1} seconds.
- Category:
- Deployer
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-149088
- The retirement for application {0}, which was scheduled to happen after {1} seconds, is canceled.
- Category:
- Deployer
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-149089
- An attempt was made to activate the application "{0}" when retirement was in progress.
- Category:
- Deployer
- Cause:
- An attempt was made to activate the application "{0}" when retirement was in progress.
- Action:
- Try to activate the application "{0}" again after the retirement is done. If it is a graceful retirement, undeploy the application to end the graceful retirement immediately.
- BEA-149091
- An attempt was made to deploy application "{0}" with specified archive version "{1}". However, the application archive, as specified in the source, has version "{2}".
- Category:
- Deployer
- Cause:
- This error occurs when an attempt is made to specify a version that is different from the manifest version of the application archive in the source location.
- Action:
- Perform the deployment again without specifying the version, or specify version "{2}" instead of "{1}".
- BEA-149092
- The source is not specified for the deployment operation of application "{0}", and the expected version is "{1}". However, the application archive at the source location for a previous deployment of version "{1}" now has version "{2}".
- Category:
- Deployer
- Cause:
- The source is not specified for the deployment operation of application "{0}", and the expected version is either explicitly specified or the currently active version. However, the application archive at the previously configured source location of the expected version has a different manifest version.
- Action:
- Perform deployment again specifying either the source location or version "{2}".
- BEA-149093
- No version specified for the versioned application named "{0}" for operation {1}, and no active version is available.
- Category:
- Deployer
- Cause:
- The version was not specified for the operation when no currently active version was available.
- Action:
- Specify the version of the application for the operation.
- BEA-149095
- The application {0} is being retired now.
- Category:
- Deployer
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-149096
- Operation {1} is deprecated and cannot be applied to versioned application "{0}". Use operation {2} instead.
- Category:
- Deployer
- Cause:
- An attempt was made to perform the deprecated operation {1} on a versioned application. Use operation {2} instead.
- Action:
- Use operation {2} instead.
- BEA-149097
- The retirement for application "{0}" failed.
- Category:
- Deployer
- Cause:
- This may have happened due to a problem with accessing the persistent store.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-149098
- An attempt was made to gracefully undeploy the application "{0}" when retirement was in progress.
- Category:
- Deployer
- Cause:
- An attempt was made to gracefully undeploy the application "{0}" when retirement was in progress.
- Action:
- To stop the graceful retirement, force the application to undeploy.
- BEA-149099
- Unexpected errors occurred while sending deployment event {1} on behalf of application "{0}".
- Category:
- Deployer
- Cause:
- Deployment event listeners that are registered to receive a deployment event generated unexpected exceptions when processing the deployment event {1} on behalf of application "{0}".
- Action:
- Report this problem to My Oracle Support.
- BEA-149100
- Unexpected errors occurred while sending a vetoable deployment event on behalf of application "{0}".
- Category:
- Deployer
- Cause:
- Deployment event listeners registered to receive a vetoable deployment event generated unexpected exceptions when processing the deployment event {1} on behalf of application "{0}".
- Action:
- Report this problem to My Oracle Support.
- BEA-149101
- Application "{0}" is not deployed on target "{1}". Therefore, it cannot be undeployed or removed. The requested operation {2} is valid only on the deployed targets of the application.
- Category:
- Deployer
- Cause:
- Incorrect target information was provided in the {2} operation request.
- Action:
- Ensure that the target information in the request is accurate.
- BEA-149102
- Production redeployment is not supported for application "{0}", which is of module type {1}. Production redeployment is supported for the following module types only: {2}. If not attempting to perform production redeployment, try deploying without a version.
- Category:
- Deployer
- Cause:
- Attempt was made to perform production redeployment for an unsupported module type.
- Action:
- Ensure that the module type is supported before performing production redeployment. Or, try deploying again without a version.
- BEA-149103
- An exception occurred while executing task {0} for application "{1}": {2}.
- Category:
- Deployer
- Cause:
- An exception occurred while executing the deployment task for the application.
- Action:
- If it is an application error, correct it if possible. If it is a system error, contact My Oracle Support.
- BEA-149104
- Update request for "{0}" does not specify any descriptors to be updated
- Category:
- Deployer
- Cause:
- The deployment plan does not include any module overrides.
- Action:
- Ensure that the deployment plan is properly constructed.
- BEA-149105
- An attempt was made to deploy a library located at "{2}" with name "{0}", which is different from the one specified in the manifest of the library: "{1}".
- Category:
- Deployer
- Cause:
- This error occurs when an attempt is made to specify a name that is different from the one in the manifest of the library in the source location.
- Action:
- Perform deployment again without specifying the name of the library.
- BEA-149106
- An attempt was made to deploy a library located at "{0}" without specifying a name, and the library does not have "Extension-Name" specified in its manifest.
- Category:
- Deployer
- Cause:
- This error occurs when an attempt is made to deploy a library without specifying a name, and the library module does not have "Extension-Name" specified in its manifest.
- Action:
- Perform deployment again specifying the name of the library either during deployment or in the manifest of the library, using the "Extension-Name" attribute.
- BEA-149107
- An attempt was made to deploy library "{0}" with specified specification version "{1}" and implementation version "{2}". However, the library manifest has specification version "{3}" and implementation version "{4}".
- Category:
- Deployer
- Cause:
- This error occurs when an attempt is made to specify a version that is different from the manifest version of the library.
- Action:
- Perform deployment again without specifying the version or after specifying the same version as specified in the manifest.
- BEA-149108
- Failures were detected while initiating {0} task.
- Category:
- Deployer
- Cause:
- Task creation can fail for many reasons.
- Action:
- Check the error message and take appropriate action.
- BEA-149110
- An exception occurred while processing the completion of the task {0}, {1}. The active application version state may not have been updated.
- Category:
- Deployer
- Cause:
- The deployment subsystem was unable to complete the persistence of the active application version state.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-149111
- Application "{0}" is non-versioned, and an attempt was made to redeploy application "{0}" with the source. Redeploying with the source is only allowed when redeploying a new version of a versioned application. Try redeploying again without specifying the source.
- Category:
- Deployer
- Cause:
- An attempt was made to redeploy with the source specified for a non-versioned application "{0}". Redeploy again without specifying the source.
- Action:
- Try redeploying again without specifying the source.
- BEA-149112
- Application "{0}" is already deployed, and the attempt was made to redeploy application "{0}" again with source. Redeploying with the source is only allowed when redeploying a new version of the application. Try redeploying again without specifying the source or with a new version.
- Category:
- Deployer
- Cause:
- An attempt was made to redeploy with the source specified for application "{0}", but application "{0}" was already deployed. Redeploy again without specifying the source or with a new version.
- Action:
- Try redeploying again without specifying the source or redeploy with a new version.
- BEA-149113
- Cannot deploy or redeploy application "{0}" because the maximum number of application versions ({2}) for application "{1}" has been exceeded. Currently deployed versions are: "{3}".
- Category:
- Deployer
- Cause:
- An attempt was made to deploy or redeploy application "{0}" when the maximum number of application versions ("{2}") for application "{1}" has been exceeded.
- Action:
- Try undeploying the existing application version(s) before deploying or redeploying the new version(s).
- BEA-149114
- Cannot deploy or redeploy application "{0}" with version identifier "{1}" because the maximum length of the version identifier ({2}) has been exceeded.
- Category:
- Deployer
- Cause:
- An attempt was made to deploy or redeploy application "{0}" with version identifier "{1}" that exceeded the maximum length ({2}).
- Action:
- Try reducing the version identifier length when deploying or redeploying the application version.
- BEA-149115
- Cannot deploy or redeploy application "{0}" with invalid version identifier "{1}". Version identifiers may only contain alphanumerics, period, underscore, and hyphen and must be less than 215 characters in length.
- Category:
- Deployer
- Cause:
- An attempt was made to deploy or redeploy application "{0}" with invalid version identifier "{1}".
- Action:
- Try changing the version identifier to a valid one when deploying or redeploying the application version. Version identifiers can only consist of alphanumeric, period, underscore, or hyphen characters and must not be "." or "..".
- BEA-149116
- Cannot obtain the deployment configuration.
- Category:
- Deployer
- Cause:
- The deployment configuration could not be obtained.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-149117
- {2} library {0} on {1}.
- Category:
- Deployer
- Cause:
- This is an informational message about the task description.
- Action:
- This is an informational message about the task description.
- BEA-149118
- "{1}" is not targeted to "{0}".
- Category:
- Deployer
- Cause:
- An attempt was made to undeploy the application from a target where it is not deployed.
- Action:
- Correct the target list for the operation.
- BEA-149119
- Different targets cannot be specified when deploying a new version "{1}" of application "{0}". The targets specified, "{3}", are different from those of the previous version, "{2}".
- Category:
- Deployer
- Cause:
- An attempt was made to deploy a new application version with targets that are different from that of the previous version.
- Action:
- Try deploying again without specifying targets, or specify the exact same target as the previous version.
- BEA-149120
- The plan version "{1}" cannot be specified when deploying a non-versioned application "{0}".
- Category:
- Deployer
- Cause:
- An attempt was made to deploy a non-versioned application with a plan version.
- Action:
- Try deploying again with an application version or without the plan version.
- BEA-149121
- Rejecting {1} request for application {0} because the deployment service is not started.
- Category:
- Deployer
- Cause:
- A deployment operation was attempted when the server was starting or shutting down.
- Action:
- Perform the deployment operation again after the server has started or before the server has shut down.
- BEA-149122
- Deployment perations on internal application "{0}" are not permitted;.
- Category:
- Deployer
- Cause:
- Deployment operations are not permitted on internal applications.
- Action:
- Do not attempt any deployment operations on internal applications.
- BEA-149123
- The application "{0}" currently has security model "{1}", and an attempt was made to redeploy the application again with a different security model "{2}". The specified security model will be ignored for the current deployment operation. To change the security model, undeploy the application and deploy it again with the new security model.
- Category:
- Deployer
- Cause:
- An attempt was made to redeploy the same application with a different security model.
- Action:
- Undeploy the application and deploy it again with the new security model.
- BEA-149124
- Failures were detected while initiating {1} task for application "{0}". Error is: "{2}"
- Category:
- Deployer
- Cause:
- Task creation can fail for many reasons.
- Action:
- Check the error message and take appropriate action.
- BEA-149125
- No application version was specified for the {0} operation of application "{1}". The {0} operation will be performed against the retired application version "{2}".
- Category:
- Deployer
- Cause:
- This is an informational message only.
- Action:
- No action is required.
- BEA-149126
- No application version was specified for the {0} operation of application "{1}". The application version "{2}" will not be removed as its retirement is still in progress. Oracle recommends that the application version "{2}" be undeployed explicitly after the retirement is done. An explicit undeploy of the application version can also be performed before retirement is done; however, exercise caution as this may interrupt inflight work.
- Category:
- Deployer
- Cause:
- No application version was specified for the {0} operation of application "{1}".
- Action:
- No action is required.
- BEA-149127
- Failures were detected while initiating "{0}" task. Error is: "{1}"
- Category:
- Deployer
- Cause:
- Task creation can fail for many reasons.
- Action:
- Check the error message and take appropriate actions.
- BEA-149128
- The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the retired application version "{3}".
- Category:
- Deployer
- Cause:
- This is an informational message only.
- Action:
- No action is required.
- BEA-149129
- The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the retiring application version "{3}". Note that retirement is still in progress for version "{3}" and any inflight work will be interrupted.
- Category:
- Deployer
- Cause:
- This is an informational message only.
- Action:
- No action is required.
- BEA-149130
- The "{1}" option was specified for the {0} operation of application "{2}". The {0} operation will be performed against the currently active version "{3}".
- Category:
- Deployer
- Cause:
- This is an informational message only.
- Action:
- No action is required.
- BEA-149131
- Cannot perform operation {2} because application "{0}" is in state {1}
- Category:
- Deployer
- Cause:
- The application is no longer active.
- Action:
- Ensure that the application is active. Deploy again if needed.
- BEA-149132
- Split directory application {0} can only be deployed on the Administration Server.
- Category:
- Deployer
- Cause:
- An attempt was made to perform the deployment operation on the split directory application on a server other than the Administration Server.
- Action:
- For split directory application {0}, perform deployment operations on the Administration Server alone.
- BEA-149133
- Auto-deployed application {0} can only be deployed on the Administration Server.
- Category:
- Deployer
- Cause:
- An attempt was made to perform the deployment operation on the auto-deployed application on a server other than the Administration Server.
- Action:
- For auto-deployed application {0}, perform deployment operations on the Administration Server alone.
- BEA-149134
- A redeploy was performed without specifying -source for the archived versioned application "{0}". Partial update of an archived application is not allowed. To perform production redeployment of versioned applications, specify -source with the redeploy operation.
- Category:
- Deployer
- Cause:
- An attempt was made to partially redeploy an archived application.
- Action:
- Specify -source for production redeployment, or redeploy the entire application.
- BEA-149135
- Operation {2} cannot be performed since application "{0}" is not deployed on the target "{1}".
- Category:
- Deployer
- Cause:
- Operation {2} could not be performed because the application was not deployed on the provided target.
- Action:
- Rery with a valid target.
- BEA-149137
- {0} is an invalid path for partial redeployment. The URI of the file or directory to be redeployed should be relative to {1}, the root of the enterprise application, or to the standalone module being redeployed.
- Category:
- Deployer
- Cause:
- The file could not be located in the application.
- Action:
- Use a valid specification for the file.
- BEA-149138
- A subset of the originally configured targets for the application "{0}" was specified. This can potentially lead to out-of-sync applications between the different server targets. The targets specified, "{2}", are different from those of the previous version, "{1}".
- Category:
- Deployer
- Cause:
- A deployment operation was performed on an existing application with a subset of the originally configured targets.
- Action:
- If the application content has changed since the last operation, Ensure that all configured targets are updated. To do so, repeat the operation without specifying targets in order to automatically use the configured targets.
- BEA-149139
- Application "{0}" is targeted to cluster "{1}", and provided the target for {3} operation is "{2}". The {3} operation on a subset of the targeted clustered servers is not supported.
- Category:
- Deployer
- Cause:
- The {3} operation was attempted on one or more servers in the targeted cluster.
- Action:
- Retry with the targeted cluster, or undeploy from the cluster and deploy to the desired individual servers.
- BEA-149140
- The task cannot be processed further until the current edit session is activated. When this occurs, task processing will continue. The user can exit the deployer tool without affecting the task.
- Category:
- Deployer
- Cause:
- The user is the current owner of the domain configuration edit lock.
- Action:
- Activate (or cancel) the edit session. The user can exit the deployer tool without affecting the task.
- BEA-149141
- The AppDeploymentMBean already exists for application "{0}".
- Category:
- Deployer
- Cause:
- The AppDeploymentMBean already exists for application "{0}".
- Action:
- Ensure that different applications do not have the same name.
- BEA-149142
- Cluster target "{0}" is configured with no servers, and therefore configuration is updated.
- Category:
- Deployer
- Cause:
- A deployment to a cluster target was attempted, but the cluster contains no servers.
- Action:
- No action is required.
- BEA-149143
- Submodule targets in an application must be specified with the correct module name.
- Category:
- Deployer
- Cause:
- A submodule target was specified incorrectly.
- Action:
- Ensure that the submodule target was specified with the correct syntax and with the correct module name.
- BEA-149145
- Unable to contact "{0}". Deployment is deferred until "{0}" becomes available. WARNING: If this is a redeploy app and contains JSP pages that have been touched, these JSP changes won't be reflected when the server starts unless precompile is set to true in weblogic.xml
- Category:
- Deployer
- Cause:
- Contact with "{0}" could not be made. Deployment is deferred until "{0}" becomes available.
- Action:
- No action is necessary.
- BEA-149146
- Attempt to reach the Administration Server with alternate URL: "{0}" failed.
- Category:
- Deployer
- Cause:
- The attempt to reach the Administration Server with the alternate URL: "{0}" failed.
- Action:
- See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149147
- Could not reach the Administration Server through any of its URLs: "{0}".
- Category:
- Deployer
- Cause:
- The Administration Server could not be reached through any of its URLs: "{0}".
- Action:
- See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149148
- Exception occurred while receiving a message on loopback.
- Category:
- Deployer
- Cause:
- An exception occurred while receiving a message on loopback.
- Action:
- See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149149
- Malformed URL: "{0}".
- Category:
- Deployer
- Cause:
- The URL: "{0}" was malformed.
- Action:
- See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149150
- An IOException occurred while reading the input.
- Category:
- Deployer
- Cause:
- An IOException occurred while reading the input.
- Action:
- See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149151
- Could not find a registered DeploymentReceiver to handle requests for "{0}".
- Category:
- Deployer
- Cause:
- A registered DeploymentReceiver could not be found to handle requests for "{0}".
- Action:
- Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149152
- No deployment request for which to set up the context.
- Category:
- Deployer
- Cause:
- No deployment request for which to set up the context.
- Action:
- Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149153
- A "prepare" message was received for ID "{0}" that has already been completed or canceled.
- Category:
- Deployer
- Cause:
- A "prepare" message was received for ID "{0}" that has already been completed or canceled.
- Action:
- Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149154
- A "get deployments response" message was received for ID "{0}" that has no request. It may have already been completed or may have been canceled.
- Category:
- Deployer
- Cause:
- A "get deployments response" message was received for ID "{0}" that has no request. It may have already been completed or may have been canceled.
- Action:
- Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149155
- Received "get deployments response" message "{0}" while already handling one. Ignoring the second request.
- Category:
- Deployer
- Cause:
- A "get deployments response" message "{0}" was received while another was being handled. The second request was ignored.
- Action:
- Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149156
- Illegal state for operation start: "{0}".
- Category:
- Deployer
- Cause:
- The start operation was called on an application that either had an update pending or was used with the administration mode flag.
- Action:
- To move the application from active to administration mode, use the stop operation.
- BEA-149157
- There is nothing to do for task "{0}".
- Category:
- Deployer
- Cause:
- There is nothing to do for task "{0}".
- Action:
- No action is required.
- BEA-149158
- No application files exist at "{0}".
- Category:
- Deployer
- Cause:
- No application files exist at "{0}".
- Action:
- No action is required.
- BEA-149159
- There was an attempt to create a staging directory that is null.
- Category:
- Deployer
- Cause:
- There was an attempt to create a staging directory that is null.
- Action:
- Ensure that the staging directory is properly configured. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149160
- There was an attempt to create a staging directory for a null application name.
- Category:
- Deployer
- Cause:
- There was an attempt to create a staging directory for a null application name.
- Action:
- Ensure that the application name is properly configured. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149161
- This operation requires that a target be specified.
- Category:
- Deployer
- Cause:
- This operation requires that a target be specified.
- Action:
- Ensure that the deployment request is complete and contains the required targeting information.
- BEA-149162
- This operation requires that a deployment plan be specified.
- Category:
- Deployer
- Cause:
- This operation requires that a deployment plan be specified.
- Action:
- Ensure that the deployment request is complete and contains the required deployment plan information.
- BEA-149163
- The domain edit lock is owned by another session in non-exclusive mode. This deployment operation requires exclusive access to the edit lock and therefore cannot proceed. If using "Automatically Aquire Lock and Activate Changes" in the Administration Console, then the lock will expire shortly, so retry this operation.
- Category:
- Deployer
- Cause:
- The domain edit lock is owned by another session in non-exclusive mode. This deployment operation requires exclusive access to the edit lock and therefore cannot proceed.
- Action:
- Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149164
- The domain edit lock is owned by another session in exclusive mode. Therefore, this deployment operation cannot proceed.
- Category:
- Deployer
- Cause:
- The domain edit lock is owned by another session in exclusive mode. Therefore, this deployment operation cannot proceed.
- Action:
- Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149165
- Invalid target specified.
- Category:
- Deployer
- Cause:
- An invalid target was specified.
- Action:
- See the exception cause and check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149166
- Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.
- Category:
- Deployer
- Cause:
- Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.
- Action:
- Ensure that the domain edit lock is available, and try again. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149167
- No action was needed to commit the request for "{0}" on "{1}".
- Category:
- Deployer
- Cause:
- No action was needed to commit the request for "{0}" on "{1}".
- Action:
- No action is required.
- BEA-149168
- Request "{0}" has already been completed or was canceled.
- Category:
- Deployer
- Cause:
- The request "{0}" has already been completed or was canceled.
- Action:
- Check the preceding conflict start message in the logs. Try to avoid the conflict by following one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-149169
- Requires server restart for completion.
- Category:
- Deployer
- Cause:
- In order to complete the action, the server must be restarted.
- Action:
- Restart the required servers.
- BEA-149170
- Invalid targeting was specified for this operation. Module and submodule targets cannot both be specified for this type of request.
- Category:
- Deployer
- Cause:
- The operation specified both module and submodule targeting, which is invalid for this operation.
- Action:
- Perform the operation separately for both module and submodule targets.
- BEA-149171
- Deferred deployment task: {0}
- Category:
- Deployer
- Cause:
- A deployment operation was requested with targets that were unreachable.
- Action:
- No action is required.
- BEA-149172
- Deployment request {0} is affecting the system resource {1}, which involves a non-dynamic property {2} in {3}. Therefore, a restart of the resource or the appropriate server targets is required for the changes to be active.
- Category:
- Deployer
- Cause:
- This is an informational message indicating that deployment involves a non-dynamic property.
- Action:
- No action is required.
- BEA-149178
- Application "{0}" is targeted to cluster "{1}", and the provided target for {3} operation is "{2}". This can potentially lead to client request problems on the cluster.
- Category:
- Deployer
- Cause:
- An operation was performed on a subset of a cluster for an application targeted to the cluster.
- Action:
- Ensure that the cluster properly serves requests by performing operations on the cluster rather then on individual servers within the cluster.
- BEA-149181
- Deployment service encountered an error while aborting the edit session before start. Initiator for this edit session is "{0}". Error is "{1}".
- Category:
- Deployer
- Cause:
- See the reported error.
- Action:
- Take appropriate action based on the reported error.
- BEA-149182
- An invalid alternate descriptor was specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.
- Category:
- Deployer
- Cause:
- An invalid alternate descriptor was specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.
- Action:
- Repeat the redeploy operation without the alternate descriptor.
- BEA-149183
- An invalid retiretimeout option was specified for the deploy operation. The retiretimeout option was specified as "{2}" for the initial deployment of application "{0}". Retirement policies must be set during the deploy or redeploy of the next version in order to apply to version "{1}" of "{0}".
- Category:
- Deployer
- Cause:
- An invalid retiretimeout option was specified for the deploy operation.
- Action:
- Specify the retiretimeout option during the deploy or redeploy of subsequent versions in order for the retirement to occur correctly at that time.
- BEA-149184
- The application "{0}" was autodeployed and may only be redeployed by touching the REDEPLOY file in the domain autodeploy directory for the respected application.
- Category:
- Deployer
- Cause:
- Autodeployed applications cannot be redeployed through tools.
- Action:
- See the WebLogic Server documentation on autodeployed applications for more information.
- BEA-149185
- The application "{0}" was autodeployed and may only be deleted by removing the files from the domain autodeploy directory.
- Category:
- Deployer
- Cause:
- Autodeployed application cannot be undeployed through tools.
- Action:
- See the WebLogic Server documentation on autodeployed applications for more information.
- BEA-149186
- The application "{0}" was autodeployed and cannot be redistributed.
- Category:
- Deployer
- Cause:
- Autodeployed application cannot be redistributed.
- Action:
- See the WebLogic Server documentation on autodeployed applications for more information.
- BEA-149187
- An unexpected error occurred when specifying configuration information for the application "{0}" due to {1}.
- Category:
- Deployer
- Cause:
- Application configuration upgrade requires targeting information.
- Action:
- Inspect the problematic application parts and deploy the application.
- BEA-149188
- No application named "{0}" exists for operation {1}. Operation cannot be performed until the server is restarted.
- Category:
- Deployer
- Cause:
- The application was created after non-dynamic changes were activated. The server needed to be restarted.
- Action:
- Restart the server and then start the application. In the future, start the application before making non-dynamic changes to the configuration.
- BEA-149189
- An attempt was made to execute the "{0}" operation on an application named "{1}" that is not currently available. The application may have been created after non-dynamic configuration changes were activated. If so, the operation cannot be performed until the server is restarted so that the application will be available.
- Category:
- Deployer
- Cause:
- The application may have been created after non-dynamic changes were activated. The server needed to be restarted.
- Action:
- Restart the server and then perform the operation on the application.
- BEA-149190
- Changes are pending from another session whose lock has expired. This deployment operation will not activate changes from another edit session and therefore cannot proceed. Either cancel the edit lock or activate the pending changes using the Administration Console or WLST.
- Category:
- Deployer
- Cause:
- Changes were made with an edit session that has now expired.
- Action:
- Cancel the edit lock or activate the pending changes using the Administration Console or WebLogic Scripting Tool (WLST).
- BEA-149191
- Operation "{0}" on application "{1}" is initializing on "{2}".
- Category:
- Deployer
- Cause:
- This is an informational message indicating deployment status change.
- Action:
- No action is required.
- BEA-149192
- Operation "{0}" on application "{1}" is in progress on "{2}".
- Category:
- Deployer
- Cause:
- This is an informational message indicating deployment status change.
- Action:
- No action is required.
- BEA-149193
- Operation "{0}" on application "{1}" has failed on "{2}".
- Category:
- Deployer
- Cause:
- This is an informational message indicating deployment status change.
- Action:
- No action is required.
- BEA-149194
- Operation "{0}" on application "{1}" has succeeded on "{2}".
- Category:
- Deployer
- Cause:
- This is an informational message indicating deployment status change.
- Action:
- No action is required.
- BEA-149195
- Operation "{0}" on application "{1}" has been deferred since "{2}" is unavailable.
- Category:
- Deployer
- Cause:
- This is an informational message indicating deployment status change.
- Action:
- No action is required.
- BEA-149196
- Rejecting {1} request for application {0} because {2} request is running for the application.
- Category:
- Deployer
- Cause:
- A second operation for an application was requested when an operation for the application was runnning.
- Action:
- Perform the operation again when the operation that is running is completed.
- BEA-149197
- Cannot perform operation {3} because application "{0}" is in state {1} and "{2}" is running.
- Category:
- Deployer
- Cause:
- The application is in the wrong state for the operation.
- Action:
- Ensure that the application is in the correct state before attempting the operation.
- BEA-149198
- Cannot rename directory "{0}" to {1}.
- Category:
- Deployer
- Cause:
- The rename operation failed since the source directory is not present or there is a privilege issue.
- Action:
- Check that the source directory is present and has the required permissions.
- BEA-149199
- Security permissions declared in the "{0}" deployment descriptor are not allowed due to the server''s configuration.
- Category:
- Deployer
- Cause:
- The server is configured not to allow Java security permissions to be declared in the Weblogic deployment descriptors.
- Action:
- Remove Java security permissions from the deployment descriptor before re-deployment.
- BEA-149202
- Encountered an exception while attempting to commit the {0} task for the application "{1}" on [partition-name: {2}].
- Category:
- Deployer
- Cause:
- The cause of this error is likely in the application or the application subsystem for that application type.
- Action:
- Review the exception and attempt to repair the application level. Then re-initiate the deployment request.
- BEA-149205
- Failed to initialize the application "{0}" due to error {1}
- Category:
- Deployer
- Cause:
- The cause of this error is likely in the application or the application subsystem for that application type.
- Action:
- Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
- BEA-149209
- The Slave Deployer is resuming.
- Category:
- Deployer
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-149229
- Server "{0}" in cluster "{1}" is unable to initialize due to failed deployments.
- Category:
- Deployer
- Cause:
- This problem occurred due to failed deployments, which are already logged.
- Action:
- Correct the deployment problem, and restart the server in the cluster.
- BEA-149231
- Unable to set the activation state to {1} for the application "{0}".
- Category:
- Deployer
- Cause:
- An unexpected error occurred.
- Action:
- Report this error to My Oracle Support.
- BEA-149233
- An unexpected error occurred during the deployment process.
- Category:
- Deployer
- Cause:
- There was a problem with the internal implementation that was not anticipated.
- Action:
- Report the error and any useful information needed to reproduce the problem to My Oracle Support.
- BEA-149239
- Application deployment failures were detected during startup of the Administration Server, "{0}", member of cluster "{1}".
- Category:
- Deployer
- Cause:
- One or more applications could not be deployed during the startup of the Administration Server.
- Action:
- Oracle recommends that the Administration Server not be part of a cluster. One response to this warning is to remove it from the cluster and restart the Administration Server. Alternatively, review the Administration Server log to understand why the deployment failed, fix the problem, and redeploy the application.
- BEA-149243
- The internal application "{0}" could not be deployed. An attempt will be made to retry deploying this application after synchronizing the application files again.
- Category:
- Deployer
- Cause:
- It is likely that the internal staged directory was corrupt or there was a failure when deploying the staged application.
- Action:
- No action is necessary if the retry succeeds. Otherwise, the nature of the failure should provide an indication of the problem and its resolution. If this is not clear, contact My Oracle Support with the relevant logs and configuration files.
- BEA-149245
- The deployment plan at "{0}" for application "{1}" does not define a valid deployment plan.
- Category:
- Deployer
- Cause:
- The application is configured with an incorrect deployment plan document.
- Action:
- Deploy the application using a valid deployment plan.
- BEA-149246
- The security realm "{0}" does not support application versioning. Deployment of application "{1}" failed.
- Category:
- Deployer
- Cause:
- The security realm "{0}" does not support application versioning. The deployment of the application version failed.
- Action:
- Deploy the application using a security realm that supports application versioning.
- BEA-149247
- Failed to transition the application "{0}" to running mode due to error {1}
- Category:
- Deployer
- Cause:
- The cause of this error is likely in the application or the application subsystem for that application type.
- Action:
- Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
- BEA-149248
- Failed to transition the application "{0}" to administration mode due to error {1}.
- Category:
- Deployer
- Cause:
- The cause of this error is likely in the application or the application subsystem for that application type.
- Action:
- Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
- BEA-149250
- Unable to unprepare the application "{0}".
- Category:
- Deployer
- Cause:
- This was an unexpected error.
- Action:
- Report this error to My Oracle Support.
- BEA-149251
- Operation {0} failed for application "{1}". Error: {2}
- Category:
- Deployer
- Cause:
- See the exception in the message body.
- Action:
- Typically, no action is required.
- BEA-149252
- No deployment "{1}" found for operation {0}.
- Category:
- Deployer
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-149256
- Failed to find deployment for application "{0}".
- Category:
- Deployer
- Cause:
- The cause of this error is likely that the deployment was not properly created, possibly because it may not have proper descriptors.
- Action:
- Review the exception and attempt to repair the application level. Then reinitiate the deployment request.
- BEA-149257
- Rejecting the attempt to distribute application or shared library "{0}" while the application is running (in state {1}). This operation is not permitted while the application is running or has pending updates.
- Category:
- Deployer
- Cause:
- The application or shared library was not stopped or had pending updates.
- Action:
- Verify that the application or shared library is stopped or has no pending updates before attempting to distribute it. You may also consider redeploying the application.
- BEA-149258
- The server failed to completely remove the staged files "{1}" for application "{0}". Check the directory and ensure that no other application is using this directory. This will result in inappropriate results when this server is partitioned and tries to deploy this application.
- Category:
- Deployer
- Cause:
- Another application might be using the files under a staging directory.
- Action:
- Delete the appropriate staged files manually.
- BEA-149259
- Server "{0}" in cluster "{1}" is being brought up in administration state due to failed deployments.
- Category:
- Deployer
- Cause:
- This problem occurred due to failed deployments, which are already logged.
- Action:
- Correct the cause of the deployment errors, redeploy the failed deployments, and resume or restart the server in the cluster.
- BEA-149260
- A failure occurred during application startup.
- Category:
- Deployer
- Cause:
- Check the error stack trace for details of the failure.
- Action:
- Correct the cause of the application failure, if possible, and redeploy the application or restart the server. If it is an Oracle internal application, report it to My Oracle Support.
- BEA-149264
- Invalid redeploy attempt on application "{0}". There was an attempt to redeploy the application when the application was not running.
- Category:
- Deployer
- Cause:
- The application was stopped.
- Action:
- Start the application.
- BEA-149265
- Failure occurred in the execution of deployment request with ID "{0}" for task "{1}" on [partition-name: {2}]. Error is: "{3}"
- Category:
- Deployer
- Cause:
- See the reported error in the message body.
- Action:
- Start the application.
- BEA-149266
- Illegal state for operation deploy: "{0}".
- Category:
- Deployer
- Cause:
- The deploy operation was called on an application that was not new.
- Action:
- Verify that the specified application name and operation are correct.
- BEA-149267
- Cancel operation on deployment task "{0}" on server "{1}" failed.
- Category:
- Deployer
- Cause:
- See the underlying exception.
- Action:
- Take action based on the underlying exception.
- BEA-149268
- Static deployment of non-versioned application "{0}" failed due to a version being defined in its manifest file.
- Category:
- Deployer
- Cause:
- The manifest file was modified with a version for a non-versioned application.
- Action:
- Remove the application and redeploy it with a version.
- BEA-149269
- Static file redeployment and module level redeployment cannot be in the same deployment task. Check the usage.
- Category:
- Deployer
- Cause:
- The server cannot determine which type of redeployment should be processed.
- Action:
- Correct the deployment option.
- BEA-149319
- {0}: List of servers being worked upon are {1}.
- Category:
- Management
- Cause:
- {0}
- Action:
- None
- BEA-149400
- Activating application: {0}
- Category:
- Application Poller
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-149401
- Removing application: {0}
- Category:
- Application Poller
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-149403
- Application {0} deployed from the applications directory has components that are deployed on servers other than the Administration Server. Refresh of static content (such as JSPs and HTML pages) will not be automatically propagated to the Managed Servers. To propagate your changes to the Managed Servers, you must redeploy the application by touching the REDEPLOY file.
- Category:
- Application Poller
- Cause:
- This is a warning message only.
- Action:
- Touch the REDEPLOY file to properly redeploy the application. The REDEPLOY file is located in the same directory as the deployment descriptor. For EAR files, it is located in META-INF/REDEPLOY.
- BEA-149407
- An error occurred while undeploying application {0} : {1}.
- Category:
- Application Poller
- Cause:
- Undeployment can fail for many reasons.
- Action:
- Review the error message and take corrective action.
- BEA-149408
- An exception occurred while deploying an application {0}: {1}.
- Category:
- Application Poller
- Cause:
- Deployment of an application can fail for many reasons. Refer to the exception details.
- Action:
- Review the exception. To redeploy the application after correcting the error condition, touch the file called REDEPLOY in the META-INF or WEB-INF directory of the exploded application.
- BEA-149409
- Caught exception while starting the applications poller on server start {0}.
- Category:
- Application Poller
- Cause:
- A misconfigured application may be present in the applications directory.
- Action:
- Review the exception message in the server log.
- BEA-149410
- Runtime deployment error while deploying - {0}.
- Category:
- Application Poller
- Cause:
- The cause of this error is unknown.
- Action:
- Refer to the runtime error in the message.
- BEA-149411
- I/O exception was encountered {0}.
- Category:
- Application Poller
- Cause:
- An I/O exception can occur during file read/write while deploying an application.
- Action:
- Take corrective action based on the exception message details.
- BEA-149412
- Application "{0}" is being redeployed, because it changed since the previous server run.
- Category:
- Application Poller
- Cause:
- This application is deployed using auto-deployment. The application was modified while the server was down, hence it will be redeployed by the auto-deployment poller. Another possible cause is that the internal file used by the poller was removed or moved from disk. In that case, it assumes applications have changed.
- Action:
- No action is required. This is an informational message to explain why this deployment was redeployed after its deployment at startup.
- BEA-149414
- Could not create directory for autodeployed applications: {0}
- Category:
- Application Poller
- Cause:
- This may be an error on the local file system of the Administration Server.
- Action:
- Correct the error by creating the directory or making sure read/write permissions exist.
- BEA-149415
- An exception was encountered while migrating application poller applications {0}.
- Category:
- Application Poller
- Cause:
- An exception occurred while modifying application's path.
- Action:
- Report this error to My Oracle Support.
- BEA-149416
- Application migrated {0} - {1}
- Category:
- Application Poller
- Cause:
- This is informational message.
- Action:
- No action is required.
- BEA-149417
- Another process is using the file "{0}". The server will attempt to deploy the application once it is unlocked by the other process.
- Category:
- Application Poller
- Cause:
- Another process has a lock on the file that is in the hot deploy directory. The application could still be in the process of being copied.
- Action:
- Ensure that no other process is attempting to lock part or all of this application file. If the copy is ongoing, then no action should be necessary.
- BEA-149500
- An exception occurred while registering the MBean {0}.
- Category:
- JMX
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- This is an internal WebLogic Server error and should be reported as a bug to My Oracle Support.
- BEA-149501
- An exception occurred while registering the MBean {0} at property {1}.
- Category:
- JMX
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- This is an internal WebLogic Server error and should be reported as a bug to My Oracle Support.
- BEA-149502
- An exception occurred while unregistering the MBean {0}.
- Category:
- JMX
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- This is an internal WebLogic Server error and should be reported as a bug to My Oracle Support.
- BEA-149503
- An exception occurred while unregistering the MBean {0} at property {1}.
- Category:
- JMX
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- This is an internal WebLogic Server error and should be reported as a bug to My Oracle Support.
- BEA-149504
- The Administration Server was unable to establish JMX Connectivity with the {0} at the JMX Service URL of {1}.
- Category:
- JMX
- Cause:
- This is likely due to a misconfiguration of the Managed Server. Often this is associated with the use of the administration channel.
- Action:
- Ensure that the Managed Server adminstration ports are properly configured. It may be helpful to review the documentation on the administration channel configuration.
- BEA-149505
- The Administration Server was unable to establish JMX Connectivity with the {0} at the JMX Service URL of {1}.
- Category:
- JMX
- Cause:
- This is likely because the Managed Server is simply not running. It may indicated that the administration channels are not properly configured.
- Action:
- Ensure that the Managed Server administration ports are properly configured. It may be helpful to review the documentation on the administration channel configuration.
- BEA-149506
- Established JMX Connectivity with {0} at the JMX Service URL of {1}.
- Category:
- JMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-149507
- JMX Connectivity has been discontinued with the Managed Server {0}.
- Category:
- JMX
- Cause:
- This message is logged whenever a Managed Server is shut down.
- Action:
- No action is required.
- BEA-149508
- Unable to establish JMX Connectivity with the Administration Server.
- Category:
- JMX
- Cause:
- This may have occurred because the Administration Server is not currently available or it may indicate a misconfiguration of the administrative channels.
- Action:
- If the Administration Server is currently running, the administrator should consult the documentation on the administration channel configuration.
- BEA-149509
- Unable to establish JMX connectivity with the Administration Server {0} at {1}.
- Category:
- JMX
- Cause:
- This may have occurred because the Administration Server is not currently available or it may indicate a misconfiguration of the administrative channels.
- Action:
- If the Administration Server is currently running, the administrator should consult the documentation on the administration channel configuration.
- BEA-149510
- Unable to establish JMX Connectivity with the Administration Server {0} at {1}.
- Category:
- JMX
- Cause:
- This may have occurred because the Administration Server is not currently available or it may indicate a misconfiguration of the administrative channels.
- Action:
- If the Administration Server is currently running, the administrator should consult the documentation on the administration channel configuration.
- BEA-149511
- Established JMX Connectivity with the Administration Server {0} at {1}.
- Category:
- JMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-149512
- JMX Connector Server started at {0}.
- Category:
- JMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-149513
- JMX Connector Server stopped at {0}.
- Category:
- JMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-149515
- An error was encountered getting the attribute {1} on the MBean {0} during a call to getAttributes.
- Category:
- JMX
- Cause:
- This problem is the result of an internal WebLogic Server error in the WebLogic Server JMX implementation.
- Action:
- Report this message to My Oracle Support.
- BEA-149516
- An error was encountered when setting the attribute {1} on the MBean {0} during a call to setAttributes.
- Category:
- JMX
- Cause:
- This problem is the result of an internal WebLogic Server error in the WebLogic Server JMX implementation.
- Action:
- Report this message to My Oracle Support.
- BEA-149518
- An attempt was made to unregister the {0} WebLogic Server MBean through JMX.
- Category:
- JMX
- Cause:
- Avoid using the JMX API to unregister a WebLogic Server MBean.
- Action:
- Use the WebLogic Server APIs to control the configuration of the server environment.
- BEA-149519
- The JMX Service URL {1} for Managed Server {0} was malformed.
- Category:
- JMX
- Cause:
- The URL used to contact a Managed Server was malformed.
- Action:
- See the exception included with this message to determine the proper action.
- BEA-149520
- An attempt was made to register an MBean with ObjectName {0} ObjectName in com.bea domain.
- Category:
- JMX
- Cause:
- An attempt was made to register an MBean with the com.bea domain name.
- Action:
- Register your MBeans with another domain name.
- BEA-149521
- An exception occurred during the processing of JMX Connectivity with the Administration Server: {0}
- Category:
- JMX
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Refer to the embedded exception information for more details and troubleshoot based on that information.
- BEA-149522
- No credentials were provided.
- Category:
- JMX
- Cause:
- Credentials are required when connecting through Remote MAnagement Interface (RMI).
- Action:
- Retry the connection, supplying a username and password.
- BEA-149523
- RmiServerManager not found.
- Category:
- JMX
- Cause:
- This problem is the result of an internal WebLogic Server error in the WebLogic Server JMX implementation.
- Action:
- Report this message to My Oracle Support.
- BEA-149524
- JMX Connector Server started at "{0}".
- Category:
- JMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-149525
- JMX Connector Server stopped at "{0}".
- Category:
- JMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-149526
- Cannot access the attribute "{0}"{ from a partition "{{1}"{ on MBean "{{2}"{ because it is annotated with @ExcludeFromPartition or its interface is annotated with @ExcludeFromPartition.
- Category:
- JMX
- Cause:
- An MBean or its attribute is annotated with @ExcludeFromPartition.
- Action:
- Either do not access the attribute, or remove the @ExcludeFromPartition annotation from the MBean interface or attribute.
- BEA-149527
- Cannot access the operation "{{0}"{ from a partition "{{1}" on MBean "{2}" because it is annotated with @ExcludeFromPartition or the MBean interface is annotated with @ExcludeFromPartition.
- Category:
- JMX
- Cause:
- An attempt was made to access an operation annotated with @ExcludeFromPartition.
- Action:
- Either do not access the operation, or remove the @ExcludeFromPartition annotation from the operation or MBean interface.
- BEA-149528
- Cannot get the attribute "{0}" on MBean "{2}" from the partition "{1}". Either the attribute does not exist or the attribute is not visible to the partition.
- Category:
- JMX
- Cause:
- The attribute does not exist or the attribute is not visible to the partition.
- Action:
- If the attribute does not exist in the MBean, either change the MBean interface and its implementation to add the attribute or change to get other existing attributes. If the attribute exists but is not visible to the partition, annotate the attribute with @VisibleToPartitions ALWAYS.
- BEA-149529
- Cannot set the attribute "{0}" on MBean "{2}" from the partition "{1}". Either the MBean does not contain the attribute or the MBean attribute is not visible to the partition.
- Category:
- JMX
- Cause:
- The attribute does not exist or the attribute is not visible to the partition.
- Action:
- If the attribute does not exist in the MBean, either change the MBean interface and its implementation to add the attribute or change to set other existing attributes. If the attribute exists but is not visible to the partition, annotate the attribute with @VisibleToPartitions ALWAYS.
- BEA-149530
- Cannot invoke the operation "{0}" on MBean "{2}" from partition "{1}". Either the MBean does not contain the operation or the operation is not visible to the partition.
- Category:
- JMX
- Cause:
- The MBean does not contain the operation or the operation is not visible to the partition.
- Action:
- If the operation does not exist in the MBean, either change the MBean interface and its implementation to add the operation or invoke other existing operations. If the operation exists but is not visible to the partition, annotate the operation with @VisibleToPartitions ALWAYS.
- BEA-149531
- Cannot find the MBean "{0}" in partition "{1}".
- Category:
- JMX
- Cause:
- The MBean is not visible to partitions.
- Action:
- The MBean is not registered correctly or the MBean needs to be annotated with @VisibleToPartitions ALWAYS.
- BEA-149532
- The MBean "{0}" contains a different Partition key property value in the ObjectName: found "{1}", should be "{2}".
- Category:
- JMX
- Cause:
- The MBean ObjectName is not correct.
- Action:
- Provide an MBean ObjectName that is owned by the current partition.
- BEA-149533
- Cannot invoke the operation "{0}" on MBean "{2}" from partition "{1}" because one or more of the MBean operation parameters is not visible to partitions: {3}
- Category:
- JMX
- Cause:
- The MBean passed in as an operation parameter is not visible to partitions.
- Action:
- Annotate the MBean passed in as an operation paramter with @VisibleToPartitions ALWAYS.
- BEA-149534
- An exception occurred while calling queryNames for all mBeans from Managed Server: {0}.
- Category:
- JMX
- Cause:
- The size of the result of call queryNames for all mBeans exceeds the configured Maximum Message Size for the Administration Server.
- Action:
- Increase the Maximum Message Size configured for the Administration Server, or disable the indicated Managed Server notifications by using the property weblogic.management.disableManagedServerNotifications=true.
- BEA-149535
- JMX Resiliency Activity Server={0} : {1}
- Category:
- JMX
- Cause:
- Refer to the embedded info fore more details.
- Action:
- Refer to the embedded info for more details.
- BEA-149536
- Received a connect event for a server : {0} to establish JMX Connectivity, which does not exist in the domain configuration. It will be ignored.
- Category:
- JMX
- Cause:
- A managed server is RUNNING while it has been deleted from domain configuration in offline mode on admin server machine.
- Action:
- Validate the domain configuration, and shutdown the managed server.
- BEA-149601
- The deployment framework was unable to resume accepting requests.
- Category:
- Deployer
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-149603
- The deployment framework was unable to cleanly shut down.
- Category:
- Deployer
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-149605
- Failed to create App/Comp MBeans for AppDeploymentMBean {0}. Error - {1}.
- Category:
- Deployer
- Cause:
- An error was found in the AppDeploymentMBean.
- Action:
- Reconfigure the AppDeploymentMBean.
- BEA-149606
- Failed to configure deployment MBean for {0}.
- Category:
- Deployer
- Cause:
- An error was found while configuring a deployment MBean.
- Action:
- Review the application and reconfigure it.
- BEA-149607
- Failed to persist state for deployment with name {0}. {1}
- Category:
- Deployer
- Cause:
- See the exception for more details on the cause of this problem.
- Action:
- See the exception. Undeploy and deploy after correcting the problem.
- BEA-149608
- Unknown type of deployable: "{0}"
- Category:
- Deployer
- Cause:
- The type of deployable: "{0}" is unknown.
- Action:
- See the exception and check for preceding messages 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-149609
- AppRuntimeStateRuntime only available on the Administration Server.
- Category:
- Deployer
- Cause:
- AppRuntimeStateRuntime only available on the Administration Server.
- Action:
- Ensure that the Administration Server is running and check for preceding messages 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-149610
- Problems were encountered while creating the persistent store.
- Category:
- Deployer
- Cause:
- An exception occurred: {0}
- Action:
- See the exception and check for preceding messages 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-149611
- Problems were encountered while creating the persistent store.
- Category:
- Deployer
- Cause:
- An exception occurred: {0}
- Action:
- See the exception and check for preceding messages 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-149612
- Problems were encountered while saving to the persistent store for "{0}".
- Category:
- Deployer
- Cause:
- {1}
- Action:
- See the exception and check for preceding messages 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-149613
- Problems were encountered while deleting from the persistent store for "{0}".
- Category:
- Deployer
- Cause:
- {1}
- Action:
- Check for preceding messages 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-149614
- There were problems during the server disconnect for listener "{0}". {1}
- Category:
- Deployer
- Cause:
- {1}
- Action:
- Check for preceding messages 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-149615
- Unrecognized type: "{0}".
- Category:
- Deployer
- Cause:
- There was an unrecognized type: "{0}".
- Action:
- Check for preceding messages 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-149616
- A critical internal application {0} was not deployed. Error: {1}
- Category:
- Deployer
- Cause:
- The cause of this error is unknown.
- Action:
- Check for 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-149617
- Non-critical internal application {0} was not deployed. Error: {1}
- Category:
- Deployer
- Cause:
- An internal application may not have been installed.
- Action:
- Install the WebLogic Server internal application by running the WebLogic Server installer and choosing the relevant option.
- BEA-149618
- Unable to deploy an internal management Web application - {0}. Managed Servers may be unable to start.
- Category:
- Deployer
- Cause:
- WebLogic Server was unable to find the relevant WAR files in RootDirectory/lib. This might also be an internal failure. See the exception stack trace for more details.
- Action:
- If you are not running the server from the directory where WebLogic Server was installed, ensure that the value of the provided RootDirectory matches the directory where the WebLogic Server product was installed. Verify that a file with the application name in the log message (with a .war extension) is present in RootDirectory/lib. If not, contact My Oracle Support.
- BEA-149619
- The deletion of configuration file {0} failed.
- Category:
- Deployer
- Cause:
- An error occurred while deleting the file.
- Action:
- Ensure that no processes have the file open for write. Ensure that the permissions on the directory allow for delete of this file.
- BEA-149621
- An error occurred while the Administration Server was performing configuration recovery. Error is : "{0}".
- Category:
- Deployer
- Cause:
- See the exception details for the cause.
- Action:
- Stop the server and do configuration recovery manually.
- BEA-149622
- Could not get file lock used to serialize access to configuration files due to {0}.
- Category:
- Deployer
- Cause:
- The lock could not be obtained before the specified timeout period has elapsed.
- Action:
- Verify the configuration files and ensure no server has hung, thereby not releasing the lock.
- BEA-149623
- Unable to create DeploymentManagerMBean.
- Category:
- Deployer
- Cause:
- This may occur if an error at the JMX level exists.
- Action:
- Report this problem to Oracle Customer Support.
- BEA-150000
- An error occurred while establishing a connection back to the Adminstration Server {0} during startup. Since bootstrap succeeded, check that {0} uniquely identifies the Administration Server.
- Category:
- Configuration Management
- Cause:
- An improper Administration Server URL has been specified, or the Administration Server is not available at the specified URL. Commonly this is because the Managed Server shares an adminstration URL with the Administration Server. Another possibility is that the host identified by {0}, or the local host, is not configured properly. For instance, an /etc/hosts or DNS lookup on the hostname results in a loopback address.
- Action:
- Verify that the URL specified for the Administration Server is valid, unique and that the Administration Server is available and listening at the specified URL. A common problem is that the administration port is enabled and both the Administration Server and Managed Server are running on the same machine. In this instance a different administration port should be selected for the Managed Server. Another possibility is that the host identified by {0}, or the local host, is not configured properly. For instance, an /etc/hosts or DNS lookup on the hostname results in a loopback address.
- BEA-150001
- An error occurred while connecting to the Administration Server to bootstrap through the URL: {0}, user: {1}.
- Category:
- Configuration Management
- Cause:
- The Administration Server might currently be unavailable or the specified URL: {0} or username: {1} might be invalid.
- Action:
- Confirm that the designated Administration Server is running and that the specified URL: {0} and username: {1} are valid for this configuration.
- BEA-150014
- The Managed Server Independence feature is disabled for this server ({0}).
- Category:
- Configuration Management
- Cause:
- The specified Administration Server is either incorrect or not reachable on the network.
- Action:
- Ensure that the Administration Server is running and reachable by this server, or set the ManagedServerIndependenceEnabled attribute on this server to true.
- BEA-150018
- This server is being started in Managed Server independence mode in the absence of the Administration Server.
- Category:
- Configuration Management
- Cause:
- The Managed Server was unable to communicate with the Adminstration Server at the provided URL because the specified Administration Server either was not running or was partitioned.
- Action:
- Restart the Administration Server with Managed Server discovery enabled so that the running Managed Server can synchronize its configuration with the Administration Server and become centrally managed.
- BEA-150020
- The Managed Server could not reach the Administration Server at {0}.
- Category:
- Configuration Management
- Cause:
- The Managed Server was given a URL on which the Administration Server could not be contacted.
- Action:
- Inspect the Administration Server address:port provided to the Managed Server that is being started. This address should be changed to point to the Administration Server rather than resolving locally on the Managed Server.
- BEA-150021
- The Administration Server failed to authenticate the identity of the user {0} starting the Managed Server. The reason for the error is {1}.
- Category:
- Configuration Management
- Cause:
- The username and password combination was not correct.
- Action:
- Inspect the username and password of the user starting the Managed Server and supply the correct credentials. The username and password are specified on startup with -Dweblogic.management.username and -Dweblogic.management.password command line options to the java weblogic.Server command.
- BEA-150024
- The server name {0} is being started again as a Managed Server.
- Category:
- Configuration Management
- Cause:
- The Administration Server is being started as the Managed Server.
- Action:
- Specify a different server name to start.
- BEA-150026
- The server {0} being started is at an invalid release level {1} with respect to the Administration Server {2}. The major version of the Administration Server must be less than or equal to the major version of the Managed Server.
- Category:
- Configuration Management
- Cause:
- A Managed Server of a different major release is attempting to start from the Administration Server.
- Action:
- Point the Managed Server to an Administration Server at the correct release level.
- BEA-150027
- Server name {0} not found in domain {1}.
- Category:
- Configuration Management
- Cause:
- A Managed Server is started with -Dweblogic.Name with a value that was not configured in the domain.
- Action:
- Specify the correct value of the parameter -Dweblogic.Name.
- BEA-150028
- A security failure or an exception occurred when retrieving the bootstrap information for the Managed Server.
- Category:
- Configuration Management
- Cause:
- An invalid username and password might have been supplied while starting the Managed Server.
- Action:
- Supply the correct credentials. Take corrective action based on the exception details.
- BEA-150032
- The Managed Server did not provide any version details at initial contact.
- Category:
- Configuration Management
- Cause:
- A Managed Server of a different major and minor release is attempting to start from the Administration Server.
- Action:
- Point the Managed Server to an Administration Server at the correct release level.
- BEA-150034
- An attempt was made to download the configuration for the server {0} without the required credentials.
- Category:
- Configuration Management
- Cause:
- This should not happen during normal operations and may represent an attempt to compromise the server.
- Action:
- Identify the server from which the connection was made and ensure that the username and password are being properly specified.
- BEA-150035
- An attempt was made to download the configuration for the server {0} by the user {1} with an invalid password.
- Category:
- Configuration Management
- Cause:
- This should not happen during normal operations and may represent an attempt to compromise the server.
- Action:
- Identify the server from which the connection was made and ensure that the username and password are being properly specified.
- BEA-150036
- An attempt was made to download the configuration for the server {0} by the unauthorized user {1}.
- Category:
- Configuration Management
- Cause:
- This should not happen during normal operations and may represent an attempt to compromise the server.
- Action:
- Identify the server from which the connection was made and ensure that the username and password are being properly specified.
- BEA-150038
- A configuration file was found in the parent directory {0}, but the root directory is empty.
- Category:
- Configuration Management
- Cause:
- This message indicates that a configuration file exists in the parent of the root directory.
- Action:
- If the specified root directory is not correct, then take appropriate action. Otherwise, this message may be ignored.
- BEA-150039
- The server name could not be determined.
- Category:
- Configuration Management
- Cause:
- The name was not specified or the specified name does not exist in the config.xml file.
- Action:
- Specify the correct value of the parameter -Dweblogic.Name.
- BEA-150041
- The server name {0} is unknown to the Administration Server. Check if restart is required.
- Category:
- Configuration Management
- Cause:
- The -Dweblogic.Name command line property specifies a server that does not exist in the configuration that is active on the Administration Server. This can occur if the Managed Server was added to the configuration along with non-dynamic changes that affect the Administration Server. In this case, the Administration Server must be restarted.
- Action:
- Check to see if the Administration Server is marked as needing a restart. If it is, then restart the Administration Server before trying to start this Managed Server. Check the configuration for the list of configured servers.
- BEA-150042
- The -Dweblogic.management.server value of {0} does not specify a port that has administrator privileges. Change the startup command to specify a -Dweblogic.management.server value of {1}. This server will remain in Managed Server independence mode until it is started with a port that has administrator privileges.
- Category:
- Configuration Management
- Cause:
- The specified Administration Server port does not support the administrator traffic required to allow the Managed Server to communicate with the Administration server.
- Action:
- Change the -Dweblogic.management.server property to specify a port that has administator privileges.
- BEA-150043
- Cannot delete server {0} in domain {1} while the server is running. Please shut down the server in order to delete the server.
- Category:
- Configuration Management
- Cause:
- An attempt was made to delete a static or dynamic Managed Server while it was still running.
- Action:
- Shut down the server and retry the change that deleted the server.
- BEA-150044
- The protection domain of class {1} does not have permission to inject a service from descriptor {0}. The protection domain is {2} and the permission is {3}.
- Category:
- Configuration Management
- Cause:
- A service does not have permission to inject a service that was found for it. The creation of the service will fail if no other appropriate service can be found to satisfy the injection point.
- Action:
- Ensure that the protection domain of the class has rights to the specified permission.
- BEA-150045
- Edit session name {0} contains illegal character(s) and cannot be used. Choose a different name.
- Category:
- Configuration Management
- Cause:
- The specified edit session name does not meet the criteria for this component. It contains illegal character(s).
- Action:
- Choose a different name.
- BEA-150046
- An edit session named {0} already exists. Choose a different name.
- Category:
- Configuration Management
- Cause:
- You attempted to create two edit sessions with the same name.
- Action:
- Choose a different name.
- BEA-150048
- Cannot destroy default edit session.
- Category:
- Configuration Management
- Cause:
- You attempted to destroy the default edit session.
- Action:
- Use a named edit session.
- BEA-150049
- The JMS server named {0} has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is {1}, and the template name is {2}. However, a JMSSystemResourceMBean of name {1} could not be found. The JMS server {0} will not boot until this problem has been fixed.
- Category:
- Configuration Management
- Cause:
- The temporary template for a JMS server must come from a JMSSystemResourceMBean. A common mistake is to put the temporary template into an AppDeployment. However, because the temporary template must be owned by the administrator, all temporary templates must come from JMSSystemResourceMBeans, not AppDeployments.
- Action:
- Put the temporary template into a JMSSystemResource.
- BEA-150050
- Cannot destroy DOMAIN partition.
- Category:
- Configuration Management
- Cause:
- You attempted to destroy DOMAIN partition. This is not a valid operation.
- Action:
- Use a named edit session.
- BEA-150051
- Cannot remove edit session. This edit session belongs to a different partition.
- Category:
- Configuration Management
- Cause:
- Entities from other partitions cannot be operated on in an edit session for a given partition.
- Action:
- Review the management request.
- BEA-150052
- Edit session {0} is locked by user {1} and cannot be deleted. Administrator permissions required.
- Category:
- Configuration Management
- Cause:
- The edit session is currently being edited.
- Action:
- Review the management request or use force=true while logged in as an administrator.
- BEA-150053
- Edit session {0} is locked by user {1} and cannot be deleted. Use destroyEditSession("{0}", force = true) to override.
- Category:
- Configuration Management
- Cause:
- The edit session is currently being edited.
- Action:
- Review management request or use force=true.
- BEA-150054
- Edit session {0} contains changes pending activation. Destroy edit session command has been aborted. Use destroyEditSession("{0}", force = true) to force the destroy operation.
- Category:
- Configuration Management
- Cause:
- The edit session contains changes that are pending activation.
- Action:
- Review the management request or use force=true.
- BEA-150055
- Edit session {0} was created by user {1}. Administrator permissions required.
- Category:
- Configuration Management
- Cause:
- The caller is not the creator of the edit session.
- Action:
- Review the management request or use force=true while logged in as an administrator.
- BEA-150056
- Edit session {0} was created by user {1}. Destroy edit session command has been aborted. Use destroyEditSession("{0}", force = true) to force the destroy operation.
- Category:
- Configuration Management
- Cause:
- The caller is not the creator of the edit session.
- Action:
- Review the management request or use force=true.
- BEA-150057
- A failure has occurred during service lookup, bind or unbind from descriptor {0} using permission {1} with: {2}
- Category:
- Configuration Management
- Cause:
- The operation being performed does not have permission to lookup, bind or unbind the service descriptor.
- Action:
- Carefully read the returned error to determine what action is required.
- BEA-150058
- The Restart In Place setting of Persistent Store "{0}" is configured to True and will be ignored. This setting is ignored when a store is directly targeted to a server within a cluster or is targeted to a migratable target. If a store is targeted to a migratable target, you can tune restart in place on the migratable target itself instead of on the store.
- Category:
- Configuration Management
- Cause:
- RestartInPlace is not supported when the store is targeted to a Single Server within a Cluster.
- Action:
- No action is required.
- BEA-150059
- RestartInPlace of ReplicatedStore {0} is configured to True, which is invalid and will be ignored, when the store is targeted to a Single Server or its Migration Policy is Off
- Category:
- Configuration Management
- Cause:
- ReplicatedStore doesn't support RestartInPlace when the store is targeted to a Single Server or its Migration Policy is Off.
- Action:
- No action is required.
- BEA-159900
- USER {0} CREATED {1}
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159901
- USER {0} CREATE {1} FAILED {2}
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159902
- USER {0} REMOVED {1}
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159903
- USER {0} REMOVE {1} FAILED {2}
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159904
- USER {0} MODIFIED {1} ATTRIBUTE {2} FROM {3} TO {4}
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159905
- USER {0} MODIFY {1} ATTRIBUTE {2} FROM {3} TO {4} FAILED {5}
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159907
- USER {0} INVOKED ON {1} METHOD {2} PARAMS {3}
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159908
- USER {0} INVOKED ON {1} METHOD {2} PARAMS {3} FAILED {4}
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159909
- USER {0}, configuration auditing is enabled.
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159910
- USER {0}, configuration auditing is disabled.
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-159911
- Invalid number {0} was found while encrypting clear text passwords.
- Category:
- Configuration Audit
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-160001
- Error deploying {0}: {1}
- Category:
- J2EE
- Cause:
- The application is misconfigured. See the logged exception for more details.
- Action:
- Check the config.xml to ensure that the component MBean is wrapped in a valid application MBean and that it has a valid URI and target attribute. Check the server log for errors.
- BEA-160032
- Unable to create mbean Name: {0} Type: {1} Exception: {2}
- Category:
- J2EE
- Cause:
- See message body.
- Action:
- See exception message logged.
- BEA-160039
- Failed to undeploy a mail session.
- Category:
- J2EE
- Cause:
- There was a JNDI unbind error.
- Action:
- Check the error that is reported in the exception.
- BEA-160040
- Deployed MailSession named {0}
- Category:
- J2EE
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-160041
- Undeployed MailSession named {0}.
- Category:
- J2EE
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-160069
- Error while looking for Web services files: {0}
- Category:
- J2EE
- Cause:
- An IOException occurred while accessing Web services files.
- Action:
- See the stack trace for details.
- BEA-160083
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" could not be resolved. The ejb-jar file "{4}" could not be found in this EAR file.
- Category:
- J2EE
- Cause:
- The path to the target EJB does not exist in the application.
- Action:
- The ejb-link must be fixed to point to the module containing the target EJB.
- BEA-160084
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" could not be resolved. The ejb-jar file "{3}" could not be found in this ear file.
- Category:
- J2EE
- Cause:
- The path to the target EJB does not exist in the application.
- Action:
- The ejb-link must be fixed to point to the module containing the target EJB.
- BEA-160085
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" could not be resolved. The EAR module "{4}" does not contain an EJB with the name "{5}".
- Category:
- J2EE
- Cause:
- The specified EJB does not exist in the module.
- Action:
- The ejb-link must be fixed to point to a valid EJB.
- BEA-160086
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" could not be resolved. The EAR module "{3}" does not contain an EJB with the name "{4}".
- Category:
- J2EE
- Cause:
- The specified EJB does not exist in the module.
- Action:
- The ejb-link must be fixed to point to a valid EJB.
- BEA-160087
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" did not resolve to a bean with component interfaces. Ensure that the link is correct.
- Category:
- J2EE
- Cause:
- The link did not resolve to a valid EJB.
- Action:
- The ejb-link must be fixed to point to a valid EJB.
- BEA-160088
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" did not resolve to a bean with component interfaces. Ensure that the link is correct.
- Category:
- J2EE
- Cause:
- The link did not resolve to a valid EJB.
- Action:
- The ejb-link must be fixed to point to a valid EJB.
- BEA-160089
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" could not be resolved. No EJB named "{0}" with component interfaces exists in the application. Ensure that the link is correct.
- Category:
- J2EE
- Cause:
- The specified EJB does not exist in the module.
- Action:
- The ejb-link must be fixed to point to a valid EJB.
- BEA-160090
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" could not be resolved. No EJB named "{0}" with component interfaces exists in the application. Ensure that the link is correct.
- Category:
- J2EE
- Cause:
- The specified EJB does not exist in the module.
- Action:
- The ejb-link must be fixed to point to a valid EJB.
- BEA-160091
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" for EJB "{2}" in the module "{3}" is ambiguous. The following list of application modules contain an EJB with the name "{0}": {4}. Qualify this ejb-link to remove the ambiguity.
- Category:
- J2EE
- Cause:
- The ejb-link is unqualified and resolves to multiple EJBs in the application.
- Action:
- The ejb-link must be fixed to point to a single EJB.
- BEA-160092
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the module "{2}" is ambiguous. The following list of application modules contain an EJB with the name "{0}": {3}. Qualify this ejb-link to remove the ambiguity.
- Category:
- J2EE
- Cause:
- The ejb-link is unqualified and resolves to multiple EJBs in the application.
- Action:
- The ejb-link must be fixed to point to a single EJB.
- BEA-160093
- Error: The ejb-link "{0}" declared in the {1} "{2}" for EJB "{3}" in the module "{4}" could not be established. The target of the ejb-link does not have {5} interfaces. Ensure that the link is correct.
- Category:
- J2EE
- Cause:
- The ejb-link resolves to an EJB which does not expose interfaces compatible with the ref type.
- Action:
- Ensure that the target of the ejb-link is correct. If it is, either add component interfaces to this EJB that are compatible with the ref type or change the ref type to be compatible with the interfaces exposed by the target EJB.
- BEA-160094
- Error: The ejb-link "{0}" declared in the {1} "{2}" in the module "{3}" could not be established. The target of the ejb-link does not have {4} interfaces. Ensure that the link is correct.
- Category:
- J2EE
- Cause:
- The ejb-link resolves to an EJB which does not expose interfaces compatible with the ref type.
- Action:
- Ensure that the target of the ejb-link is correct. If it is, either add component interfaces to this EJB that are compatible with the ref type or change the ref type to be compatible with the interfaces exposed by the target EJB.
- BEA-160095
- Warning: The {0} "{1}" for EJB "{2}" in the module "{3}" has an invalid {4} element value "{5}". The target bean does not declare that {4} interface. Ensure that the values are correct.
- Category:
- J2EE
- Cause:
- The home or component interface name in the ejb-ref or ejb-local-ref does not match the home or component interface name of the target EJB.
- Action:
- Ensure that the target of the ejb-link is correct. If it is, fix the ejb-ref or ejb-local-ref so that the names of the home and component interfaces match the names of the home and component interfaces of the target EJB.
- BEA-160096
- Warning: The {0} "{1}" in the module "{2}" has an invalid {3} element value "{4}". The target bean does not declare that {3} interface. Ensure that the values are correct.
- Category:
- J2EE
- Cause:
- The home or component interface name in the ejb-ref or ejb-local-ref does not match the home, component or business interface name of the target EJB.
- Action:
- Ensure that the target of the ejb-link is correct. If it is, fix the ejb-ref or ejb-local-ref so that the names of the home and component interfaces match the names of the home and component interfaces of the target EJB.
- BEA-160098
- Unable to parse the file "{0}" because it uses an invalid encoding name, "{1}". All deployment descriptors must use an IANA or Java encoding name. Change the encoding of the descriptor to be a supported encoding.
- Category:
- J2EE
- Cause:
- The encoding name used by the deployment descriptor is not supported.
- Action:
- Change the encoding name of the deployment descriptor to an IANA or Java encoding name.
- BEA-160100
- Could not deploy role: {0} for application: {1}.
- Category:
- J2EE
- Cause:
- The application could not deploy the role defined in application.xml.
- Action:
- Ensure that the security is configured properly in the server. Also, check the stack trace for the exact cause.
- BEA-160101
- Error: The ejb-link "{0}" declared in the ejb-ref or ejb-local-ref "{1}" in the application module "{2}" could not be resolved. The target EJB for the ejb-ref could not be found. Ensure that the link is correct.
- Category:
- J2EE
- Cause:
- The target of the ejb-link could not be found in the application.
- Action:
- Fix the ejb-link to point to a valid EJB.
- BEA-160104
- Invalid local reference in application {0}. A local reference from module {1} to {2} is not allowed because the referencing module does not have visibility to the classes of the referenced module.
- Category:
- J2EE
- Cause:
- The current module does not have visibility to the classloader of the EJB being referenced.
- Action:
- Look at the classloader organization defined by the classloader-structure element in weblogic-application.xml and ensure that the calling module is either using the same classloader as the module containing the referenced EJB or that the calling module is using a classloader that is an offspring of the classloader of the EJB module.
- BEA-160106
- ERROR: The source file, "{0}", could not be found.
- Category:
- J2EE
- Cause:
- The source file could not be found.
- Action:
- Ensure that the specified source file exists and try again.
- BEA-160108
- ERROR: Error accessing input file "{0}": {1}
- Category:
- J2EE
- Cause:
- The source file could not be accessed.
- Action:
- Ensure that the source file is accessible and try again.
- BEA-160109
- ERROR: Error copying files to the directory "{0}": {1}
- Category:
- J2EE
- Cause:
- The compiler was unable to extract the source archive to a directory. This can be caused by a lack of permission to write to the directory or a lack of disk space.
- Action:
- Ensure that the directory is writable and that there is enough free disk space to extract the archive. Alternatively, manually extract the archive to a directory and specify the directory name as the appc argument instead of the archive.
- BEA-160110
- ERROR: appc could not create the working directory, "{0}". Ensure that this directory can be created and try again.
- Category:
- J2EE
- Cause:
- A directory was specified in the appc command and it could not be created. appc will not be able to finish compiling the application because of this.
- Action:
- Ensure that the directory can be created and try again.
- BEA-160111
- ERROR: appc can not write to the working directory, "{0}". Ensure that you have write permission for this directory and try again.
- Category:
- J2EE
- Cause:
- The specified directory is not writable.
- Action:
- Ensure that the directory is writable and try again.
- BEA-160112
- Error: The directory, "{0}", does not contain a valid module. If the directory represents an EAR file, it must contain a META-INF/application.xml file. If the directory represents an ejb-jar file, it must contain a META-INF/ejb-jar.xml file. If the directory represents a WAR file, it must contain a WEB-INF/web.xml file. Ensure that the source directory is a valid module and try again.
- Category:
- J2EE
- Cause:
- The specified directory does not contain a valid module to compile.
- Action:
- Ensure that the specified source directory contains a valid module and try again.
- BEA-160113
- Error: The source file, "{0}", is not a valid ejb-jar file. To be valid, it must contain a META-INF/ejb-jar.xml file.
- Category:
- J2EE
- Cause:
- The specified source file is not a valid ejb-jar file.
- Action:
- Ensure that the specified source file is a valid ejb-jar file and try again.
- BEA-160114
- Error: The source file, "{0}", is not a valid WAR file. To be valid, it must contain a WEB-INF/web.xml file.
- Category:
- J2EE
- Cause:
- The specified source file is not a valid WAR file.
- Action:
- Ensure that the specified source file is a valid WAR file and try again.
- BEA-160115
- Error: The source file, "{0}", is not a valid EAR file. To be valid, it must contain a META-INF/application.xml file.
- Category:
- J2EE
- Cause:
- The specified source file is not a valid EAR file.
- Action:
- Ensure that the specified source file is a valid EAR file and try again.
- BEA-160117
- appc is unable to continue processing file "{0}": {1}
- Category:
- J2EE
- Cause:
- An error occurred while processing the specified source file.
- Action:
- Find the cause of the exception and take any necessary steps to remedy it.
- BEA-160118
- appc is unable to continue processing the file "{0}". The following error occurred while accessing it: {1}
- Category:
- J2EE
- Cause:
- An error occurred while processing the specified source file.
- Action:
- Find the cause of the exception and take any necessary steps to remedy it.
- BEA-160119
- appc is unable to process the file "{0}". The following error occurred: {1}
- Category:
- J2EE
- Cause:
- An error occurred while processing the specified source file.
- Action:
- Find the cause of the exception and take any necessary steps to remedy it.
- BEA-160120
- Error: The module, "{0}", is declared either in the application.xml or in the weblogic-application.xml descriptor but cannot be found in the EAR file.
- Category:
- J2EE
- Cause:
- The specified module cannot be found in the EAR file.
- Action:
- Ensure that either the application.xml or the weblogic-application.xml declaration is correct.
- BEA-160121
- Errors encountered while compiling module "{0}": {1}
- Category:
- J2EE
- Cause:
- Errors were encountered while compiling the specified module.
- Action:
- Investigate the specific errors and take any recommended actions.
- BEA-160122
- Errors validating EAR file: {0}
- Category:
- J2EE
- Cause:
- Errors were encountered while validating the EAR file.
- Action:
- Investigate the specific errors and take any recommended actions.
- BEA-160123
- ERROR: Could not create output archive, "{0}", restoring previous archive. The error was: {1}
- Category:
- J2EE
- Cause:
- An error occurred while creating the output archive.
- Action:
- Investigate the specific error and take any necessary actions.
- BEA-160124
- ERROR: Could not create output archive "{0}". The error was: {1}
- Category:
- J2EE
- Cause:
- An error occurred while creating the output archive.
- Action:
- Investigate the specific error and take any necessary actions.
- BEA-160125
- ERROR: Could not delete old backup file: {0}.
- Category:
- J2EE
- Cause:
- An old backup file could not be removed.
- Action:
- Determine why the old backup file could not be deleted and remedy the problem. Manually deleting the old backup file prior to running appc should fix this issue.
- BEA-160126
- ERROR: Could not create backup file "{0}". The error was: {1}
- Category:
- J2EE
- Cause:
- The specified backup file could not be created.
- Action:
- Determine why the backup file could not be created and remedy the problem. In particular, ensure that you have write permission to the specified file and that the disk is not full.
- BEA-160127
- ERROR: Could not delete previous archive: {0}
- Category:
- J2EE
- Cause:
- The specified archive could not be removed.
- Action:
- Determine why the archive could not be deleted and remedy the problem. In particular, ensure that you have permission to modify the specified file.
- BEA-160128
- ERROR: Incorrect appc command. Too many arguments were given. The appc command only takes a single argument, the source file, in addition to the supported options.
- Category:
- J2EE
- Cause:
- Too many arguments were specified in the appc command.
- Action:
- Correct the command and try again.
- BEA-160129
- ERROR: The alt-dd "{0}", specified for application module "{1}", could not be found. Remove the alt-dd entry from the application.xml descriptor or ensure that it points to a valid deployment descriptor.
- Category:
- J2EE
- Cause:
- The specified alt-dd could not be found.
- Action:
- Remove the invalid alt-dd entry from application.xml or ensure that it points to a valid deployment descriptor.
- BEA-160130
- ERROR: The application level alt-dd "{0}", specified in the appc command, could not be found. Ensure that the alt-dd points to a valid deployment descriptor or remove it from the command line.
- Category:
- J2EE
- Cause:
- The specified alt-dd could not be found.
- Action:
- Correct or remove the invalid alt-dd setting in the appc command.
- BEA-160132
- Warning: The {0} "{1}" for EJB "{2}" in the module "{3}" has an ejb-ref-type of {4} but the ejb-link does not resolve to an EJB of that type. Ensure that the ejb-link and ejb-ref-type are correct.
- Category:
- J2EE
- Cause:
- The ejb-ref or ejb-local-ref resolves to an EJB of a different type than is declared in the ejb-ref.
- Action:
- Ensure that the ejb-ref or ejb-local-ref resolves to the correct EJB. Once this is verified, ensure that the ejb-ref-type declared in the ejb-ref corresponds to the type of EJB being referred to.
- BEA-160133
- Warning: The {0} "{1}" in the module "{2}" has an ejb-ref-type of {3} but the ejb-link does not resolve to an EJB of that type. Ensure that the ejb-link and ejb-ref-type are correct.
- Category:
- J2EE
- Cause:
- The ejb-ref or ejb-local-ref resolves to an EJB of a different type than is declared in the ejb-ref.
- Action:
- Ensure that the ejb-ref or ejb-local-ref resolves to the correct EJB. Once this is verified, ensure that the ejb-ref-type declared in the ejb-ref corresponds to the type of EJB being referred to.
- BEA-160134
- Error: The EJB with the name "{0}" in ear module "{1}" has an entity-cache-ref with the name "{2}" in its weblogic-ejb-jar.xml descriptor but no application level entity cache with that name is defined in the weblogic-application.xml descriptor for the application.
- Category:
- J2EE
- Cause:
- The entity-cache referred to by the EJB could not be found.
- Action:
- Ensure that the entity-cache-ref is correct in the weblogic-ejb-jar.xml descriptor for the EJB. Also, ensure that an entity-cache with the same name is declared in the weblogic-application.xml descriptor for the application.
- BEA-160137
- Error: The message-destination-link "{0}" declared in the message-destination-ref "{1}" in the application module "{2}" could not be resolved. The target message-destination for the message-destination-ref could not be found. Ensure that the link is correct.
- Category:
- J2EE
- Cause:
- The target of the message-destination-link could not be found in the application.
- Action:
- Fix the message-destination-link to point to a valid message-destination.
- BEA-160138
- Could not set active version state for application: {0}.
- Category:
- J2EE
- Cause:
- See the message detail.
- Action:
- Contact My Oracle Support.
- BEA-160139
- The following library reference has "context-path" set, which has no effect when referencing a {1} library: {0}.
- Category:
- J2EE
- Cause:
- The library reference has "context-path" set, but is not referencing a WAR library.
- Action:
- Remove "context-path" from the library reference.
- BEA-160140
- Unresolved optional package references (in META-INF/MANIFEST.MF): {0}. Ensure that the referenced optional package has been deployed as a library.
- Category:
- J2EE
- Cause:
- One or more MANIFEST.MF files contain references to optional packages (using the Extension-List attribute). One or more of the referenced optional packages are not available.
- Action:
- Register the required optional packages or remove the reference(s) from the manifest(s).
- BEA-160141
- Could not initialize the library {0}. Ensure that the deployment unit is a valid library type (WAR, EJB, EAR, plain JAR). {1}
- Category:
- J2EE
- Cause:
- Refer to the exception in the message body.
- Action:
- Examine the stack trace.
- BEA-160142
- The library at {0} has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0; for example: 2.1.1
- Category:
- J2EE
- Cause:
- The Specification-Version for the library at {0} cannot be parsed.
- Action:
- Fix the library Specification-Version to conform to the required version string syntax.
- BEA-160143
- Library {0} has an illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1.
- Category:
- J2EE
- Cause:
- The library cannot be statically deployed because its MBean has an invalid Specification-Version.
- Action:
- Undeploy the library and deploy it again with a correct Specification-Version.
- BEA-160144
- Failed to register library {0}: {1}
- Category:
- J2EE
- Cause:
- The error is: {1}
- Action:
- Examine the error message.
- BEA-160145
- Failed to deploy library {0}, because of conflicting library Manifest values, and library information registered with the server: {1}. Check the library MANIFEST.MF file and correct version information there to match server settings, or undeploy the misconfigured library.
- Category:
- J2EE
- Cause:
- Conflict between library manifest values and library settings in the LibraryMBean.
- Action:
- Check the library MANIFEST.MF file and correct the version information there to match server settings, or undeploy the misconfigured library.
- BEA-160146
- Failed to process library at {0}, because of conflicting library manifest values and the library information provided on the appc command line: {1}.
- Category:
- J2EE
- Cause:
- There was a conflict between the library manifest values and the library information provided on the appc command line.
- Action:
- Avoid setting the library name and version information on the appc command line if its already set in the manifest or remove values from the manifest and set them on the appc command line.
- BEA-160147
- One or more libraries could not be processed. See error above.
- Category:
- J2EE
- Cause:
- See error above.
- Action:
- See error above.
- BEA-160148
- These libraries were not referenced by the compiled application: {0}.
- Category:
- J2EE
- Cause:
- The compiled application did not reference the libraries that were passed to appc.
- Action:
- These libraries do not need to be passed to appc to compile this particular application.
- BEA-160149
- Error while processing library references. {0}
- Category:
- J2EE
- Cause:
- The application has library references that do not resolve.
- Action:
- Ensure that the library references are accurate and that the required libraries are available.
- BEA-160150
- A library reference in weblogic-application.xml has an illegal Specification-Version: {0}. The Specification-Version must be a valid version string: int(.int)*, int >=0; example: 2.1.1
- Category:
- J2EE
- Cause:
- The Specification-Version of a library reference in weblogic-application.xml cannot be parsed.
- Action:
- Fix the library Specification-Version in weblogic-application.xml to conform to the required version string syntax.
- BEA-160151
- Registered library {0}.
- Category:
- J2EE
- Cause:
- Library registration was successful.
- Action:
- No action is required.
- BEA-160152
- The library at {0} was not recognized as a valid library type.
- Category:
- J2EE
- Cause:
- The library at {0} was not recognized as a valid library type.
- Action:
- Ensure that the library is one of the supported library types.
- BEA-160153
- Error while cleaning up library {0}: {1}
- Category:
- J2EE
- Cause:
- Error while cleaning up library {0}: {1}
- Action:
- Examine the stack trace.
- BEA-160154
- Error while cleaning up library: {0}. {1}
- Category:
- J2EE
- Cause:
- Error while cleaning up library: {0}. {1}
- Action:
- Examine the stack trace.
- BEA-160155
- Cannot find library at: {0}.
- Category:
- J2EE
- Cause:
- {0} is not a file.
- Action:
- Fix the path to the library.
- BEA-160156
- Cannot process libdir: {0} is not a directory.
- Category:
- J2EE
- Cause:
- {0} is not a directory.
- Action:
- Fix the path to libdir.
- BEA-160157
- The referenced library, {0}, is not a supported application library.
- Category:
- J2EE
- Cause:
- {0} is not a supported application library.
- Action:
- Remove the reference to library {0} from weblogic-application.xml.
- BEA-160158
- Ignoring Extension-List reference {0}, because the manifest does not have an entry for {0}-Extension-Name. The manifest is at {1}/META-INF/MANIFEST.MF
- Category:
- J2EE
- Cause:
- A declared Extension-List name does not have the required Extension-Name entry.
- Action:
- Remove {0} from the Extension-List or add {0}-Extension-Name entry into the manifest.
- BEA-160159
- Bad optional package reference in manifest at {2}/META-INF/MANIFEST.MF, for optional package with Extension-Name: {0}. Illegal Specification-Version: {1}. The Specification-Version must be a valid version string: int(.int)*, int >=0; example: 2.1.1. Ignoring this Optional Package reference.
- Category:
- J2EE
- Cause:
- Cannot parse the Specification-Version of an optional package reference.
- Action:
- Change the optional package reference Specification-Version to the required version string syntax.
- BEA-160161
- Error while parsing the application descriptors for {0}: {1}.
- Category:
- J2EE
- Cause:
- The cause is {1}
- Action:
- Examine the error message.
- BEA-160162
- No META-INF/application.xml was found in the EAR at {0}.
- Category:
- J2EE
- Cause:
- The application.xml file could not be found.
- Action:
- Ensure that the path to the EAR file is correct and add the missing application.xml.
- BEA-160163
- No modules were found in application.xml for EAR: {0}. Nothing to do.
- Category:
- J2EE
- Cause:
- There are no modules in this EAR's application.xml
- Action:
- Add module entries to the EAR's application.xml.
- BEA-160164
- Error while importing library {0}: {1}
- Category:
- J2EE
- Cause:
- See the exception: {1}.
- Action:
- Examine the stack trace.
- BEA-160165
- The EAR library at {0} is organized using the splitdir directory structure. splitdir is not supported for libraries.
- Category:
- J2EE
- Cause:
- splitdir is not supported for EAR libraries.
- Action:
- Archive this library. If a build file was generated using BuildXMLGen, run the EAR target in that file.
- BEA-160166
- References were found in the deployment plan for module "{0}" with URI, "{1}". The plan was merged.
- Category:
- J2EE
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-160167
- The module {1} in application {0} uses ejb-links but no EJB modules were found for this application.
- Category:
- J2EE
- Cause:
- The ejb-links must correspond to an EJB module deployed within the same application.
- Action:
- Ensure that the EJB modules to which you intended to link exist and have been configured properly.
- BEA-160168
- An error occurred while merging descriptors: {0}
- Category:
- J2EE
- Cause:
- An error occurred while merging descriptors. Check the stack trace.
- Action:
- Check the stack trace.
- BEA-160169
- An error occurred while parsing descriptors: {0}
- Category:
- J2EE
- Cause:
- An error occurred while parsing descriptors.
- Action:
- Check the stack trace.
- BEA-160170
- Imported library {0} for Application {1}
- Category:
- J2EE
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-160171
- ERROR: The plan file, "{0}", could not be found.
- Category:
- J2EE
- Cause:
- The plan file could not be found.
- Action:
- Ensure that the specified plan file exists and try again.
- BEA-160172
- ERROR: To run appc, specify a plan file ending with the suffix .xml.
- Category:
- J2EE
- Cause:
- The plan file type is not supported.
- Action:
- Correct the plan argument and try again.
- BEA-160173
- ERROR: Error accessing input file "{0}": {1}
- Category:
- J2EE
- Cause:
- The plan file could not be accessed.
- Action:
- Ensure that the plan file is accessible and try again.
- BEA-160174
- ERROR: Failed to parse deployment plan "{0}": {1}
- Category:
- J2EE
- Cause:
- The plan file could not be parsed.
- Action:
- Resolve parse errors in the plan and retry.
- BEA-160175
- ERROR: Could not find JMS module of name "{2}" specified in the resource-link named "{3}" in the "{1}" component named "{0}".
- Category:
- J2EE
- Cause:
- The JMS module used in the resource-link cannot be found in the application package.
- Action:
- Package the missing JMS module as part of this application and retry.
- BEA-160176
- ERROR: Could not find the JMS resource named "{4}" of type "{5}" inside the JMS module "{2}" that is specified in the resource-link named "{3}" in the "{1}" component named "{0}".
- Category:
- J2EE
- Cause:
- The JMS resource used in th resource-link was not found in the application package.
- Action:
- Create the missing JMS resource in the corresponding JMS module and retry.
- BEA-160177
- The application at "{0}" was not recognized as a valid application type. If this is an EAR file, please ensure the META-INF/application.xml exists. EJB-JARs should have a META-INF/ejb-jar.xml or corresponding annotations exist. If this is an exploded WAR, the name of directory must be end with ".war". RARs require a META-INF/ra.xml. A JMS deployment should be an XML file whose name ends with "-jms.xml". A JDBC deployment should be an XML file whose name ends with "-jdbc.xml". For other application types, consult the WebLogic Server documentation.
- Category:
- J2EE
- Cause:
- The application was not a valid J2EE application.
- Action:
- Correct the application and try again.
- BEA-160180
- An error was encountered and ignored while rolling back an update to application {0}. The error was: {1}
- Category:
- J2EE
- Cause:
- See the included error message.
- Action:
- Correct the application based on the reported error.
- BEA-160181
- An error was encountered and ignored during undeployment. The error was: {0}
- Category:
- J2EE
- Cause:
- See the included error message.
- Action:
- Correct the application based on the reported error.
- BEA-160182
- An error was encountered and ignored during transition to administration mode. The error was: {0}
- Category:
- J2EE
- Cause:
- See the included error message.
- Action:
- Correct the application based on the reported error.
- BEA-160183
- Unable to find the jar-uri: {1} specified for the ApplicationLifecycleListener, Startup, or Shutdown class in the weblogic-application.xml of application: {0}.
- Category:
- J2EE
- Cause:
- The JAR URI is incorrect or the file does not exist or cannot be read.
- Action:
- Correct the application based on the reported error.
- BEA-160184
- ERROR: Could not find JDBC module of name "{2}" specified in the resource-link named "{3}" in the "{1}" component named "{0}".
- Category:
- J2EE
- Cause:
- The JDBC module used in the resource-link was not found in the application package.
- Action:
- Package the missing JDBC module as part of this application and retry.
- BEA-160185
- ERROR: Could not find the JDBC resource named "{4}" of type "{5}" inside the JDBC module "{2}" that is specified in the resource-link named "{3}" in the "{1}" component named "{0}".
- Category:
- J2EE
- Cause:
- The JDBC resource used in the resource-link was not found in the application package.
- Action:
- Create the missing JDBC resource in the corresponding JDBC module and retry.
- BEA-160186
- Compiling EAR module "{0}"
- Category:
- J2EE
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-160187
- weblogic.appc failed to compile the application. Recompile with the -verbose option for more details about the issue.
- Category:
- J2EE
- Cause:
- Compilation can fail for many reasons. See the specific error message for details.
- Action:
- Use the provided error message to track down and fix the problem.
- BEA-160188
- {0}.
- Category:
- J2EE
- Cause:
- The application has library references that do not resolve.
- Action:
- Ensure that the library references are accurate and that the required libraries are available.
- BEA-160189
- There are no modules in the application that match URIs: {0}. Note that for Web applications, you should specify the context-root rather than the web-uri.
- Category:
- J2EE
- Cause:
- The specified URIs were not found in the running application.
- Action:
- Specify the correct URIs which are typically found in your application's META-INF/application.xml.
- BEA-160191
- While upgrading weblogic.xml, the server encountered "{1}" parameter "{0}". This parameter has been deprecated and will be removed
- Category:
- J2EE
- Cause:
- This is a deprecated parameter.
- Action:
- Remove the deprecated parameter from the weblogic.xml deployment descriptor.
- BEA-160192
- While upgrading weblogic.xml, the server encountered "{1}" parameter "{0}". This parameter is unknown and will be removed
- Category:
- J2EE
- Cause:
- The parameter is not defined in the schema.
- Action:
- Check the weblogic.xml deployment descriptor and remove the parameter.
- BEA-160193
- Error: The source file, ''{0}'', is not a valid RAR file. To be valid, it must contain a META-INF/ra.xml file.
- Category:
- J2EE
- Cause:
- The specified source file is not a valid RAR file.
- Action:
- Ensure that the specified source file is a valid RAR file and try again.
- BEA-160194
- The following modules cannot be started because they are already running: {0}.
- Category:
- J2EE
- Cause:
- The specified modules are already running.
- Action:
- Remove the specified modules from the list of modules to partially stop.
- BEA-160195
- The application version lifecycle event listener {1} is ignored because the application {0} is not versioned.
- Category:
- J2EE
- Cause:
- The application is not a versioned application.
- Action:
- If the application is deployed as a non-versioned application in error, undeploy the current application and deploy it as a versioned application. If the application version lifecycle listener is specified in error, remove it from the application or specify a non-versioned application lifecycle listener.
- BEA-160196
- Unable to find the jar-uri: {1} specified for the Singleton class in the weblogic-application.xml of application: {0}
- Category:
- J2EE
- Cause:
- The JAR URI is incorrect or the file does not exist or cannot be read.
- Action:
- Correct the application based on the reported error.
- BEA-160197
- Unable to load descriptor {1} of module {0}. The error is {2}.
- Category:
- J2EE
- Cause:
- The descriptor is not valid.
- Action:
- Correct the descriptor based on the reported error.
- BEA-160198
- Error: The ejb-ref "{3}" configured via an @EJB annotation in the module "{0}" is linked to the EJB "{1}". However, the EJB "{1}" does not declare the interface "{2}", as specified by the @EJB annotation. Ensure that the ejb-ref is linked to the correct bean and that the target bean declares the interface specified by the ejb-ref.
- Category:
- J2EE
- Cause:
- The @EJB has an incorrect beanName (ejb-link) attribute or the target bean must implement the interface declared by the @EJB annotation.
- Action:
- Ensure that the ejb-ref is linked to the correct bean and that the target bean declares the interface specified by the ejb-ref.
- BEA-160199
- Error resolving ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref does not have an ejb-link and the JNDI name of the target Bean has not been specified.
- Category:
- J2EE
- Cause:
- Attempts to automatically link the ejb-ref to its target Bean failed because multiple EJBs in the application were found to implement the "{3}" interface, including {4}.
- Action:
- Specify a qualified ejb-link for this ejb-ref to indicate which EJB is the target of this ejb-ref.
- BEA-160200
- Error resolving ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref does not have an ejb-link and the JNDI name of the target bean has not been specified. Attempts to automatically link the ejb-ref to its target bean failed because no EJBs in the application were found to implement the "{3}" interface. Link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.
- Category:
- J2EE
- Cause:
- See the error message for details.
- Action:
- Link or map this ejb-ref to its target EJB and ensure the interfaces declared in the ejb-ref are correct.
- BEA-160201
- Error resolving ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref specifies an ejb-link but the target bean does not implement the interface "{3}" as specified in the ejb-ref declaration. Ensure that the ejb-link and interface name(s) declared in the ejb-ref are correct.
- Category:
- J2EE
- Cause:
- See the error message for details.
- Action:
- Ensure that the ejb-link and interface name(s) declared in the ejb-ref are correct.
- BEA-160202
- You have specified a {1} setting in your configuration for persistence unit {0}. This setting will be ignored and all log messages will be sent to the WebLogic Server logging subsystem. Trace-level logging is controlled by the various JPA-specific debug settings in config.xml, or through the WebLogic Server Administration Console.
- Category:
- J2EE
- Cause:
- Persistence unit configuration specifies logging information, but WebLogic Server will ignore this information.
- Action:
- Remove the {1} setting from persistence unit {0}.
- BEA-160203
- You have specified a {1} setting in your configuration for persistence unit {0}. This value will be replaced with {1}.
- Category:
- J2EE
- Cause:
- The persistence unit configuration specifies ID information, but WebLogic Server will ignore this information.
- Action:
- Remove the {1} setting from persistence unit {0}.
- BEA-160204
- The ApplicationLifecycleListener "{1}" of application "{0}" has a run-as user configured with the principal name "{2}" but a principal of that name could not be found. Ensure that a user with that name exists.
- Category:
- J2EE
- Cause:
- The run-as principal configured for this ApplicationLifecycleListener does not exist in the security realm.
- Action:
- Ensure that the user exists or choose another principal for the run-as configuration.
- BEA-160205
- The ApplicationLifecycleListener "{1}" of application "{0}" has a run-as user configured with the principal name "{2}" but a principal of that name has higher privileges than the user performing the deployment. As a result, this deployment user cannot perform the current deployment action. Try the deployment action with an administrative privileged user.
- Category:
- J2EE
- Cause:
- Higher run-as privileges are needed to deploy an ApplicationLifecycleListener in this situation.
- Action:
- Try the deployment action with an administrative privileged user.
- BEA-160207
- Error autowiring ejb-ref "{0}" from module "{1}" of application "{2}". The ejb-ref does not specify an interfaceName but multiple interfaces on the target bean were found. Specify a beanInterface to indicate which EJB is the target for ejb-ref "{0}".
- Category:
- J2EE
- Cause:
- There was a problem resolving the target of the specified ejb-ref.
- Action:
- Specify a beanInterface to indicate which EJB is the target.
- BEA-160210
- ERROR: The moduleUri, "{0}", could not be found.
- Category:
- J2EE
- Cause:
- The moduleUri could not be found.
- Action:
- Ensure that the specified moduleUri exists and try again.
- BEA-160211
- Waiting for ExecuteQueue {0} to finish {1} pending requests
- Category:
- J2EE
- 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-160212
- This is an unexpected exception.
- Category:
- J2EE
- Cause:
- See the message detail.
- Action:
- No action is required.
- BEA-160213
- This directory contains internal files used by the deployment system. Contents of this directory should never be removed while the corresponding server is running. Removing sub-directories when the server is down will slow down the subsequent deployment of the corresponding applications because these sub-directories need to be created again. The individual sub-directories are removed when the corresponding application is undeployed.
- Category:
- J2EE
- Cause:
- See the message detail.
- Action:
- No action is required.
- BEA-160214
- Output location exists {0}
- Category:
- J2EE
- Cause:
- The file pointed to by the output location already exists,
- Action:
- No action is required.
- BEA-160215
- ERROR: The moduleUri, "{0}", is not Web module.
- Category:
- J2EE
- Cause:
- The moduleUri is not valid Web module.
- Action:
- Ensure that the specified moduleUri is a valid Web module and try again.
- BEA-160216
- Unexpected errors occurred while sending deployment event {1} on behalf of application ''{0}''.
- Category:
- J2EE
- Cause:
- The deployment event listener(s) registered to receive deployment event caused unexpected exceptions when processing deployment event {1} on behalf of application ''{0}''.
- Action:
- Report this problem to My Oracle Support.
- BEA-160217
- Unexpected errors occurred while sending a vetoable deployment event on behalf of application ''{0}''.
- Category:
- J2EE
- Cause:
- The deployment event listener(s) registered to receive vetoable deployment events caused unexpected exception(s) when processing deployment event {1} on behalf of application ''{0}''.
- Action:
- Report this problem to My Oracle Support.
- BEA-160218
- Filtering classloader configuration ignored for module {1} of application {0}
- Category:
- J2EE
- Cause:
- Filtering classloader configuration is only supported in descriptors at the main level of the deployment (for example, in enterprise applications or standalone Web applications). Such configuration is not supported in modules of an enterprise application.
- Action:
- Remove the filtering classloader configuration from the deployment descriptor of module {1} of application {0}.
- BEA-160219
- The JPA persistence unit {0} will use the following configured default persistence provider: {1}
- Category:
- J2EE
- Cause:
- No provider element was specified in the associated persistence.xml file.
- Action:
- No action is required unless you want a different JPA provider to be used for the given persistence unit, in which case you can specify the provider in the persistence.xml file or change the default provider for the domain.
- BEA-160220
- Compilation completed successfully.
- Category:
- J2EE
- Cause:
- The compilation task has completed successfully.
- Action:
- No action is required.
- BEA-160221
- env-entry for type java.lang.Character had length = 0.
- Category:
- J2EE
- Cause:
- See the error message body.
- Action:
- See the error message body.
- BEA-160222
- Could not create a new JMS ConnectionFactory for the application: {0}.
- Category:
- J2EE
- Cause:
- See the error message body.
- Action:
- See the error message body.
- BEA-160223
- The resource-env-ref ''{0}'' declared in the standard descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic proprietary descriptor or corresponding annotation.
- Category:
- J2EE
- Cause:
- See the error message body.
- Action:
- See the error message body.
- BEA-160224
- Encountered an error cleaning up references for application: ${0} - ${1}
- Category:
- J2EE
- Cause:
- See the error message body.
- Action:
- See the error message body.
- BEA-160225
- A new JPA API method is being invoked against an older version of the persistence provider, in which the method is not supported yet. Update the application to use a compliant provider, or ensure that the application does not attempt to invoke unsupported methods that are not supported by the current provider.
- Category:
- J2EE
- Cause:
- A new JPA API method is being invoked against an older version of the persistence provider, in which the method is not supported yet.
- Action:
- Update the application to use a compliant provider, or ensure that the application does not attempt to invoke unsupported methods that are not supported by the current provider.
- BEA-160226
- Ignoring the configuration file [{0}: {1}]. Only applications that use Kodo as the JPA provider can be configured with this file.
- Category:
- J2EE
- Cause:
- This file can configure only persistence units that use Kodo.
- Action:
- Remove the configuration file or specify the information in persistence.xml; otherwise, one or more persistence units in this application use Kodo.
- BEA-160227
- The persistence unit "{0}" in "{1}" does not use Kodo as a JPA provider. Ignoring the configuration for this persistence unit found in persistence-configuration.xml.
- Category:
- J2EE
- Cause:
- The persistence-configuration.xml file cannot configure persistence units that do not use Kodo.
- Action:
- Remove the persistence unit from the persistence-configuration.xml file or specify in persistence.xml, or otherwise, that the persistence unit uses Kodo.
- BEA-160228
- AppMerge failed to merge your application. If you are running AppMerge on the command-line, merge again with the -verbose option for more details. See the error message(s) below.
- Category:
- J2EE
- Cause:
- AppMerge can fail for many reasons. See the specific error message for details.
- Action:
- Use the provided error message to track down and fix the problem.
- BEA-160229
- Ignoring plan file {0} as does not exist.
- Category:
- J2EE
- Cause:
- Either the plan specified is not a file or the plan file does not exist.
- Action:
- Use the provided error message to track down and fix the problem.
- BEA-160230
- Created working directory: {0}
- Category:
- J2EE
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-160231
- Unable to identify application type for {0}
- Category:
- J2EE
- Cause:
- The source file type may not be supported.
- Action:
- Use the provided error message to track down and fix the problem.
- BEA-160232
- Unable to identify module type for {0}
- Category:
- J2EE
- Cause:
- The module specified in the application descriptor may not be supported.
- Action:
- Use the provided error message to track down and fix the problem.
- BEA-160233
- Unable to identify module type {0}
- Category:
- J2EE
- Cause:
- A module specified in the application descriptor may not be supported.
- Action:
- Use the provided error message to track down and fix the problem.
- BEA-160238
- The message-destination {0} declared in the deployment descriptor or by annotation does not have a corresponding message-destination-descriptor element in the weblogic deployment descriptor or corresponding annotation. Alternatively, mapped-name or lookup-name of message-destination can be specified for the destination.
- Category:
- J2EE
- Cause:
- A declared message-destination is not mapped correctly.
- Action:
- Map the declared message-destination to the actual message destination using the message-destination-descriptor element in the weblogic deployment descriptor, or specify mapped-name or lookup-name of message-destination.
- BEA-160239
- Conflicting environment entry {0}, name is {1}.
- Category:
- J2EE
- Cause:
- Multiple entries have the same environment entry name, but have different values.
- Action:
- Ensure that each environment entry has a different environment name, or that entries with the same have identical values.
- BEA-160240
- The resource-ref "{0}" declared in the standard descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic proprietary descriptor or corresponding annotation.
- Category:
- J2EE
- Cause:
- See the error message for details.
- Action:
- See the error message for details.
- BEA-160241
- Error: There are validation errors for environment entries in module {0}. {1}
- Category:
- J2EE
- Cause:
- There are validation errors in the environment entries. With an EJB in WAR files, it is possible that names for environment entries may clash. Care must be taken by the deployer or application assembler to avoid these name collisions, as they can cause the application to fail. An environment entry that is declared in the application.xml descriptor must specify a JNDI name in the java:app or java:global namespace.
- Action:
- Correct the validation errors.
- BEA-160242
- Warning: Data source definition {0} in interceptor {1} may have been overwritten by EJB component in module {2}, ignored.
- Category:
- J2EE
- Cause:
- The EJB component may have overwritten data source definitions in its interceptors. In this case, data source definitions in interceptors will be ignored.
- Action:
- Please verify the cause above is not an issue for the application.
- BEA-160243
- A creating StoredProcedureQuery API method is being invoked on a container-managed and transaction-scoped EntityManager outside of a transaction, but the method is not supported yet. Update the application to start a transaction before creating the StoredProcedureQuery objects.
- Category:
- J2EE
- Cause:
- A creating StoredProcedureQuery API method is being invoked on a container-managed and transaction-scoped EntityManager outside of a transaction, but the method is not supported yet.
- Action:
- Update the application to start a transaction before creating the StoredProcedureQuery objects.
- BEA-160244
- An environment entry {0} declared in the application.xml descriptor does not specify a JNDI name in the java:app or java:global namespace.
- Category:
- J2EE
- Cause:
- An environment entry declared in the application.xml descriptor must specify a JNDI name in the java:app or java:global namespace.
- Action:
- Specify a JNDI name in the java:app or java:global namespace.
- BEA-160245
- It is an error for both the env-entry-value and lookup-name elements to be specified for a given env-entry element {0}.
- Category:
- J2EE
- Cause:
- An environment entry declared in the application.xml descriptor specified both the env-entry-value and lookup-name elements.
- Action:
- Specify either the env-entry-value or lookup-name, but not both.
- BEA-160246
- Warning: It is an error to request injection of two resources into the same target class {0} and target name {1}.
- Category:
- J2EE
- Cause:
- Injection of two resources into the same target was requested.
- Action:
- Remove one of the targets from the application.
- BEA-160247
- Warning: Ignore the realm name: {0} in deployment descriptor.
- Category:
- J2EE
- Cause:
- The realm name was ingored in the deployment descriptor.
- Action:
- No action is required.
- BEA-160248
- Unable to parse class file: {0}. {1}
- Category:
- J2EE
- Cause:
- This is generally due to a corrupted class file in the application.
- Action:
- Use an external tool such as JAD to ascertain the validity of the class. It is important to fix any invalid class in order to avoid potentially severe errors later in deployment or at runtime.
- BEA-160249
- Skipping schema-generation actions for persistence unit {0} by overriding relevant properties because this is only a server startup instead of an application deployment.
- Category:
- J2EE
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-160250
- No ComponentMBeanFactory with the class name {0} was found among the registered DeploymentFactory instances. Creating an instance using reflection.
- Category:
- J2EE
- Cause:
- There was no registered DeploymentFactory instance that had the same name as {0}.
- Action:
- No action is required.
- BEA-160251
- Failed to create an instance of ComponentMBeanFactory with the class name {0} because of an exception {1}
- Category:
- J2EE
- Cause:
- The ComponentMBeanFactory instance could not be located among registered DeploymentFactory instances.
- Action:
- No action is required.
- BEA-160252
- The following application inconsistencies must be corrected {0}. Code path: {1}
- Category:
- J2EE
- Cause:
- WebLogic Server detected multiple declarations of the same env-entry.
- Action:
- Search the application, including any shared library, for the listed env-entry declarations in both the descriptors and code annotations. Make sure that all the declarations are consistent. It is better to declare each env-entry only once to avoid this issue.
- BEA-160253
- {0}
- Category:
- J2EE
- Cause:
- See the message ddetails.
- Action:
- Consider eliminating redundant declarations of entries to avoid potential conflicts.
- BEA-160254
- Unable to read from application cache file {0} because of exception {2} with message: {1}
- Category:
- J2EE
- Cause:
- The cause of this exception is an underlying Java exception.
- Action:
- No action is needed, since WebLogic can recover from this failure by constructing these objects again.
- BEA-160255
- Unable to write to application cache file {0} because of exception message: {1}
- Category:
- J2EE
- Cause:
- The cause of this exception is an underlying Java IOException.
- Action:
- No action is needed, since WebLogic can recover from this failure by constructing these objects again when it need to read from this location.
- BEA-160256
- Unable to close {1} object stream to application cache file {0} because of exception message: {2}
- Category:
- J2EE
- Cause:
- The cause of this exception is an underlying Java IOException.
- Action:
- No action is needed, since WebLogic can recover from this failure.
- BEA-160257
- Application with name "{0}" cannot be deployed because the name is already in use in {1} named "{2}".
- Category:
- J2EE
- Cause:
- The deployment failed due to another application or library that already exists with the same name in the current deployment scope.
- Action:
- Retry the deployment with a different application name.
- BEA-160258
- The multi-version file {0} is expected to be a directory
- Category:
- J2EE
- Cause:
- Action:
- Correct the file format
- BEA-160259
- The version directory {0} is expected to be named in a dot-decimal format
- Category:
- J2EE
- Cause:
- The name format is incorrect
- Action:
- Correct the directory name
- BEA-160260
- No valid version found in multi-version directory {0}
- Category:
- J2EE
- Cause:
- No valid version exists in the multi-version directory
- Action:
- Add a valid version to the directory
- BEA-160261
- Exception in application {0}, marked to be in MultiVersionFormat. The application is located at {1}. The exception is {2}
- Category:
- J2EE
- Cause:
- {2}
- Action:
- Please correct the underlying problem represented by {2}
- BEA-160262
- The application version is "{0}"
- Category:
- J2EE
- Cause:
- This is an informational message giving the hash version of an application using the appmerge tool
- Action:
- None
- BEA-160263
- The files included in the application hash are {0}
- Category:
- J2EE
- Cause:
- This is an informational message giving the names of the files included in the version hash in the appmerge tool
- Action:
- None
- BEA-169800
- A PooledConnectionFactory object with an invalid external version of {0} was found.
- Category:
- JMSPool
- Cause:
- The version of WebLogic Server that stored the PooledConnectionFactory object is not compatible with the version that is retrieving it.
- Action:
- Contact My Oracle Support.
- BEA-169801
- The JMS method {0} may not be called inside an EJB or servlet.
- Category:
- JMSPool
- Cause:
- The application code has violated the Java EE specifications.
- Action:
- Change the code to avoid calling the specified method.
- BEA-169802
- Cannot create a wrapped JMS connection using a username and password when the res-auth element is set to Container.
- Category:
- JMSPool
- Cause:
- The application code is not using the Java EE APIs properly.
- Action:
- Either remove the username and password, or set the res-auth element to Application.
- BEA-169803
- JNDI lookup of the JMS connection factory {0} failed
- Category:
- JMSPool
- Cause:
- The remote JNDI server or JMS server is not available, or the name was incorrectly specified.
- Action:
- Check that the server is running, and check the name in the deployment descriptor XML files.
- BEA-169804
- Cannot use a JMS connection factory because the object is of the wrong type.
- Category:
- JMSPool
- Cause:
- Either the name of the connection factory in the deployment descriptor XML files is wrong, or the wrong object was bound into JNDI.
- Action:
- Check the name in the XML files against what is actually registered in JNDI.
- BEA-169805
- A pooled JMS connection is being closed because an exception was detected on the connection: {0}
- Category:
- JMSPool
- Cause:
- The JMS server is unavailable or there is some other problem with it that makes it impossible to send or receive messages.
- Action:
- Check the configuration parameters for the JMS server, and check that it is available on the network.
- BEA-169806
- Cannot use a JMS destination because the object is of the wrong type.
- Category:
- JMSPool
- Cause:
- Change the application to use a valid destination type.
- Action:
- Change the application to use a valid destination type.
- BEA-169807
- There was an error while making the initial connection to the JMS resource named {0} from within an EJB or a servlet. The server will attempt the connection again later. The error was {1}
- Category:
- JMSPool
- Cause:
- See the error message from the JMS provider.
- Action:
- No action is required.
- BEA-169808
- There was an error while making the initial connection to the JMS resource named {0} from the EJB "{1}" inside application "{2}". The server will attempt the connection again later. The error was {3}
- Category:
- JMSPool
- Cause:
- See the error message from the JMS provider.
- Action:
- No action is required.
- BEA-169809
- An error occurred while registering the JMS connection with JTA.
- Category:
- JMSPool
- Cause:
- The JMS connection factory specified does not properly support XA or something is wrong with the transaction system.
- Action:
- Check the linked exception and verify that the JMS provider properly supports XA.
- BEA-169810
- An error occurred while committing or rolling back a JTA transaction used for a JMS operation by the Java EE container
- Category:
- JMSPool
- Cause:
- There was a problem with the transaction system.
- Action:
- See the linked exception for more information.
- BEA-169811
- The JMS object may not be used because it has been closed.
- Category:
- JMSPool
- Cause:
- The object has been closed.
- Action:
- Fix the programming error.
- BEA-169812
- The pooled JMS session is enlisted in another transaction and may not be used elsewhere.
- Category:
- JMSPool
- Cause:
- Check the application code to ensure that a pooled JMS session (retrieved from the JNDI java:comp/env/jms context) is not kept between transactions. It should be closed so that it is returned to the pool.
- Action:
- Check the application code.
- BEA-169813
- There was an error while closing a JMS session pool or a pooled JMS connection: {0} The pool or object was forcibly closed.
- Category:
- JMSPool
- Cause:
- See the linked exception for more information.
- Action:
- No action is required.
- BEA-169814
- The JMS session pool has been disabled.
- Category:
- JMSPool
- Cause:
- An administrative action was taken.
- Action:
- Re-enable the session pool.
- BEA-169815
- A JMS session pool could not be created because the {0} property was not specified.
- Category:
- JMSPool
- Cause:
- A JMS session pool was either created directly by the user or by internal container code that did not properly specify a property.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-169816
- The JMS session pool is shutting down.
- Category:
- JMSPool
- Cause:
- The pool is being shut down, possibly because of an error.
- Action:
- Check for other errors that indicate why the pool is being shut down and retry the operation.
- BEA-169817
- The JMS connection factory resource {0} declared in the EJB "{1}" as part of application "{2}" does not support XA. It cannot be used inside a transaction context.
- Category:
- JMSPool
- Cause:
- If the specified JMS connection factory is intended to be used inside a transaction context, then the EJB was configured improperly.
- Action:
- If the specified JMS connection factory is intended for use inside a transaction context, then the connection factory used by the EJB must be changed so that it supports XA, or the EJB descriptor must be changed to point to a different connection factory. However, if the connection factory will never be used inside a transaction context, then no action is necessary.
- BEA-169818
- The JMS connection pool named "{0}" has a configured connection factory JNDI name of "{1}". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "{2}".
- Category:
- JMSPool
- Cause:
- An object other than a ConnectionFactory is bound to the configured JNDI name of the connection pool.
- Action:
- Either change the JNDI name of the JMS connection pool property or change the JNDI name of the object that is currently bound into JNDI.
- BEA-169819
- There was an error with a resource pool used to pool JMS sessions
- Category:
- JMSPool
- Cause:
- There is a problem with the resource pool.
- Action:
- See the linked exception for details.
- BEA-169820
- A JMS message consumer could not be created using a temporary queue or topic that was created using another connection.
- Category:
- JMSPool
- Cause:
- This is an application programming error.
- Action:
- Change the application code.
- BEA-169821
- Error creating or instantiating a wrapper for class {0}
- Category:
- JMSPool
- Cause:
- There may be an error with the classpath or with the underlying JMS provider's code.
- Action:
- Check the classpath. If this does not fix the problem, contact My Oracle Support.
- BEA-169822
- Unable to use a wrapped JMS session in the transaction because two-phase commit is not available.
- Category:
- JMSPool
- Cause:
- The JMS connection factory specified does not support two-phase commit.
- Action:
- For WebLogic Server JMS, two-phase commit may be enabled by setting the "UserTransactionsEnabled" flag on the JMS connection factory. For other JMS providers, you must specify a JMS connection factory that supports XA.
- BEA-169823
- Failure occured on createQueueConnection. Unexpected return type.
- Category:
- JMSPool
- Cause:
- Probable cause is the JMS 1.1 ConnectionFactory with the JMS 1.0.2 createQueueConnection() API. Some JMS providers do not support backward compatibility.
- Action:
- Either change the API call to createConnection() or change the connection factory type to QueueConnectionFactory.
- BEA-169824
- Failure occured on createTopicConnection. Unexpected return type.
- Category:
- JMSPool
- Cause:
- Probable cause is the JMS 1.1 ConnectionFactory with the JMS 1.0.2 createTopicConnection() API. Some JMS providers do not support backward compatibility.
- Action:
- Either change the API call to createConnection() or change the connection factory type to TopicConnectionFactory.
- BEA-169825
- Cannot create a wrapped JMSContext using a username and password when the res-auth element is set to Container.
- Category:
- JMSPool
- Cause:
- The application code is not using the Java EE APIs properly.
- Action:
- Either remove the username and password, or set the res-auth element to Application.
- BEA-169826
- The JMSContext pool named "{0}" has a configured connection factory JNDI name of "{1}". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "{2}".
- Category:
- JMSPool
- Cause:
- An object other than a ConnectionFactory is bound to the configured JNDI name of the JMSContext pool.
- Action:
- Either change the JNDI name of the JMSContext pool property or change the JNDI name of the object that is currently bound into JNDI.
- BEA-169827
- The resource reference "{0}" of type JMS Connection Factory in application "{1}" does not specify a JNDI name. As of Java EE 7 and WebLogic version 12.2.1, such references return a "java:comp/DefaultJMSConnectionFactory" by default when no Connection Factory with a JNDI name that matches the resource name is found.
- Category:
- JMSPool
- Cause:
- See the error message from the JMS provider.
- Action:
- If the application intends to use a specific JMS Connection Factory, Oracle recommends (a) checking for a misspelling of the resource reference name either in the @Resource annotation or, if there is a deployment descriptor file, in the <resource-ref-name> of the deployment descriptor, and (b) if there is no misspelling, explicitly setting the desired JNDI name using a lookup or mappedName attribute in the descriptor or annotation.
- BEA-169828
- An invalid value ({0}) for session mode was specified.
- Category:
- JMSPool
- Cause:
- An invalid value of the sessionMode parameter was specified when creating a JMSContext. The only valid values are JMSContext.AUTO_ACKNOWLEDGE, JMSContext.CLIENT_ACKNOWLEDGE, JMSContext.DUPS_OK_ACKNOWLEDGE and JMSContext.SESSION_TRANSACTED
- Action:
- Change the code so that it passes in a valid session mode. See the JMS API for more information.
- BEA-169829
- JMS 2.0 method "{0}", called on the interface "{1}", is not implemented by this JMS Provider.
- Category:
- JMSPool
- Cause:
- JMS 2.0 method "{0}", called on the interface "{1}", is not implemented by this JMS Provider.
- Action:
- Either use a JMS 1.1 method instead or use a JMS provider that supports JMS 2.0.
- BEA-169830
- JMS Connection Factory unmapped resource reference mode : {0}
- Category:
- JMSPool
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-169831
- System property weblogic.jms.JMSConnectionFactoryUnmappedResRefMode has 2 legal values "{0}" and "{1}". The value "{2}" is invalid and will be ignored.
- Category:
- JMSPool
- Cause:
- There are two legal values for the weblogic.jms.JMSConnectionFactoryUnmappedResRefMode property.
- Action:
- No action is required.
- BEA-169832
- The JMS connection factory with JNDI name {0} is object-based-security enabled and is not supported by JMS pools.
- Category:
- JMSPool
- Cause:
- The JMS connection factory with JNDI name {0} is object-based-security enabled and is not supported by JMS pools.
- Action:
- Do not use object-based-security enabled JMS connection factory for JMS pools.
- BEA-169833
- A foreign server does not support referencing a Connection Factory that enables Object Based Security.
- Category:
- JMSPool
- Cause:
- A foreign server does not support referencing a Connection Factory that enables Object Based Security.
- Action:
- Configure the foreign server to reference a Connection Factory that does not enable Object Based Security.
- BEA-170003
- The DomainLogfile Handler is unable to open the domain logfile {0}. The domain logfile is disabled.
- Category:
- Log Management
- Cause:
- The filepath specified for the domain log is invalid or the server process cannot write to the domain log file.
- Action:
- Specify a valid filepath for the domain log file.
- BEA-170011
- The LogBroadcaster on this server failed to broadcast log messages to the Administration Server. The Administration Server may not be running. Message broadcasts to the Administration Server will be disabled.
- Category:
- Log Management
- Cause:
- The Managed Server may not be able to reach the Administration Server. One of the possible causes could be that the Administration Server is shut down.
- Action:
- To fix this problem, inspect the exception stack trace, and correct the problem. If the Administration Server is shut down, restart it to resume normal log broadcasting to the domain.
- BEA-170019
- The server log file {0} is opened. All server side log events will be written to this file.
- Category:
- Log Management
- Cause:
- This message is for informational purposes.
- Action:
- No action is needed.
- BEA-170020
- The server log file {0} could not be opened successfully.
- Category:
- Log Management
- Cause:
- The filepath configured for the server's log file is not valid.
- Action:
- Please specify a valid filepath for the server's log file.
- BEA-170022
- Log4j failed to initialize for {0}. The default JDK Logging implementation will be used.
- Category:
- Log Management
- Cause:
- The Log4j libraries may not be in the server CLASSPATH.
- Action:
- Take corrective action based on the stack trace details.
- BEA-170023
- The Server Logging is initialized with Java Logging API implementation.
- Category:
- Log Management
- Cause:
- This message is for informational purposes.
- Action:
- No action is needed.
- BEA-170024
- The Server Logging is initialized with Apache''s Log4j Logging API implementation.
- Category:
- Log Management
- Cause:
- This message is only for informational purposes.
- Action:
- No action is needed.
- BEA-170025
- Initialized Domain Logging. Domain log events will be written to {0}.
- Category:
- Log Management
- Cause:
- This message is for informational purposes.
- Action:
- No action is needed.
- BEA-170026
- The servlet context logger could not be initialized for servlet context {0} to write to its own log file.
- Category:
- Log Management
- Cause:
- There was an I/O error when opening the file for the servlet context log.
- Action:
- Ensure that the logging configuration for the web application is valid.
- BEA-170027
- The server has successfully established a connection with the Domain level Diagnostic Service.
- Category:
- Log Management
- Cause:
- The server has successfully established contact with the Domain Diagnostic Service.
- Action:
- No action is needed.
- BEA-170028
- The remote handler is not available, so the trap notification information can not be sent.
- Category:
- Log Management
- Cause:
- The Managed Server may not be able to reach the Administration Server. One of the possible causes could be that the Administration Server is shut down.
- Action:
- If the Administration Server is shut down, restart it to resume normal communication for the domain.
- BEA-170029
- The data gathering handler could not be initialized.
- Category:
- Log Management
- Cause:
- An error occurred while initializing the data gathering handler.
- Action:
- Review the nested exception details for the cause.
- BEA-170030
- There was an error initializing the global Log4j configuration.
- Category:
- Log Management
- Cause:
- The error could be due to incorrect configuration parameters in the log4j configuration file.
- Action:
- Review the nested exception details for the cause.
- BEA-170031
- The Server Logging bridge has initialized successfully.
- Category:
- Log Management
- Cause:
- This message is logged for informational purpose only.
- Action:
- No action is needed.
- BEA-170032
- The Server has detected ODL configuration for java.util.logging. The PlatformLoggerLevels attribute configuration on the LogMBean will be ignored.
- Category:
- Log Management
- Cause:
- This message is logged for informational purpose only.
- Action:
- Users should specify the java.util.logging Logger Level configuration with ODL.
- BEA-170033
- The Server logging bridge could not be registered.
- Category:
- Log Management
- Cause:
- See the stack trace for the exact cause of this error, it could be due to misconfiguration or incorrect CLASSPATH being set for the logging APIs.
- Action:
- Take appropriate action based on the error message.
- BEA-170034
- LogMonitoring Service counted {0} log messages in the last {1} seconds. This exceeds the throttle threshold value of {2}, certain repetitive messages will now be throttled.
- Category:
- Log Management
- Cause:
- This message is logged for informational purpose only.
- Action:
- No action is needed.
- BEA-170035
- LogMonitoring Service counted {0} log messages in the last {1} seconds which is below the threshold value of {2}. Log messages are not being throttled.
- Category:
- Log Management
- Cause:
- This message is logged for informational purpose only.
- Action:
- No action is needed.
- BEA-170036
- The Logging monitoring service timer has started to check for logged message counts every {0} seconds.
- Category:
- Log Management
- Cause:
- This message is logged for informational purpose only.
- Action:
- No action is needed.
- BEA-170037
- The log monitoring service timer has been stopped.
- Category:
- Log Management
- Cause:
- This message is logged for informational purpose only.
- Action:
- No action is needed.
- BEA-170038
- The log monitoring service is throttling messages with the following Message ID/LoggerName/Message signature and the total count of logged messages over the throttle period is: {0}
- Category:
- Log Management
- Cause:
- This message is logged for informational purpose only.
- Action:
- No action is needed.
- BEA-170039
- The log monitoring service encountered an error when it was trying to reopen the server log file.
- Category:
- Log Management
- Cause:
- The cause of the error is included in the error stack trace of the message.
- Action:
- Please take corrective action based on the error stack trace reported in the log message to resolve the issue.
- BEA-170040
- The log monitoring service detected missing Server log file and forced log rotation to reopen the server log file.
- Category:
- Log Management
- Cause:
- An external process or tool likely deleted the Server's current log file.
- Action:
- Please take corrective action to find the source of deletion and not delete the active log file being used by the Server.
- BEA-171500
- The embedded LDAP configuration file: {0} was not found, and the embedded LDAP server has not been started. To resolve the problem, ensure that weblogic.home is defined correctly (it should have a lib subdirectory that contains this file).
- Category:
- EmbeddedLDAP
- Cause:
- The embedded LDAP server cannot find the specified file. This file is installed as part of the installation process. Most likely, the default directory is not the server root directory and the lib subdirectory cannot be found.
- Action:
- Set the default directory to the server root directory, or use the weblogic.EmbeddedLDAPConfigDirectory system property to set the location of the embedded LDAP server configuration files.
- BEA-171503
- The listen address for the Administration Server is obtained from either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property. None of these returned a listen address.
- Category:
- EmbeddedLDAP
- Cause:
- The listen address was null.
- Action:
- Check if the listen address for the Administration Server is defined in either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property.
- BEA-171507
- The embedded LDAP replica file: {0} could not be written. The underlying exception was {1}.
- Category:
- EmbeddedLDAP
- Cause:
- An exception occurred when saving the replica properties to the replicas file.
- Action:
- Verify that the file {1} can be written. Read the exception text for more information in diagnosing the problem.
- BEA-171512
- When attempting to clean up after a failed embedded LDAP replica initialization, the file {0} could not be deleted. The {1} directory and all its files must be deleted manually.
- Category:
- EmbeddedLDAP
- Cause:
- It is not always possible to delete files that are open by a process.
- Action:
- Delete the {1} directory and all its files manually using the appropriate command for the operating system on which WebLogic Server runs.
- BEA-171513
- Could not schedule the trigger used for embedded LDAP timer activities. The underlying exception was {0}.
- Category:
- EmbeddedLDAP
- Cause:
- A TimeTrigger exception occurred when scheduling the trigger.
- Action:
- See the exception text in {0} for more information on diagnosing the problem.
- BEA-171517
- An error occurred while attempting to obtain exclusive access to the embedded LDAP data files directory: {0}. The exception that occurred is {1}.
- Category:
- EmbeddedLDAP
- Cause:
- An exclusive lock for the directory {0} could not be obtained because an exception occurred.
- Action:
- Investigate the associated exception to determine why the exclusive lock failed.
- BEA-171518
- The following exception has occurred:
- Category:
- EmbeddedLDAP
- Cause:
- An error condition has occurred.
- Action:
- Read the associated exception in the log. In general, a stack trace will help when debugging an existing problem.
- BEA-171519
- Could not obtain an exclusive lock to the embedded LDAP data files directory: {0} because another WebLogic Server instance is already using this directory. Ensure that the first WebLogic Server instance is completely shut down and restart the server.
- Category:
- EmbeddedLDAP
- Cause:
- An exclusive lock for the directory {0} could not be obtained because another WebLogic Server is already using this directory.
- Action:
- Ensure that the first WebLogic Server instance is shut down and try restarting the server.
- BEA-171520
- Could not obtain an exclusive lock for directory: {0}. Waiting for {1} seconds and then retrying in case the existing WebLogic Server instance is still shutting down.
- Category:
- EmbeddedLDAP
- Cause:
- An exclusive lock for the directory {0} could not be obtained because another WebLogic Server is already using this directory.
- Action:
- If the server eventually boots, ignore this warning as the lock was obtained. If the server fails to boot, ensure that the first WebLogic Server is shut down and try restarting the server.
- BEA-171521
- An error occurred while initializing the embedded LDAP server. The exception that occurred is {0}. This may indicate a problem with the data files for the embedded LDAP server. This Managed Server has a replica of the data contained on the master embedded LDAP server in the Administration Server. This replica has been marked invalid and will be refreshed on the next boot of the Managed Server. Try to reboot this server.
- Category:
- EmbeddedLDAP
- Cause:
- There may be a problem with either the embedded LDAP server configuration files or the data files.
- Action:
- Investigate the associated exception to determine why the exception occurred. Try to reboot the server and see if the refresh of the replica data files solves the problem.
- BEA-171522
- An error occurred while initializing the embedded LDAP server. The exception that occurred is {1}. This may indicate a problem with the data files for the embedded LDAP server. If the problem is with the data files, and it cannot be corrected, backups of previous versions of the data files exist in {0}.
- Category:
- EmbeddedLDAP
- Cause:
- There may be a problem with either the embedded LDAP server configuration files or the data files.
- Action:
- Investigate the associated exception to determine why the exception occurred. Try to reboot the server.
- BEA-171523
- Embedded LDAP server Credential unavailable: a credential value must be supplied for the embedded LDAP configuration.
- Category:
- EmbeddedLDAP
- Cause:
- The Credential attribute is invalid.
- Action:
- Set the Credential attribute for the embedded LDAP server configuration.
- BEA-171524
- Cannot determine the listen address for the Administration Server. The Administration Server URI {0}, obtained from either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property, has invalid syntax.
- Category:
- EmbeddedLDAP
- Cause:
- The Administration Server URI has invalid syntax.
- Action:
- Ensure that a valid listen address for the Administration Server is defined in either the Server MBean, the ServerRuntime MBean, or the URL specified by the weblogic.management.server command line property.
- BEA-171525
- Error loading initial replica file. Check the EmbeddedLDAP log for more details.
- Category:
- EmbeddedLDAP
- Cause:
- An error occurred during the loading of the initial replica file.
- Action:
- Check the EmbeddedLDAP log for more details.
- BEA-171526
- Error loading the initial replica file, attempting to reload.
- Category:
- EmbeddedLDAP
- Cause:
- An error occurred during the loading of the initial replica file.
- Action:
- No action is required. The initial replica file will be loaded again.
- BEA-171527
- Added all LDAP entries successfully for the initial replica.
- Category:
- EmbeddedLDAP
- Cause:
- An error occurred during the initial loading of the replica file.
- Action:
- No action is required. The reload of the initial replica file was successful.
- BEA-171528
- Could not mark replica as invalid.
- Category:
- EmbeddedLDAP
- Cause:
- The AdminServer was unable to connect to the managed server to mark it as invalid.
- Action:
- Reboot the managed server so its EmbeddedLDAP can be refreshed from the AdminServer.
- BEA-171529
- Unable to download the initial replica of security data from the AdminServer. Verify that clock skew has not occurred between the servers in the domain. The underlying exception was {0}
- Category:
- EmbeddedLDAP
- Cause:
- The managed server was unable to download the replica file due to an exception.
- Action:
- Verify that clock skew has not occurred between the servers in the domain. Read the exception text for more information in diagnosing the problem.
- BEA-180000
- Start parsing the configuration MBean information.
- Category:
- WTC
- Cause:
- All other initialization has completed, and this method is now ready to begin reading its own configuration information.
- Action:
- No action is required.
- BEA-180001
- WTC finished parsing the configuration MBean information.
- Category:
- WTC
- Cause:
- All WTC configuration MBeans were parsed without any problems.
- Action:
- No action is required.
- BEA-180002
- Invalid attributes exception occurred while trying to create subcontext: {0}
- Category:
- WTC
- Cause:
- An attempt was made to add an attribute set that has been specified incompletely or incorrectly.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-180003
- Naming exception error: {0}
- Category:
- WTC
- Cause:
- The specified name could not be resolved.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-180004
- Name already bound error: {0}
- Category:
- WTC
- Cause:
- The name used by the Tuxedo connection factory or Tuxedo CORBA connection factory already bonded to another object.
- Action:
- Do not use the same name as the Tuxedo or Tuxedo CORBA connection factory.
- BEA-180005
- Invalid attributes exception when binding connection factory: {0}
- Category:
- WTC
- Cause:
- An attempt was made to add an attribute set that has been specified incompletely or incorrectly.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-180006
- Naming exception error: {0}
- Category:
- WTC
- Cause:
- The specified name could not be resolved.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-180007
- Unable to register the resource with transaction manager: {0}.
- Category:
- WTC
- Cause:
- WebLogic Tuxedo Connector (WTC) was not running with the server transaction manager.
- Action:
- Contact My Oracle Support.
- BEA-180008
- A transaction identifier exists for a non-existent domain {0}.
- Category:
- WTC
- Cause:
- The remote Tuxedo domain involved in the transaction is no longer in the WebLogic Tuxedo Connector (WTC) configuration.
- Action:
- Manually correct the transaction. If the removal of the remote Tuxedo domain is intentional, temporarily add the remote Tuxedo domain back to the configuration and wait for the transaction to complete. Otherwise, add the Tuxedo domain back to the configuration.
- BEA-180009
- Could not complete the execution for the MBean named: {0}.
- Category:
- WTC
- Cause:
- The definition contains input information that is not consistent with the usage model.
- Action:
- Check the MBean definition to see if the individual attributes are consistent with the rest of the MBean definitions.
- BEA-180010
- Could not create a TDMLocalTDomain {0}.
- Category:
- WTC
- Cause:
- The AccessPoint attribute definition for the WTCLocalTuxDom MBean was invalid.
- Action:
- Check the AccessPoint attribute of the WTCLocalTuxDom MBean.
- BEA-180011
- Could not create a TDMRemoteTDomain {0}.
- Category:
- WTC
- Cause:
- The AccessPoint attribute definition for the WTCRemoteTuxDom MBean was invalid.
- Action:
- Check the AccessPoint attribute of the WTCRemoteTuxDom MBean.
- BEA-180012
- The LocalTDomain {0} is unknown.
- Category:
- WTC
- Cause:
- The LocalAccessPoint attribute for the WTCRemoteTuxDom MBean is not a valid name for a LocalTDomain.
- Action:
- Verify that the WTCRemoteTuxDom MBean definition has a valid name for the LocalAccessPoint attribute.
- BEA-180013
- The LocalTDomain {0} is unknown.
- Category:
- WTC
- Cause:
- The LocalAccessPoint attribute for the WTCExport MBean is not a valid name for a LocalTDomain.
- Action:
- Verify that the WTCExport MBean definition has a valid name for the LocalAccessPoint attribute.
- BEA-180014
- Could not create a TDMExport {0}.
- Category:
- WTC
- Cause:
- The ResourceName attribute definition for the WTCExport MBean is invalid or the LocalTDomain is not usable.
- Action:
- Check the ResourceName attribute of the WTCExport MBean.
- BEA-180015
- The LocalTDomain {0} is not known.
- Category:
- WTC
- Cause:
- The LocalAccessPoint attribute for the WTCImport MBean is not a valid name for a LocalTDomain.
- Action:
- Confirm that the WTCImport MBean definition has a valid name for the LocalAccessPoint Attribute.
- BEA-180016
- The RemoteTDomain {0} is unknown.
- Category:
- WTC
- Cause:
- The RemoteAccessPointList attribute for the WTCImport MBean does not contain a valid name for a RemoteTDomain.
- Action:
- Verify that the WTCImport MBean definition has valid names in a comma-separated list defined in the RemoteAccessPointList attribute.
- BEA-180017
- Could not create a TDMImport {0}.
- Category:
- WTC
- Cause:
- The ResourceName attribute definition for the WTCImport MBean is invalid. The LocalTDomain or the RemoteTDomains are not usable.
- Action:
- Check the ResourceName attribute of the WTCImport MBean.
- BEA-180018
- Missing {0} Password or PasswordIV information.
- Category:
- WTC
- Cause:
- The Password or PasswordIV attribute is not set.
- Action:
- Verify that the Password and PasswordIV attributes are valid.
- BEA-180019
- The LocalTDomain {0} is unknown.
- Category:
- WTC
- Cause:
- The LocalAccessPoint attribute for the WTCPassword MBean is not a valid name for a LocalTDomain.
- Action:
- Verify that the WTCPassword MBean definition has a valid name for the LocalAccessPoint attribute.
- BEA-180020
- The RemoteTDomain {0} is unknown.
- Category:
- WTC
- Cause:
- The RemoteAccessPoint attribute for the WTCPassword MBean is not a valid name for a RemoteTDomain.
- Action:
- Verify that the WTCPassword MBean definition has a valid name for the RemoteAccessPoint attribute.
- BEA-180021
- Could not create a TDMPasswd {0}.
- Category:
- WTC
- Cause:
- The LocalTDomain or the RemoteTDomain is not usable.
- Action:
- Check the LocalAccessPoint and RemoteAccessPoint attributes of the WTCPassword MBean.
- BEA-180022
- Could not set up the field table information for TDMResources: {0}.
- Category:
- WTC
- Cause:
- The fully qualified name for any field table may be incorrect or could not be found.
- Action:
- Check the FldTblClass definitions of the WTCResources MBean and verify that the fully qualified name is correct, that it is consistent with the current CLASSPATH usage, and that the system is able to access it.
- BEA-180023
- Commit of Xid failed with status {0}.
- Category:
- WTC
- Cause:
- The transaction became a heuristic hazard, or the resource manager encountered an error.
- Action:
- Correct the transaction manually if it became a heuristic hazard, or correct the resource manager problem.
- BEA-180024
- Unable to reply to unknown transaction with exception: {0}.
- Category:
- WTC
- Cause:
- The connection to the remote Tuxedo domain was already terminated or an IOException occurred while writing to the network.
- Action:
- If the TPException is TPEPROTO, try to reboot the remote Tuxedo domain. If the TPException is TPESYSTEM, check the network connection.
- BEA-180025
- Unknown field type requested {0}.
- Category:
- WTC
- Cause:
- TypedFML32 data is possibly being used instead of TypedFML.
- Action:
- Verify that the type of input data is correct.
- BEA-180026
- While trying to use FML data, this Ferror exception occurred: {0}
- Category:
- WTC
- Cause:
- The data was not created correctly.
- Action:
- Check the data that was passed into this method.
- BEA-180027
- While trying to use FML data, an Unknown exception occurred: {0}
- Category:
- WTC
- Cause:
- The data was not created correctly.
- Action:
- Check the data that was passed into this method.
- BEA-180028
- Unknown field type requested {0}.
- Category:
- WTC
- Cause:
- Possibly, TypedFML data is being used instead of TypedFML32.
- Action:
- Verify that the type of input data was correct.
- BEA-180029
- The Ferror exception: {0} occurred. Additional exception information found: {1}.
- Category:
- WTC
- Cause:
- The data was not created correctly.
- Action:
- Check the data that was passed into this method.
- BEA-180030
- While trying to use FML32 data, an Unknown exception occurred: {0}
- Category:
- WTC
- Cause:
- The data was not created correctly.
- Action:
- Check the data that was passed into this method.
- BEA-180031
- XML argument is null.
- Category:
- WTC
- Cause:
- The argument that was passed in was not initialized.
- Action:
- Check the XML argument that was passed in.
- BEA-180032
- The FldTbl[] input argument is null or an empty array.
- Category:
- WTC
- Cause:
- The argument that was passed in was not initialized.
- Action:
- Check the FldTbl[] argument that was passed in.
- BEA-180033
- TypedFML argument is null.
- Category:
- WTC
- Cause:
- The argument that was passed in was not initialized.
- Action:
- Check the TypedFML argument that was passed in.
- BEA-180034
- An error occurred while searching {0} for the document root element.
- Category:
- WTC
- Cause:
- The input XML string was not formatted correctly.
- Action:
- Check for other listed errors that should indicate what was unacceptable about the XML input.
- BEA-180035
- TypedFML32 argument is null.
- Category:
- WTC
- Cause:
- The argument that was passed in was not initialized.
- Action:
- Check the TypedFML32 argument that was passed in.
- BEA-180036
- XML input {0} caused the SAX parser exception {1}
- Category:
- WTC
- Cause:
- The Document Object Model (DOM) parser did not accept the XML string that it received.
- Action:
- Check the SAX exception information that was returned and the XML string that was entered.
- BEA-180037
- XML input {0} caused IOException {1}.
- Category:
- WTC
- Cause:
- The XML string was not convertible to an InputSource() class.
- Action:
- Check the IOException information that was returned and the XML string that was entered.
- BEA-180038
- XML input {0} caused an unknown exception {1}.
- Category:
- WTC
- Cause:
- The XML string was not able to be parsed.
- Action:
- Check the exception information that was returned and the XML string that was entered.
- BEA-180039
- The DOM parser returned a null value for input {0}.
- Category:
- WTC
- Cause:
- The input may not be a valid XML string.
- Action:
- Check the string that was passed to the parser.
- BEA-180040
- Could not obtain a top document element from input {0}.
- Category:
- WTC
- Cause:
- The XML input did not have any elements defined.
- Action:
- Verify that the input string has a proper definition for a root element.
- BEA-180041
- Could not obtain a tag name for the root element in XML input {0}.
- Category:
- WTC
- Cause:
- The XML input does not have a tag name for the root element.
- Action:
- Verify that the root element has a proper definition.
- BEA-180042
- Internal TypedFML data is null.
- Category:
- WTC
- Cause:
- The internal data that is using the XMLtoFML() API was not initialized.
- Action:
- Use XMLtoFML to initialize the internal data.
- BEA-180043
- XML element name is null.
- Category:
- WTC
- Cause:
- The XML element information was not properly defined.
- Action:
- Check the XML element definition.
- BEA-180044
- XML element value is null for the element name {0}.
- Category:
- WTC
- Cause:
- The XML element information was not properly defined.
- Action:
- Check the XML element definition.
- BEA-180045
- Internal TypedFML32 data is null.
- Category:
- WTC
- Cause:
- The internal data that was using the XMLtoFML32() API was not initialized.
- Action:
- Use XMLtoFML32 to initialize the internal data.
- BEA-180047
- The tBridge must have at least one redirect command.
- Category:
- WTC
- Cause:
- The tBridge was not configured properly.
- Action:
- At least one redirect command must be configured in the WTC_CONFIG for the tBridge section.
- BEA-180048
- The tBridge cannot find the TuxedoConnectionFactory.
- Category:
- WTC
- Cause:
- The WebLogic Tuxedo Connector (WTC) was not properly configured.
- Action:
- Review the WTC documentation and restart the WTC.
- BEA-180049
- The tBridge cannot locate the WLXT option for translation.
- Category:
- WTC
- Cause:
- The WLXT package might not be loaded or might be in the proper CLASSPATH.
- Action:
- Install the WLXT and properly configure the translator option.
- BEA-180050
- The tBridge internal FML-to-XML conversion failed.
- Category:
- WTC
- Cause:
- The syntax of the incoming message could not be understood.
- Action:
- Correct the message syntax and retry.
- BEA-180052
- Unable to cancel ON_STARTUP connection retry due to: {0}.
- Category:
- WTC
- Cause:
- The timer service object for the ON_STARTUP connection policy could not be deleted during connection termination.
- Action:
- Contact My Oracle Support.
- BEA-180053
- Failure occurred during the token creating token: {0}.
- Category:
- WTC
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-180054
- Failure occurred while reading the received domain security token: {0}.
- Category:
- WTC
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-180055
- Received an unexpected token type, error information({0}, {1}, {2}).
- Category:
- WTC
- Cause:
- The cause could be that WTC communicates with a newer version of the TDomain protocol or an unknown alien protocol, or a breach of security attempt was detected.
- Action:
- Verify who is trying to connect to this WTC and determine whether there is a security violation or a need to upgrade WTC to a newer version.
- BEA-180056
- atntd(1) crypto error: {0}
- Category:
- WTC
- Cause:
- There was not enough free memory space to continue.
- Action:
- Try to force garbage collection, and remove some services to reduce memory usage.
- BEA-180057
- Invalid return challenge
- Category:
- WTC
- Cause:
- This is caused by an incorrect configuration and mismatched password.
- Action:
- Correct the configuration and the password.
- BEA-180058
- atntd(3) I/O error: {0}
- Category:
- WTC
- Cause:
- This is an internal system error.
- Action:
- Contact My Oracle Support.
- BEA-180059
- atntd(2) crypto error: {0}
- Category:
- WTC
- Cause:
- There is not enough free memory space to continue.
- Action:
- Try to force garbage collection, and remove some services to reduce memory usage.
- BEA-180063
- Invalid handler address length: {0}.
- Category:
- WTC
- Cause:
- The client did not talk to a valid listener.
- Action:
- Check the listener address and correct the configuration.
- BEA-180067
- WSRPCRQ discriminator {0} is invalid.
- Category:
- WTC
- Cause:
- The client is not talking to a valid handler.
- Action:
- Check the configuration and correct the error.
- BEA-180068
- Invalid WSRPCRQ type {0}.
- Category:
- WTC
- Cause:
- The client is not talking to a valid handler.
- Action:
- Check the configuration and correct it.
- BEA-180069
- Unable to read {0}. The following exception occurred: {1}.
- Category:
- WTC
- Cause:
- A general I/O exception occurred.
- Action:
- Read the exception description to determine the actual cause and act accordingly.
- BEA-180070
- TypeFML32 received a pointer of unknown type {0}. Will replace with null.
- Category:
- WTC
- Cause:
- The application was incorrectly written with an unknown data type.
- Action:
- Correct the data type in the application.
- BEA-180071
- Invalid typed FML32 field {0}. Equals null.
- Category:
- WTC
- Cause:
- The embedded FML32 buffer was incorrectly constructed in the FML32 buffer.
- Action:
- Check the source of the embedded FML32 buffer, and correct the problem.
- BEA-180074
- The tpinit buffer was not received.
- Category:
- WTC
- Cause:
- The server is likely talking to an invalid handler.
- Action:
- Check the configuration and correct the problem.
- BEA-180075
- Invalid receive size {0}
- Category:
- WTC
- Cause:
- The remote tuxedo domain gateway is not valid.
- Action:
- Check the configuration of the remote Tuxedo domain and correct the error.
- BEA-180076
- Unable to format password. The following exception occurred: {0}.
- Category:
- WTC
- Cause:
- An I/O error occurred.
- Action:
- Check for system memory usage and see if force garbage collection is possible. If the problem persists, contact My Oracle Support.
- BEA-180077
- Unable to close the domain socket. The following exception occurred: {0}.
- Category:
- WTC
- Cause:
- An I/O error occurred while closing the socket.
- Action:
- Check the network and system environment. If the problem persists, contact My Oracle Support.
- BEA-180078
- Dropping OWS_AREPLY on ground.
- Category:
- WTC
- Cause:
- The ACALL request already timed out.
- Action:
- No action is required. This message is informational only.
- BEA-180079
- rsession.run read_tfmh failed.
- Category:
- WTC
- Cause:
- The received message header is not properly formatted or it failed to decompress the data.
- Action:
- Check the configuration of the remote Tuxedo domain and correct any problem in the configuration. Ensure that a supported version of the remote Tuxedo domain is being used. Also, check the network for possible network dropping of the packet. If the problem persists, contact My Oracle Support.
- BEA-180080
- rsession.run tmmsg.ws was not provided.
- Category:
- WTC
- Cause:
- There is no connection with a valid remote Tuxedo domain.
- Action:
- Check the remote Tuxedo domain configuration and correct the problem.
- BEA-180081
- Unexpected close on rsession socket. The following exception occurred: {0}
- Category:
- WTC
- Cause:
- An I/O error occurred while reading the message header from the input stream.
- Action:
- Check the system memory usage and force garbage collection. If the problem persists, contact My Oracle Support.
- BEA-180082
- Unable to close the WSH socket. The following exception occurred: {0}.
- Category:
- WTC
- Cause:
- An I/O error occurred.
- Action:
- Check the network and system configuration.
- BEA-180083
- An unknown TCM type was received: {0}.
- Category:
- WTC
- Cause:
- WebLogic Tuxedo Connector (WTC) is communicating with an unsupported Tuxedo version.
- Action:
- Check the configuration and correct the error.
- BEA-180084
- Unable to write TCM. The following exception occurred: {0}.
- Category:
- WTC
- Cause:
- An I/O error occurred.
- Action:
- Check the system memory usage and force garbage collection.
- BEA-180085
- Unable to send an unsolicited acknowledgment. The following exception occurred: {0}.
- Category:
- WTC
- Cause:
- An I/O error occurred.
- Action:
- Check the system memory usage.
- BEA-180086
- Accepted connection from the remote domain {0}.
- Category:
- WTC
- Cause:
- The connection request was received from a remote domain.
- Action:
- No action is required.
- BEA-180087
- Established a connection to a remote domain {0}.
- Category:
- WTC
- Cause:
- The connection request to a remote domain was initiated.
- Action:
- No action is required.
- BEA-180088
- Error occurred while building {0} message.
- Category:
- WTC
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-180089
- Error occurred while decoding {0} message.
- Category:
- WTC
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-180090
- Remote domain {0} rejected the connection request.
- Category:
- WTC
- Cause:
- An error exists in the configuration.
- Action:
- Check both sides of the configuration, including the password, to see whether a mismatch exists in the configuration.
- BEA-180091
- Rejected remote domain {0} connection request.
- Category:
- WTC
- Cause:
- An error exists in the configuration.
- Action:
- Check both sides of the configuration, including the password, to see whether a mismatch exists in the configuration.
- BEA-180092
- Failed security validation with remote domain {0}.
- Category:
- WTC
- Cause:
- An error exists in the configuraiton, resulting in unauthorized access.
- Action:
- Check both sides of the configuration, including the password, to see if a mismatch exists in the configuration.
- BEA-180093
- Naming exception occurred during the lookup of the administrator name: {0}.
- Category:
- WTC
- Cause:
- The specified name could not be resolved.
- Action:
- Contact My Oracle Support.
- BEA-180094
- The tBridge failed to initialize the JMS targetName queue.
- Category:
- WTC
- Cause:
- The JMS targetName queue does not exist or the JMS server was not running on the system.
- Action:
- Correct the JMS problem and restart the WebLogic Tuxedo Connector (WTC) tBridge.
- BEA-180095
- The tBridge could not initialize the JMS sourceName queue.
- Category:
- WTC
- Cause:
- The sourceName queue cannot exist in JMS or the JMS server was not started.
- Action:
- Correct the JMS problem and restart the WebLogic Tuxedo Connector (WTC) tBridge.
- BEA-180096
- The tBridge could not initialize the wlsErrorDestination JMS queue.
- Category:
- WTC
- Cause:
- The JMS wlsErrorDestination queue may not be properly configured in WebLogic Server.
- Action:
- Correct the JMS problem and restart the WebLogic Tuxedo Connector (WTC) tBridge.
- BEA-180097
- Due to a translation error, the tBridge has redirected the message to the wlsErrorDestination.
- Category:
- WTC
- Cause:
- A translation error was detected from XML-to-FML or from FML-to-XML.
- Action:
- Correct the message structure and resend the message.
- BEA-180098
- The tBridge failed to send the message to wlsErrorDestination.
- Category:
- WTC
- Cause:
- The JMS wlsErrorDestination could be full or paused.
- Action:
- Recover the message from the sourceName JMS queue and resend.
- BEA-180099
- The MinEncryptionBits is greater then the MaxEncryptionBits in {0} domain {1}.
- Category:
- WTC
- Cause:
- There is a configuration error.
- Action:
- Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration so that it will use the correct values for the MinEncryptionBits and MaxEncryptionBits.
- BEA-180100
- Configuration error: {0}
- Category:
- WTC
- Cause:
- There is a configuration error.
- Action:
- Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration so that it will use the correct values for the corresponding error.
- BEA-180102
- Duplicated local domain ID {0} found.
- Category:
- WTC
- Cause:
- Two local domains have the same ID.
- Action:
- Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration to use a unique ID for the local domain.
- BEA-180103
- There are two remote domains {0} with the same local domain {1}.
- Category:
- WTC
- Cause:
- Two remote domains have the same local domain.
- Action:
- Use the WebLogic Server Administration Console to modify the WebLogic Tuxedo Connector (WTC) configuration to remove the redundant entry or correct the configuration information.
- BEA-180104
- Unsupported JMS message type
- Category:
- WTC
- Cause:
- A JMS Stream or Mapped message type was sent to the tBridge.
- Action:
- Correct the JMS message type and resend.
- BEA-180105
- A message has been dropped.
- Category:
- WTC
- Cause:
- The most common cause of this failure is that an unrecognized buffer type has been received by the WTC gateway.
- Action:
- Modify the application to ensure that unknown buffer types are not sent to the WTC gateway.
- BEA-180106
- Unable to find a transaction manager. Transaction recovery will not continue.
- Category:
- WTC
- Cause:
- A transaction manager could not be found.
- Action:
- Contact My Oracle Support.
- BEA-180107
- While attempting to recover transactions, the recover method failed.
- Category:
- WTC
- Cause:
- The recover method on the WebLogic Server XA sesource generated an exception.
- Action:
- Contact My Oracle Support.
- BEA-180108
- WebLogic Server rollback had a failure: {0}.
- Category:
- WTC
- Cause:
- The rollback method on the WebLogic Server XA resource generated an exception.
- Action:
- Contact My Oracle Support.
- BEA-180109
- Internal FML to XML conversion failed.
- Category:
- WTC
- Cause:
- The FML buffer that was received from Tuxedo contained field buffer names that were not provided to WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.
- Action:
- Verify that the field tables have been properly transfered as described in the WTC documentation.
- BEA-180110
- Internal FML32-to-XML conversion failed.
- Category:
- WTC
- Cause:
- The FML32 buffer that was received from Tuxedo contained field buffer names that were not provided to the WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.
- Action:
- Verify that the field tables have been properly transferred as described in the WTC documentation.
- BEA-180111
- Internal FML to XML conversion failed.
- Category:
- WTC
- Cause:
- The FML buffer that was received from Tuxedo contained field buffer names that were not provided to the WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.
- Action:
- Verify that the field tables have been properly transferred as described in the WTC documentation.
- BEA-180112
- Internal FML32 to XML conversion failed.
- Category:
- WTC
- Cause:
- The FML32 buffer that was received from Tuxedo contained field buffer names that were not provided to the WebLogic Tuxedo Connector (WTC). Therefore, the name translation failed.
- Action:
- Verify the field tables have been properly transferred as described in the WTC documentation.
- BEA-180115
- The tBridge cannot parse the configuration MBeans: {0}.
- Category:
- WTC
- Cause:
- The MBeans for the tBridge contain invalid attributes.
- Action:
- Correct the attribute definitions for the tBridge MBeans.
- BEA-180116
- The specified field table type {0} is incorrect.
- Category:
- WTC
- Cause:
- The WTCStartup.getFldTbls() method was called with an invalid argument.
- Action:
- Verify that the Type argument for this is either fml16 or fml32.
- BEA-180117
- The encoding {0} is not supported. JVM default encoding is used.
- Category:
- WTC
- Cause:
- Specified encoding name is not supported.
- Action:
- Correct the encoding name and restart WebLogic Server.
- BEA-180118
- Failed to find TPUSR file: {0}.
- Category:
- WTC
- Cause:
- The specified file TPUSR file does not exist.
- Action:
- Correct the configuration by specifying the correct TPUSR file or create it before using the file.
- BEA-180119
- The specified filename is not a valid file: {0}.
- Category:
- WTC
- Cause:
- The WebLogic Tuxedo Connector (WTC) had the incorrect configuration.
- Action:
- Correct the WTC TPUSR file configuration.
- BEA-180120
- The file {0} is not readable.
- Category:
- WTC
- Cause:
- The user does not have the read permission to read the configured TPUSR file.
- Action:
- Change the permissions of the TPUSR file.
- BEA-180121
- Cannot find file {0}.
- Category:
- WTC
- Cause:
- The configured WebLogic Tuxedo Connector (WTC) TPUSR file does not exist.
- Action:
- Correct the WTC TPUSR file configuration or create the file.
- BEA-180122
- No permission to read the file {0}.
- Category:
- WTC
- Cause:
- The user does not have the read permission to read the configured TPUSR file.
- Action:
- Change the permissions of the TPUSR file.
- BEA-180123
- File I/O error for file {0}, reason: {1}.
- Category:
- WTC
- Cause:
- The file was corrupted or deleted.
- Action:
- Correct the file corruption or use a new TPUSR file.
- BEA-180124
- The specified number is not in a valid number format: {0}.
- Category:
- WTC
- Cause:
- The configured cache size was not in a valid number format.
- Action:
- Correct the configuration in the WebLogic Tuxedo Connector (WTC) TpUsrFile.
- BEA-180132
- Custom AppKey generator class {0} not found.
- Category:
- WTC
- Cause:
- The configured custom AppKey class full path name was incorrect.
- Action:
- Ensure that the configuration is correct and that the custom class exists.
- BEA-180133
- AppKey plug-in initialization failed. Reason: {0}
- Category:
- WTC
- Cause:
- The most likely reason is that the user database was not available or the initialization parameter was incorrect.
- Action:
- Ensure that the user database is available and that the configuration is correct.
- BEA-180134
- Create new AppKey class {0} instance failed.
- Category:
- WTC
- Cause:
- Either the class is not accessible, there is no permission to create a new instance of this class, or the class is not valid.
- Action:
- Ensure that the class is accessible with the correct permission. Also, the class must be based on the weblogic.wtc.jatmi.AppKey interface.
- BEA-180136
- The {0} attribute on the {1} MBean is undefined but required.
- Category:
- WTC
- Cause:
- The attribute value must be defined, but it was not defined.
- Action:
- Check that the MBean attribute is set correctly.
- BEA-180137
- The {0} attribute on the {1} MBean is set incorrectly.
- Category:
- WTC
- Cause:
- The attribute was defined improperly.
- Action:
- Check that the MBean attribute is set correctly.
- BEA-180138
- The {0} MBean appears to contain previously defined import service information.
- Category:
- WTC
- Cause:
- The attributes defined on this MBean have already been used to define and import a service.
- Action:
- Check that the Resourcename,RemoteAccessPointList, and LocalAccessPoint attributes are not all duplicated in another import MBean.
- BEA-180139
- A {0} type MBean is not defined, but it is required to be defined.
- Category:
- WTC
- Cause:
- An MBean was not defined, but it is required to be defined.
- Action:
- Check that the MBean type specified is defined in the configuration.
- BEA-180141
- Message header contains an invalid magic number, connection closed.
- Category:
- WTC
- Cause:
- Either an invalid TDOMAIN protocol data unit was received, or the remote domain gateway did not have network encoding enabled.
- Action:
- Ensure that the local access point is configured with the correct port number, and that the remote gateway does not have the same MTYPE configured for this TDOMAIN session.
- BEA-180142
- Local domain {0} in use and cannot be deleted.
- Category:
- WTC
- Cause:
- The local domain was in use by another resource.
- Action:
- Check for remote domains, imported or exported services, or passwords that use this local domain.
- BEA-180143
- Cannot find local domain {0}.
- Category:
- WTC
- Cause:
- The local domain could not be found.
- Action:
- Check the access point name.
- BEA-180144
- Duplicate remote domain {0}. Cannot add.
- Category:
- WTC
- Cause:
- The access point name was duplicated.
- Action:
- Check the access points and access point IDs for existing domains.
- BEA-180145
- Remote domain {0} in use. Cannot delete.
- Category:
- WTC
- Cause:
- The remote domain is referenced by another resource or has an active connection.
- Action:
- Shut down the connection to this remote domain. Check other resources that may reference this domain.
- BEA-180146
- Remote domain {0} cannot be found.
- Category:
- WTC
- Cause:
- The specified remote domain cannot be found.
- Action:
- Check the access point name for the remote domain.
- BEA-180147
- Cannot find imported service {0}.
- Category:
- WTC
- Cause:
- The specified imported service could not be found.
- Action:
- Check the name of the imported service.
- BEA-180148
- Cannot find exported service {0}.
- Category:
- WTC
- Cause:
- The specified exported service could not be found.
- Action:
- Check the name of the exported service.
- BEA-180149
- Cannot find password entry {0}.
- Category:
- WTC
- Cause:
- The specified password entry could not be found.
- Action:
- Check the local and remote access point names.
- BEA-180150
- Connection policy for {0} is INCOMING_ONLY.
- Category:
- WTC
- Cause:
- The connection policy specified INCOMING_ONLY, so an outbound connection could not be started.
- Action:
- Check the access point ID for the remote domain.
- BEA-180151
- Cannot modify resource {0} because it may be in use.
- Category:
- WTC
- Cause:
- There is an active connection that may use this resource.
- Action:
- Stop connections associated with this resource before attempting to delete the resource.
- BEA-180152
- Registration of notification listeners for the configured MBeans has failed.
- Category:
- WTC
- Cause:
- This is an internal system error.
- Action:
- Contact My Oracle Support.
- BEA-180153
- No valid host Internet address for WTC remote access point {0}.
- Category:
- WTC
- Cause:
- This is a configuration error.
- Action:
- Correct the WTC remote access point's network address list.
- BEA-180154
- No valid listening address configured for local access point {0}.
- Category:
- WTC
- Cause:
- This is an internal system error.
- Action:
- Contact My Oracle Support.
- BEA-180155
- No valid network address for TDomain session ({0}, {1}) to try to connect to.
- Category:
- WTC
- Cause:
- Either there is a configuration error or the remote access point was not available and cannot be accessed using the configured information.
- Action:
- Correct the configuration, or boot the remote access point.
- BEA-180156
- Failed to connect to remote access point(//{0}:{1}), try next address.
- Category:
- WTC
- Cause:
- Either a configuration error exists or the remote access point was not available at the address specified.
- Action:
- No action is required.
- BEA-180157
- Failed to connect to remote access point(//{0}:{1}), no more address to try.
- Category:
- WTC
- Cause:
- Either a configuration error exists or the remote access point was not available at the address specified.
- Action:
- Correct the configuration or make the remote access point available.
- BEA-180158
- No more valid network addresses for the local access point {0} to listen.
- Category:
- WTC
- Cause:
- There is a configuration error.
- Action:
- Correct the configuration.
- BEA-180159
- Failed to listen for local access point {0} on address (//{1}:{2}), try next address.
- Category:
- WTC
- Cause:
- Either a configuration error exists or this was intended.
- Action:
- No action is required.
- BEA-180160
- Failed to create listening endpoint for local access point {0} on address (//{1}:{2}), no more addresses to try.
- Category:
- WTC
- Cause:
- There is a configuration error.
- Action:
- Correct the configuration.
- BEA-180161
- Failed to find the imported service for QSpace {0}, so the tBridge has redirected the message to the wlsErrorDestination.
- Category:
- WTC
- Cause:
- The WebLogic Tuxedo Connector (WTC) import was incorrectly configured.
- Action:
- Correct the configuration.
- BEA-180162
- Cannot find imported service {0}, so the tBridge has redirected the message to the wlsErrorDestination.
- Category:
- WTC
- Cause:
- There is a configuration error.
- Action:
- Correct the configuration.
- BEA-180163
- The received Tuxedo reply uses the unsupported buffer type {0}, so the tBridge has redirected the message to the wlsErrorDestination.
- Category:
- WTC
- Cause:
- The Tuxedo server returned a reply with an unsupported buffer type.
- Action:
- Modify the Tuxedo server to return the reply with a WebLogic Tuxedo Connector (WTC) supported buffer type.
- BEA-180164
- Failed to send message to JMS, so the tBridge has redirected the message to the WLSErrorDestination.
- Category:
- WTC
- Cause:
- The JMS replyQ is configured incorrectly.
- Action:
- Correct the configuration of the JMS queue to be used for the tBridge reply queue.
- BEA-180165
- TDomain session ({0}, {1}) disconnected because no keep alive acknowledgement was received.
- Category:
- WTC
- Cause:
- A network outage may have occurred.
- Action:
- Check the network connection between the two gateways to determine if it is connected.
- BEA-180166
- The remote gateway does not support application level keep alive. This feature is disabled for the TDomain session ({0}, {1}).
- Category:
- WTC
- Cause:
- The remote gateway does not support this application level keep alive feature.
- Action:
- Update the remote gateway to a version of Tuxedo that supports the TDomain application level keep alive feature.
- BEA-180167
- The imported resource {0} uses a TDomain session ({1}, {2}) that does not exist.
- Category:
- WTC
- Cause:
- The imported resource was not configured properly.
- Action:
- Correct the configuration for the imported service.
- BEA-180168
- A connection cannot be established between local domain {0} and remote domain {1} due to a problem with the local or remote password used to authenticate the connections between these domains.
- Category:
- WTC
- Cause:
- The domain passwords were not configured properly.
- Action:
- Encrypt the correct local and remote passwords for the connection using the weblogic.wtc.gwt.genpasswd utility and use the results to configure a WTCPasswordMBean.
- BEA-180169
- XA.end() failed: {0}
- Category:
- WTC
- Cause:
- The transaction may have been marked as ROLLBACK_ONLY.
- Action:
- Inspect the application logic to determine the cause of the error.
- BEA-180170
- Unexpected exception while converting View {0} to XML: {1}
- Category:
- WTC
- Cause:
- Refer to the exception details.
- Action:
- Refer to the exception details.
- BEA-180171
- SSL null ciphers are not enabled and will be upgraded to the minimum 56 bits.
- Category:
- WTC
- Cause:
- The null cipher suites were disabled by SSL configuration.
- Action:
- This can be ignored because stronger encryption strength is allowed by WTC configuration and is also available by SSL. However, WTC configuration can be corrected to use only 56 bits and stronger cipher suites or SSL null ciphers can be enabled, if desired.
- BEA-180172
- SSL null ciphers are not enabled.
- Category:
- WTC
- Cause:
- The null cipher suites were disabled by SSL configuration.
- Action:
- Either the SSL null cipher suites must be explicitly enabled, or the WTC configuration must be updated to use stronger encryption cipher suites.
- BEA-180173
- Invalid private key for identity alias {0} from key store {1}, detected by {2}.
- Category:
- WTC
- Cause:
- An invalid key store or the private key alias configuration does not exist in the key store, or an incorrect private key store passphrase was configured.
- Action:
- Correct the key store or private key alias information in the configuration.
- BEA-180174
- Invalid private key store {0}, detected by {1}
- Category:
- WTC
- Cause:
- The private key store configured does not exist or is corrupted.
- Action:
- Correct the private key store configuration information.
- BEA-180175
- Invalid trust certificate store {0}, detected by {1}
- Category:
- WTC
- Cause:
- The private key store configured does not exist or is corrupted.
- Action:
- Correct the private key store configuration information.
- BEA-180176
- An error occurred while retrieving the trusted certificate from trust store {0}, detected by {1}.
- Category:
- WTC
- Cause:
- The configured trust certificate was corrupted or an incorrect passphrase was configured.
- Action:
- Correct the trust certificate store configuration information.
- BEA-180177
- An error occurred while retrieving trusted certificates from WebLogic Server, detected by {0}.
- Category:
- WTC
- Cause:
- The configured trust certificate was corrupted or an incorrect passphrase was configured.
- Action:
- Correct the trust certificate store configuration information.
- BEA-180178
- The requested encryption strength of 256 bits of local access point {0} is not supported by LLE. Downgrade to 128 bits.
- Category:
- WTC
- Cause:
- The configured encryption strength is not supported by LLE.
- Action:
- Either change the encryption strength to the LLE supported strength or use SSL for connection privacy. LLE supports 0, 40, 56, and 128 bits encryption strength. SSL supports 0, 56, 128, and 256 bits encryption strength.
- BEA-180179
- When enabling access point {0} to support SDP, the SSL support setting for this access point was ignored.
- Category:
- WTC
- Cause:
- When SDP is configured, SSL is not supported.
- Action:
- No action is required if SDP support is expected. Otherwise, update the configuration to disable SDP support.
- BEA-180180
- An error occurred while trying to open class com.oracle.net.Sdp when WTC support for SDP was enabled.
- Category:
- WTC
- Cause:
- The current JRE does not support SDP.
- Action:
- Use the JRockit version of the JRE provided with this release of WebLogic Server.
- BEA-190000
- Initializing Java EE Connector Service.
- Category:
- Connector
- Cause:
- The Java EE Connectoor Services is currently initializing.
- Action:
- No action required.
- BEA-190001
- Java EE Connector Service initialized successfully.
- Category:
- Connector
- Cause:
- The Java EE Connector Service has initialized successfully.
- Action:
- No action required.
- BEA-190004
- ConnectionFactory not found for jndiName {0}.
- Category:
- Connector
- Cause:
- This warning can occur upon viewing the JNDI tree for the Managed Server on the Administration Console. The other likely cause for this error is that an incorrect JNDI name was specified for the desired resource adapter or that the resource adapter is not deployed.
- Action:
- Ignore the warning if it occurs while viewing the JNDI tree of a Managed Server. Otherwise, check the deployed connectors in the Administration Console and verify the name that was used to access it.
- BEA-190005
- An error occurred while creating a connection factory for ManagedConnectionFactory with jndiName {0}.
- Category:
- Connector
- Cause:
- The cause is unknown. Consult the resource adapter vendor documentation.
- Action:
- Examine the exception in the log for more information about how to correct the problem. You may need to refer to the resource adapter vendor documentation to determine an appropriate course of action.
- BEA-190008
- An error occurred while {2} the connection instance {1} for {0} resource adapter. Exception is: {3}
- Category:
- Connector
- Cause:
- This error occurred as the result of an attempt to call cleanup() or destroy() on a resource adapter managed connection. The resource adapter can generate a ResourceException if the operation fails. It can also generate an IllegalStateException if, for example, an attempt was made to clean up a connection when a transaction was in progress. A ResourceAdapterInternalException may be generated if an error condition is detected in the resource adapter.
- Action:
- Examine the log for the exact type of exception that was generated. In the case of an IllegalStateException, report the error to My Oracle Support. In the case of a ResourceAdapterInternalException, report the error to the resource adapter vendor.
- BEA-190009
- No ConnectionRequestInfo was provided for Application Managed Security Context.
- Category:
- Connector
- Cause:
- No ConnectionRequestInfo was provided for Application Managed Security Context.
- Action:
- No action required.
- BEA-190010
- Unable to determine resource principal for the container-managed security context.
- Category:
- Connector
- Cause:
- Improper security principal map configuration for resource adapter.
- Action:
- Check the resource adapter configuration.
- BEA-190012
- Component using JNDIName: {0} has {1} managed security.
- Category:
- Connector
- Cause:
- The component with the indicated JNDI name has the indicated managed security type.
- Action:
- No action required.
- BEA-190013
- An error occurred while processing context: java:/comp/env/wls-connector-resref.
- Category:
- Connector
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Report this error to My Oracle Support.
- BEA-190019
- < {0} > An error occurred when opening the log file {1} for the resource adapter.
- Category:
- Connector
- Cause:
- The log file is either a directory rather than a regular file, or it could not be opened for some other reason.
- Action:
- Check the log-filename configuration parameter in weblogic-ra.xml.
- BEA-190020
- < {0} > An error occurred while setting the log file to the resource adapter.
- Category:
- Connector
- Cause:
- An error occurred when WebLogic Server called the resource adapter's ManagedConnectionFactory.setLogWriter() method.
- Action:
- Contact your resource adapter supplier about the ManagedConnectionFactory.setLogWriter() method.
- BEA-190023
- < {0} > Error invoking the ManagedConnectionFactory "set" method for the configuration property "{1}". Reason: {2}
- Category:
- Connector
- Cause:
- The method required for setting the config-property could not be properly invoked.
- Action:
- Check the config-property of the ra.xml file in the resource adapter and ensure that the indicated property is specified correctly.
- BEA-190024
- < {0} > Error making initial connections for pool. Reason: {1}
- Category:
- Connector
- Cause:
- The backend system to which the resource adapter connects may be down, or the resource adapter may be misconfigured.
- Action:
- Check the availability of the backend system, then confirm the correct configuration of the resource adapter.
- BEA-190032
- < {0} > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "{1} "
- Category:
- Connector
- Cause:
- The cause should be evident from the exception. One likely cause is a misconfigured weblogic-ra.xml or ra.xml. The property(ies) specifying the connection information may not be correct.
- Action:
- Check the exception to determine the cause and attempt to remedy the indicated problem. You may need to consult the configuration for the resource adapter or the resource adapter documentation. You might also consult the resource adapter vendor support information or organization.
- BEA-190033
- < {0} > createManagedConnection returned a null ManagedConnection.
- Category:
- Connector
- Cause:
- This generally is a resource adapter error. A resource adapter should never return a null managed connection.
- Action:
- Check the exception to determine the cause and attempt to remedy the indicated problem. You may need to consult the configuration for the resource adapter or the resource adapter documentation, or consult the resource adapter vendor support information or organization
- BEA-190049
- The connector service failed to initialize. ServiceMBean initialization error: {0}
- Category:
- Connector
- Cause:
- This error should not occur under normal operations. Possible causes of this error could be low memory, file corruption, or machine instability.
- Action:
- Try rebooting the machine and restarting the server again. If the problem persists, note the error details and contact My Oracle Support.
- BEA-190050
- An error occurred in the connector service shutdown. Error: {0}
- Category:
- Connector
- Cause:
- The error occurred as a result of shutting down a connection pool or unregistering the ServiceMBean.
- Action:
- Report the error to My Oracle Support.
- BEA-190051
- An error occurred while shutting down the connection pool with pool name: {0}. Reason: {1}
- Category:
- Connector
- Cause:
- An error occurred while shutting down the connection pool. The error occurred while unregistering the ConnectionPoolRuntimeMBean. pool name:{0}. Reason: {1}
- Action:
- Report the error to My Oracle Support.
- BEA-190052
- An error occurred while creating a connection pool Runtime MBean with pool name: {0}. Reason: {1}
- Category:
- Connector
- Cause:
- An error occurred while creating a connection pool Runtime MBean. The error occurred while initializing the ConnectionPoolRuntimeMBean. pool name:{0}. Reason: {1}
- Action:
- Report the error to My Oracle Support.
- BEA-190053
- An error occurred while creating a resource for a connection pool {0}. Reason: {1}
- Category:
- Connector
- Cause:
- Error occurred while instantiating a ConnectionRuntimeMBean for the connection being created. Pool name: {0}. Reason: {1}
- Action:
- Report the error to My Oracle Support.
- BEA-190054
- An error occurred while destroying a resource for a connection pool {0}. Reason: {1}
- Category:
- Connector
- Cause:
- An error occurred while unregistering a ConnectionRuntimeMBean for the connection being destroyed. Pool name: {0}, Reason: {1}
- Action:
- Report the error to My Oracle Support.
- BEA-190056
- An error occurred while reserving a resource from a connection pool {0}. Reason: {1}
- Category:
- Connector
- Cause:
- An error occurred while registering an XAResource for the connection being reserved with the transaction manager. Pool name:{0}. Reason: {1}
- Action:
- Report the error to My Oracle Support.
- BEA-190064
- Access has been denied to {0}, Application: {1}, Module: {2}, EIS Type: {3}, while reserving a connection.
- Category:
- Connector
- Cause:
- The entitlement check did not pass for the connection request to the connection pool with name: {0}.
- Action:
- Check your entitlement configuration in the Administration Console.
- BEA-190075
- The resource adapter returned a null connection factory when createConnectionFactory was called for "{0}".
- Category:
- Connector
- Cause:
- The resource adapter is not functioning according to the specification.
- Action:
- Contact the resource adapter vendor.
- BEA-190079
- The descriptor element {0} has been replaced by {1}.
- Category:
- Connector
- Cause:
- A deprecated descriptor element has been detected.
- Action:
- Convert the old descriptor element to the replacement element.
- BEA-190080
- An inactive deprecated descriptor element {0} has been detected.
- Category:
- Connector
- Cause:
- An inactive deprecated descriptor element has been detected.
- Action:
- Refer to the connector documentation for more information.
- BEA-190081
- Testing resource adapter "{0}" for viability of connection proxies.
- Category:
- Connector
- Cause:
- The indicated resource adapter is currently being tested for viability connection proxies.
- Action:
- No action required.
- BEA-190082
- Proxy test passed. WebLogic Server will use connection proxies for resource adapter "{0}".
- Category:
- Connector
- Cause:
- The proxy test passed for the incidated resource adapter.
- Action:
- No action required.
- BEA-190084
- Unable to complete connection proxy test for "{0}" due to the following exception. WebLogic Server will attempt to use connection proxies for resource adapter "{0}" as usual.
- Category:
- Connector
- Cause:
- WebLogic Server attempted to pose as an application component to determine whether a generated proxy class is compatible with a resource adapter (to support late transaction enlistment and leak and idle detection of connections). The connection proxy test failed.
- Action:
- No action is required.
- BEA-190085
- The linkref RAR {0} has been marked for late deployment since its base has not been deployed.
- Category:
- Connector
- Cause:
- The base RAR that the linkref points to has not been deployed yet.
- Action:
- Do not use the linkref until its base has been deployed.
- BEA-190088
- Trying to deploy a connector with a JNDI name that already exists {0}.
- Category:
- Connector
- Cause:
- Trying to deploy a connector with a JNDI name that already exists {0}.
- Action:
- Use a unique JNDI name while deploying the connector.
- BEA-190089
- Unexpected error occurred while processing a resource adapter JAR file.
- Category:
- Connector
- Cause:
- The cause is unknown.
- Action:
- Examine the stack trace for the cause and action.
- BEA-190090
- Call to implementation of ManagedConnection.getLocalTransaction in resource adapter with jndiName = {1} failed: {0}
- Category:
- Connector
- Cause:
- Refer to the error message for more information.
- Action:
- See the error message for more information. If it is still unclear, contact the resource adapter vendor or My Oracle Support.
- BEA-190091
- Call to implementation of ManagedConnection.getXAResource in resource adapter with jndiName = {1} failed: {0}
- Category:
- Connector
- Cause:
- Refer to the error message for more information.
- Action:
- Refer to the error message for more information. If still unclear, contact the resource adapter vendor or My Oracle Support.
- BEA-190092
- An error occurred while reserving a resource from a connection pool {0}. Reason: {1}
- Category:
- Connector
- Cause:
- An error occurred while registering a non-XAResource for the connection being reserved with the transaction manager. pool name:{0}. Reason: {1}
- Action:
- Report this error to My Oracle Support.
- BEA-190097
- Unable to complete the connection proxy test for "{0}" due to an exception. WebLogic Server will attempt to use connection proxies for resource adapter "{0}" as usual. Exception: {1}
- Category:
- Connector
- Cause:
- WebLogic Server attempted to pose as an application component to determine whether a generated proxy class is compatible with a resource adapter (to support late transaction enlistment and leak and idle detection of connections). The connection proxy test failed.
- Action:
- No action is required.
- BEA-190098
- Trying to release a resource that has already been released for {0}.
- Category:
- Connector
- Cause:
- Trying to release a resource that has already been released for {0}. It is possible that the connection was already released due to an error that occurred with the connection.
- Action:
- No action is required.
- BEA-190099
- Attempting to close a connection that has already been closed for {0}.
- Category:
- Connector
- Cause:
- An attempt was made to close a connection that has already been closed for {0}.
- Action:
- No action is required.
- BEA-190100
- A close() method was not found on the connection handle while testing for the viability for connection proxies : {0}
- Category:
- Connector
- Cause:
- A close() method was not found on the connection handle while testing for the viability for connection proxies : {0}. As per the 1.0 specification, a close() method is required on the connection handle.
- Action:
- Implement a close() method for the connection handle.
- BEA-190101
- Linkrefs are deprecated for 1.0 resource adapters: {0}
- Category:
- Connector
- Cause:
- Linkrefs are deprecated for 1.0 resource adapters.
- Action:
- No action is required.
- BEA-190102
- Failed to unregister the Diagnostic Image for the Connector Service.
- Category:
- Connector
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-190103
- Failed to register the Diagnostic Image for the Connector Service.
- Category:
- Connector
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-190104
- While configuring an object of type: {0} of Resource Adapter {1}, the following errors/omissions were found: {2}
- Category:
- Connector
- Cause:
- Properties have been specified in a resource adapter deployment descriptor which are inconsistent with those defined by the resource adapter code. There may be properties specified in the descriptor that do no exist in the object or are of the wrong type.
- Action:
- Check that the specified properties are spelled properly. Check with the resource adapter documentation or the vendor to determine whether or not these warnings can be ignored.
- BEA-190105
- Failed to initialize the AnonymousSubject.
- Category:
- Connector
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-190106
- Failed to find the RuntimeMBean for the module: {0}
- Category:
- Connector
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-190107
- Failed to unregister the RuntimeMBean for the module: {0}
- Category:
- Connector
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-190108
- Failed to initialize the Jndi Subcontexts for the adapter: appId = {0}, {1}
- Category:
- Connector
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-190109
- Extracting file {0} to {1}.
- Category:
- Connector
- Cause:
- The indicated file is being extracted to the indicated native Lib directory.
- Action:
- No action required.
- BEA-190110
- Resource adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server. This may adversely impact the performance or operation of WebLogic Server.
- Category:
- Connector
- Cause:
- A resource adapter is calling BootstrapContext.createTimer() and allocating a Timer Thread that is not managed by WebLogic Server.
- Action:
- Contact the resource adapter vendor and notify them of this warning condition.
- BEA-190111
- InvalidDyeException was generated: Module Name = {0}, {1}.
- Category:
- Connector
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-190112
- Failed to register the XAResource to be used for recovery: {0}
- Category:
- Connector
- Cause:
- See the error description in the message body.
- Action:
- See the stack trace and report the error to My Oracle Support.
- BEA-190113
- Failed to Unregister the XAResource used for recovery: {0}
- Category:
- Connector
- Cause:
- See the error description in the message body.
- Action:
- See the stack trace and report the error to My Oracle Support.
- BEA-190114
- Failed to apply dynamic pool changes: {0}
- Category:
- Connector
- Cause:
- See the error description in the message body.
- Action:
- See the error description in the message body.
- BEA-190115
- The ManagedConnectionFactory class does not implement the ResourceAdapterAssociation interface: {0}
- Category:
- Connector
- Cause:
- See the error in the message body for information.
- Action:
- Please contact the resource adapter vendor and notify them of this error condition.
- BEA-190116
- An invalid event was triggered on the XAResource used for recovery: {0}
- Category:
- Connector
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-190117
- Invocation of ManagedConnection.cleanup() failed: {0}
- Category:
- Connector
- Cause:
- See the error in the message body for information.
- Action:
- Examine the stack trace and error message for more information.
- BEA-190118
- ConnectionErrorOccurred event was triggered: {0}
- Category:
- Connector
- Cause:
- The adapter has indicated an error occurred on the exception.
- Action:
- Examine the stack trace and error message for more information.
- BEA-190119
- Invocation of ManagedConnection.destroy() failed: {0}
- Category:
- Connector
- Cause:
- The implementation of the resource adapter's cleanup() method threw an exception.
- Action:
- Examine the stack trace and error message for more information.
- BEA-190120
- Invocation of ManagedConnection.getXAResource() returned null.
- Category:
- Connector
- Cause:
- The implementation of the resource adapter's getXAResource() returned null.
- Action:
- Please contact the resource adapter vendor to determine why getXAResource() returned null.
- BEA-190121
- Failed to dissociate the Connection Handles from a ManagedConnection: Adapter JndiName = {0}, {1}
- Category:
- Connector
- Cause:
- See the stack trace for details about the cause of this error.
- Action:
- Take appropriate action based on the information in the stack trace.
- BEA-190122
- The resource adapter passed a null ManagedConnection into WebLogic Server''s implementation of ConnectionManager.lazyEnlist().
- Category:
- Connector
- Cause:
- The resource adapter's implementation passed a null ManagedConnection into the lazyEnlist() method.
- Action:
- Please notify the resource adapter's vendor about this error.
- BEA-190123
- Outbound adapter for jndiName = {0}, is using sharing scope = {1}.
- Category:
- Connector
- Cause:
- The outbound adapter with the indicated JNDI name is using the indicated sharing scope.
- Action:
- No action required.
- BEA-190124
- Failed to deploy LinkRef Adapter, moduleName = {0}, baseRA = {1}, Exception: {2}
- Category:
- Connector
- Cause:
- Refer to the message body and exception message for more information.
- Action:
- Refer to the message body and exception message for more information.
- BEA-190125
- An internal consistency check failed, assertion failed: {0}
- Category:
- Connector
- Cause:
- An internal consistency check failed, indicating a software defect.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-190126
- anonymous
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190127
- CloseCount
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190128
- CreateCount
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190129
- FreePoolSize
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190130
- PoolSize
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190131
- WaitingThreadCount
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190133
- Number of times create was called on the connection pool
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190134
- Number of connections in the pool that are free for use
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190135
- Size of the connection pool
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190136
- Number of threads in the waiting state
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190137
- Never
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190138
- <Unavailable>
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190139
- Running
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190140
- Suspended
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190141
- New
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190142
- Initialized
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190143
- Prepared
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190144
- Activated
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190145
- Unknown
- Category:
- Connector
- Cause:
- This message is used only for localization (internationalization) purposes.
- Action:
- No action is required.
- BEA-190146
- An error occurred while setting the log file to the resource adapter''s ManagedConnectionFactory: {0}. The exception was "{1}" with cause "{2}".
- Category:
- Connector
- Cause:
- An error occurred when WebLogic Server called the resource adapter's ManagedConnectionFactory.setLogWriter() method.
- Action:
- Examine the message and cause, or contact the resource adapter provider, or both.
- BEA-190147
- Profiling Record for Pool: PoolName = "{0}", Type = "{1}", Timestamp = "{2}", Properties : {3}
- Category:
- Connector
- Cause:
- This message is informational. The Harvester logged this Profiling Record for debug purposes.
- Action:
- No action is required.
- BEA-190148
- The attempt to set the property "{1}" of type "{2}" of object "{0}" to value "{3}" failed with a PropertyVetoException generated by the resource adapter. The veto message was "{4}".
- Category:
- Connector
- Cause:
- See the veto message for more information.
- Action:
- See the veto message for more information. Contact the resource adapter provider if more assistance is needed.
- BEA-190149
- No JNDI Name has been specified for the resource adapter in module {0} of application {1}. Since this is an inbound resource adapter, <jndi-name> must also be specified in weblogic-ra.xml for endpoint activation by a message endpoint MDB to work.
- Category:
- Connector
- Cause:
- There is a missing <jndi-name> element in weblogic-ra.xml.
- Action:
- Specify the <jndi-name> in weblogic-ra.xml that corresponds to the JNDI name expected by the MDB that is using this inbound resource adapter.
- BEA-190150
- The process of creating the Connector Diagnostic Image has been timed out by the Diagnostic Framework. The resulting image may be incomplete.
- Category:
- Connector
- Cause:
- The process of creating the Connector Diagnostic Image has been timed out by the Diagnostic Framework.
- Action:
- Please investigate the contents of the log and Diagnostic Images for more information.
- BEA-190151
- Parsing error, buildOutboundResourceAdapter() error in parsing ra.xml. While looking for connectionfactory-interface, failed to find: "{0}"
- Category:
- Connector
- Cause:
- There is an error in the XML configuration for this adapter.
- Action:
- Please contact the vendor to obtain a resource adapter with a valid configuration.
- BEA-190152
- Failed to create a new ConnectorInboundRuntimeMBeanImpl for "{0}", {1}
- Category:
- Connector
- Cause:
- See the error in the logged message for more information.
- Action:
- See the error in the logged message for more information.
- BEA-190153
- Failed to close the logging stream for pool: "{0}", {1}
- Category:
- Connector
- Cause:
- See the error in the logged message for more information.
- Action:
- See the error in the logged message for more information.
- BEA-190154
- Failed to create the logging stream for pool: "{0}", {1}
- Category:
- Connector
- Cause:
- See the error in the logged message for more information.
- Action:
- See the error in the logged message for more information.
- BEA-190155
- Compliance checking and validation of the resource adapter {0} resulted in the following warnings: {1}
- Category:
- Connector
- Cause:
- The specified resource adapter failed to pass compliance and validity checking as indicated by the listed warnings and errors.
- Action:
- Correct the ra.xml, weblogic-ra.xml or the resource adapter archive.
- BEA-190156
- There were no compliance or validation errors found in the resource adapter {0}.
- Category:
- Connector
- Cause:
- No compliance or validation errors were found in the indicated resource adapter.
- Action:
- No action required.
- BEA-190157
- There were {1} critical compliance or validation error(s), {2} non-critical compliance or validation error(s), and {3} warning(s) found in the resource adapter {0}.
- Category:
- Connector
- Cause:
- This message is logged to incidate the number of errors and warnings that were found for the indicated resource adapter.
- Action:
- No action required.
- BEA-190158
- This is a link ref resource adapter for {0}. No validation can be done at this time.
- Category:
- Connector
- Cause:
- Since there is no ra.xml in this resource adapter, validation of the adapter cannot be performed until it and the base adapter are deployed.
- Action:
- No action is required.
- BEA-190159
- Connection Pool {0} has been reset.
- Category:
- Connector
- Cause:
- The indicated connection pool was reset.
- Action:
- No action required.
- BEA-190160
- Connection pool {0} is in use and cannot be reset. Try forceReset instead.
- Category:
- Connector
- Cause:
- Since there are connections reservered from connection pool {0}, reset of the pool cannot be performed.
- Action:
- Try forceReset instead.
- BEA-190161
- Failed to extract adapter {0} to server temporary directory due to exception {1}.
- Category:
- Connector
- Cause:
- Extraction of the adapter {0} to server temporary directory failed due to the exception.
- Action:
- Check the permissions on the server temporary directory or check the exception.
- BEA-190162
- Failed to create server temporary directory {1} while extracting adapter {0}.
- Category:
- Connector
- Cause:
- Creation of the server temporary directory {1} failed while extracting the adapter {0}.
- Action:
- Check the permissions on the server temporary directory.
- BEA-199000
- Only positive values are allowed for initial-capacity unless initial and max capacity are equal.
- Category:
- Connector
- Cause:
- Refer to the message body and exception for more information.
- Action:
- Refer to the message body and exception for more information.
- BEA-199001
- Zero value for max-capacity is allowed only for link-ref adapters.
- Category:
- Connector
- Cause:
- The max-capacity is zero.
- Action:
- Check the max-capacity and update it.
- BEA-199002
- Negative values are not allowed for max-capacity.
- Category:
- Connector
- Cause:
- The max-capacity is negative.
- Action:
- Check the max-capacity and update it.
- BEA-199003
- max-capacity should be greater than or equal to initial-capacity. {0}
- Category:
- Connector
- Cause:
- The max-capacity is less than initial-capacity.
- Action:
- Check the max-capacity and update it.
- BEA-199004
- Only positive values are allowed for capacity-increment.
- Category:
- Connector
- Cause:
- The capacity-increment is zero or negative.
- Action:
- Check the capacity-increment and update it.
- BEA-199005
- capacity-increment should be less than or equal to ( max_capacity-initial_capacity ). {0}
- Category:
- Connector
- Cause:
- The capacity-increment is greater than max_capacity-initial_capacity.
- Action:
- Check the capacity-increment and update it.
- BEA-199006
- Only positive values are allowed for shrink-frequency-seconds.
- Category:
- Connector
- Cause:
- The shrink-frequency-seconds is zero or negative.
- Action:
- Check the shrink-frequency-seconds.
- BEA-199007
- Only values greater than or equal to 0 are allowed for inactive-connection-timeout-seconds.
- Category:
- Connector
- Cause:
- The value of inactive-connection-timeout-seconds must be positive.
- Action:
- Please check the inactive-connection-timeout-seconds.
- BEA-199010
- No ra.xml or weblogic-ra.xml has been specified. The RAR is null and there is no alternate descriptor.
- Category:
- Connector
- Cause:
- The deployment descriptor for this adapter cannot be found.
- Action:
- Define the deployment descriptor in ra.xml or weblogic-ra.xml or an annotation.
- BEA-199011
- No ra.xml or weblogic-ra.xml has been specified.
- Category:
- Connector
- Cause:
- The deployment descriptor for this adapter could not be found.
- Action:
- Define the deployment descriptor in ra.xml or weblogic-ra.xml.
- BEA-199012
- Unable to find the schema.
- Category:
- Connector
- Cause:
- The schema could not be found.
- Action:
- Check the location of the schema for the XML file.
- BEA-199013
- Application {0} does not have any components in it.
- Category:
- Connector
- Cause:
- The application does not contain any components.
- Action:
- Add components in the application and define them in the deployment descriptor.
- BEA-199014
- Application {0} is a RAR file, but it contains more than 1 component.
- Category:
- Connector
- Cause:
- The application contains multiple adapter components.
- Action:
- Check the deployment descriptor or the annotation.
- BEA-199015
- Error occurred while trying to rollback the module: {0}
- Category:
- Connector
- Cause:
- The module cannot be rolled back. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199016
- Unable to create runtime MBean for connector: Module "{0}", {1}
- Category:
- Connector
- Cause:
- The runtime MBean cannot be created. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199017
- Error closing virtual JAR file for {0}, {1}
- Category:
- Connector
- Cause:
- The virtual JAR file cannot be closed. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199018
- Error creating virtual JAR file for {0}, {1}
- Category:
- Connector
- Cause:
- The virtual JAR file cannot be created. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199019
- Failed to initialize the connector-specific JNDI sub-contexts for the application, {0}, {1}
- Category:
- Connector
- Cause:
- The connector-specific JNDI sub-contexts cannot be initialized. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199020
- Failed to prepare changes for dynamic update, {0}, {1}
- Category:
- Connector
- Cause:
- Changes for dynamic update cannot be prepared. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199021
- JNDI name is null or empty.
- Category:
- Connector
- Cause:
- The JNDI name must contain characters that are not spaces.
- Action:
- Check the JNDI name.
- BEA-199022
- Unable to get InitialContext while attempting to verify JNDI name of a resource adapter object.
- Category:
- Connector
- Cause:
- Failed to create the InitialContext.
- Action:
- Check the environment properties of the InitialContext.
- BEA-199023
- ResourceLink is null or empty.
- Category:
- Connector
- Cause:
- ResourceLink is null or empty.
- Action:
- Check the ResourceLink.
- BEA-199024
- Unable to get InitialContext while attempting to verify resource link of resource adapter.
- Category:
- Connector
- Cause:
- The InitialContext cannot be created.
- Action:
- Check the environment properties of the InitialContext.
- BEA-199028
- Resource Adapter with JNDIName: {0} already deployed.
- Category:
- Connector
- Cause:
- Multiple apdaters are deployed with the same JNDI name.
- Action:
- Change the adapter's JNDI name in deployment descriptor.
- BEA-199029
- Bind operation failed: {0}, {1}
- Category:
- Connector
- Cause:
- The JNDI name cannot be bound. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199031
- Failed to unbind the ConnectionFactory, {0}, {1}
- Category:
- Connector
- Cause:
- The ConnectionFactory cannot be unbound. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199032
- Unable to getInitialContext() during unbindConnectionFactory, {0}
- Category:
- Connector
- Cause:
- The getInitialContext() method cannot be called. See the reported exception for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199036
- ResourceLink: {0} already bound into application-scoped JNDI tree.
- Category:
- Connector
- Cause:
- The ResourceLink has been bound into the JNDI tree.
- Action:
- Change the JNDI name of ResourceLink.
- BEA-199037
- Unable to bind to the app-scoped jndi tree: {0}#{1} : {2}
- Category:
- Connector
- Cause:
- The ResourceLink cannot be bound. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199038
- NamingException while trying to unbind references during unbindAdminObject of resource adapter, {0}
- Category:
- Connector
- Cause:
- AdminObjects cannot be unbound. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199039
- Unable to get the connection factory for {0}. Verify that the resource adapter has been deployed.
- Category:
- Connector
- Cause:
- The connection factory cannot be found.
- Action:
- Verify that the resource adapter has been deployed.
- BEA-199041
- An exception occurred while calling newInstance in the Resource Adapter, classname = {0}, Exception = {1}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199042
- An exception occurred while trying to create the Connector Diagnostic Image, Exception = {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199043
- Trying to prepare a resource adapter that has not been initialized.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199044
- Trying to activate a resource adapter that has not been prepared. Current state : {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199045
- Trying to rollback an RA that is in the ACTIVATED state
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199046
- Unable to create the native lib directory.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199047
- Bad resource adapter class specification for class "{0}": {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199048
- Trying to version a resource adapter that is not versionable.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199049
- Unable to populate the Work Manager during resource adapter initialization.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199050
- Caught exception while starting the resource adapter : {0}, {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199051
- Caught exception while creating the BootstrapContext : {0}, {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199052
- Unable to version the resource adapter.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199053
- Unable to set up the work runtimer.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199054
- Unable to introspect the object that was passed in. {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199055
- Unable to get the setter method for the key: {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199056
- Unable to invoke the setter method for the key: {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199065
- An invalid type {0} has been specified for a key.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199066
- For property "{0}", the type and value do not match. Type = {1}, Value = {2}, Exception: {3}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action accordingly.
- BEA-199067
- LoginException while trying to establish security identity for user "{0}" in weblogic-ra.xml element {2}: {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199068
- No deployed ResourceAdapter with adapter JNDI name = "{0}" was found.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199071
- Unable to initialize ActivationSpec {0}. Cause unknown.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199072
- Failed to instantiate class {0}, {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199073
- {0} passed {1} of "{2}".
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199074
- Required Configuration Properties Missing in ActivationSpec: {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199075
- Located a resource adapter with JNDI name = "{0}", but that adapter is not yet fully deployed and active.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199076
- Could not locate a resource adapter with JNDI name = "{0}".
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199077
- The resource adapter with JNDI name = "{0}" does not have a <messagelistener> element with a <messagelistener-type> of "{1}".
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199089
- The resource adapter does not have a <inbound-resourceadapter> element in ra.xml.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199090
- The resource adapter does not have a <messageadapter> element in ra.xml.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199091
- The resource adapter does not have any <messagelistener> elements in ra.xml.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199092
- Internal error occurred, Assertion Failed: {0}
- Category:
- Connector
- Cause:
- An internal consistency check failed indicating a software defect.
- Action:
- Please note the circumstances of the error as well as any related log messages and contact My Oracle Support.
- BEA-199093
- setDyeBits failed because diagnostic contexts are not enabled.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199094
- Invalid dye value specified, {0}. Value must be between 0 and 15 in order to fit within a 4-bit space.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199095
- getDyeBits failed, moduleName = {0}: {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199096
- setDyeBits failed: Failed to obtain Diagnostic Context. ModuleName = {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199097
- getDyeBits failed because Diagnostic Contexts are not enabled.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199098
- This connection does not meet the criteria for manual deletion.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199099
- Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = "{0}", {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199100
- Resource Adapter threw Non-ResourceException from its implementation of ManagedConnection.getLocalTransaction(), Pool = "{0}", {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199101
- Resource Adapter returned null from its implementation of ManagedConnection.getLocalTransaction(), Pool = "{0}".
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199102
- Unable to register NonXAResource, {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199103
- Commit Failed: {0}, Stack Trace: {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199104
- Rollback Failed: {0}, Stack Trace: {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199105
- Resource Adapter returned null from ManagedConnection.getXAResource() while trying to obtain XAResource for recovery.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199106
- Resource Adapter threw non-ResourceException in call to ManagedConnection.getXAResource(): {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199107
- Resource Adapter returned null from ManagedConnectionFactory.createManagedConnection() while trying to create ManagedConnection for recovery.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199108
- Failed to initialize ManagedConnection for recovery: {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199109
- Connector Internal Error: Illegal type found during enlistResource.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199110
- Connector Internal Error: Invalid type found in registerResource: {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199111
- Attempt to start an XA Transaction inside a Resource Adapter''s Local Transaction is illegal.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199112
- Failed to create managed connection: {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199113
- Failed to setup the ManagedConnection with WLS after successfully getting it from a call to the Resource Adapter''s ManagedConnectionFactory.createManagedConnection method.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199114
- Internal WLS Connector Error: Object Id is null.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Please contact My Oracle Support.
- BEA-199116
- Resource Adapter Error: getConnection method returned null from the adapter''s ManagedConnection implementation in class "{0}".
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199117
- The resource adaptor has returned the same connection handle that was returned on a prior call to getConnection(). A new connection handle must be returned with every call to getConnection() as per the JCA specification.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199118
- While testing connection, the adapter''s implementation of getInvalidConnections() threw ResourceException: {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199119
- While testing connection, the adapter''s implementation of getInvalidConnections() threw non-ResourceException: {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199120
- Connections should not be tested for a ManagedConnectionFactory that does not implement ValidatingManagedConnectionFactory.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199121
- The ResourceAdapter with pool = "{0}" passed a null value to the Application Server''s implementation of the lazyEnlist method for the ConnectionManager class.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199122
- Access to resource adapter, with pool = "{0}", has been denied.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199123
- Unable to get a connection for pool = "{0}", {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199124
- Pool "{0}" is disabled, cannot allocate resources to applications.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199125
- The resource adapter''s implementation of ManagedConnectionFactory returned null from the createConnectionFactory() method.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199126
- Stack trace at connection create:
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199127
- Local Transaction not supported for this Resource Adapter.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199128
- The connection handle has not been set for the connection closed event as per the JCA specification.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199129
- Error preparing the pool with key : "{0}", {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199130
- Unable to resume the pool, {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199131
- Unable to bind to the jndi tree : "{0}", {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199132
- Key = {0}, Message = {1}, Exception = {2}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199133
- Unable to shut down the pool : Key = "{0}", Message = {1}, Exception = {2}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199134
- Attempting to create a connection factory with a JNDI name that already exists: "{0}".
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199135
- Attempting to create a connection factory with a resource link that already exists: "{0}".
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199136
- There was a problem verifying the JNDI name of the outbound connection: {0}, {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199137
- The ManagedConnectionFactory class implementation "{0}" does not implement the ResourceAdapterAssociation interface and does not implement setResourceAdapter() and/or getResourceAdapter().
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199138
- Unable to set the ResourceAdapter class for the mcf "{0}", {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199139
- Unexpected exception thrown by resource adapter''s ManagedConnectionFactory implementation "{0}", {1}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Take appropriate action based on the cause reported in the logs.
- BEA-199140
- Could not find the managed connection factory class "{0}", {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199141
- Failed to instantiate the resource adapter''s implementation of the ManagedConnectionFactory class "{0}," {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199142
- Unable to access the Resource Adapter'' implementation of the ManagedConnectionFactoryClass "{0}", {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199143
- Internal WebLogic Server Connector Error: Failed to get the connection pool for jndiName: "{0}".
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Please contact My Oracle Support.
- BEA-199144
- A resource adapter may only be accessed from within the same application from which it was deployed.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199145
- Operation is not supported, {0}, {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199146
- If only a weblogic-ra.xml has been specified for the resource adapter, it must be a linkref.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199147
- The resource adapter only has a weblogic-ra.xml specified. It also needs the ra.xml.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199148
- Error Creating Native Lib Directory: {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199149
- FileNotFoundException when creating native lib dir for {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199150
- Failure while creating native library directory for {0}, {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199151
- An error occurred while starting the pool: {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199152
- test-frequency-seconds is set to non-zero.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199153
- Connection testing cannot be enabled for a pool when the ManagedConnectionFactory does not implement ValidatingManagedConnectionFactory. The following invalid settings have been detected:
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199154
- Work instance passed in to the Work Manager is null.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199155
- The Work Manager is currently not accepting doWork() calls.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199156
- The Work Manager is currently suspended. New work is not being accepted.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199157
- Unable to establish Execution Context or enlist work in imported transaction, {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199158
- Global tx id "{0}" not associated with specified Work instance.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199159
- Global tx id "{0}" not registered with the Work Manager.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199160
- The <security-principal-map> element was deprecated in WebLogic Server 7.0 and is no longer supported. Please remove the element from the weblogic-ra.xml for the Resource Adapter.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199161
- Work instance with global tx id "{0}" already active; conncurrent work disallowed.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199162
- Bad ManagedConnectionFactory class specification for class "{0}" : {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199164
- Unable to activate the pool, {0}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199165
- test-connections-on-create is set to true.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199166
- test-connections-on-release is set to true.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199167
- test-connections-on-reserve is set to true.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199168
- Unable to force log rotation: The connection pool for "{0}" is configured to use the server log.
- Category:
- Connector
- Cause:
- Log rotation cannot be forced for pools that are configured to use the server log.
- Action:
- Change the pool's logging parameters to use a different log other than the server log.
- BEA-199169
- Failed to get the Connection Factory for the pool "{0}", {1}
- Category:
- Connector
- Cause:
- See the details of the error message for more information.
- Action:
- See the details of the error message for more information.
- BEA-199170
- For the setting {0}: "{1}" has higher privileges than the deployment user: "{2}".
- Category:
- Connector
- Cause:
- The deployment user does not have the privileges to perform the current deployment action.
- Action:
- Try the deployment action with a user account that has administrator privileges.
- BEA-199171
- The security-principal-map is not a valid element.
- Category:
- Connector
- Cause:
- The security-principal-map is not a valid element. You will need to define the mapping using the Administration Console.
- Action:
- Define the mapping using the Administration Console.
- BEA-199172
- The following error occurred in the ra.xml: {0}
- Category:
- Connector
- Cause:
- Refer to the text of the message for the description of the problem and the likely cause.
- Action:
- Correct the problem in the ra.xml file.
- BEA-199173
- The following error occurred in the weblogic-ra.xml file: {0}
- Category:
- Connector
- Cause:
- Refer to the text of the message for the description of the problem and the likely cause.
- Action:
- Correct the problem in the weblogic-ra.xml file.
- BEA-199174
- The resource adapter (RA) was deactivated previously when it was in "Suspended" state. The RA cannot be activated again since this will lead to inconsistent state. Redeploy the RA to bring it back to a normal state. Current state: {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199175
- This ManagedConnection is managed by a container for its transactional behavior and has been enlisted to a JTA transaction by a container; application/adapter must not call the local transaction begin/commit/rollback API. Reject event {0} from adapter.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199176
- Unable to execute {1} on ConnectionManager. A stale Connection Factory or Connection Handle may be used. The connection pool associated with it has already been destroyed. Try to perform another lookup of the Connection Factory {0} from JNDI and get a new Connection Handle.
- Category:
- Connector
- Cause:
- A stale Connection Factory or Connection Handle was used.
- Action:
- Perform another lookup of the Connection Factory from JNDI and get a new Connection Handle.
- BEA-199177
- Trying to deserialize an obsolete ConnectionManager.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199178
- Deploy side-by-side versioning of resource adapter with JNDI name {0}; old version: {1}; new version: {2}.
- Category:
- Connector
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-199179
- This adapter will not be deployed as side-by-side versioning since there is no old version adapter instance deployed.
- Category:
- Connector
- Cause:
- No old version adapter instance is currently deployed.
- Action:
- No action required.
- BEA-199180
- This application EAR is not deployed in a side-by-side versioning style.
- Category:
- Connector
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-199181
- Waiting for complete callback from Side-by-side versioning adapter {0}.
- Category:
- Connector
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-199182
- The resource adapter with module name {0} version {1} called ExtendedBootstrapContext.complete() to indicate it is safe to undeploy.
- Category:
- Connector
- Cause:
- The indicated resource adapter is safe to undeploy.
- Action:
- No action required.
- BEA-199183
- HintsContext: Ignore unknown hint name [{0}] and its value [{1}].
- Category:
- Connector
- Cause:
- An unknown hint was used.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199184
- ManagedConnectionFactory of connection pool [{0}] implements javax.resource.spi.TransactionSupport interface. Will use runtime TransactionSupport value [{2}] and igore the value [{1}] configured in DD or annotation.
- Category:
- Connector
- Cause:
- A new feature was used, see Section 7.13 of the Connector 1.6 specification.
- Action:
- No action is required if this behavior is expected.
- BEA-199185
- There is no META-INF/validation.xml file in the adapter archive {0}. The default Bean Validation configuration will be used.
- Category:
- Connector
- Cause:
- No META-INF/validation.xml file was found in the RAR archive.
- Action:
- No action is required if this behavior is expected.
- BEA-199186
- Found META-INF/validation.xml in adapter archive {0}.
- Category:
- Connector
- Cause:
- A META-INF/validation.xml file was found in the RAR archive.
- Action:
- No action is required if this behavior is expected.
- BEA-199187
- Found {2} constraint violation error(s) for {0} on instance [{1}]: {3}
- Category:
- Connector
- Cause:
- Bean Validation failed and got constraint violation errors.
- Action:
- Check the adapter configuration.
- BEA-199188
- Bean validation failed when validating for {0} on bean instance [{1}]. Exception: {2}
- Category:
- Connector
- Cause:
- Bean validation failed.
- Action:
- Check the adapter configuration and exception details.
- BEA-199189
- A long-running work submission has been rejected because the count of current active long-running work requests has reached the MaxConcurrentLongRunningRequests limit {0}.
- Category:
- Connector
- Cause:
- A long-running work submission was rejected because the count of current active long-running work requests has reached the MaxConcurrentLongRunningRequests limit {0}.
- Action:
- Check the adapter configuration and increase MaxConcurrentLongRunningRequests if necessary.
- BEA-199190
- The max-concurrent-long-running-requests limit was changed from {0} to {1}.
- Category:
- Connector
- Cause:
- The configuration was changed or initialized.
- Action:
- No action is required.
- BEA-199191
- Warning: Caller application {2} defines a shareable resource reference {1} to outbound connection pool {0}, but the pool does not support share by its design either because its transaction support level is NOTransaction or the ManagedConnectionFactory class has the @Unshareable annotation. Will treat as unshareable.
- Category:
- Connector
- Cause:
- An invalid resource reference definition was made to an unshareable ConnectionFactory.
- Action:
- Change the SharingScope of the resource reference definition to Unshareable.
- BEA-199192
- Warning: Caller application {2} defines a resource reference {1} to outbound connection pool {0} without defining SharingScope explicitly. The pool does not support share by its design either because its transaction support level is NOTransaction or the ManagedConnectionFactory class has the @Unshareable annotation. Will treat as unshareable.
- Category:
- Connector
- Cause:
- An invalid resource reference definition was made to an unshareable ConnectionFactory.
- Action:
- Change the SharingScope of the resource reference definition to Unshareable.
- BEA-199193
- ManagedConnection {0} of connectionInfo {1} in Connection Pool {2} has been destroyed already. Previous destroy stacktrace: {3} New destroy stacktrace: {4}
- Category:
- Connector
- Cause:
- The ManagedConnection was destroyed again.
- Action:
- Check the server log.
- BEA-199194
- Resource adapter generated unexpected exception during work event notification for event {0}. Ignored. Exception: {1}
- Category:
- Connector
- Cause:
- The resource adapter generated an unexpected exception during work event notification.
- Action:
- Check the work event processing codes of the resource adapter.
- BEA-199195
- Connector annotation scan: Ignored unexpected error [{2}] when processing annotations on {0} while {1}.
- Category:
- Connector
- Cause:
- Check the error message and stacktrace to determine the cause.
- Action:
- Check error message and stacktrace to determine the appropriate action to take.
- BEA-199196
- Ignore @javax.resource.Connector annotation on class {0} since ResourceAdapter Bean {1} is already specifed in ra.xml.
- Category:
- Connector
- Cause:
- ra.xml already specifies the ResourceAdapter bean to use.
- Action:
- No action is required if this behavior is expected.
- BEA-199197
- An exception occurred when removing admin object {0}. Exception is: {1}
- Category:
- Connector
- Cause:
- This exception occurs as the result of an attempt to unbind the admin object from JNDI.
- Action:
- Examine the log for the exact exception. Report the error to My Oracle Support.
- BEA-199198
- An exception occurred when invoking preDestroy on {0}: {1}. Exception is: {1}
- Category:
- Connector
- Cause:
- This exception occurs as the result of the CDI container calling the preDestroy method.
- Action:
- Examine the log for the exact exception. You may need to report the error the resource adapter vendor.
- BEA-199199
- The work was rejected because it has expired before WorkManager executed it.
- Category:
- Connector
- Cause:
- The time value for the startTimeout argument is too short. The WorkManager cannot start the work within the specified time period.
- Action:
- Increase the time value for the startTimeout argument and ensure that it is big enough for WarkManager to start the work.
- BEA-199200
- Annotation scan/process of the resource adapter {0} resulted in the following {1} warnings: {2}
- Category:
- Connector
- Cause:
- The specified resource adapter failed to pass the annotation scan/process as indicated by the listed warnings.
- Action:
- Check warning messages and fix the annotations that are involved.
- BEA-199201
- Failed to merge resource adapter {0} when processing annotations due to {1} error(s) found.
- Category:
- Connector
- Cause:
- Failed to merge resource adapter {0} when processing annotations due to {1} error(s) found.
- Action:
- Check the errors and fix them.
- BEA-199202
- Ignored unexpected exception [{1}] when unregistering runtime mbean {0}.
- Category:
- Connector
- Cause:
- Check error message and stack trace to figure out the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199211
- Compliance checking and validation of the resource adapter {0} resulted in the following non-critical errors: {1}
- Category:
- Connector
- Cause:
- The specified resource adapter failed to pass compliance and validity checking as indicated by the listed warnings and errors.
- Action:
- Correct the ra.xml or weblogic-ra.xml files, or check the resource adapter archive.
- BEA-199212
- Failed to create connection pool [{0}] due to error: {1}
- Category:
- Connector
- Cause:
- Check the reported error message and stack trace to determine the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199213
- A new error occurred when trying to destroy a connection pool [{0}] that was previously in a failed state : the following new error will be ignored: {1}
- Category:
- Connector
- Cause:
- Check the error message and stack trace to determine the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199214
- The connection pool [{0}] was in a HEALTH_CRITICL state already, therefore this method call is not allowed.
- Category:
- Connector
- Cause:
- Check the error message and stack trace to determine the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199215
- The connection pool [{0}] will move to a HEALTH_CRITICAL state because the adapter is not in deploy-as-a-whole mode. This pool failed due to errors: {1}
- Category:
- Connector
- Cause:
- Check the error message and stack trace to determine the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199216
- An error occurred when performing action {2} on connection pool [{0}]. The following error will be ignored: {1}
- Category:
- Connector
- Cause:
- Check the error message and stack trace to determine the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199217
- Connection pool [{0}] has validation errors and cannot be reset. Try to fix all validation errors and then do a dynamic update or redeploy this adapter.
- Category:
- Connector
- Cause:
- Check the error message and stack trace to determine the cause.
- Action:
- Try to fix all validation errors and then do a dynamic update or redeploy this adapter.
- BEA-199218
- Unable to determine whether properties were changed for Connection pool [{0}]. If there are changed properties, they may be ignored during a dynamic update: {1}
- Category:
- Connector
- Cause:
- Check the error message and stack trace to determine the cause.
- Action:
- Try to fix all validation errors and then do a dynamic update or redeploy this adapter.
- BEA-199219
- Invalid shrink threshold value {0} specified for the system property weblogic.connector.cmm.shrinkThreshold. Value must be between 0 and 10 (inclusive).
- Category:
- Connector
- Cause:
- The value of the system property weblogic.connector.cmm.shrinkThreshold is invalid.
- Action:
- Check the value of the system property weblogic.connector.cmm.shrinkThreshold. Ensure that it is between 0 and 10 (inclusive). A value of 0 indicates that the connector will not take any action on any memory pressure level.
- BEA-199220
- Failed to parse the string for UniversalResourceKey: {0}.
- Category:
- Connector
- Cause:
- The UniversalResourceKey string representation is incorrect.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199221
- Failed to parse the defining application information for UniversalResourceKey: {0}.
- Category:
- Connector
- Cause:
- The UniversalResourceKey string representation is incorrect.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199222
- The UniversalResourceKey is defined by application information: {1}#{2}#{3}, but its JNDI name {0} has the wrong name space.
- Category:
- Connector
- Cause:
- An application-defined resource has an invalid JNDI name.
- Action:
- Check the name field of @ConnectionFactoryDefinition/@AdministeredObjectDefinition or the equivalent deployment descriptor element. Ensure that it has a valid JNDI name space.
- BEA-199223
- The name space of a JNDI name {0} does not match its application information: {1}#{2}#{3}
- Category:
- Connector
- Cause:
- An application-defined resource has an invalid JNDI name.
- Action:
- Check the name field of @ConnectionFactoryDefinition/@AdministeredObjectDefinition or the equivalent deployment descriptor element. Ensure that it has a valid JNDI name space.
- BEA-199224
- JNDI name {0} has prefix of 'java:', but has no defining application information.
- Category:
- Connector
- Cause:
- An invalid JNDI name was specified for a resource.
- Action:
- Check the jndi-name field of the resource and ensure that it has a valid JNDI name.
- BEA-199300
- Cannot find Connection Definition via interfaceName:{0} from Resource Adapter:{1}. The application information: {2}#{3}#{4} The JNDI name:{5}
- Category:
- Connector
- Cause:
- The interfaceName field may be filled incorrectly for the ConnectionFactoryDefinition annotiation or the equivalent deployment descriptor.
- Action:
- Use the correct interfaceName for the ConnectionFactoryDefinition annotation or the equivalent deployment descriptor.
- BEA-199301
- Cannot find AdminObject definition in Resource Adapter {0} with className: {1} and interfaceName: {2} The application information: {3}#{4}#{5} The JNDI name:{6}
- Category:
- Connector
- Cause:
- Either the className field or the interfaceName field contains an incorrect value.
- Action:
- Fill the className or interfaceName field or both with the correct value.
- BEA-199302
- Cannot determine the AdminObject interface from class:{0} from Resource Adapter:{1} The application information: {2}#{3}#{4} The JNDI name:{5}
- Category:
- Connector
- Cause:
- 1. The interfaceName field has no entry. 2. An incorrect className field was used for AdminObject.
- Action:
- 1. Fill the interfaceName field with a valid value. 2. Fill the className field with the correct value.
- BEA-199303
- The connector resource {4} is defined in application: {1}#{2}#{3}. The corresponding resource adapter {0} is not globally accessible and is not in the same application with {1}.
- Category:
- Connector
- Cause:
- The resource adapter's deployment descriptor is not accessible from the component that defines the connector resource.
- Action:
- 1. Use another resource adapter for the connector resource. 2. Update the resource adapter's deployment descriptor, and ensure that it is accessible from the component that defines the connector resource.
- BEA-199304
- Failed to export object of class:{0} from Resource Adapter:{1} The application information: {2}#{3}#{4} The JNDI name:{5}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199305
- Duplicated resource definition for Resource Adapter:{0} The application information: {1}#{2}#{3} The JNDI name:{4}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199306
- At least one application-defined resource is found for Resource Adapter:{0} The application information: {1}#{2}#{3} The JNDI name:{4}
- Category:
- Connector
- Cause:
- The resource adapter cannot be undeployed when an application-defined resource exists.
- Action:
- Undeploy the application first.
- BEA-199307
- Failed to unexport object: {0} which JNDI name is {1}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199308
- Failed to find PartitionRuntimeMBean for the partition {0}.
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199309
- Unable to register runtime MBean for connector: {0}.
- Category:
- Connector
- Cause:
- The runtime MBean cannot be registered. See the reported error for the cause.
- Action:
- Examine the exception in the log for more information about how to correct the problem.
- BEA-199310
- Failed to lookup JNDI name: {3}. This resource is defined in application: {0}#{1}#{2}.
- Category:
- Connector
- Cause:
- The corresponding resource adapter may not be activated.
- Action:
- Check the status of the corresponding resource adapter and activate it or take other appropriate action.
- BEA-199311
- Failed to find Resource Adapter:{0} The application information: {1}#{2}#{3} The JNDI name:{4}
- Category:
- Connector
- Cause:
- Check the logs for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199312
- At least one of the permissions declared in permissions.xml is not allowed.
- Category:
- Connector
- Cause:
- Check the permissions.xml configuration for the cause of this exception.
- Action:
- Inspect the cause and take appropriate action.
- BEA-199313
- Application classloader is used for loading resource adaptor {1}''s classes in application {0}.
- Category:
- Connector
- Cause:
- <enable-ee-compliant-classloading-for-embedded-adapters> is set to true.
- Action:
- No action is required.
- BEA-199314
- Resource adaptor''s classloader is used for loading resource adaptor {1}''s classes in application {0}. This classloader is the child classloader of the application classloader.
- Category:
- Connector
- Cause:
- <enable-ee-compliant-classloading-for-embedded-adapters> is set to false.
- Action:
- No action is required.
- BEA-199315
- The <classloader-structure> configuration in application {0}''s weblogic-application.xml is ignored by resource adapter {1} because resource adapter {1}''s <enable-global-access-to-classes> is set to true.
- Category:
- Connector
- Cause:
- <enable-global-access-to-classes> is set to true.
- Action:
- No action is required.
- BEA-199316
- Failed to destroy pool [{0}] due to error: {1}
- Category:
- Connector
- Cause:
- Check the reported error message and stack trace to determine the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199317
- Failed to create admin object [{0}] due to error: {1}
- Category:
- Connector
- Cause:
- Check the reported error message and stack trace to determine the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199318
- It is not supported to access connector resource outside server {0} which defines the resource, current server is {1}.
- Category:
- Connector
- Cause:
- Check the reported error message and stack trace to determine the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-199319
- It is not supported to access resource adapter outside partition {0} which defines the resource, current partition is {1}.
- Category:
- Connector
- Cause:
- Check the reported error message and stack trace to determine the cause.
- Action:
- Take appropriate action based on the cause determined from the reported error message and stack trace.
- BEA-200000
- Failed to initialize the messaging bridge service.
- Category:
- MessagingBridge
- Cause:
- Most of the time, this results from configuration errors.
- Action:
- Check the configuration file and reboot the system.
- BEA-200001
- The messaging bridge service has successfully shut down.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the messaging bridge service has been shut down, either at the request of the administrator or due to errors.
- Action:
- No action is required.
- BEA-200002
- Failed to deploy the messaging bridge "{0}" because the messaging bridge service is shut down.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the messaging bridge service has been shut down, either at the request of the administrator or due to errors.
- Action:
- Reboot the system.
- BEA-200003
- Failed to deploy the messaging bridge "{0}" due to error: {1}.
- Category:
- MessagingBridge
- Cause:
- This is likely due to configuration errors or an internal WebLogic Server error as indicated in the message body.
- Action:
- Check the configuration file, and reboot the server.
- BEA-200004
- The messaging bridge "{0}" has been successfully deployed.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the messaging bridge has been successfully deployed.
- Action:
- No action is required.
- BEA-200005
- Failed to start messaging bridge "{0}" due to error: {1}
- Category:
- MessagingBridge
- Cause:
- This is likely due to configuration errors or an internal WebLogic Server error, as indicated in the message body.
- Action:
- Check the configuration file, and reboot the server.
- BEA-200008
- Bridge "{0}" does not have a configured source destination.
- Category:
- MessagingBridge
- Cause:
- This is likely due to configuration errors.
- Action:
- Update the configuration, and restart the server.
- BEA-200009
- Bridge "{0}" does not have a configured target destination.
- Category:
- MessagingBridge
- Cause:
- This is likely due to configuration errors.
- Action:
- Update the configuration, and restart the server.
- BEA-200011
- The bridge "{0}" failed to find the adapter "{1}". The bridge will periodically retry to look up the adapter. If this message stops reappearing, it means that the bridge has finally successfully found the adapter.
- Category:
- MessagingBridge
- Cause:
- One of the adapters was not deployed.
- Action:
- Deploy the required adapters.
- BEA-200012
- Bridge "{0}" successfully found the adapters that are configured for it.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the bridge successfully found the adapters.
- Action:
- No action is required.
- BEA-200013
- Invalid properties are defined for the source destination of bridge "{0}".
- Category:
- MessagingBridge
- Cause:
- The configuration was invalid.
- Action:
- Update the configuration, and restart the server.
- BEA-200014
- Invalid properties are defined for the target destination of bridge "{0}".
- Category:
- MessagingBridge
- Cause:
- The configuration was invalid.
- Action:
- Update the configuration, and restart the server.
- BEA-200015
- An error occurred in bridge "{0}" during the transfer of messages ({1}).
- Category:
- MessagingBridge
- Cause:
- An error occurred on one of the bridge destinations.
- Action:
- Check the system on both the source and target sides, and restart the server.
- BEA-200020
- Bridge "{0}" is stopped.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the messaging bridge has stopped.
- Action:
- No action is required.
- BEA-200021
- Bridge "{0}" failed to get one of the adapters from JNDI ({1}).
- Category:
- MessagingBridge
- Cause:
- At least one adapter was not deployed when the bridge started. It is also possible that the JNDI names configured in the bridge destinations do not match the ones in the adapter deployment descriptor file.
- Action:
- Check to see if the adapter(s) required by the source and target destinations are deployed on the server where the bridge is configured. Ensure that the JNDI name in the adapter deployment descriptor file matches the one in the configuration of the bridge destinations. Otherwise, no action is required. The bridge will automatically try again later.
- BEA-200022
- Bridge "{0}" failed to obtain adapter metadata ({1}).
- Category:
- MessagingBridge
- Cause:
- This is an internal WebLogic Server error that should not occur.
- Action:
- No action is required.
- BEA-200024
- Bridge "{0}" refused to obtain connections and transfer any messages, because it has been stopped, suspended, or is shutting down.
- Category:
- MessagingBridge
- Cause:
- The administrator has shut down or stopped the bridge, or the bridge is suspended for migration.
- Action:
- No action is required.
- BEA-200025
- Bridge "{0}" failed to start because the quality of service configured ({1}) is unreachable. This is likely due to an invalid configuration or adapter limitations.
- Category:
- MessagingBridge
- Cause:
- The configuration does not match the ability of the adapters and underlying systems.
- Action:
- Change the configuration of the bridge with a reachable quality of service, or turn on the QOSDegrationAllowed boolean.
- BEA-200026
- Bridge "{0}" encountered problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception that occurred was {1})
- Category:
- MessagingBridge
- Cause:
- There was a problem in receiving or sending messages to one of the sides of the bridge.
- Action:
- No action is required.
- BEA-200027
- Bridge "{0}" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.
- Category:
- MessagingBridge
- Cause:
- This may occur because the source destination is empty or because the connection to the source was stale and needs to be reestablished.
- Action:
- Check the source system.
- BEA-200028
- The bridge "{0}" has started transferring messages.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the bridge has just started transferring messages.
- Action:
- No action is required.
- BEA-200030
- Bridge "{0}" is configured to work in "{1}" mode, but it is actually working in "{2}" mode.
- Category:
- MessagingBridge
- Cause:
- This message reveals what quality of service the bridge is actually providing.
- Action:
- No action is required.
- BEA-200031
- Bridge "{0}" is configured to allow degradation of its quality of service in cases where the configured quality of service cannot be reached.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the quality of service of this bridge is allowed to be downgraded if the required one is unreachable.
- Action:
- No action is required.
- BEA-200032
- Bridge "{0}" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the quality of service of the bridge is not allowed to be downgraded.
- Action:
- No action is required.
- BEA-200033
- Bridge "{0}" is obtaining connections to the two adapters.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the messaging bridge is obtaining connections to the two adapters.
- Action:
- No action is required.
- BEA-200034
- Bridge "{0}" is shut down.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the messaging bridge is shut down.
- Action:
- No action is required.
- BEA-200035
- Bridge "{0}" has been started from the stopped mode.
- Category:
- MessagingBridge
- Cause:
- This message indicates that the bridge was in stopped mode and has just been restarted.
- Action:
- No action is required.
- BEA-200036
- The started attribute of bridge "{0}" has been changed from "{1}" to "{2}".
- Category:
- MessagingBridge
- Cause:
- This is due to a configuration change.
- Action:
- No action is required.
- BEA-200037
- The "{1}" attribute of bridge "{0}" has been changed from "{2}" to "{3}".
- Category:
- MessagingBridge
- Cause:
- This is due to a configuration change.
- Action:
- No action is required.
- BEA-200038
- Bridge "{0}" is inactive because it is configured to be stopped.
- Category:
- MessagingBridge
- Cause:
- The bridge is configured to be stopped.
- Action:
- No action is required.
- BEA-200039
- Bridge "{0}" has the same destination as its source and target.
- Category:
- MessagingBridge
- Cause:
- This is due to a configuration error.
- Action:
- Update the configuration.
- BEA-200040
- Bridge destination {0}: connection URL cannot be null if the initial context factory is not weblogic.jndi.WLInitialContextFactory.
- Category:
- MessagingBridge
- Cause:
- This is due to a configuration error.
- Action:
- Update the configuration.
- BEA-200041
- Bridge destination {0}: a bridge destination for JMS must have a connection factory JNDI name and a destination JNDI name configured.
- Category:
- MessagingBridge
- Cause:
- This is due to a configuration error.
- Action:
- Update the configuration.
- BEA-200042
- Bridge {0} failed to connect to the source destination and will try again in {2} seconds. This could be a temporary condition unless the messages repeat several times. ({1})
- Category:
- MessagingBridge
- Cause:
- An error occurred on the source destination of the bridge. The error may occur because the source destination does not exist or has not been active yet.
- Action:
- Check the source system and its configuration. Ensure that the destination is configured in the system and the system is running.
- BEA-200043
- Bridge "{0}" failed to connect to the target destination and will try again in {2} seconds. This could be a temporary condition unless the messages repeat several times. ({1})
- Category:
- MessagingBridge
- Cause:
- The error occurred on the target destination of the bridge. The error may occur because the target destination does not exist or has not been active yet.
- Action:
- Check the target system and its configuration. Ensure that the destination is configured in the system and the system is running.
- BEA-200044
- The following exception has occurred:
- Category:
- MessagingBridge
- Cause:
- An error condition has occurred.
- Action:
- Look for the associated exception in the log or the program to see the results. In general, this stack trace will help in debugging an existing problem.
- BEA-200045
- Bridge "{0}" failed to start because it has been suspended or is shutting down.
- Category:
- MessagingBridge
- Cause:
- The administrator has shut down the bridge, or the bridge is suspended for migration.
- Action:
- No action is required.
- BEA-200046
- The "{1}" attribute of bridge "{0}" has been changed from "{2}" to "{3}".
- Category:
- MessagingBridge
- Cause:
- This is due to a configuration change.
- Action:
- No action is required.
- BEA-200047
- Bridge "{0}" failed to start because its migratable target has not been activated for this server.
- Category:
- MessagingBridge
- Cause:
- The bridge is targeted to a migrable target that has not yet been activated on this server.
- Action:
- No action is required.
- BEA-200048
- {1} destination "{2}" of bridge "{0}" has a configured adapter JNDI name "{3}", so it will find the internal automatically deployed adapter with JNDI name "{4}". The bridge will ignore an explicitly configured and deployed adapter with adapter JNDI name "{3}". The deployed adapter will be ignored, the bridge does not need to deploy a separate adapter.
- Category:
- MessagingBridge
- Cause:
- This is due to a configuration upgrade.
- Action:
- No action is required.
- BEA-200049
- {1} destination "{2}" of bridge "{0}" uses a custom adapter JNDI name "{3}" instead of the expected names of eis.jms.WLSConnectionFactoryJNDIXA or eis.jms.WLSConnectionFactoryJNDINOXA.
- Category:
- MessagingBridge
- Cause:
- The bridge destination uses a configured adapter JNDI name.
- Action:
- No action is required.
- BEA-200050
- The bridge has a configured adapter JNDI name "{1}", so it will find the internal automatically deployed adapter with JNDI name "{2}". The bridge will ignore an explicitly configured and deployed adapter "{0}". The deployed adapter will be ignored.
- Category:
- MessagingBridge
- Cause:
- The bridge destination uses a configured adapter.
- Action:
- No action is required.
- BEA-210003
- No network channel is available to handle COM requests.
- Category:
- COM
- Cause:
- The server is not configured with at least one non-SSL port.
- Action:
- Configure a plain text listener port if COM is enabled.
- BEA-213500
- Partition {0} has ResourceDeploymentPlanPath set to {1} but the zip file from which it is being imported does not have an entry for it.
- Category:
- Partition Portability
- Cause:
- While importing the paritition, an attempt was made to import a partition without proper configuration. The element resource-deployment-plan-path points to a plan which is to be used for overwriting resource attributes. As part of exporting a partition, this plan should have been archived as part of the overall partition archive created, but the exported archive is missing the plan.
- Action:
- Export the partition once again and verify that the exported archive ZIP file contains the file referred to by <resource-deployment-plan-path > in config.xml before importing the partition.
- BEA-213501
- Could not find partition by name {0} to export in the current domain.
- Category:
- Partition Portability
- Cause:
- The partition name that was provided for export does not exist in the domain.
- Action:
- Check the name of the partition and then run exportPartition again.
- BEA-213502
- A ResourceGroupTemplate with name {0} already exists.
- Category:
- Partition Portability
- Cause:
- This error occurs if importPartition is called with the createNew parameter set to null, and the partition being imported references a ResourceGroupTemplate that has the same name as one of the ResourceGroupTemplates in the domain.
- Action:
- If you want to use the existing ResourceGroupTemplate, run importPartition again with createNew set to false. If you want to clone the ResourceGroupTemplate with a new name, run importPartition again with createNew set to true.
- BEA-213503
- Could not delete temporary pending file {0}.
- Category:
- Partition Portability
- Cause:
- During import, if the option createNew is set to false, then it is imperative that the files corresponding to the ResourceGroupTemplate copied into the pending directory as part of import be deleted before activate is called.
- Action:
- Delete the file {0} and run importPartition again.
- BEA-213504
- The destination for writing imported app {0} already exists at {1}.
- Category:
- Partition Portability
- Cause:
- While importing a partition with the application binaries/plan, the destination for writing the binary/plan file in an imported domain file system already has a file with the same name.
- Action:
- Delete the file in the domain at {1} and run importPartition again.
- BEA-213505
- Application {0} with staging mode set to {1} does not exist at the specified sourcepath {2}.
- Category:
- Partition Portability
- Cause:
- The imported partition references an application that is neither in the exported ZIP file nor at the specified location as specified by the source-path attribute of the app-deployment bean.
- Action:
- Check that source-path is correct and run importPartition again after placing the application binary at the specified source-path.
- BEA-213506
- The application {0} has the stagingMode set to {1} but the exported ZIP file does not have application binaries to import.
- Category:
- Partition Portability
- Cause:
- The imported partition references an application that is in {1} staged mode. The exported ZIP file does not, however, contain the application binary.
- Action:
- Either change the staging mode in the attributes.json file to external_stage/nostage or export again with the application binaries included.
- BEA-213507
- attributes.json has a reference attribute {0} with its value set to {1}, but this attribute was not found in the imported domain''s configuration.
- Category:
- Partition Portability
- Cause:
- A wrong attributes value was specified in the attributes.json file during importPartition.
- Action:
- Look at config.xml before importing and use the proper attribute values for updating attributes.json before importing the partition.
- BEA-213508
- The name of the object {0} in partition-config.xml is {1} whereas {2} has the name changed to something else. Therefore it could not be found. Changing names of attributes in {2} is not supported.
- Category:
- Partition Portability
- Cause:
- The name of an attribute was changed in {2}.
- Action:
- Revert the name change in {2} and importPartition again.
- BEA-213509
- Partition {0} is in an unknown state because of a non-dynamic change that was made which affects {1}. The server must be rebooted in order for the partition to become stable and export Partition to work.
- Category:
- Partition Portability
- Cause:
- The partition being exported is in an unknown state. A common cause of this is that a non-dynamic configuration change was made to the domain that has deferred the initialization of the partition until the Administration Server is restarted.
- Action:
- Restart the Administration Server.
- BEA-213510
- {0} for partition {1} failed.
- Category:
- Partition Portability
- Cause:
- TBD
- Action:
- Look at the stack trace and fix appropriate error.
- BEA-240001
- {0}
- Category:
- Console
- Cause:
- The Administration Console logs informational messages about console usage.
- Action:
- No action is required.
- BEA-240002
- {0}
- Category:
- Console
- Cause:
- The Administration Console encountered an error that is potentially harmful.
- Action:
- Review the warning message text to determine the appropriate action.
- BEA-240003
- Administration Console encountered the following error: {0}
- Category:
- Console
- Cause:
- The Administration Console encountered an error, but the console may continue to run.
- Action:
- Review the error message text to determine the appropriate action.
- BEA-240004
- The Administration Console encountered the following error: {0}
- Category:
- Console
- Cause:
- The Administration Console encountered a critical error.
- Action:
- Review the message text to determine the appropriate action.
- BEA-240005
- A Cross-site Request Forgery (CSRF) has been detected. Task={0}, address={1}, user={2}
- Category:
- Console
- Cause:
- The Administration Console encountered a CSRF.
- Action:
- Take action based upon the provided exception details.
- BEA-260000
- WebLogic Local Deployment Manager
- Category:
- J2EE Deployment SPI
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-260001
- "{0}" does not identify a known Deployment Manager. The URI must be of the form: deployer:WebLogic:host:port. The host and port are required if attempting to acquire a connected Deployment Manager.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid URI was provided when allocating a Deployment Manager.
- Action:
- No action is required.
- BEA-260002
- "{0}" is not a valid URI. The URI must be of the form: "deployer:WebLogic:protocol://host:port". The host and port are required if attempting to acquire a connected Deployment Manager. The protocol should be a well-known IP protocol.
- Category:
- J2EE Deployment SPI
- Cause:
- Incorrect host/port used when attempting to allocate a Deployment Manager.
- Action:
- No action is required.
- BEA-260003
- Feature not available when in disconnected mode.
- Category:
- J2EE Deployment SPI
- Cause:
- A deployment tool allocated a disconnected Deployment Manager or released it.
- Action:
- Allocate a connected Deployment Manager.
- BEA-260004
- Locale, "{0}", is not supported.
- Category:
- J2EE Deployment SPI
- Cause:
- The locale was incorrectly specified.
- Action:
- No action is required.
- BEA-260008
- J2EE version {0} not supported by this Deployment Manager.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid argument was used.
- Action:
- No action is required.
- BEA-260009
- Exception caught for class "{0}" while attempting to create Deployment Manager: {1}
- Category:
- J2EE Deployment SPI
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-260010
- Unable to connect to "{0}" as user, "{1}". Error received: {2}
- Category:
- J2EE Deployment SPI
- Cause:
- Authorization failed.
- Action:
- No action is required.
- BEA-260012
- No configured targets match provided target with name, "{0}", and type, "{1}"
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid argument was used.
- Action:
- No action is required.
- BEA-260013
- The target array passed to Deployment Manager was null or empty.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid argument was used.
- Action:
- No action is required.
- BEA-260015
- The "{0}" operation is not supported.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid request was made; the operation is not supported.
- Action:
- No action is required.
- BEA-260016
- "{0}" does not exist.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid argument was used.
- Action:
- No action is required.
- BEA-260017
- Unable to locate deployment task, "{0}"
- Category:
- J2EE Deployment SPI
- Cause:
- The task was removed from the system.
- Action:
- No action is required.
- BEA-260020
- Module {1} of application {0} successfully transitioned from {2} to {3} on server {4}.
- Category:
- J2EE Deployment SPI
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-260021
- Module {1} of application {0} failed to transition from {2} to {3} on server {4}.
- Category:
- J2EE Deployment SPI
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-260022
- {2} application {0} on server {1}.
- Category:
- J2EE Deployment SPI
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-260023
- Deployment task does not exist for ProgressObject
- Category:
- J2EE Deployment SPI
- Cause:
- The deployment task was removed from the system.
- Action:
- No action is required.
- BEA-260024
- Connection errors occurred while reporting a progress event. The event was from application, {0}, module, {1}, on server {2}. The event was {3}. The error was {4}.
- Category:
- J2EE Deployment SPI
- Cause:
- There was a deployment failure.
- Action:
- No action is required.
- BEA-260026
- Task failed for unknown reason. Task description is {0}
- Category:
- J2EE Deployment SPI
- Cause:
- The cause is unknown.
- Action:
- No action is required.
- BEA-260027
- Non-root module, "{1}", is not supported for {0} operations. All modules must represent root modules.
- Category:
- J2EE Deployment SPI
- Cause:
- All modules must represent root modules. This operation does not support embedded modules.
- Action:
- Use DeploymentManager.enableModuleTargeting.
- BEA-260028
- No targeting information was provided for {0} operation.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid argument was used.
- Action:
- No action is required.
- BEA-260029
- "{1}" is not part of application, "{2}". Only one application allowed for {0} operation.
- Category:
- J2EE Deployment SPI
- Cause:
- Multiple applications were specified in the same operation. An invalid argument was used.
- Action:
- No action is required.
- BEA-260030
- Module, "{0}", is not part of any application.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid argument was used.
- Action:
- No action is required.
- BEA-260031
- No action performed or required for {0} request.
- Category:
- J2EE Deployment SPI
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-260036
- Module type, "{0}", is not supported.
- Category:
- J2EE Deployment SPI
- Cause:
- The operation is unsupported.
- Action:
- No action is required.
- BEA-260037
- Encountered unexpected descriptor for module "{0}".
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid application descriptor was used in the EAR file.
- Action:
- Fix the application descriptor.
- BEA-260040
- No files provided in {0} request.
- Category:
- J2EE Deployment SPI
- Cause:
- At least one file must be specified for update.
- Action:
- No action is required.
- BEA-260041
- Unable to upload "{1}" to "{0}"
- Category:
- J2EE Deployment SPI
- Cause:
- Check the log for further details. Requested files need to be uploaded to a remote Administration Server.
- Action:
- No action is required.
- BEA-260050
- "{0}" does not implement weblogic.deploy.api.spi.WebLogicDConfigBeanRoot, or cannot be instantiated: {1}.
- Category:
- J2EE Deployment SPI
- Cause:
- See the message body.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-260052
- null DConfigBeanRoot.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid argument was used.
- Action:
- No action is required.
- BEA-260055
- Unable to parse deployment plan: "{0}".
- Category:
- J2EE Deployment SPI
- Cause:
- The document is invalid and could not be read or parsed during a deployment operation.
- Action:
- No action is required.
- BEA-260056
- MBean must be for Application or Component: "{0}".
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid argument was used.
- Action:
- No action is required.
- BEA-260061
- Unable to recognize DDBean with xpath, "{0}".
- Category:
- J2EE Deployment SPI
- Cause:
- Unable to restore configuration from an invalid descriptor; an invalid argument was used.
- Action:
- No action is required.
- BEA-260067
- Restored configuration for module, {0}
- Category:
- J2EE Deployment SPI
- Cause:
- DeploymentConfiguration.restoreDConfigBean was invoked
- Action:
- No action is required.
- BEA-260068
- Removed configuration for module, {0}
- Category:
- J2EE Deployment SPI
- Cause:
- DeploymentConfiguration.removeDConfigBean was invoked.
- Action:
- No action is required.
- BEA-260070
- Saved configuration for module, {0}
- Category:
- J2EE Deployment SPI
- Cause:
- DeploymentConfiguration.saveDConfigBean was invoked.
- Action:
- No action is required.
- BEA-260071
- Restored configuration for application, {0}
- Category:
- J2EE Deployment SPI
- Cause:
- DeploymentConfiguration.restore was invoked.
- Action:
- No action is required.
- BEA-260072
- Saved configuration for application, {0}
- Category:
- J2EE Deployment SPI
- Cause:
- DeploymentConfiguration.save was invoked.
- Action:
- No action is required.
- BEA-260073
- Unable to introspect on bean, "{0}".
- Category:
- J2EE Deployment SPI
- Cause:
- See the message detail.
- Action:
- No action is required.
- BEA-260078
- No DConfigBean is available for invalid module, "{0}": {1}.
- Category:
- J2EE Deployment SPI
- Cause:
- Check the error message for the specific problem.
- Action:
- No action is required.
- BEA-260080
- Unable to define the application install directory at "{0}". Directory could not be created or is a file.
- Category:
- J2EE Deployment SPI
- Cause:
- The directory could not be created or is a file.
- Action:
- Specify a valid directory.
- BEA-260081
- The descriptor at "{0}" could not be parsed.
- Category:
- J2EE Deployment SPI
- Cause:
- The descriptor contains syntax errors and is invalid.
- Action:
- No action is required.
- BEA-260082
- A required descriptor, {0}, for a CMP bean is missing.
- Category:
- J2EE Deployment SPI
- Cause:
- A descriptor file is missing.
- Action:
- Place the necessary descriptor file in the archive file or its external configuration area.
- BEA-260083
- No plan document at "{0}"
- Category:
- J2EE Deployment SPI
- Cause:
- The path for the plan may have been incorrectly specified. If this is the first time the application is being configured; this may not be a problem; the plan will be created.
- Action:
- Specify the correct plan location as necessary.
- BEA-260085
- The configuration descriptor for "{0}" already exists ( {1} ), or was not modified ( {2} ), and will not be saved.
- Category:
- J2EE Deployment SPI
- Cause:
- The descriptors do not need to be saved.
- Action:
- No action is required.
- BEA-260086
- The descriptor information at {0} was saved to the configuration area.
- Category:
- J2EE Deployment SPI
- Cause:
- The configuration was saved.
- Action:
- No action is required.
- BEA-260087
- The descriptor at "{0}" is missing the required {1} element for custom module with URI, "{2}", and provider, "{3}".
- Category:
- J2EE Deployment SPI
- Cause:
- The named element is missing from the weblogic-extensions.xml descriptor.
- Action:
- Correct the errors in the weblogic-extensions.xml descriptor.
- BEA-260088
- The {1} descriptor at "{0}" is missing.
- Category:
- J2EE Deployment SPI
- Cause:
- The referenced JMS/JDBC descriptor is not present in the archive.
- Action:
- Ensure that all of the descriptors are in place.
- BEA-260091
- Errors were detected when reading "{0}": {1}
- Category:
- J2EE Deployment SPI
- Cause:
- Check the error message to determine the probable cause.
- Action:
- No action is required.
- BEA-260094
- Registering config module descriptor support with base URI, {0}, and configuration URI, {1}.
- Category:
- J2EE Deployment SPI
- Cause:
- The weblogic-extensions descriptor specified custom configuration descriptor support.
- Action:
- No action is required.
- BEA-260095
- Unable to create archive for "{0}"
- Category:
- J2EE Deployment SPI
- Cause:
- An attempt to name a file with the appropriate extension failed.
- Action:
- No action is required.
- BEA-260096
- Unable to determine type of application for "{0}".
- Category:
- J2EE Deployment SPI
- Cause:
- The archive does not contain standard descriptors.
- Action:
- Ensure that the correct file was passed into the deployment operation.
- BEA-260097
- Unable to understand DDBeanRoot provided by deployer tool: "{0}".
- Category:
- J2EE Deployment SPI
- Cause:
- The model API is not providing the expected information
- Action:
- Resolve API problems in the class that implements javax.enterprise.deploy.model.DDBeanRoot.
- BEA-260098
- No descriptor type is registered for modules of type, {0}
- Category:
- J2EE Deployment SPI
- Cause:
- The module type is not registered with a configurable descriptor.
- Action:
- Register non-standard descriptors using the weblogic-extension.xml descriptor.
- BEA-260099
- No root element in {0} descriptor, {1} at {2}.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid deployment descriptor was provided for the module.
- Action:
- Either the wrong descriptor was specified or the module type is incorrect; take the appropriate actions to fix the problem.
- BEA-260100
- Invalid value for Security Model, {0}; Should be one of {1}.
- Category:
- J2EE Deployment SPI
- Cause:
- An unrecognized security model was requested.
- Action:
- Use a valid security model
- BEA-260101
- Parameter "{0}" may not be null.
- Category:
- J2EE Deployment SPI
- Cause:
- A null parameter was passed to the method.
- Action:
- Resolve the client programming error.
- BEA-260102
- Type parameter, "{0}", provided to export method is invalid
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid export type parameter was used.
- Action:
- Use a valid export type.
- BEA-260103
- The provided bean is not part of this configuration: "{0}".
- Category:
- J2EE Deployment SPI
- Cause:
- An attempt was made to export bean properties against the wrong DConfigBeanRoot object
- Action:
- Invoke export on the correct DConfigBeanRoot.
- BEA-260104
- {0} is not a changable property
- Category:
- J2EE Deployment SPI
- Cause:
- One of the properties is not changeable.
- Action:
- Remove the property that is not changeable from the list.
- BEA-260106
- Failed to parse descriptor at "{1}" for module "{0}": {2}.
- Category:
- J2EE Deployment SPI
- Cause:
- The descriptor is not valid
- Action:
- Ensure that the application is accessible and contains valid descriptors.
- BEA-260107
- Failed to write descriptor for module "{0}" configuration: {1}.
- Category:
- J2EE Deployment SPI
- Cause:
- Either an I/O error prevented the save operation or the descriptor is missing some required elements.
- Action:
- Depends on the specific error. See the error message for details.
- BEA-260108
- Failed to restore descriptors: {0}.
- Category:
- J2EE Deployment SPI
- Cause:
- An I/O or parse error prevented the restore operation.
- Action:
- The course of action depends on the specific error. See the error message for details.
- BEA-260109
- Failed to write deployment plan: {0}.
- Category:
- J2EE Deployment SPI
- Cause:
- Either an I/O error prevented the save operation or the plan is missing some required elements.
- Action:
- The course of action depends on the specific error; see the error message for details.
- BEA-260110
- Failed to create configuration for module: {0}
- Category:
- J2EE Deployment SPI
- Cause:
- The configuration artifacts for the application could not be processed. This could result from simple access errors, descriptor parsing failures, or basic application architecture problems.
- Action:
- The course of action depends on the specific error. See the error message for details.
- BEA-260111
- Errors were detected while attempting to communicate with the Administration Server.
- Category:
- J2EE Deployment SPI
- Cause:
- Depends on the specific error. The associated exception will contain the root exception.
- Action:
- The course of action depends on the specific error. See the exception.
- BEA-260112
- Unable to determine application name from null or empty TargetModuleID list.
- Category:
- J2EE Deployment SPI
- Cause:
- No TargetModuleID objects were provided.
- Action:
- Resolve the client programming error by providing a list of TargetModuleID objects.
- BEA-260113
- Plan at "{0}" is a directory. A deployment plan is always an XML document.
- Category:
- J2EE Deployment SPI
- Cause:
- Plan at "{0}" is a directory, not an XML document.
- Action:
- Resolve the client programming error.
- BEA-260114
- Application root at "{0}" is not a directory.
- Category:
- J2EE Deployment SPI
- Cause:
- An invalid root directory was specified.
- Action:
- Resolve the client programming error.
- BEA-260115
- Must specify application to configure.
- Category:
- J2EE Deployment SPI
- Cause:
- No application was specified for the configuration.
- Action:
- Resolve the client programming error.
- BEA-260116
- Configuration is not initialized
- Category:
- J2EE Deployment SPI
- Cause:
- SessionHelper.initialize() was not yet invoked.
- Action:
- Resolve the client programming error.
- BEA-260117
- Unable to load factory, "{0}"
- Category:
- J2EE Deployment SPI
- Cause:
- The factory is not in the classpath.
- Action:
- Ensure that the factory is in the classpath.
- BEA-260118
- A null target was included in a deployment request.
- Category:
- J2EE Deployment SPI
- Cause:
- The target list is invalid.
- Action:
- Resolve the client programming error.
- BEA-260119
- The path provided, "{0}", does not represent a directory.
- Category:
- J2EE Deployment SPI
- Cause:
- The first argument must be a directory.
- Action:
- Resolve the client programming error.
- BEA-260121
- Initiating {0} operation for application, {1} [archive: {2}], to {3}.
- Category:
- J2EE Deployment SPI
- Cause:
- A deployment operation is starting.
- Action:
- No action is required.
- BEA-260122
- Initiating {0} operation for application, {1}, from stream to {2}.
- Category:
- J2EE Deployment SPI
- Cause:
- A deployment operation is starting.
- Action:
- No action is required.
- BEA-260123
- Unable to determine targets for deployment request on application, {0}
- Category:
- J2EE Deployment SPI
- Cause:
- No targets were specified for the new deployment.
- Action:
- Specify the targets to which you want to deploy the application.
- BEA-260124
- configured targets
- Category:
- J2EE Deployment SPI
- Cause:
- No targets were specified.
- Action:
- No action is required.
- BEA-260125
- Errors were detected when attempting to communicate with Administration Server: {0}
- Category:
- J2EE Deployment SPI
- Cause:
- Depends on the specific error. The associated exception will contain the root exception.
- Action:
- The course of action depends on the specific error. See the exception.
- BEA-260126
- Cannot override plan version, "{0}", with version from options, "{1}".
- Category:
- J2EE Deployment SPI
- Cause:
- A plan version was specified in the deployment options, but the plan defines its own version.
- Action:
- Avoid specifying the plan version.
- BEA-260128
- Changes not allowed to DTD based descriptors. The attempt to modify property "{0}" in {1} for module "{2}" will be vetoed if possible. The change will not be persisted in either case.
- Category:
- J2EE Deployment SPI
- Cause:
- A property in a DTD based descriptor was modified.
- Action:
- Upgrade the application with schema based descriptors.
- BEA-260129
- Export not allowed on DTD based descriptors. No properties for the {0} descriptor in module, "{1}", will be exported.
- Category:
- J2EE Deployment SPI
- Cause:
- An attempt was made to export a DTD based descriptor.
- Action:
- Upgrade the application with schema based descriptors.
- BEA-260130
- Shutting down Deployment Manager connection failed.
- Category:
- J2EE Deployment SPI
- Cause:
- See the message detail.
- Action:
- Allocate a new Deployment Manager.
- BEA-260131
- No URI was provided.
- Category:
- J2EE Deployment SPI
- Cause:
- An attempt was made to create a Deployment Manager without providing an appropriate deployer URI.
- Action:
- Provide an appropriate deployer URI.
- BEA-260132
- "{0}" is not a child of "{1}".
- Category:
- J2EE Deployment SPI
- Cause:
- "{0}" is not a child of "{1}".
- Action:
- Check for a 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-260133
- The descriptor at "{0}" could not be parsed due to error: {1}.
- Category:
- J2EE Deployment SPI
- Cause:
- The named descriptor is invalid.
- Action:
- No action is required.
- BEA-260134
- Unable to identify application for {0} operation.
- Category:
- J2EE Deployment SPI
- Cause:
- Insufficient information was provided to identify which application to deploy.
- Action:
- Resolve the client programming error.
- BEA-260137
- Failures were detected while restoring the original plan file {0}. The current plan may not reflect the accurate state of the application. Either attempt to update the application again with the current plan, or make use of the backup plan "{1}".
- Category:
- J2EE Deployment SPI
- Cause:
- Failures were detected while restoring the original plan file {0}. The current plan may not reflect the accurate state of the application.
- Action:
- Either attempt to update the application again with the current plan or make use of the backup plan "{1}".
- BEA-260138
- Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.
- Category:
- J2EE Deployment SPI
- Cause:
- Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.
- Action:
- Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.
- BEA-260139
- Unchanged plan.xml was restored due to problems updating new plan {0}.
- Category:
- J2EE Deployment SPI
- Cause:
- Unchanged plan.xml was restored due to problems updating new plan {0}.
- Action:
- Unchanged plan.xml was restored due to problems updating new plan {0}.
- BEA-260140
- Unable to remove descriptor bean {0} due to "{1}". The remover should first check to see if the bean is removable in the deployment plan prior to removing it.
- Category:
- J2EE Deployment SPI
- Cause:
- Unable to remove descriptor bean {0} due to {1}.
- Action:
- The remover should first check to see if the bean is removable in the deployment plan prior to removing it.
- BEA-260141
- An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close().
- Category:
- J2EE Deployment SPI
- Cause:
- An attempt to reinitialize this object by calling either inspect() or initializeConfiguration() was made without first calling close(). This SessionHelper object is stateful and must be properly closed by calling close().
- Action:
- Call close() on the SessionHelper instance, and avoid reusing the same instance.
- BEA-260142
- The descriptor at "{0}" in module "{1}" is not recognized, and could not be parsed.
- Category:
- J2EE Deployment SPI
- Cause:
- The descriptor was not recognized and could not be parsed.
- Action:
- No action is required.
- BEA-260143
- "{0}" and "{1}" cannot both be specified.
- Category:
- J2EE Deployment SPI
- Cause:
- The combination of the two parameters is inconsistent.
- Action:
- Use only one of the parameters.
- BEA-260144
- The specified partition "{0}" does not exist in the domain.
- Category:
- J2EE Deployment SPI
- Cause:
- A partition needs to exist in the domain before deploying to it.
- Action:
- Create the specified partition before deploying to it.
- BEA-260145
- The specified resource group "{0}" does not exist in the specified partition "{1}".
- Category:
- J2EE Deployment SPI
- Cause:
- A resource group needs to exist before deploying to it.
- Action:
- Create the specified resource group before deploying to it.
- BEA-260146
- The specified resource group template "{0}" does not exist in the domain.
- Category:
- J2EE Deployment SPI
- Cause:
- A resource group template needs to exist before deploying to it.
- Action:
- Create the specified resource group template before deploying to it.
- BEA-260147
- The resource group name cannot be derived in this case. Specify the resource group option along with the partition option.
- Category:
- J2EE Deployment SPI
- Cause:
- A resource group option need to be specified with the partition option for the cases where it cannot be derived.
- Action:
- Specify the resource group option with partition option.
- BEA-260148
- A resource group template option cannot be specified with a resource group option.
- Category:
- J2EE Deployment SPI
- Cause:
- Cannot specify a resource group template option and a resource group option together.
- Action:
- Either specify a resource group template option or specify a resource group option.
- BEA-260149
- The specified resource group "{0}" does not exist in the domain.
- Category:
- J2EE Deployment SPI
- Cause:
- A resource group needs to exist before deploying to it.
- Action:
- Create the specified resource group before deploying to it.
- BEA-260150
- A partition administrator cannot perform deployment operations to a resource group template.
- Category:
- J2EE Deployment SPI
- Cause:
- A partition administrator cannot operate on a resource group template.
- Action:
- Operate on the resource group template as a system administrator.
- BEA-260151
- Partition administrator from partition {0} cannot perform deployment operations to partition {1}.
- Category:
- J2EE Deployment SPI
- Cause:
- A partition administrator is trying to operate someone else' partition.
- Action:
- A partition administrator should only operate on their own partition.
- BEA-260152
- "config-root" {0} is not a directory/file.
- Category:
- J2EE Deployment SPI
- Cause:
- The "config-root" may not have been set properly.
- Action:
- Verify that the "config-root" is correct.
- BEA-260153
- "config-root"should not be empty.
- Category:
- J2EE Deployment SPI
- Cause:
- The "config-root" may not have been set properly.
- Action:
- Verify that the "config-root" is correct/not empty.
- BEA-280008
- Opening the persistent file store "{0}" for recovery: directory={1} requestedWritePolicy="{2}" fileLockingEnabled={3} driver="{4}".
- Category:
- Store
- Cause:
- Informational message.
- Action:
- No action required.
- BEA-280009
- The persistent file store "{0}" ({1}) has been opened: blockSize={2} actualWritePolicy="{3}" explicitIOEnforced={4} records={5}.
- Category:
- Store
- Cause:
- Informational message.
- Action:
- No action required.
- BEA-280012
- Recovery is not yet complete.
- Category:
- Store
- Cause:
- This was caused by a programming error.
- Action:
- Check the code and try again.
- BEA-280013
- The specified store record is longer than the maximum length of {0} bytes.
- Category:
- Store
- Cause:
- This was caused by a programming error.
- Action:
- Either change the code or increase the size of the record.
- BEA-280019
- There was an error while writing to a storage.
- Category:
- Store
- Cause:
- See the detail message for the cause.
- Action:
- Ensure that the hardware and operating system are functioning properly and that there is enough space available for the storage area.
- BEA-280020
- There was an error while reading from the storage.
- Category:
- Store
- Cause:
- See the detail message for the cause.
- Action:
- Ensure that the hardware and operating system are functioning properly and that all the storage spaces are available online.
- BEA-280021
- There was an error while opening the file store file "{0}".
- Category:
- Store
- Cause:
- Either the specified file does not exist, the server does not have permissions to open the file, or there is a hardware or operating system problem.
- Action:
- Ensure that the file exists and that the directory name was specified correctly.
- BEA-280024
- There was an error while creating a new file named "{0}" for the file store.
- Category:
- Store
- Cause:
- See the detail message. The disk may be full, or there may be a hardware or operating system problem.
- Action:
- Ensure that there is enough disk space and that the hardware and operating system are working properly.
- BEA-280026
- The primary or cache file "{0}" is not both readable and writeable.
- Category:
- Store
- Cause:
- The file permissions are incorrect, or the server is running under the wrong user ID.
- Action:
- Fix the file permissions or run the server under the correct user ID.
- BEA-280029
- The store record {0} could not be found.
- Category:
- Store
- Cause:
- This is caused by a programming error.
- Action:
- Ensure that the correct record ID was specified.
- BEA-280031
- The store named "{0}" has not yet been opened.
- Category:
- Store
- Cause:
- This is a programming error.
- Action:
- Fix the code and try again.
- BEA-280032
- The store suffered a fatal error and it must be reopened.
- Category:
- Store
- Cause:
- A fatal error occurred previously.
- Action:
- Restart the server.
- BEA-280035
- Unable to access the store directory "{0}".
- Category:
- Store
- Cause:
- See the detail message.
- Action:
- Check that the specified path name is correct, that it exists, and that the directory is readable and writeable by the server's user ID.
- BEA-280036
- Missing the file store file "{0}" in the directory "{1}".
- Category:
- Store
- Cause:
- The file has been accidentially deleted or moved, or the wrong directory name was specified, or the server process does not have permissions to read and write the file.
- Action:
- Ensure that the directory name is correct and that the server process has permissions to read and write the files. If necessary, create an empty file with the same name.
- BEA-280037
- The file store has reached the maximum number of {0} files and no more files can be created.
- Category:
- Store
- Cause:
- There are too many records in the store.
- Action:
- Delete data from the store and try again.
- BEA-280038
- An error occurred while flushing the contents of a file store file.
- Category:
- Store
- Cause:
- See the detail message.
- Action:
- See the detail message.
- BEA-280039
- The store handle {0} is not valid.
- Category:
- Store
- Cause:
- This is caused by a programming error.
- Action:
- Fix the code and try again.
- BEA-280040
- An invalid record was found in the store: Code={0}.
- Category:
- Store
- Cause:
- The store has been corrupted, possibly by a hardware or operating system error.
- Action:
- For File store, Change the DirectIOMode or restore from backup if the problem persists.
- BEA-280041
- A record was found in the store with an invalid version of {0}
- Category:
- Store
- Cause:
- The store may have been used with an incompatible version of WebLogic Server.
- Action:
- Restore from backup.
- BEA-280042
- The file store primary or cache file "{0}" cannot be opened because it is actually a directory.
- Category:
- Store
- Cause:
- A directory was accidentially created in the file store's own main or cache directory, or the specified path is incorrect.
- Action:
- Check that the file store path is correct.
- BEA-280044
- The file store directory "{0}" does not exist.
- Category:
- Store
- Cause:
- The directory has not yet been created, or its filesystem is not available.
- Action:
- Check that the directory path has been correctly specified, and create the directory if necessary.
- BEA-280045
- The file store primary or cache directory "{0}" is not a directory.
- Category:
- Store
- Cause:
- The directory has not yet been created, or its filesystem is not available.
- Action:
- Check that the directory path has been correctly specified, remove any file or directory that already exists in its place, and create the directory if necessary.
- BEA-280046
- The directory "{0}" is not both readable and writeable.
- Category:
- Store
- Cause:
- The file permissions are incorrect, or the server is running under the wrong user ID.
- Action:
- Fix the file permissions or run the server under the correct user ID.
- BEA-280051
- The store was not able to create a new record.
- Category:
- Store
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-280052
- The store was not able to read a record.
- Category:
- Store
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-280055
- Invalid name for store write policy: "{0}".
- Category:
- Store
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-280056
- A store error occurred: {0}
- Category:
- Store
- Cause:
- See the description of the underlying exception.
- Action:
- See the description of the underlying exception
- BEA-280057
- The store named "{0}" is already open.
- Category:
- Store
- Cause:
- This is a programming error.
- Action:
- Fix the code and try again.
- BEA-280059
- "{0}" is not a valid store connection name.
- Category:
- Store
- Cause:
- This is a programming error.
- Action:
- Fix the code and try again.
- BEA-280060
- The store "{0}" encountered a fatal error, and it must be shut down: {1}
- Category:
- Store
- Cause:
- There was a serious I/O error, either with file I/O, replicated store IO or the JDBC connection to the database.
- Action:
- Restart the server.
- BEA-280061
- The store "{0}" could not be deployed: {1}
- Category:
- Store
- Cause:
- See he detail message.
- Action:
- See the detail message.
- BEA-280062
- The store "{0}" could not be shut down: {1}
- Category:
- Store
- Cause:
- See the detail message.
- Action:
- See the detail message.
- BEA-280063
- 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:
- Store
- 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-280064
- {0} (server="{1}" store="{2}" table="{3}")
- Category:
- Store
- Cause:
- See the exception text, and linked exception (if one exists).
- Action:
- See the exception text, and linked exception (if one exists).
- BEA-280065
- {0} (server="{1}" store="{2}" table="{3}"):(Linked Cause, "{4}")
- Category:
- Store
- Cause:
- See the exception text and linked exception text.
- Action:
- See the exception text and linked exception text.
- BEA-280066
- Empty field value in table reference "{0}" (format [[[catalog.]schema.]table).
- Category:
- Store
- 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, make sure 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-280067
- JDBC store "{0}" did not find a database table at "{1}", so it created one using the commands in file "{2}".
- Category:
- Store
- Cause:
- The JDBC store did not find its backing table, so it created one.
- Action:
- No action is required.
- BEA-280068
- JDBC store failed to initialize. It did not find its database table and failed trying to create a new empty table using the commands in file "{0}".
- Category:
- Store
- Cause:
- See the linked exception text and linked exception stack trace.
- Action:
- See the linked exception text and linked exception stack trace.
- BEA-280069
- JDBC store failed to initialize. It did not find an already existing database table and failed to create a new empty table because the JDBC driver is unknown and/or unsupported. To force table creation with an unknown and/or unsupported driver, see the JDBC store "CreateTableDDLFile" configuration attribute. Driver information: database product name = "{0}", driver name = "{1}".
- Category:
- Store
- Cause:
- See the exception text and exception stack trace.
- Action:
- See the text exception text and exception stack trace.
- BEA-280070
- JDBC store failed to initialize. It did not find an already existing database table and failed to create a new empty table because it could not locate the configured DDL file "{0}".
- Category:
- Store
- Cause:
- The configured file is located in the server file path.
- Action:
- For supported databases, consider the option of not configuring a custom DDL file. There is usually no need to configure a custom DDL file unless custom database-specific tuning commands have been added to the file. If a DDL file must be configured (perhaps because it is for an unsupported database), ensure that the configured file is located either in the server file path or server class path.
- BEA-280071
- JDBC store "{0}" opened table "{1}" and loaded {2,choice,0#0 records|1#1 record|2#{0} records}. For additional JDBC store information, use the diagnostics framework while the JDBC store is open.
- Category:
- Store
- Cause:
- A JDBC store booted.
- Action:
- No action is required.
- BEA-280072
- JDBC store "{0}" failed to open table "{1}".
- Category:
- Store
- Cause:
- See the linked exception.
- Action:
- See the linked exception.
- BEA-280073
- The file store "{0}" could not be opened because it contained a file with an invalid version {1}. A file of version {2} was expected.
- Category:
- Store
- Cause:
- The file store has not been properly upgraded from a previous version of WebLogic Server, or the file has been corrupted on the disk.
- Action:
- Ensure that the file store was upgraded using the weblogic.Upgrade tool.
- BEA-280074
- The store "{0}" encountered an unresolvable failure while processing transaction "{1}". Shut down and restart to resolve this transaction. {2}
- Category:
- Store
- Cause:
- There was a serious I/O error, either with file I/O, replicated I/O or the JDBC connection to the database, or an unexpected exception occurred while processing a transaction.
- Action:
- Restart the server.
- BEA-280075
- JDBC store "{0}" failed to retain ownership of database table "{1}", either due to database access problems or due to concurrent accessors of the table. See the linked exception for more information.
- Category:
- Store
- Cause:
- Some other WebLogic server process or JDBC store has taken over ownership of the database table, or some database access error prevented this JDBC store from renewing ownership of the database table.
- Action:
- The error message has information to identify potential owners in conflict.
- BEA-280076
- Database table "{1}" for store "{0}" is currently owned by "{2}". Trying to wait for ownership.
- Category:
- Store
- Cause:
- Some other WebLogic Server process or JDBC store has ownership of the database table.
- Action:
- The warning message has information to identify the current owner of the database table. If the current owner does not yield ownership within some time, this server will not be able to open the JDBC store and will log an error.
- BEA-280077
- JDBC store "{0}" in this server is not the owner of database table "{1}". Unexpected current owner is "{2}", expected current owner is "{3}".
- Category:
- Store
- Cause:
- Some other WebLogic Server process or JDBC store has ownership of the database table.
- Action:
- The error message has information to identify and resolve the owners in conflict.
- BEA-280078
- The handle that was passed was created from a different store connection.
- Category:
- Store
- Cause:
- This is a programming error.
- Action:
- Ensure that the correct connection was used.
- BEA-280079
- An instance of the mSA PersistentStore
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280080
- Number of create requests issued by this store.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280081
- Number of read requests issued by this store.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280082
- Number of update requests issued by this store
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280083
- Number of delete requests issued by this store
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280084
- Number of objects contained in the store
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280085
- Number of times the store flushed its data to durable storage
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280086
- An instance of an mSA PersistentStoreConnection
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280087
- Number of create requests issued by this store connection
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280088
- Number of read requests issued by this store connection
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280089
- Number of update requests issued by this store connection
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280090
- Number of delete requests issued by this store connection
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280091
- Number of objects contained in the store connection
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280092
- Specified value "{1}" of the property "{0}" is not a valid Integer system property. Using default value "{2}" instead.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- Check the Javadoc for the valid formats of Integer system properties: http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Integer.html#decode(java.lang.String).
- BEA-280093
- Block size "{1}" specified by the property {0} is outside the valid range from {2} to {3}. Using default value "{2}" instead.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
- BEA-280094
- The size "{1}" specified by the property {0} is not power of 2. Rounding down to "{2}" instead.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
- BEA-280095
- Opening existing file store "{1}". The block size value specified by the property {0} is ignored because the block size of preexisting files cannot change.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
- BEA-280096
- Opening existing store "{2}". The direct IO mode "{1}" specified by the property "{0}" is invalid and will be ignored. Using the default value "{3}"
- Category:
- Store
- Cause:
- See the message body.
- Action:
- Use a valid direct I/O mode. The valid values are: "read-buffered", "single-handle-unbuffered", and "single-handle-buffered".
- BEA-280097
- A file store failed to open file "{0}" in the Direct-Write read-buffered/write-unbuffered mode and is instead opening the file in a purely unbuffered mode. When there are high request loads, this may reduce file store performance. However, the store is still operating in a transactionally safe synchronous mode.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- To fix this problem, configure a different synchronous write policy, or if using the Direct-Write policy, force the store into read-write-buffered mode using the AvoidDirectIO command line property documented in the store chapter of the Performance and Tuning Guide.
- BEA-280101
- The persistent file store "{0}" is forced to use buffered I/O because the Operating System or hardware environment does not support unbuffered I/O. The store is still operating in a transactionally safe synchronous mode. See store open log messages for the final write policy.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- See the documentation for store synchronous write policy configuration.
- BEA-280102
- The perisistent file store "{0}" must reinitialize its cache: recovery may take longer than usual. The signature in the cache file "{2}" for the persistent store file "{1}" could not be verified, or the cache file is missing. Ignore this Warning if this is the first time the store has ever booted. Possible causes include: first boot of store (potentially after using a write policy different from Direct-Write-With-Cache), store migration, unclean shutdown, off-line store compression, and manual removal of cache files.
- Category:
- Store
- Cause:
- The cache file is missing, or the signature stored in the cache file does not match the signature of the primary file.
- Action:
- Make sure that the configuration is correct, do not delete cache files, and ensure a clean shutdown.
- BEA-280103
- The persistent file store "{0}" will cache in {1}.
- Category:
- Store
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-280104
- The persistent file store "{0}" will use buffered writes instead of direct IO because the configured block size "{2}" is not a multiple of the environment''s direct IO alignment "{1}". When there are high request loads, this may reduce file store performance. The store is still operating in a transactionally safe synchronous mode.
- Category:
- Store
- Cause:
- Direct I/O requires the block size to be a multiple of directIO granularity.
- Action:
- Reconfigure the store with a block size that is a multiple of the direct I/O alignment for your environment. If the store is not empty and contains useful data, use the store admin compact utility to change block size, otherwise make sure that all storage areas are removed before starting WebLogic Server again.
- BEA-280105
- The persistent file store "{0}" cannot open file {1}.
- Category:
- Store
- Cause:
- An IOException occurred.
- Action:
- No action is required.
- BEA-280106
- The persistent file store "{0}" cannot memory-map the locked file "{1}" and has to downgrade to explicit buffered IO. For example, in some NFS environments memory-mapping and locking are not compatible. Consider configuring a local cache directory.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- Consult your storage vendor and operating system documentation.
- BEA-280107
- The store record {0}, connection "{1}", in the store named "{2}" does not exist because it has been deleted.
- Category:
- Store
- Cause:
- This was caused by a programming error.
- Action:
- Ensure that the correct record ID was specified.
- BEA-280108
- The store record {0}, connection "{1}" already exists in the store named "{2}".
- Category:
- Store
- Cause:
- This was caused by a programming error.
- Action:
- Ensure that the correct record ID was specified.
- BEA-280109
- The JVM was unable to load the native wlfileio library for the store "{0}". File and paging stores will continue to function correctly. Specifically, file stores that are configured with a transactionally safe synchronous write policy will continue to operate safely and transactionally but may open with a different write-policy. Other store types may not be able to open.
- Category:
- Store
- Cause:
- See message body.
- Action:
- See file store open log messages for the requested and final file store write policies. See the documentation for file store synchronous write policy configuration.
- BEA-280110
- The "{1}" attribute of Store "{0}" has been changed from "{2}" to "{3}".
- Category:
- Store
- Cause:
- This is due to a configuration change.
- Action:
- No action is required.
- BEA-280111
- The "{1}" attribute of Store "{0}" has been changed from "{2}" to "{3}".
- Category:
- Store
- Cause:
- This is due to a configuration change.
- Action:
- No action is required.
- BEA-280112
- [StoreBootOnError] "{0}" Ignoring AssertionError on bootHandle: record type: {1}, handle:{2}, row: {3}
- Category:
- Store
- Cause:
- There is some corruption of the JDBC store.
- Action:
- Contact My Oracle Support.
- BEA-280113
- The JDBC store "{0}" is initially pointing to RAC instance "{1}".
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-280114
- The JDBC store "{0}" is configured with worker count as "{1}" but only started "{2}" workers as it is not able to acquire enough JDBC connections for the configured worker count.
- Category:
- Store
- Cause:
- The JDBC store was not able to acquire enough JDBC connections for the configured worker count.
- Action:
- Modify the data source configuration.
- BEA-280115
- Replicated store "{0}": the daemon is approaching its shared memory limit and the store itself has used up to "{1}%" of its shared memory.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-280116
- Replicated store "{0}": the daemon is approaching its shared memory limit and the store itself has used up to "{1}%" of its shared memory. It will reject new JMS persistent messages.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- Check if there are things that need to be cleaned up, for example abandoned durable subscriptions. Consider restart the daemon with a bigger limit.
- BEA-280117
- Replicated store "{0}" the daemon has used up to "{1}%" of its shared memory limit.
- Category:
- Store
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-280118
- Replicated store "{0}": the daemon has used up to "{1}%" of its shared memory limit. It may take actions, including rejecting new JMS persistent messages or failing on creating any new stores or opening any recovered stores.
- Category:
- Store
- Cause:
- The amount of shared memory used by the replicated store daemon has met or exceeded the configured warning threshold.
- Action:
- Check if there are things that need to be cleaned up, for example abandoned durable subscriptions. Consider restart the daemon with a bigger limit.
- BEA-280119
- Replicated store "{0}": the daemon used up to "{1}%" of its shared memory limit. It will fail on creating new stores or opening any recovered store.
- Category:
- Store
- Cause:
- The amount of shared memory used by the replicated store daemon has met or exceeded the configured error threshold.
- Action:
- Check if there are things that need to be cleaned up, for example abandoned durable subscriptions. Consider restart the daemon with a bigger limit.
- BEA-280120
- Opening the Replicated store "{0}(Region Name={1})" for recovery: directory={2} driver="{3}".
- Category:
- Store
- Cause:
- Informational message.
- Action:
- No action required.
- BEA-280121
- The Replicated store "{0}(Region Name={1})" ({2}) has been opened: blockSize={3} records={4}.
- Category:
- Store
- Cause:
- Informational message.
- Action:
- No action required.
- BEA-280122
- Missing the region "{1}" from this replicated store(name="{0}").
- Category:
- Store
- Cause:
- The region has been accidentially deleted or moved, or the wrong name was specified, or the server process does not have permissions to read and write to the region.
- Action:
- Ensure that the replicated Store name is correct and that the server process has permissions to read and write to the regions in replicated store. If necessary, create an empty region with the same name.
- BEA-280123
- The replicated store has reached the maximum number of {0} regions and no more region can be created.
- Category:
- Store
- Cause:
- There are too many records in the store.
- Action:
- Delete data from the store and try again.
- BEA-280124
- An error occurred while flushing the contents of a replicated store region.
- Category:
- Store
- Cause:
- See the detail message.
- Action:
- See the detail message.
- BEA-280125
- The replicated store "{0}(Region Name={1})" could not be opened because it contained a region with an invalid version {2}. A region of version {3} was expected.
- Category:
- Store
- Cause:
- The replicated store has not been properly upgraded from a previous version of WebLogic Server, or the region has been corrupted on the memory store.
- Action:
- Ensure that the file store was upgraded using the weblogic.Upgrade tool.
- BEA-280126
- Opening existing replicated store "{1}(Region Name={2})". The block size value specified by the property {0} is ignored because the block size of preexisting regions cannot change.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
- BEA-280127
- The replicated store "{0}" cannot open region {1}.
- Category:
- Store
- Cause:
- An IOException occurred.
- Action:
- No action is required.
- BEA-280128
- The store can't be initialized.
- Category:
- Store
- Cause:
- See the message body.
- Action:
- Please check that the cryptographic services of the execution environment and the host operating system are properly configured and operating correctly.
- BEA-280129
- JDBC store "{0}" will be opened with connection caching policy "{1}" and will keep {2,choice,1#1 database connection|2#{2} database connections} open.
- Category:
- Store
- Cause:
- Informational message.
- Action:
- No action is required.
- BEA-280130
- The configuration property "{2}" with value "{3}" on JDBC store "{0}" is incompatible with connection policy "{1}".
- Category:
- Store
- Cause:
- Conflicting configuration options.
- Action:
- Either the connection caching policy must be changed or the property value must be changed.
- BEA-280131
- The use of piggy-back commit is incompatible connection policy "{1}" and has been disabled for JDBC store "{0}".
- Category:
- Store
- Cause:
- Conflicting configuration options.
- Action:
- Either the connection caching policy must be changed or the property value must be changed.
- BEA-280132
- JDBC store "{0}" will be opened with connection caching policy "{1}" and will get one connection from its data source as needed.
- Category:
- Store
- Cause:
- Informational message.
- Action:
- No action is required.
- BEA-280133
- The version record is missing from the table "{1}" for the JDBC store "{0}". Make sure that only Weblogic processes are accessing and modifying the table.
- Category:
- Store
- Cause:
- The version record is missing from the non-empty table backing the JDBC store.
- Action:
- Contact My Oracle Support regarding restoring the version record in the JDBC store.
- BEA-280134
- The version record is missing from the table "{1}" for the JDBC store "{0}" and will be restored.
- Category:
- Store
- Cause:
- Informational message.
- Action:
- No action is required.
- BEA-280135
- The non-critical store "{0}" failed to open and some associated features may be impacted. Please consult the log for more details.
- Category:
- Store
- Cause:
- See the log files.
- Action:
- See the detail message.
- BEA-280136
- DEPRECATION NOTICE: With WebLogic Server 12.2.1.3 and with the Exalogic X6 initial release, the WebLogic Replicated Store for JMS messages is deprecated. It will be removed in a future release. Oracle recommends that you use either a custom file store or a JDBC store for JMS message storage. See "Administering the WebLogic Persistent Store" in the documentation for more information about these options.
- Category:
- Store
- Cause:
- A deprecated store type is in use.
- Action:
- Oracle recommends using a file store or a JDBC store.
- BEA-281002
- The SAF service has been started.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281003
- The SAF service has been initialized.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281004
- The SAF service has been suspended.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281005
- The SAF service has been shut down.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281006
- FailedMessage for store-and-forward: MessageId={0} > </FailedMessage.
- Category:
- SAFService
- Cause:
- A message expired before it was successfully forwarded by an SAF agent, and there is no error handling policy configured for the endpoint. The message ID was logged.
- Action:
- No action is required.
- BEA-281007
- SAF Agent "{0}" has been successfully prepared.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281008
- SAF Agent "{0}" has been successfully activated.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281009
- SAF Agent "{0}" has been deactivated.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281010
- SAF Agent "{0}" has been unprepared.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281011
- SAF Agent "{0}" failed to be prepared because of exception "{1}".
- Category:
- SAFService
- Cause:
- There was either an error in the configuration.
- Action:
- Check the agent's configuration.
- BEA-281012
- SAF Agent "{0}" failed to be started because of exception "{1}".
- Category:
- SAFService
- Cause:
- There was either an error in the configuration.
- Action:
- Check the agent's configuration.
- BEA-281016
- SAFAgent "{0}" byte threshold for the agent has been exceeded.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281017
- SAFAgent "{0}" byte threshold for agent has cleared.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281018
- SAFAgent "{0}" message threshold for the agent has been exceeded.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281019
- SAFAgent "{0}" message threshold for the agent has cleared.
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281020
- SAF service has successfully connected to the remote endpoint "{0}".
- Category:
- SAFService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-281021
- SAF service failed to connect to the remote endpoint "{0}", because of {1}.
- Category:
- SAFService
- Cause:
- This is either due to a configuration error or a network failure, or the remote endpoint is temporarily unavailable.
- Action:
- Check the configuration, the network connection, or the remote endpoint.
- BEA-281022
- SAF Agent "{0}" failed to resume because of exception "{1}".
- Category:
- SAFService
- Cause:
- There was either an error in the configuration.
- Action:
- Check the agent's configuration.
- BEA-281025
- SAFAgent "{0}" has been paused for incoming messages.
- Category:
- SAFService
- Cause:
- An Incoming Message Pause request was issued for the specified SAFAgent.
- Action:
- No action is required.
- BEA-281026
- SAFAgent "{0}" has been resumed for new incoming messages.
- Category:
- SAFService
- Cause:
- An Incoming Message Resume request was issued for the specified SAFAgent.
- Action:
- No action is required.
- BEA-281027
- SAFAgent "{0}" has been paused for forwarding
- Category:
- SAFService
- Cause:
- A Forwarding Pause request was issued for the specified SAFAgent.
- Action:
- No action is required.
- BEA-281028
- SAFAgent "{0}" has been resumed for forwarding.
- Category:
- SAFService
- Cause:
- A Forwarding Resume request was issued for the specified SAFAgent.
- Action:
- No action is required.
- BEA-281029
- RemoteEndpoint "{0}" has been paused for new incoming messages.
- Category:
- SAFService
- Cause:
- An Incoming Pause Request was issued for the specified remote endpoint.
- Action:
- No action is required.
- BEA-281030
- RemoteEndpoint "{0}" has been resumed for new incoming messages.
- Category:
- SAFService
- Cause:
- An Incoming Resume Request was issued for the specified remote endpoint.
- Action:
- No action is required.
- BEA-281031
- RemoteEndpoint "{0}" has been paused for forwarding.
- Category:
- SAFService
- Cause:
- A Forwarding Pause Request was issued for the specified remote endpoint.
- Action:
- No action is required.
- BEA-281032
- RemoteEndpoint "{0}" has been resumed for forwarding.
- Category:
- SAFService
- Cause:
- A Forwarding Resume request was issued for the specified remote endpoint.
- Action:
- No action is required.
- BEA-282000
- Unsupported class version {0}. Expected a value between {1} and {2} inclusive.
- Category:
- Messaging
- Cause:
- While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {2}, then it is possible an attempt was made to access a newer version than the current version. Otherwise, a possible attempt has been made to interoperate with an unsupported older version.
- Action:
- Ensure that the versions of Oracle products that are interoperating are supported. If the versions need to be supported, contact My Oracle Support.
- BEA-282001
- The messaging kernel {0} is beginning recovery of its persistent state.
- Category:
- Messaging
- Cause:
- This is normal operation.
- Action:
- No action is required.
- BEA-282002
- The messaging kernel {0} has recovered {1} persistent messages.
- Category:
- Messaging
- Cause:
- This is normal operation.
- Action:
- No action is required.
- BEA-282003
- The messaging kernel {0} will use up to {1} bytes of memory before paging begins.
- Category:
- Messaging
- Cause:
- This is normal operation.
- Action:
- No action is required.
- BEA-282004
- Message redirection has failed in a non-recoverable way for the messaging kernel {0}. Restart the server in order to restart message redirection.
- Category:
- Messaging
- Cause:
- See the previous error messages, which should explain the cause.
- Action:
- Restart the WebLogic Server.
- BEA-282005
- An error occurred while redirecting a message for the messaging kernel {0}: {1}.
- Category:
- Messaging
- Cause:
- See the attached detail message.
- Action:
- No action is required.
- BEA-282006
- An error occurred while deleting an expired message for the messaging kernel {0}: {1}.
- Category:
- Messaging
- Cause:
- See the attached detail message.
- Action:
- No action is required.
- BEA-282007
- An error occurred in the transaction prepare phase of a message send operation for the messaging kernel {0}.
- Category:
- Messaging
- Cause:
- See the attached stack trace.
- Action:
- No action is required.
- BEA-282008
- A message send transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.
- Category:
- Messaging
- Cause:
- A server was shut down or a destination was removed while a transaction was in progress.
- Action:
- No action is required.
- BEA-282009
- A message receive transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.
- Category:
- Messaging
- Cause:
- A server was shut down or a destination was removed while a transaction was in progress.
- Action:
- No action is required.
- BEA-282010
- A sequence number update transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.
- Category:
- Messaging
- Cause:
- A server was shut down or a destination was removed while a transaction was in progress.
- Action:
- No action is required.
- BEA-282011
- There was an error making a message visible after a delivery delay: {0}.
- Category:
- Messaging
- Cause:
- Most likely, a transient I/O error occurred.
- Action:
- Consider restarting the server if the error persists. The message will not be lost.
- BEA-282012
- There was a failure while performing paging I/O.
- Category:
- Messaging
- Cause:
- Either a transient I/O error occurred, or the server did not have enough memory to complete the paging I/O request.
- Action:
- Consider restarting the server if the error persists.
- BEA-282013
- Skipping unexpected null message encountered on store boot, {0}.
- Category:
- Messaging
- Cause:
- Message data corruption has occurred. The corrupted message will be skipped to allow data recovery on other non-corrupted messages.
- Action:
- Report this issue to My Oracle Support.
- BEA-282014
- [StoreBootOnError] "{0}" Ignoring 2PC record for sequence={1}, queue={2}, type={3}, id={4}, xid={5}; message reference element cannot be found.
- Category:
- Messaging
- Cause:
- Potential message data corruption has occurred. A 2PC record was found in the store without an associated message reference element. The 2PC record will be ignored.
- Action:
- Contact My Oracle Support.
- BEA-282015
- "{0}" An error occurred while writing a message to store: info={1}; null message body detected.
- Category:
- Messaging
- Cause:
- An error was detected while attempting to write a message to the persistent store.
- Action:
- Contact My Oracle Support.
- BEA-282016
- A problem occurred while SAF Agent "{0}" recovered SAF messages from its persistent store: data was found in both old (pre-12.2.1.0.0) store connections and in new (12.2.1.x.0) store connections. The old store connections and the data within them are going to be ignored.
- Category:
- Messaging
- Cause:
- The SAF agent in question has been upgraded from a pre-12.2.1.0.0 release to an unpatched 12.2.1.x.0 release while it had unprocessed persistent messages, and then upgraded to a patched 12.2.1.x.0 release. As a result, there are pre-12.2.1.0.0 data (which were ignored during the first upgrade), and unpatched 12.2.1.x.0 data in the store.
- Action:
- Use -Dweblogic.saf.StoreUpgradeMode="OldOnly" to recover only the old messages. Use -Dweblogic.saf.StoreUpgradeMode="IgnoreOld" to suppress this warning message. Or contact My Oracle Support.
- BEA-283002
- Path Service has been started on server {0} with jndiName {1} with store {2}
- Category:
- PathService
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-290001
- Error occurred in the deployment service servlet. It received an unacceptable request of type "{0}" with content type "{1}".
- Category:
- DeploymentService
- Cause:
- An invalid request was made to the deployment service servlet.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290003
- Deployment service servlet encountered an exception while handling request of type "{0}". Exception is: "{1}".
- Category:
- DeploymentService
- Cause:
- Error occurred while handling the deployment servlet request.
- Action:
- This is an internal WebLogic Server error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
- BEA-290006
- Deployment service servlet received a request of type "{0}" with no application name.
- Category:
- DeploymentService
- Cause:
- An invalid deployment service servlet request was made.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290007
- Deployment service servlet unable to find upload directory while handling request of type "{0}" for application "{1}".
- Category:
- DeploymentService
- Cause:
- The servlet was unable to find the upload directory.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290008
- Deployment service servlet encountered an error while extracting uploaded file to directory "{0}". Exception is: "{1}".
- Category:
- DeploymentService
- Cause:
- An exception occurred while extracting the uploaded file.
- Action:
- This is an internal WebLogic Server error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
- BEA-290009
- Deployment service servlet failed to get initialized due to unavailable security service.
- Category:
- DeploymentService
- Cause:
- The WebLogic Server security service is not present in the installation files.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290010
- Deployment service servlet failed to get initialized due to privileged action violation. Exception is: "{0}".
- Category:
- DeploymentService
- Cause:
- An exception occurred while initializing the deployment service servlet.
- Action:
- This is an internal WebLogic Server error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
- BEA-290011
- Unauthorized request of type "{0}" for user "{1}"
- Category:
- DeploymentService
- Cause:
- The user is unauthorized for downloading files.
- Action:
- Check the user and try again with an authorized user.
- BEA-290012
- Deployment service servlet received jspRefresh request with no upload file name.
- Category:
- DeploymentService
- Cause:
- The request parameter upload file name was null.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290013
- No user name or password provided for the request.
- Category:
- DeploymentService
- Cause:
- The user name or password in the request were null.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290014
- Invalid user name or password.
- Category:
- DeploymentService
- Cause:
- The request contained an invalid user name or password.
- Action:
- Try again with a valid user name and password.
- BEA-290015
- Domain wide secret mismatch or clock skew between servers
- Category:
- DeploymentService
- Cause:
- Thee was an invalid signature between the Administration Server and Managed Servers.
- Action:
- This is an internal WebLogic Server error. Verify that the Administration Server and Managed Servers have the same SerializedSystemIni.dat file. Verify that clock skew has not occurred between the servers in the domain.
- BEA-290016
- Access not allowed for server "{0}" on boot.
- Category:
- DeploymentService
- Cause:
- The user does not have boot permission for the specified server.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290020
- Exceptions encountered while invoking application lifecycle listeners
- Category:
- DeploymentService
- Cause:
- A registered lifecycle listener detected an error and generated an exception.
- Action:
- Refer to the exception message from the lifecycle listener and determine if the error can be corrected.
- BEA-290021
- {0} does not exist.
- Category:
- DeploymentService
- Cause:
- The file does not exist on the Administration Server.
- Action:
- This is an internal WebLogic Server error. No action is required.
- BEA-290022
- This request needs to be initiated through a start control.
- Category:
- DeploymentService
- Cause:
- This is an internal protocol error.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290024
- Deployment type {0} has already been registered with the DeploymentService.
- Category:
- DeploymentService
- Cause:
- More than one deployment handler was registered for this deployment type.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290025
- Cannot call "start()" when DeploymentRequest has already been started.
- Category:
- DeploymentService
- Cause:
- The start method was called more than once.
- Action:
- This is an internal WebLogic Server error. No action is required.
- BEA-290026
- Request "{0}" is in "{1}" state - request has already been cancelled.
- Category:
- DeploymentService
- Cause:
- More than one cancel request was received.
- Action:
- No action is required.
- BEA-290027
- Request "{0}" is in "{1}" state - it is too late to attempt cancelling it.
- Category:
- DeploymentService
- Cause:
- A cancel request was received while the request was being committed.
- Action:
- No action is required.
- BEA-290028
- Deployment "{0}" has been cancelled.
- Category:
- DeploymentService
- Cause:
- The request was already cancelled.
- Action:
- No action is required.
- BEA-290029
- Deployment "{0}" timed out on Administration Server.
- Category:
- DeploymentService
- Cause:
- The request has timed out.
- Action:
- No action is required.
- BEA-290030
- No data handler registered for type "{0}".
- Category:
- DeploymentService
- Cause:
- A handler was not registered for the specified type.
- Action:
- This is an internal WebLogic Server error. No action is required.
- BEA-290031
- No tasks associated with this deployment request that can be cancelled.
- Category:
- DeploymentService
- Cause:
- Tasks have already completed.
- Action:
- No action is required.
- BEA-290032
- Data Transfer Handler exists for handler type: "{0}".
- Category:
- DeploymentService
- Cause:
- The handler type is already registered
- Action:
- This is an internal WebLogic Server error. No action is required.
- BEA-290036
- Deployment for request id "{0}" is deferred since target "{1}" is disconnected.
- Category:
- DeploymentService
- Cause:
- Target server "{1}" is disconnected.
- Action:
- No action is required. When the server reconnects, the deployment will be performed.
- BEA-290039
- Unrecognized callback
- Category:
- DeploymentService
- Cause:
- The callback was not a supported type.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290040
- The cancel call cannot be completed at this point because the deployment request "{0}" has already been partially committed.
- Category:
- DeploymentService
- Cause:
- A cancel was requested on a committed deployment task.
- Action:
- Wait until the deployment task has completed and then perform the necessary actions to restore the application to the desired state.
- BEA-290041
- Commit failed message received for id: "{0}" that has no request. It may be completed or cancelled. Sending commit succeeded message anyway.
- Category:
- DeploymentService
- Cause:
- No corresponding request was found for the commit failure message.
- Action:
- Check for a 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-290042
- Received a commit message call without a corresponding request. It may have been completed or cancelled. Sending commit failed message.
- Category:
- DeploymentService
- Cause:
- No corresponding request was found for the commit message.
- Action:
- Check for a 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-290043
- Cancel failure encountered when attempting to cancel "{0}" due to optimistic concurrency violation.
- Category:
- DeploymentService
- Cause:
- A failure occurred during the cancel of the request.
- Action:
- Wait until the deployment task has completed and then perform the necessary actions to restore the application to the desired state.
- BEA-290044
- {0} delivery
- Category:
- DeploymentService
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-290045
- prepare
- Category:
- DeploymentService
- Cause:
- Not applicable.
- Action:
- No action is required.
- BEA-290048
- Request with id "{0}" timed out.
- Category:
- DeploymentService
- Cause:
- The request timed out.
- Action:
- Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-290049
- Deploy failed for id "{0}" since no targets are reachable.
- Category:
- DeploymentService
- Cause:
- No targets were reachable.
- Action:
- Ensure targeted servers are alive and available from the Administration Server.
- BEA-290050
- Failed to deliver commit message to the following targets "{0}".
- Category:
- DeploymentService
- Cause:
- An exception occurred while committing the deployment request.
- Action:
- Ensure that targeted servers are alive and available from the Administration Server. Check for a 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-290051
- The commit message for the deployment "{0}" could not be completed because the deployment timed out.
- Category:
- DeploymentService
- Cause:
- The deployment timed out.
- Action:
- Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-290052
- {0} timeout
- Category:
- DeploymentService
- Cause:
- Not applicable.
- Action:
- No action is required.
- BEA-290053
- Request with id "{0}" timed out on the Administration Server.
- Category:
- DeploymentService
- Cause:
- The request timed out on the Administration Server.
- Action:
- Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-290054
- Deployment request "{0}" was explicitely cancelled.
- Category:
- DeploymentService
- Cause:
- Not applicable.
- Action:
- No action is required.
- BEA-290055
- Deployment request "{0}" timed out on the Administration Server during "{1}".
- Category:
- DeploymentService
- Cause:
- The deployment request timed out.
- Action:
- Try increasing the deployment timeout value. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-290056
- indeterminate
- Category:
- DeploymentService
- Cause:
- Not applicable
- Action:
- No action is required.
- BEA-290057
- Invalid DeploymentRequest: the object returned by the DeploymentService has been modified in an incompatible way.
- Category:
- DeploymentService
- Cause:
- The deployment request is not of the expected type.
- Action:
- Check for a 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-290058
- There is no request corresponding to request ID "{0}" currently being processed. The request will be cancelled if it is received in the future.
- Category:
- DeploymentService
- Cause:
- The specified request ID is not active.
- Action:
- Check that your task ID is the task that you would like to cancel.
- BEA-290059
- Operation "{0}" is not one of the supported types when creating a Change Descriptor.
- Category:
- DeploymentService
- Cause:
- An invalid change descriptor type was specified.
- Action:
- This is an internal WebLogic Server error. If the problem persists, contact My Oracle Support.
- BEA-290060
- Duplicate registration for "{0}".
- Category:
- DeploymentService
- Cause:
- Two different deployment instances were registered for the same type.
- Action:
- This is an internal WebLogic Server error. If the problem persists, contact My Oracle Support.
- BEA-290061
- UnrecognizedTypes: "{0}", "{1}"
- Category:
- DeploymentService
- Cause:
- A deployment type is invalid.
- Action:
- This is an internal WebLogic Server error. If the problem persists, contact My Oracle Support.
- BEA-290062
- The server configuration is out of date with the domain configuration and an attempt to synchronize with the admin server failed in {0} phase. This server needs to be restarted to enable it to synchronize with the domain configuration.
- Category:
- DeploymentService
- Cause:
- The server configuration is out of date with the domain configuration and an attempt to synchronize with the admin server failed in {0} phase. This server needs to be restarted to enable it to synchronize with the domain configuration.
- Action:
- Restart the server and if that does not resolve the problem, contact My Oracle Support and provide the stack trace for further analysis.
- BEA-290063
- Commit for request "{0}" will not proceed further since its requires restart flag is set.
- Category:
- DeploymentService
- Cause:
- The changes in the deployment request require a restart.
- Action:
- Restart either the server or the system resource that is part of the request.
- BEA-290064
- Deployment service servlet encountered an exception while handling the deployment service message for request id "{0}" from server "{1}". Exception is: "{2}".
- Category:
- DeploymentService
- Cause:
- Error occurred while handling the deployment service message request.
- Action:
- This is an internal WebLogic Server error. Refer to the underlying error message and determine if the error can be corrected. Verify that there are no network connection issues between the administration and managed servers.
- BEA-290065
- Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "{0}" from server "{1}". Exception is: "{2}".
- Category:
- DeploymentService
- Cause:
- Error occurred while handling the deployment datatransfer request.
- Action:
- This is an internal WebLogic Server error. Refer to the underlying error message and determine if the error can be corrected. Verify that there are no network connection issues between the administration and managed servers.
- BEA-290066
- Error occurred while downloading files from Administration Server for deployment request "{0}". Underlying error is: "{1}"
- Category:
- DeploymentService
- Cause:
- The connection used for the file download received an error.
- Action:
- Refer to the underlying error message and determine if the error can be corrected. Verify that there are no network connection issues between the administration and managed servers.
- BEA-290067
- Deployment request ''{0}'' was cancelled because servers: ''{1}'' were unreachable and the domain has cluster-constraints-enabled is set to true. To deploy to this cluster, either start the unreachable servers or remove the unreachable servers from the cluster, then reattempt the deployment. If this behaviour is not intended, set cluster-constraints-enabled on the domain to false and restart the Administration Server. This allows you to deploy the application only to those servers that can be reached.
- Category:
- DeploymentService
- Cause:
- Not all the servers in the cluster are running and cluster-constraints-enabled is set to true.
- Action:
- Start all the servers in the cluster and try deployment again, or if this behaviour is not intended, set cluster-constraints-enabled on the domain to false and restart the Administration Server.
- BEA-290068
- A deployment service request has been received by this Managed Server that was intended for the Administration Server. The source of the request is "{0}".
- Category:
- DeploymentService
- Cause:
- The source Managed Server was started with a URL for the Administration Server that incorrectly identified this server.
- Action:
- Start the source Managed Server with the correct URL for the Administration Server.
- BEA-290069
- Commit failed message received for id: "{0}", but exception details cannot be transported. Please look at target server log file for more details.
- Category:
- DeploymentService
- Cause:
- The send of the commit message failed.
- Action:
- Check the exception details in the server log and determine if the failure can be corrected.
- BEA-290070
- Deployment service servlet encountered an exception while parsing the multipart/form-data request:"{0}". Exception is: "{1}".
- Category:
- DeploymentService
- Cause:
- The request is not an RFC 1867-compliant multipart/form-data request.
- Action:
- This is an internal WebLogic Server error. No action is required.
- BEA-290071
- Deployment service servlet failed when parsing the request or uploading the file.
- Category:
- DeploymentService
- Cause:
- The request is not an RFC 1867-compliant multipart/form-data stream.
- Action:
- The request should comply with RFC 1867. Verify that the Administration Server and Managed Servers are running versions that interoperate.
- BEA-290073
- Deployment service servlet received a request of type "{0}" with an invalid application name: "{1}".
- Category:
- DeploymentService
- Cause:
- An invalid deployment service servlet request was made.
- Action:
- Correct the application name and retry the request.
- BEA-290074
- Deployment service servlet received file download request for file "{0}". The file may exist, but automatic download of this file is not allowed; it must be manually transferred.
- Category:
- DeploymentService
- Cause:
- The file to download is a security file or is outside of the domain root directory.
- Action:
- Enter a valid file name for download.
- BEA-290075
- Target Server encountered an error in sending "{0}" of id "{1}" with "{2}".
- Category:
- DeploymentService
- Cause:
- The deployment message cannot be delivered to the Administration Server.
- Action:
- This is an internal WebLogic Server error. No action is required.
- BEA-290076
- Total size of transferred files is "{0}" GB and it exceeded configured limit "{1}" GB.
- Category:
- DeploymentService
- Cause:
- Total size of transferred file exceeded the configured limit.
- Action:
- Delete unwanted files from the directory and try again
- BEA-290077
- Transfered files and its file size is like as follows.
- Category:
- DeploymentService
- Cause:
- Total size of transferred file exceeded the configured limit.
- Action:
- Delete unwanted files from the directory and try again
- BEA-290078
- "{0}" : "{1}" GB
- Category:
- DeploymentService
- Cause:
- Total size of transferred file exceeded the configured limit.
- Action:
- Delete unwanted files from the directory and try again
- BEA-290079
- Deployment service servlet received a request of type "{0}" with an invalid upload path: "{1}".
- Category:
- DeploymentService
- Cause:
- An invalid deployment service servlet request was made.
- Action:
- Correct the upload path and retry the request.
- BEA-290080
- Deployment service servlet received a request of type "{0}" with no upload path.
- Category:
- DeploymentService
- Cause:
- An invalid deployment service servlet request was made.
- Action:
- This is an internal WebLogic Server error. No action is required. If the problem persists, contact My Oracle Support.
- BEA-290081
- Deployment service servlet received a request of type "{0}" with an invalid partition name: "{1}".
- Category:
- DeploymentService
- Cause:
- An invalid deployment service servlet request was made.
- Action:
- Correct the partition name and retry the request.
- BEA-290082
- Deployment service servlet received a request of type "{0}" unable to overwrite existing file: "{1}".
- Category:
- DeploymentService
- Cause:
- An invalid deployment service servlet request was made.
- Action:
- Remove existing user file and retry the request.
- BEA-290083
- Deployment service servlet received a request of type "{0}" file already exists: "{1}".
- Category:
- DeploymentService
- Cause:
- An invalid deployment service servlet request was made.
- Action:
- Remove existing user file or set overwrite flag and retry the request.
- BEA-290084
- Can not create upload directory: {0}.
- Category:
- DeploymentService
- Cause:
- The upload directory cannot be created.
- Action:
- Check the file permission on the parent directory.
- BEA-290085
- The directory for upload is not a directory: {0}.
- Category:
- DeploymentService
- Cause:
- The directory for upload is not a directory.
- Action:
- Check the file path and permission on the directory.
- BEA-290086
- Upload directory is not writable: {0}.
- Category:
- DeploymentService
- Cause:
- Can not write to the upload directory.
- Action:
- Check the file permission on the directory.
- BEA-290087
- Data transfer between administration and managed server failed for resource "{0}".
- Category:
- DeploymentService
- Cause:
- The named resource was unavailable, the read failed, or communication between administration and managed server failed.
- Action:
- Inspect the underlying file-system error, correct the problem, and retry.
- BEA-300037
- The NodeManager at host {0} and port {1} seems to be down. Start the NodeManager and rerun the command.
- Category:
- NodeManager
- Cause:
- The NodeManager is not running.
- Action:
- Start the NodeManager and rerun the command.
- BEA-300040
- An I/O error occurred while writing a NodeManager status change message.
- Category:
- NodeManager
- Cause:
- Possible causes are that the standard output stream has been closed or the NodeManager stopped monitoring.
- Action:
- If this server requires monitoring, restart the server.
- BEA-300043
- NodeManager native library not found - server process ID not saved.
- Category:
- NodeManager
- Cause:
- The NodeManager native library is not in the library search path or is unavailable on this platform.
- Action:
- Ensure that the NodeManager native library is available and in the library search path.
- BEA-300044
- An I/O error occurred while writing the server PID file: "{0}".
- Category:
- NodeManager
- Cause:
- The server PID file might be write-protected.
- Action:
- Ensure that the server PID file is not write-protected. In addition, check to see if the parent directory exists (should have been created by the NodeManager server before starting the server).
- BEA-300048
- Unable to start the server {0} : {1}
- Category:
- NodeManager
- Cause:
- The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration.
- Action:
- Ensure that you can access the remote NodeManager. This may require setting up SSH permissions for the SSH-based NodeManager. In addition, ensure that the default PATH settings for the remote NodeManager are correct. See the NodeManager documentation for more information.
- BEA-300049
- An I/O error occurred while writing the server URL file: "{0}".
- Category:
- NodeManager
- Cause:
- The server URL file might be write-protected.
- Action:
- Ensure that the server URL file is not write-protected. In addition, check to see if the parent directory exists (it should have been created by the NodeManager server before starting the server).
- BEA-300051
- An I/O error occurred while updating the startup properties for "{0}". This probably occurred because the NodeManager is unreachable. This could mean that the servers boot.properties or startup.properties file is out of date, and the next time NodeManager attempts to automatically restart the server on a failure, it will use out of date properties. To resolve this issue, either ensure that the NodeManager is able to receive the updates and reset the properties, or restart the server.
- Category:
- NodeManager
- Cause:
- An I/O error occurred while updating the startup properties for "{0}". This probably occured because the NodeManager is unreachable.
- Action:
- Either ensure that the NodeManager is able to receive the updates and reset the properties, or restart the server.
- BEA-300053
- A migratable server was not found to contain any specified IP address in the ServerMBean or custom network channels for migration. No IPs will be passed to NodeManager and no IPs will be migrated. The server may not start without an available address, or may not be accessible throughout migration without a consistent IP. Configure an appropriate floating listen address for the server.
- Category:
- NodeManager
- Cause:
- A migratable server was not found to contain any specified IP address in the ServerMBean or custom network channels for migration. No IPs will be passed to NodeManager and no IPs will be migrated. The server may not start without an available address, or may not be accessible throughout migration without a consistent IP.
- Action:
- Configure an appropriate floating listen address for the server.
- BEA-300054
- Could not find appropriate IP for ListenAddress "{0}" specified for a migratable server. Reason: "{1}". The NodeManager may not be able to bind the specified address and the server may not start without the available address. Configure an appropriate floating listen address for the server.
- Category:
- NodeManager
- Cause:
- No appropriate IP was found for a migratable server's listen address. The NodeManager may not be able to bind the address specified and the server may not start without the available address. Configure an appropriate floating listen address for the server.
- Action:
- Configure an appropriate floating listen address for the server.
- BEA-300055
- The NodeManagerMonitor add requires a non-null MachineMBean to monitor the active status of a NodeManager.
- Category:
- NodeManager
- Cause:
- See the message body.
- Action:
- Provide a non-null MachineMBean.
- BEA-300056
- Could not execute the native output file rotation logic due to "{0}".
- Category:
- NodeManager
- Cause:
- Could not execute the native output file rotation logic due to "{0}".
- Action:
- Could not execute the native output file rotation logic due to "{0}".
- BEA-300057
- Starting server {0} on machine {2} at {1}
- Category:
- NodeManager
- Cause:
- Starting server {0} on machine {2} at {1}
- Action:
- No action is required.
- BEA-300058
- Starting server {0} on machine at {1}
- Category:
- NodeManager
- Cause:
- Starting server {0} on machine at {1}
- Action:
- No action is required.
- BEA-310001
- Subsystem {0} in partition {1} has failed. Setting server state to FAILED.
- Category:
- Health
- Cause:
- One of the critical subsystems of the server has failed.
- Action:
- Check the server log to determine the cause of the subsystem failure.
- BEA-310002
- {0}% of the total memory in the server is free.
- Category:
- Health
- Cause:
- The percentage of free memory in the server has changed.
- Action:
- No action is required.
- BEA-310003
- Free memory in the server is {0} bytes. There is danger of receiving an OutOfMemoryError.
- Category:
- Health
- Cause:
- Free memory in the server is very low.
- Action:
- Analyze heap memory usage for possible memory leak. If no memory leak is found, consider restarting server with a larger maximum heap size.
- BEA-310006
- Critical subsystem {0} in partition {1} has failed. Setting server state to FAILED. Reason: {2}
- Category:
- Health
- Cause:
- One of the critical subsystems of the server has failed.
- Action:
- Check the server log to determine the cause of the subsystem failure.
- BEA-310007
- Subsystem {0} in partition {1} has failed because of: {2} However, notification did not occur because {0} was not registered with the HealthMonitorService.
- Category:
- Health
- Cause:
- One of the subsystems of the server has failed.
- Action:
- Check the server log to determine the cause of the subsystem failure. MigratableTargets may need to be manually moved, since the automatic migration subsystem requires HealthMonitor notification to work properly.
- BEA-310008
- Non-critical subsystem {0} in partition {1} has failed. Reason: {2}
- Category:
- Health
- Cause:
- One of the non-critical subsystems of the server has failed.
- Action:
- Check the server log to determine the cause of the subsystem failure.
- BEA-310009
- Restart of persistent store {0} and its upper services in partition {1} has failed after {2} restart attempts in {3} seconds. Reason: {4}
- Category:
- Health
- Cause:
- Restart of persistent store and its upper services has failed.
- Action:
- Check the server log to determine the cause of the Restart failure.
- BEA-310010
- Persistent store "{0}" in partition "{1}" is reporting a failure. It will attempt up to {2} restarts with {3} seconds between each attempt.
- Category:
- Health
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-310011
- Persistent store "{0}" in partition "{1}" and the services that depend on this store have been restarted successfully.
- Category:
- Health
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-320000
- The Diagnostics subsystem is initializing on Server {0}.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320001
- The ServerDebug service initialized successfully.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320002
- The Diagnostics subsystem is stopping on Server {0}.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320004
- The following unexpected exception was thrown: {0}
- Category:
- Diagnostics
- Cause:
- An exception was thrown unexpectedly.
- Action:
- Take appropriate action based on the unexpected exception message.
- BEA-320005
- Diagnostic monitor of unknown type {1} used in instrumentation scope {0}.
- Category:
- Diagnostics
- Cause:
- The Diagnostic Monitor library is probably out of date.
- Action:
- Update the Diagnostic Monitor library.
- BEA-320008
- Error occurred while collecting diagnostic metrics:
- Category:
- Diagnostics
- Cause:
- An error occurred while constructing a Harvester instance.
- Action:
- Ensure that all harvester configuration parameters are set appropriately.
- BEA-320009
- The elapsed time of the last snapshot of diagnostic metrics exceeded the configured sample period by the following number of milliseconds: {0}.
- Category:
- Diagnostics
- Cause:
- Harvested MBeans and/or DataSources are taking too long to return sampled attribute values.
- Action:
- Increase the sample period window.
- BEA-320010
- An error occurred while generating a diagnostic image: {0}
- Category:
- Diagnostics
- Cause:
- Permissions were abruptly changed on the zip/directory. The file system does not have sufficient disk space to continue writing the image.
- Action:
- Allocate sufficient disk space and provide the proper permissions to create the image zip file.
- BEA-320011
- The following diagnostic image destination directory could not be created: {0}
- Category:
- Diagnostics
- Cause:
- You have not given write permissions to the absolute path for the default directory, or you have not allocated sufficient disk space for the directory to be created.
- Action:
- You must give write permissions to the absolute path for the default directory if no configured destination directory is specified. You must also allocate sufficient disk space for the default directory to be created if no destination directory is specified.
- BEA-320012
- The following destination directory for diagnostic images could not be read or written to: {0} or there is not enough free space available to create the diagnostic image.
- Category:
- Diagnostics
- Cause:
- The directory was not created or directory read and write permissions were not given to the directory.
- Action:
- Create the destination directory with the appropriate read and write permissions.
- BEA-320013
- Diagnostic image capture was attempted during a lockout period.
- Category:
- Diagnostics
- Cause:
- The ImageManager has locked image captures for a specified number of minutes.
- Action:
- The lockout period must expire before a new image capture request is accepted.
- BEA-320014
- Lockout of {0} above allowed maximum lockout minutes for image captures.
- Category:
- Diagnostics
- Cause:
- The specified a number of minutes exceeds the maximum allowed lockout minutes.
- Action:
- Specify a lockout period between the minimum and maximum.
- BEA-320015
- Lockout of {0} below allowed minimum lockout minutes for image captures.
- Category:
- Diagnostics
- Cause:
- The specified a number of minutes falls below the minimum allowed lockout minutes.
- Action:
- Specify a lockout period between the minimum and maximum.
- BEA-320016
- Creating diagnostic image in {0} with a lockout minute period of {1}.
- Category:
- Diagnostics
- Cause:
- A FirstFailure has occurred, a diagnostic image notification handler was configured, or a capture image method was explicitly invoked on ImageManager.
- Action:
- No action is required. The diagnostic image capture request will be scheduled and executed.
- BEA-320018
- Instrumentation engine configuration {0} could not be parsed due to: {1}
- Category:
- Diagnostics
- Cause:
- The instrumentation engine configuration is possibly malformed.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320019
- Code generator class {1} for standard monitor {0} could not be found.
- Category:
- Diagnostics
- Cause:
- The standard monitor code generator was not on the class path.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320020
- Code generator {1} for standard monitor {0} could not be instantiated.
- Category:
- Diagnostics
- Cause:
- The standard monitor code generator is missing the default constructor.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320021
- The code generator {1} could not be accessed for standard monitor {0}.
- Category:
- Diagnostics
- Cause:
- The standard monitor code generator implementation has problems.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320022
- An error was encountered while creating SerialVersionUID for class {0}.
- Category:
- Diagnostics
- Cause:
- SerialVersionUID for a class could not be created.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320023
- File {0} does not contain a valid Java class
- Category:
- Diagnostics
- Cause:
- The file does not contain a valid Java class.
- Action:
- Make sure that the file being instrumented is a valid Java class file.
- BEA-320024
- Class in file {0} could not be instrumented.
- Category:
- Diagnostics
- Cause:
- This can happen when the input file or output file cannot be read from or written to.
- Action:
- Check the file permissions and disk space.
- BEA-320025
- Input file {0} for instrumentation engine cannot be found.
- Category:
- Diagnostics
- Cause:
- The input class file does not exist.
- Action:
- Provide the correct path to the input class file.
- BEA-320026
- Monitor {0} could not be found in instrumentation engine configuration.
- Category:
- Diagnostics
- Cause:
- The monitor name may be misspelled.
- Action:
- Specify the correct monitor name on the command line.
- BEA-320030
- Delegating monitor {1} in scope {0} allows using action of type {2}, which does not exist.
- Category:
- Diagnostics
- Cause:
- A delegating monitor was not properly configured in the instrumentation engine configuration.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320031
- An attempt to add a monitor of type {1} to instrumentation scope {0} failed because the monitor already exists in the scope.
- Category:
- Diagnostics
- Cause:
- Instrumentation configuration was incorrect.
- Action:
- Remove multiple monitor entries with same types from the instrumentation scope configuration.
- BEA-320032
- Attempt to add duplicate action {2} to monitor {1} in scope {0} failed.
- Category:
- Diagnostics
- Cause:
- Instrumentation scope configuration is incorrect. It has duplicate actions attached to the same monitor.
- Action:
- Remove duplicate actions attached to the same monitor.
- BEA-320033
- Attempt to attach incompatible action of type {2} to a delegating monitor of type {1} in scope {0}.
- Category:
- Diagnostics
- Cause:
- Instrumentation configuration is incorect.
- Action:
- Make sure that only compatible actions are used with delegating monitors.
- BEA-320034
- Instrumentation engine configuration {0} could not be parsed. {1}
- Category:
- Diagnostics
- Cause:
- The instrumentation configuration is malformed.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320035
- Instrumentation configuration {0} could not be read.
- Category:
- Diagnostics
- Cause:
- The instrumentation configuration is missing or invalid.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320036
- Instrumented method {1}{2} in class {0} exceeds size limit. Original method is preserved.
- Category:
- Diagnostics
- Cause:
- The original method is too large to begin with. The class to which it belongs is probably generated by a generator program.
- Action:
- If possible, split the method into multiple methods. Exclude the class from instrumentation to speed up the instrumentation process.
- BEA-320037
- Class bytes for {0} do not conform to class format.
- Category:
- Diagnostics
- Cause:
- The class file is corrupt.
- Action:
- Make sure that the class file is not corrupt.
- BEA-320038
- Could not instrument class {0}
- Category:
- Diagnostics
- Cause:
- This is a general instrumentation failure.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320039
- Invalid class inclusion pattern(s) for instrumentation engine/scope {0}. Disabling instrumentation in scope {0}.
- Category:
- Diagnostics
- Cause:
- Inclusion patterns are malformed.
- Action:
- Specify inclusion patterns in the correct format.
- BEA-320040
- Invalid class exclusion pattern(s) for instrumentation engine/scope {0}. Disabling instrumentation in scope {0}.
- Category:
- Diagnostics
- Cause:
- One or more exclusion patterns are malformed.
- Action:
- Specify exclusion patterns in the correct format.
- BEA-320041
- Invalid lockout minutes {0} specified in image notification. Image capture was not performed.
- Category:
- Diagnostics
- Cause:
- The value is invalid.
- Action:
- Recreate the notification with a valid lockout minutes value.
- BEA-320042
- Invalid diagnostic image location {0} specified in notification, exception message is {1}. Image capture was not performed.
- Category:
- Diagnostics
- Cause:
- The value is not a valid directory or file name.
- Action:
- Recreate the notification with a valid image location. Take appropriate action based on the exception message.
- BEA-320043
- Image notification was not performed because the image capture was attempted before the lockout time expired. The exception message is {0}
- Category:
- Diagnostics
- Cause:
- An image capture was attempted before the lockout period expired.
- Action:
- Recreate the image notification with a smaller value for lockout minutes. Optionally, use the watch alarm feature to ensure that the notification does not occur again before the lockout period has expired.
- BEA-320044
- Error occurred while performing a watch notification:
- Category:
- Diagnostics
- Cause:
- An error occurred while performing the operations required for the notification.
- Action:
- Take appropriate action based on the unexpected exception message.
- BEA-320047
- Mail notification has not been sent due to an error that occurred while creating or sending a mail message:
- Category:
- Diagnostics
- Cause:
- An error occurred while performing the mail operations required for the notification.
- Action:
- Verify the MailSession properties and email destination. Take appropriate action based on the Messaging exception message.
- BEA-320048
- JMS notification message has not been sent due to an error that occurred while creating a JMS map message:
- Category:
- Diagnostics
- Cause:
- An error occurred while performing the JMS operation.
- Action:
- Verify the JMS queue and connection factory configuration settings in the JMS notification. Take appropriate action based on the JMS exception message.
- BEA-320049
- An exception occurred sending JMS notification message. Reinitializing JMS objects and retrying.
- Category:
- Diagnostics
- Cause:
- An error occurred while sending the JMS message.
- Action:
- Look for additional error messages in the log from the reinitialization or resend of the message.
- BEA-320052
- An error occurred while initializing a SMTP notification:
- Category:
- Diagnostics
- Cause:
- The mail session is incorrectly configured or not available.
- Action:
- Ensure that the mail session JNDI name is correct. Ensure that the mail session MBean properties are valid. Take appropriate action based on the exception message.
- BEA-320053
- The SNMP Agent is not configured. The trap for the SNMP Watch notification cannot be sent.
- Category:
- Diagnostics
- Cause:
- The SNMP Agent is not enabled.
- Action:
- Enable the SNMP Agent using the console.
- BEA-320054
- An error occurred while sending an SNMP notification:
- Category:
- Diagnostics
- Cause:
- An exception occurred in the SNMP Agent when sending the SNMP trap to the configured trap destinations.
- Action:
- Ensure that the trap destinations are configured correctly. Take appropriate action based on the exception message.
- BEA-320055
- Could not read or create index on log file {0}.
- Category:
- Diagnostics
- Cause:
- The drive may be full or the directory is not writable.
- Action:
- Check whether the drive is full or the directory is not writable.
- BEA-320056
- Log index file {0} has an invalid magic number.
- Category:
- Diagnostics
- Cause:
- The index file is corrupt or invalid.
- Action:
- Delete the corrupt index file.
- BEA-320057
- Log index file {0} contents are inconsistent with its header.
- Category:
- Diagnostics
- Cause:
- The index file is corrupt or truncated.
- Action:
- Delete the index file.
- BEA-320058
- Could not parse log record: {0}
- Category:
- Diagnostics
- Cause:
- The log record is malformed.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320063
- An attempt to add watch {0} failed because the watch has already been defined.
- Category:
- Diagnostics
- Cause:
- Two different watch definitions have the same name.
- Action:
- Remove one of the watch entries that has the same name.
- BEA-320064
- Watch {0} could not be created due to the following unexpected exception: {1}
- Category:
- Diagnostics
- Cause:
- An exception occurred unexpectedly.
- Action:
- Take appropriate action based on the unexpected exception message.
- BEA-320066
- An attempt to add notification {0} failed because the notification has already been defined.
- Category:
- Diagnostics
- Cause:
- Two different notification definitions have the same name.
- Action:
- Remove one of the notification entries with the same name.
- BEA-320068
- Watch "{0}" in module "{1}" with severity "{2}" on server "{3}" has triggered at {4}. Notification details: {5}
- Category:
- Diagnostics
- Cause:
- A configured watch has evaluated to true and has triggered.
- Action:
- No action is required.
- BEA-320069
- Watch {0} contains an invalid notification {1} that is not defined.
- Category:
- Diagnostics
- Cause:
- The notification does not exist.
- Action:
- Define the notification or remove the notification from the watch.
- BEA-320070
- Error occurred while performing notification {1} for watch {0}. Notification may not have completed.
- Category:
- Diagnostics
- Cause:
- An exception occurred while performing the notification.
- Action:
- Validate the definition for the specified watch and notification. Take appropriate action based on the error message.
- BEA-320071
- Error occurred while creating watch notification {0}. Notifications may not have completed for this watch.
- Category:
- Diagnostics
- Cause:
- An exception occurred while creating the watch notification.
- Action:
- Validate the definition for the specified watch and notification. Take appropriate action based on the error message.
- BEA-320073
- Error while locating a record for timestamp {0} in the archive
- Category:
- Diagnostics
- Cause:
- There is a misconfigured or missing data archive for harvested data.
- Action:
- Check that the harvested data archive exists.
- BEA-320074
- Error while executing query.
- Category:
- Diagnostics
- Cause:
- A runtime error occurred while executing a query.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320075
- Error while reading a record from the archive
- Category:
- Diagnostics
- Cause:
- The harvested data archive may be corrupt.
- Action:
- Reconfigure the harvested data archive.
- BEA-320076
- Could not initialize index information for harvester data archive.
- Category:
- Diagnostics
- Cause:
- The harvested data archive may be corrupt.
- Action:
- Reconfigure the harvested data archive.
- BEA-320077
- Initialized the Diagnostic Accessor Service.
- Category:
- Diagnostics
- Cause:
- This is a normal operation.
- Action:
- No action is needed.
- BEA-320078
- Could not initialize the Diagnostic Accessor Service Runtime during server startup.
- Category:
- Diagnostics
- Cause:
- The exception message includes the details about the cause of this problem.
- Action:
- Take corrective action based on the exception stack trace.
- BEA-320079
- Watch "{0}" rule expression evaluation failed with an exception. No notifications will be performed for this watch. The exception is:
- Category:
- Diagnostics
- Cause:
- An exception occurred during rule evaluation.
- Action:
- Verify that the rule expression is valid. Take appropriate action based on the exception message.
- BEA-320080
- The log type {0} is unknown. Unable to lookup the DiagnosticDataAccessRuntimeMBean instance.
- Category:
- Diagnostics
- Cause:
- This message indicates that the logical name that was specified to look up the DiagnosticDataAccessRuntimeMBean is not correct.
- Action:
- Verify that the log type is valid. Take appropriate action based on the exception message.
- BEA-320082
- Configuration for diagnostic monitor {0} in instrumentation scope {1} has errors. The exception is:
- Category:
- Diagnostics
- Cause:
- An exception occurred while reading the configuration of a diagnostic monitor in a scope.
- Action:
- Verify that the configuration for the diagnostic monitor is valid.
- BEA-320083
- Custom diagnostic monitor {0} in instrumentation scope {1} has missing or invalid location attribute.
- Category:
- Diagnostics
- Cause:
- There is a missing or invalid value of the "location" attribute of a custom diagnostic monitor.
- Action:
- Verify that the "location" attribute of the custom monitor has a correct value.
- BEA-320084
- The user {0} does not have authorization to view the logs.
- Category:
- Diagnostics
- Cause:
- A user with insufficient authorization attempted to access the server logs.
- Action:
- Ensure that the right users are granted access to view the logs.
- BEA-320085
- The diagnostic data is accessible only through https in Production mode.
- Category:
- Diagnostics
- Cause:
- An attempt to access the diagnostic data was made over a non-secure protocol in Production mode.
- Action:
- Ensure that the SSL is enabled in Production mode and that the servlet is accessed only over a secure protocol.
- BEA-320086
- The monitor type {1} in scope {0} contains unacceptable characters.
- Category:
- Diagnostics
- Cause:
- The monitor type contains unacceptable characters. It must start with an alphabetic character, followed by alphanumeric or underscore characters.
- Action:
- Fix the assigned monitor type, which must start with an alphabetic character, optionally followed by alphanumeric or underscore characters.
- BEA-320087
- The cursor {0} has timed out and is being removed from the registry of open cursors.
- Category:
- Diagnostics
- Cause:
- This message is emitted when a cursor has not been invoked and is being removed to free up the associated resources.
- Action:
- Ensure that fetch is not called anymore on the closed cursor.
- BEA-320088
- The cursor with name {0} does not exist.
- Category:
- Diagnostics
- Cause:
- The cursor could have timed out or been closed by the user explicitly. Otherwise, or an invalid name has been provided.
- Action:
- Invoke the fetch method with the name of a valid cursor.
- BEA-320091
- Attempt to use unknown action {1} in action group {0}
- Category:
- Diagnostics
- Cause:
- This is due to an incorrect or incomplete instrumentation engine configuration.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320092
- Monitor {0} used empty or non-existent action group {1}
- Category:
- Diagnostics
- Cause:
- This is due to an incorrect or incomplete instrumentation engine configuration.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320093
- Encountered problem while reading attributes of monitor {0}. Attributes: {1}
- Category:
- Diagnostics
- Cause:
- Possibly invalid attribute names were specified with the diagnostic monitor.
- Action:
- Specify correct attributes for the diagnostic monitor.
- BEA-320094
- Could not initialize server instrumentation scope.
- Category:
- Diagnostics
- Cause:
- Internal error
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320096
- Cannot create custom monitor {0} in server instrumentation scope.
- Category:
- Diagnostics
- Cause:
- Custom monitors can not be defined in the server instrumentation scope.
- Action:
- Remove the custom monitor definition from the server instrumentation scope.
- BEA-320097
- Monitor {0} can be created only in an application instrumentation scope. It cannot be created in server instrumentation scope.
- Category:
- Diagnostics
- Cause:
- An attempt was made to create a monitor in the server scope, but it can only be created in the application scope.
- Action:
- Remove the monitor definition from the server instrumentation scope.
- BEA-320098
- Monitor {0} can be created only in server instrumentation scope. It can not be created in application instrumentation scope {1}.
- Category:
- Diagnostics
- Cause:
- An attempt was made to create a monitor in the application scope, but it can only be created in the server scope.
- Action:
- Remove the monitor definition from the application instrumentation scope.
- BEA-320100
- Configuration for JDBC-based diagnostic archives is invalid or incomplete. Using file based diagnostic archive.
- Category:
- Diagnostics
- Cause:
- The configuration for JDBC-based diagnostic archives is invalid or incomplete.
- Action:
- Fix the configuration for JDBC-based diagnostic archives.
- BEA-320101
- Attempt to target more than one WLDFSystemResource to server {0}.
- Category:
- Diagnostics
- Cause:
- This error indicates that an invalid targeting was specified for a WLDFSystemResource.
- Action:
- Ensure that only one WLDFSystemResource is targeted to a server.
- BEA-320102
- An error occcurred when trying to access the diagnostic data while executing the query expression {0}.
- Category:
- Diagnostics
- Cause:
- The query was not specified properly.
- Action:
- Ensure that the query is valid.
- BEA-320103
- An error occurred while creating the DiagnosticDataRuntimeMBean instance with the given logical name {0}.
- Category:
- Diagnostics
- Cause:
- The logical name is not a valid parameter or an error occurred while reading the diagnostic data.
- Action:
- Ensure that the logical name is valid and take corrective action based on the reported error.
- BEA-320104
- An error occurrred when invoking the log4j operation while activating/deactivating log watch rules.
- Category:
- Diagnostics
- Cause:
- The log4j libraries may not be in the CLASSPATH.
- Action:
- Ensure that the log4j libraries are available when using Log watch rules with Log4j enabled.
- BEA-320105
- The watch rule expression {0} is not valid.
- Category:
- Diagnostics
- Cause:
- The watch rule expression does not conform to the correct syntax.
- Action:
- Specify a valid watch rule expression.
- BEA-320106
- The watch notification configuration already contains a notification with the given name {0}.
- Category:
- Diagnostics
- Cause:
- The name for the WLDFNotification you are adding is not unique.
- Action:
- Specify a unique name for the notification.
- BEA-320111
- The elapsed time since the last Harvester cycle ({0} milliseconds) is unacceptably short. Skipping this cycle in order to smooth out the responses.
- Category:
- Diagnostics
- Cause:
- The previous Harvesting process consumed a large percentage of the sample period. This can happen for 3 reasons: 1) you requested that a very large amount of data be harvested, 2) the system is consistently slow for some reason, 3) an intermittent service caused the process to slow down temporarily (for example, for garbage collection).
- Action:
- No action is required. The Harvester will compensate by skipping cycles that occur too soon. If this happens consistently, either because you are harvesting a large amount of data, or the Harvester is running on a slow system, you can either increase the samplePeriod or increase system resources.
- BEA-320113
- The type {0} is no longer being harvested.
- Category:
- Diagnostics
- Cause:
- This is caused by an earlier problem. Sufficient log messages should have been issued at the point of failure to allow the problem to be debugged. Note that the type will remain deleted until the Harvester configuration is reloaded. At that time, if the problem is not yet resolved, this message may be issued again.
- Action:
- No action is required. Typically, this type of error will cause some of the requested data to not be harvested. It is advisable to fix the issue.
- BEA-320114
- Initializing the Diagnostics Harvester.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320115
- The Harvester is configured to be disabled.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320116
- Harvester type {0} is configured to be disabled. No harvesting will occur for this type.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320117
- The Harvester is being disabled because there are no valid Harvestable types configured.
- Category:
- Diagnostics
- Cause:
- This may occur because you did not provide any type specifications, or, if type specifications were provided, none of the specified types were harvestable.
- Action:
- No action is required.
- BEA-320118
- The Harvester timer has been initiated for an interval of {0} milliseconds.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320119
- The Harvester is now in a {0} state.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320122
- Unable to harvest attribute {0} on item {1} due to errors. This attribute will no longer be harvested.
- Category:
- Diagnostics
- Cause:
- The actual problem occurred at a previous point in time. Sufficient messages should have been issued at the point of failure to facilitate debugging the problem.
- Action:
- No action is required. Typically, this type of error will cause some of the requested data to not be Harvested. It is advisable to fix the issue.
- BEA-320123
- Could not add MBean instance {0} to the harvested instance list for type {1}: {2}.
- Category:
- Diagnostics
- Cause:
- The actual problem occurred at a previous point in time. Sufficient messages should have been issued at the point of failure to facilitate debugging the problem.
- Action:
- No action is required. Typically, this type of error will cause some of the requested data to not be Harvested. It is advisable to fix the issue.
- BEA-320124
- The harvester has discovered a new instance of harvested type {1} named {0}.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320125
- Attention: {0}
- Category:
- Diagnostics
- Cause:
- This indicates a system error, not a user error. Further investigation is required to determine the cause.
- Action:
- In most cases, you should be able to turn on Harvester debug to obtain additional information.
- BEA-320126
- Reinitializing the Diagnostics Harvester.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320127
- An error occurred while generating Image Source {0} as part of the diagnostic image zip file:
- Category:
- Diagnostics
- Cause:
- An unexpected error occurred while the subsystem was collecting or persisting the diagnostic image source information.
- Action:
- Take appropriate action based on the unexpected exception message.
- BEA-320128
- The WLDFResourceBean is not found for the WLDFSystemResource {0}.
- Category:
- Diagnostics
- Cause:
- This error is caused by either a deleted or corrupt WLDF descriptor file.
- Action:
- Ensure that the descriptor file exists for the WLDFSytemResource and that it conforms to the expected schema.
- BEA-320129
- Instrumentation module {0} created.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320130
- Instrumentation module {0} is disabled.
- Category:
- Diagnostics
- Cause:
- This instrumentation module for server or application is disabled.
- Action:
- No action is required.
- BEA-320131
- Instrumentation module {0} is configured, but disabled because a WLDF system resource is not targeted to the server, or its instrumentation component is not enabled.
- Category:
- Diagnostics
- Cause:
- There is no WLDF system resource targeted to the server, or its instrumentation component is disabled.
- Action:
- Check if there is a WLDF system resource targeted to the server and its instrumentation component is enabled.
- BEA-320132
- Updating classes within scope {0} since its instrumentation configuration has changed.
- Category:
- Diagnostics
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320133
- Could not instantiate one of the known accessors during server startup.
- Category:
- Diagnostics
- Cause:
- The exception message includes the details about the cause of this problem.
- Action:
- Take corrective action based on the exception stack trace.
- BEA-320134
- An error occurred while creating a domain log handler: {0}.
- Category:
- Diagnostics
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320135
- JDBC-based {0} archive could not be created. Falling back on persistent store based archive.
- Category:
- Diagnostics
- Cause:
- This happens when the JDBC data source to be used with the archive is misconfigured or unavailable, or database tables are not available.
- Action:
- Ensure that the JDBC data source is correctly configured and available, and that database tables have been created prior to use.
- BEA-320136
- Class {0} could not be instrumented, due to reason: "{1}".
- Category:
- Diagnostics
- Cause:
- This can happen because the class may contain constructs that are unsafe to transform, for example, custom attributes.
- Action:
- Ensure that class does not have custom attributes or other such constructs.
- BEA-320137
- Invalid class inclusion pattern(s) for instrumentation monitor {1} in scope {0}. Disabling instrumentation in scope {0}.
- Category:
- Diagnostics
- Cause:
- There are malformed inclusion patterns in the instrumentation monitor.
- Action:
- Specify inclusion patterns in the instrumentation monitor using the correct format.
- BEA-320138
- Invalid class exclusion pattern(s) for instrumentation monitor {1} in scope {0}. Disabling instrumentation in scope {0}.
- Category:
- Diagnostics
- Cause:
- There are malformed exclusion patterns in the instrumentation monitor.
- Action:
- Specify exclusion patterns in the instrumentation monitor using the correct format.
- BEA-320139
- Archive {0} is not found during a data retirement operation.
- Category:
- Diagnostics
- Cause:
- Data retirement may be configured for a custom archive that does not yet exist.
- Action:
- Ensure that the custom archive is created, or disable or remove this retirement configuration.
- BEA-320140
- Scheduling data retirement tasks as per configuration.
- Category:
- Diagnostics
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-320141
- An error was encountered while performing age-based data retirement on archive {0}.
- Category:
- Diagnostics
- Cause:
- An error was encountered while performing age-based data retirement on the indicated archive.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320142
- An error was encountered while performing size-based data retirement on archive {0}.
- Category:
- Diagnostics
- Cause:
- An error was encountered while performing size-based data retirement on the indicated archive.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320143
- Scheduled {0} data retirement tasks as per configuration.
- Category:
- Diagnostics
- Cause:
- Finished processing the data retirement configuration.
- Action:
- No action is required.
- BEA-320144
- {0} operation started on archive {1}.
- Category:
- Diagnostics
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-320145
- {0} operation completed on archive {1}. Retired {2} records in {3} ms.
- Category:
- Diagnostics
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-320146
- Failed to register dye {0} at index {1}.
- Category:
- Diagnostics
- Cause:
- A dye with the same name or index already exists.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320147
- Instrumentation system is disabled because the instrumentation library is invalid.
- Category:
- Diagnostics
- Cause:
- The instrumentation engine configuration is corrupt or a required DyeInjection monitor cannot be found.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320148
- Required diagnostic monitor {0} is missing from the instrumentation library.
- Category:
- Diagnostics
- Cause:
- The instrumentation engine configuration is corrupt.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320149
- The DomainRuntime MBeanServer was not available for harvesting.
- Category:
- Diagnostics
- Cause:
- The DomainRuntime MBeanServer could not be loaded by the Harvester.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320151
- The instance name {0} in the Watch configuration {1} is invalid.
- Category:
- Diagnostics
- Cause:
- The instance name or instance-name pattern was not a valid JMX ObjectName or instance name pattern supported by the WLDF Watch and Notifications framework.
- Action:
- Check that the instance name is a valid ObjectName, or an instance-name pattern as specified in the WLDF Watch and Notifications framework documentation.
- BEA-320152
- An unexpected exception occurred while removing the set of watched metrics "{0}" from the harvester: {1}
- Category:
- Diagnostics
- Cause:
- An attempt was made to delete a set of watched metrics from the harvester that has already been removed, or one that was never activated within the harvester.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320153
- Instrumentation configuration for application "{0}" has changed. However, it will take effect only after redeploying the application, since hot-swap is not enabled.
- Category:
- Diagnostics
- Cause:
- Hot-swap is not enabled.
- Action:
- Redeploy the application, or restart the server with the diagnostic agent on the command line to enable hot-swap.
- BEA-320154
- Class redefinition failed after instrumentation configuration was changed for application "{0}" : {1}
- Category:
- Diagnostics
- Cause:
- An unexpected exception occurred while redefining classes after the instrumentation configuration was updated.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320155
- Inconsistent instrumentation handling information was specified in the same pointcut definition for {0} : {1} : {2}.
- Category:
- Diagnostics
- Cause:
- The instrumentation configuration contains a pointcut definition that specifies conflicting information for the method.
- Action:
- Review the pointcuts that specify the method listed in the error, and verify that there are not multiple definitions for the methods with which they conflict. For example, one indicating an argument is not-sensitive while another indicates it is.
- BEA-320156
- The renderer class {0} could not be loaded due to {1}, the following renderer will be used instead: {2}.
- Category:
- Diagnostics
- Cause:
- The instrumentation configuration specified a renderer class that either was not found, is not accessible, or is not a renderer.
- Action:
- Verify that the renderer class is correctly specified in the instrumentation configuration and that it is available to the server classloader.
- BEA-320157
- An error occurred when registering the log4j for data gathering operations.
- Category:
- Diagnostics
- Cause:
- The log4j libraries may not be in the CLASSPATH.
- Action:
- Ensure that the log4j libraries are available when using Log watch rules with Log4j enabled.
- BEA-320158
- An error was detected while capturing the flight recorder image.
- Category:
- Diagnostics
- Cause:
- The specified exception provides details on the error that was encountered.
- Action:
- Review the provided exception information to determine the cause and action to take.
- BEA-320159
- An error was detected while initializing the flight recording.
- Category:
- Diagnostics
- Cause:
- The specified exception provides details on the error that was encountered.
- Action:
- Review the provided exception information to determine the cause and action to take.
- BEA-320160
- The type-based renderer class {0} for type {1} could not be loaded due to {1}, that type-based renderer will not be used.
- Category:
- Diagnostics
- Cause:
- The instrumentation configuration specified a type-based renderer class that either was not found, is not accessible, or is not a renderer. It may also be that the type itself was not found or loadable.
- Action:
- Verify that the type-based renderer class and type class are correctly specified in the instrumentation configuration and that they are available to the server classloader.
- BEA-320161
- A legacy Spring instrumentation API was called for an unknown method {0}.
- Category:
- Diagnostics
- Cause:
- A legacy Spring instrumentation API was called for an unknown method {0}.
- Action:
- Instrument Spring using the tools in the current release.
- BEA-320162
- A legacy Spring instrumentation API was called.
- Category:
- Diagnostics
- Cause:
- A legacy Spring instrumentation API was called.
- Action:
- Legacy Spring features should function normally, but you should instrument Spring using the tools in the current release.
- BEA-320163
- Wildcarded types are not allowed to be marked as being insensitive with %.
- Category:
- Diagnostics
- Cause:
- A % character was specified for a wildcarded type, such as an asterisk or ellipses. This is not allowed, as it could lead to inadvertantly exposing a type that should be treated as being sensitive.
- Action:
- Review the pointcuts that specify the % character to ensure that it is not supplied for any types that are wildcarded using an asterisk or ellipses.
- BEA-320164
- Circular class load detected during stackmap frame computation for {0}.
- Category:
- Diagnostics
- Cause:
- An attempt was made to class load the class currently being instrumented. This is not supported.
- Action:
- Do not instrument the class that encountered the cycle.
- BEA-320165
- Received an unexpected error dispatching an Instrumentation event for Watch rule processing: {0}
- Category:
- Diagnostics
- Cause:
- An exception occurred while dispatching a WLDF Instrumentation event for Watch rule processing.
- Action:
- Check the server log for details on the error.
- BEA-320166
- Received an unexpected error dispatching an logging event for Watch rule processing: {0}
- Category:
- Diagnostics
- Cause:
- An exception occurred while dispatching a WLDF log event for Watch rule processing.
- Action:
- Check the server log for details on the error.
- BEA-320167
- Expected monitors were not instrumented : {0}
- Category:
- Diagnostics
- Cause:
- Monitors which were specified as being expected to be instrumented were not instrumented.
- Action:
- Review the instrumentation configuration and the code being instrumented, and then verify that all dependencies are available in the classpath to allow the instrumentor to walk the class hierarchy for inheritance matches.
- BEA-320168
- Disabling instrumentation on application "{0}" in partition "{1}" since it may contain shareable classloaders.
- Category:
- Diagnostics
- Cause:
- The deployment descriptor of this application may have indicated that its classloaders may be shared with applications in other partitions.
- Action:
- If application instrumentation for this application is needed, remove shareable classloader definitions from the weblogic-application.xml deployment descriptor.
- BEA-320169
- Activating dynamic debug patch "{0}" at system level.
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being activated at the system level.
- Action:
- No action is required.
- BEA-320170
- Activating dynamic debug patch "{0}" at application "{1}"
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being activated at the application level.
- Action:
- No action is required.
- BEA-320171
- Activating dynamic debug patch "{0}" at module "{2}" in application "{1}"
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being activated at the indicated module in the indicated application.
- Action:
- No action is required.
- BEA-320172
- Activating dynamic debug patch "{0}" at application "{1}" in partition "{2}"
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being activated at the indicated application in the indicated partition.
- Action:
- None
- BEA-320173
- Activating dynamic debug patch "{0}" at module "{2}" in application "{1}" in partition "{3}"
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being activated at the indicated module in the indicated application in the indicated partition.
- Action:
- No action is required.
- BEA-320174
- Successfully activated debug patch "{0}".
- Category:
- Diagnostics
- Cause:
- Debug patch was successfully activated.
- Action:
- No action is required.
- BEA-320175
- Failed to activate dynamic debug patch "{0}".
- Category:
- Diagnostics
- Cause:
- Classes in the dynamic debug patch may be structurally different than the original classes.
- Action:
- Check whether the class(es) in the dynamic debug patch are structurally different than the original classes.
- BEA-320176
- Deactivating dynamic debug patch "{0}" at system level.
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being deactivated at the system level.
- Action:
- No action is required.
- BEA-320177
- Deactivating dynamic debug patch "{0}" at application "{1}"
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being deactivated at the application level.
- Action:
- No action is required.
- BEA-320178
- Deactivating dynamic debug patch "{0}" at module "{2}" in application "{1}"
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being deactivated at the indicated module in the indicated application.
- Action:
- No action is required.
- BEA-320179
- Deactivating dynamic debug patch "{0}" at application "{1}" in partition "{2}"
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being disabled at the indicated application in the indicated partition.
- Action:
- No action is required.
- BEA-320180
- Deactivating dynamic debug patch "{0}" at module "{2}" in application "{1}" in partition "{3}"
- Category:
- Diagnostics
- Cause:
- Dynamic debug patch is being deactivated.
- Action:
- No action is required.
- BEA-320181
- Successfully deactivated debug patch "{0}".
- Category:
- Diagnostics
- Cause:
- Debug patch was successfully deactivated.
- Action:
- No action is required.
- BEA-320182
- Failed to deactivate dynamic debug patch "{0}".
- Category:
- Diagnostics
- Cause:
- The indicated dynamic debug patch was not deactivated.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-320183
- Debug patch "{0}" contains unknown classes: "{1}
- Category:
- Diagnostics
- Cause:
- Debug patch contains unknown classes that cannot be found on the classpath.
- Action:
- Contact the patch producers and have them address this issue.
- BEA-320184
- Failed to open diagnostic store file {0} due to reason: {1}. Re-trying to open..
- Category:
- Diagnostics
- Cause:
- This usually happens when the file is locked at the system level.
- Action:
- Identify the entity holding the lock and release the lock. This may be a system-dependent operation.
- BEA-320185
- Failed to open diagnostic store file {0} after {1} attempts. Some diagnostics features will be unavailable.
- Category:
- Diagnostics
- Cause:
- This usually happens when the file is locked at the system level.
- Action:
- Identify the entity holding the lock and release the lock. This may be a system dependent operation.
- BEA-320186
- Unable to find canonical path to diagnostic store directory {0}
- Category:
- Diagnostics
- Cause:
- The specified store directory path is not correct.
- Action:
- Specify the correct store directory path.
- BEA-320187
- ClassInfo for {0} is not available.
- Category:
- Diagnostics
- Cause:
- The ClassInfo for the class was not able to be retrieved or computed.
- Action:
- Enable instrumentation debug logging to determine the root cause.
- BEA-320188
- Long RID value with {0} components was created.
- Category:
- Diagnostics
- Cause:
- RID values grow during DiagnosticContext propagation, which are outbound calls to other JVMs or when Work is scheduled. Extremely long RID values may be expected but if they are growing rapidly, this may indicate a problem if they are growing unbounded. Note that the first occurrence of this message is reported immediately. After that it is throttled and only reported periodically if further growth is being seen. A corresponding log event is also produced to the FlightRecorder.
- Action:
- Enable DiagnosticContext debug and review the FlightRecorder data to look for JFRDebugEvents which indicate extreme RID growth and where it is seen. Pay particular attention to the scheduling of work from daemon threads. These can cause RID growth and may require that the daemon thread call DiagnosticContextHelper.handleLocalContextAsNonInheritable() to prevent propagating the Context.
- BEA-320189
- Log file or rotation directory for accessor {0} changed, but the accessor failed to adapt to the change.
- Category:
- Diagnostics
- Cause:
- There may have been an error while refreshing the accessor due to an internal WebLogic error.
- Action:
- Enable DebugDiagnosticAccessor and DebugDiagnosticArchive and review logs to get more information on the possible cause of the internal WebLogic error leading to this error.
- BEA-320190
- Failed to close diagnostic store.
- Category:
- Diagnostics
- Cause:
- Failed to close diagnostic store, likely to be due to an internal error.
- Action:
- Review logs to get more information on the possible cause of the internal WebLogic error leading to this error.
- BEA-320200
- Action {0} of type {1} not valid for current WLDF deployment, ignoring.
- Category:
- DiagnosticsWatch
- Cause:
- The action type requested may not be valid for the WLDF deployment; for example, this can happen if the action is deployed on a managed server, but is only valid deployed within the administration server.
- Action:
- Check the action documentation, and revise the Watch and/or action configuration accordingly.
- BEA-320201
- An unexpected error occurred while instantiating action {1} for action type {0}: {2}
- Category:
- DiagnosticsWatch
- Cause:
- An unexpected error occurred while instantiating the specified action instance.
- Action:
- Check the error in the server logs and make any necessary configuration changes.
- BEA-320202
- Map entry string {0} is not valid.
- Category:
- DiagnosticsWatch
- Cause:
- A Map object entry in the WLDFActionBean did not have the proper form.
- Action:
- Fix the entry in the WLDF System Resource descriptor.
- BEA-320203
- The timeout period of {1} seconds expired for action {0}, canceling the action execution.
- Category:
- DiagnosticsWatch
- Cause:
- The action did not complete withing the specified timeout interval.
- Action:
- Consider increasing the timeout for the action, or see if an error occurred during processing that needs to be addressed.
- BEA-320204
- Executing action {0} with timeout period {1} seconds.
- Category:
- DiagnosticsWatch
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-320205
- An IOException occurred while communicating with server {0}, unable to query it for instances matching "{1}"
- Category:
- DiagnosticsWatch
- Cause:
- A network error occurred while attempting to communicate with server {0}. If the error persists, check the server logs and Node Manager logs.
- Action:
- Determine the source of the communication error and correct it if possible.
- BEA-320206
- An error occurred while executing the script action {0}: {1}
- Category:
- DiagnosticsWatch
- Cause:
- The configured script was not executed successfully. This may be due to an error in the action configuration or an error that was encountered within the script itself.
- Action:
- Check the action configuration, and ensure that the script is available and has executable permissions.
- BEA-320207
- The script action {0} was interrupted during execution, exception: {1}
- Category:
- DiagnosticsWatch
- Cause:
- The script action may have timed out, or was abruptly terminated.
- Action:
- Check the error message for details about what may have caused execution to be interrupted.
- BEA-320208
- An invalid action configuration type {0} was passed into the ScriptAction service, expected a configuration of type {1}.
- Category:
- DiagnosticsWatch
- Cause:
- The ScriptAction service is not receiving the expected configuration type. This is likely a product defect and should be reported to My Oracle Support.
- Action:
- Contact My Oracle Support and provide them with the log file for further analysis.
- BEA-320209
- The executable path {1} for script action {0} is not valid.
- Category:
- DiagnosticsWatch
- Cause:
- The executable path indicated in the script action config is either missing or empty, or the path does not exist.
- Action:
- Check the action configuration and correct the executable path.
- BEA-320210
- Script action {0} execution of {1} completed with exit code {2}.
- Category:
- DiagnosticsWatch
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-320211
- Script action {0} starting, stdout redirected to {1}, stderr redirected to {2}.
- Category:
- DiagnosticsWatch
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-320212
- Cancel was requested for script action {0}, destroying the process.
- Category:
- DiagnosticsWatch
- Cause:
- The currently executing script action was cancelled externally, either by user request or by the action exceeding the configured timeout.
- Action:
- No action is required.
- BEA-320213
- REST notification {0} could not be delivered successfully to end point {1}. The response code is {2} and the detailed reason is {3}.
- Category:
- DiagnosticsWatch
- Cause:
- The REST end point may not be available or the REST notification is not configured correctly.
- Action:
- Take appropriate action based on the status code and detailed reason reported in the error.
- BEA-320214
- No action config present in action context.
- Category:
- DiagnosticsWatch
- Cause:
- There is likely a misconfiguration in the WLDFSystemResourceMBean associated with the action.
- Action:
- Check the configuration and resolve any issues.
- BEA-320215
- Scale down action {0} invoked for cluster {1} with scaling size {2} and timeout period of {3} seconds.
- Category:
- DiagnosticsWatch
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-320216
- Scale down task {0} for cluster {1} complete, status: {2}
- Category:
- DiagnosticsWatch
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-320217
- Invalid configuration {0} of type {1} passed to scale down action, expected an object of type {2}.
- Category:
- DiagnosticsWatch
- Cause:
- This was caused by an invalid configuration or a software defect.
- Action:
- Verify the action and policy configuration.
- BEA-320218
- No scale-up action config present in action context
- Category:
- DiagnosticsWatch
- Cause:
- There is likely a misconfiguration in the WLDFSystemResourceMBean associated with the action.
- Action:
- Check the configuration and resolve any issues.
- BEA-320219
- Invalid configuration {0} of type {1} passed to scale down action, expected an object of type {2}.
- Category:
- DiagnosticsWatch
- Cause:
- This was caused by an invalid configuration or a software defect.
- Action:
- Verify the action and policy configuration.
- BEA-320220
- Scale up action {0} invoked for cluster {1} with scaling size {2} and timeout period of {3} seconds.
- Category:
- DiagnosticsWatch
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-320221
- Scale up task {0} for cluster {1} complete, status: {2}
- Category:
- DiagnosticsWatch
- Cause:
- The scale up task for the cluster is complete.
- Action:
- No action is required.
- BEA-320222
- Skipping actions processing for policy {0} since processing for a previous invocation is still in progress.
- Category:
- DiagnosticsWatch
- Cause:
- A previous invocation of the actions processing was found to be in progress. The new invocation was skipped.
- Action:
- No action is required.
- BEA-320223
- Another ThreadDumpAction is already in progress, so skipping execution of action {0}.
- Category:
- DiagnosticsWatch
- Cause:
- Another ThreadDumpAction is already in progress.
- Action:
- No action is required.
- BEA-320224
- Thread dump created at {0} by thread dump action {1} for policy {2} in diagnostics module {3}.
- Category:
- DiagnosticsWatch
- Cause:
- Thread dump is created due to execution of ThreadDumpAction.
- Action:
- Analyze generated thread dumps.
- BEA-320225
- Failed to write thread dump file {0}. {1}
- Category:
- DiagnosticsWatch
- Cause:
- Failed to write thread dump file due to permission or other file system problem.
- Action:
- Ensure appropriate permissions and sufficient disk space.
- BEA-320226
- Waiting for {0} seconds before capturing next thread dump.
- Category:
- DiagnosticsWatch
- Cause:
- Wait for configured time between successive thread dump captures.
- Action:
- No action is required.
- BEA-320227
- An attempt to capture a heap was made while another capture was already in progress.
- Category:
- DiagnosticsWatch
- Cause:
- An attempt to capture a new heap dump was made while another capture was already in progress; only one capture is allowed at a time.
- Action:
- No action is required.
- BEA-320228
- Capturing heap heap dump to file {0}, liveSetOnly={1}
- Category:
- DiagnosticsWatch
- Cause:
- Action:
- BEA-320229
- An unexpected exception occurred checking for the availability of the heap dump operation, heap dump action is not available: {0}
- Category:
- DiagnosticsWatch
- Cause:
- The HotSpot Diagnostic MBean is not available in the local JVM, therefore the heap dump action will not be available.
- Action:
- If the heap dump action is required, consider using a version of the Java Virtual Machine that supports the HotSpot Diagnostic MBean.
- BEA-320230
- Heap dump capture by action {1} for policy {2} in module {3} complete, located at {0}
- Category:
- DiagnosticsWatch
- Cause:
- Action:
- BEA-320231
- HeapDumpAction {0} was deployed on a JVM platform that does not suport it, the action will be disabled
- Category:
- DiagnosticsWatch
- Cause:
- HeapDumpAction {0} was deployed on a JVM platform that does not suport it.
- Action:
- If the action is required, consider using a JVM that supports the HotSpot Diagnostic MBean.
- BEA-320232
- The JMX Platform MBeanServer can not be found, heap dump actions are not available.
- Category:
- DiagnosticsWatch
- Cause:
- The Platform MBeanServer could not be found, check that the JVM supports the HotSpot Diagnostic MXBean.
- Action:
- If the heap dump action is required, consider using a JVM that supports the HotSpot Diagnostic MXBean.
- BEA-320233
- The dumpHeap() method could not be found, heap dump actions will not be available for this JVM.
- Category:
- DiagnosticsWatch
- Cause:
- The dumpHeap() method could not be found on the Hotspot Diagnostic MBean.
- Action:
- If the heap dump action is required, consider using a JVM that supports the HotSpot Diagnostic MXBean.
- BEA-320234
- The Hotspot Diagnostic MBean with ObjectName {0} could not be found, heap dump actions will not be available for this JVM
- Category:
- DiagnosticsWatch
- Cause:
- The JVM may not support heap dump operations.
- Action:
- If the heap dump action is required, consider using a JVM that supports the HotSpot Diagnostic MXBean.
- BEA-320235
- Caught unexpected error capturing heap dump: {0}
- Category:
- DiagnosticsWatch
- Cause:
- An unexpected error occurred while capturing a heap dump.
- Action:
- Check the exception message in the server logs, contact Oracle Support if the issue can not be corrected.
- BEA-320236
- Thread dump action {0} canceled
- Category:
- DiagnosticsWatch
- Cause:
- Thread dump action was cancelled.
- Action:
- No action necessary.
- BEA-320237
- Older dump file {0} removed to make space for new dump file.
- Category:
- DiagnosticsWatch
- Cause:
- Limit for number of heap or thread dump files is already reached. Removing older dump files to make space for new dump file.
- Action:
- No action necessary.
- BEA-320238
- Unable to execute scale down action {0}, cluster {1} is already at the minimum number of required running servers: {2}.
- Category:
- DiagnosticsWatch
- Cause:
- Action:
- BEA-320239
- Unable to execute scale up action {0}, cluster {1} is already at the maximum allowed number of running servers: {2}.
- Category:
- DiagnosticsWatch
- Cause:
- Action:
- BEA-320300
- The WLS ServerRuntime MBeanServer was not available for harvesting; custom MBean harvesting will not be available.
- Category:
- DiagnosticsHarvester
- Cause:
- This could be the result of a serious error in the OA&M infrastructure. Check for other error messages in the log in that area.
- Action:
- Contact My Oracle Support.
- BEA-320301
- The WLDF Harvester could not activate the Watch and Notifications framework due to an exception: {0}
- Category:
- DiagnosticsHarvester
- Cause:
- During server startup, the Watch and Notifications activation is deferred until the WLDF Harvester is fully activated. The deferred activation encountered an unexpected exception, potentially impairing the Watch and Notifications functionality.
- Action:
- Contact My Oracle Support.
- BEA-320303
- The namespace {1} for the harvested type specification {0} can not be serviced by a Managed Server instance; it is valid only when targed to an Administration Server.
- Category:
- DiagnosticsHarvester
- Cause:
- A harvested type specifying the DomainRuntime namespace was targeted to a Managed Server. A Managed Server can only service the ServerRuntime namespace.
- Action:
- Correct the namespace declaration of the harvested type, or retarget the WLDF configuration to an Administration Server in order to service this type.
- BEA-320304
- The following errors were reported during the validation of the metrics for watched values {0}: {1}
- Category:
- DiagnosticsHarvester
- Cause:
- Some of the configured harvested types may have errors, resulting in the harvester being unable to process them for collection.
- Action:
- Correct any issues with the harvested type configuration.
- BEA-320305
- The instance name {0} is not a valid ObjectName or instance name pattern.
- Category:
- DiagnosticsHarvester
- Cause:
- The instance name must be a valid JMX ObjectName, or a pattern conforming to the syntax supported by the WebLogic Diagnostics Framework.
- Action:
- Correct the instance name in the harvested type.
- BEA-320400
- The log file {0} will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.
- Category:
- LoggingService
- Cause:
- This event happens whenever the log file is about to be rotated based on either size or time rotation criterion.
- Action:
- On certain platforms, if some application is tailing the log, the rotation fails. Stop the application tailing and reopen the tail after the rotation is complete.
- BEA-320401
- The log file has been rotated to {1}. Log messages will continue to be logged in {0}.
- Category:
- LoggingService
- Cause:
- This event happens after the log file is rotated based on either size or time rotation criterion.
- Action:
- No action is required.
- BEA-320450
- The DebugScope name {0} is not valid.
- Category:
- DebugModule
- Cause:
- The DebugScope with the given name is not defined in the ServerDebugMBean interface.
- Action:
- Configure the debug scope with a valid name.
- BEA-320451
- An error occurred while applying the DebugScopes configuration.
- Category:
- DebugModule
- Cause:
- This may be due to an I/O error while reading the DebugScopes from the disk.
- Action:
- Take action based on the error stack trace.
- BEA-320452
- An error occurred while adding PropertyChangeListener to bean {0}.
- Category:
- DebugModule
- Cause:
- The debug configuration bean does not support PropertyChangeListeners.
- Action:
- Take action based on the error stack trace.
- BEA-320453
- An error occurred while removing PropertyChangeListener from bean {0}.
- Category:
- DebugModule
- Cause:
- The debug configuration bean does not support PropertyChangeListeners.
- Action:
- Take action based on the error stack trace.
- BEA-320454
- An error occurred while initializing Server Debug from older DebugCategory mappings.
- Category:
- DebugModule
- Cause:
- The error details are included in the stack trace of the Exception reported.
- Action:
- Take action based on the error stack trace.
- BEA-320500
- The built-in WebLogic Diagnostics Framework resource descriptor ${0} for the selected level "{1}" could not be found; setting built-in resource to ${2}.
- Category:
- DiagnosticsRuntimeControl
- Cause:
- The WebLogic Diagnostics Framework resource descriptor for the desired built-in monitoring state could not be loaded due to either an issue with the WebLogic Server kit installation or an environmental issue in the domain configuration.
- Action:
- Contact My Oracle Support.
- BEA-320800
- Failed to cache the instrumentation engine configuration at {0} with exception {1}
- Category:
- DiagnosticsInstrumentor
- Cause:
- The destination file may not be writable or some other I/O error occurred.
- Action:
- Check to see if the destination file is writable.
- BEA-320801
- Failed to load instrumentation engine configuration {0}.
- Category:
- DiagnosticsInstrumentor
- Cause:
- The instrumentation engine configuraion may be missing or corrupt.
- Action:
- Contact My Oracle Support.
- BEA-320802
- Missing the name attribute for the instrumentation engine configuration at {0}.
- Category:
- DiagnosticsInstrumentor
- Cause:
- The engine configuration does not have the required name attribute.
- Action:
- Contact My Oracle Support.
- BEA-320803
- Duplicate instrumentation engine configuration {0} found.
- Category:
- DiagnosticsInstrumentor
- Cause:
- A duplicate instrumentation engine configuration was found.
- Action:
- Contact My Oracle Support.
- BEA-320804
- Invalid parent "{1}" for instrumentation engine configuration "{0}".
- Category:
- DiagnosticsInstrumentor
- Cause:
- The instrumentation engine configuration has an incorrect parent configuration.
- Action:
- Contact My Oracle Support.
- BEA-320805
- Required root instrumentation engine configuration was not found.
- Category:
- DiagnosticsInstrumentor
- Cause:
- The required root instrumentation engine configuration was not found.
- Action:
- Contact My Oracle Support.
- BEA-320806
- Found circular dependency with instrumentation engine configurations: {0}
- Category:
- DiagnosticsInstrumentor
- Cause:
- The instrumentation engine configurations are invalid.
- Action:
- Contact My Oracle Support.
- BEA-320807
- Parent "{0}" for instrumentation engine configurations {1}.
- Category:
- DiagnosticsInstrumentor
- Cause:
- The parent configuration for an instrumentation engine configuration cannot be located.
- Action:
- Contact My Oracle Support.
- BEA-320900
- Agent will be unable to proxy for the agents specified due to Proxy initialization error.
- Category:
- SNMP
- Cause:
- Refer to exception message for cause of initialization failure.
- Action:
- Take appropriate action based upon the specified exception message.
- BEA-320913
- Failed to register Attribute Change listener {0} for MBean type {1} on server {2}.
- Category:
- SNMP
- Cause:
- This may be due to a misconfigured SNMPAttributeChange entry specification in config.xml. Please refer to the exception message for more specific cause information.
- Action:
- Modify configuration of the SNMPAttributeChange entry or take appropriate action based upon the specific exception message.
- BEA-320918
- Failed to add NotificationListener to logBroadcaster for SNMPLogFilter {0}.
- Category:
- SNMP
- Cause:
- Please refer to the exception message for more specific cause information.
- Action:
- Take appropriate action based upon the specific exception message.
- BEA-320923
- Error creating JMX Monitor {0} of type {1} for MBean {2}.
- Category:
- SNMP
- Cause:
- This may be due to a misconfigured Monitor entry specification. Please refer to the exception message for more specific cause information.
- Action:
- Modify the configuration of the SNMPJMXMonitorMBean entry or take appropriate action based upon the specific exception message.
- BEA-320925
- Failed to send Monitor trap for server {0} for type {1} for object {2}.
- Category:
- SNMP
- Cause:
- Please refer to the exception message for more specific cause information.
- Action:
- Take appropriate action based upon the specific exception message.
- BEA-320927
- SNMP agent is initializing.
- Category:
- SNMP
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320928
- SNMP Agent initialization failed while accessing server information for the configured Domain.
- Category:
- SNMP
- Cause:
- Refer to earlier SNMP error log information for specific information on the cause of the problem.
- Action:
- Take appropriate action based upon the specific exception message.
- BEA-320929
- SNMP agent initialization completed successfully.
- Category:
- SNMP
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320930
- SNMP Agent Generic coldStart trap sent.
- Category:
- SNMP
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320931
- The SNMP trap version is {0}.
- Category:
- SNMP
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320937
- Exception occurred sending SNMP message, {0}.
- Category:
- SNMP
- Cause:
- This is an internal WebLogic Server error that occurred during the sending of an SNMP message using the TCP transport provider.
- Action:
- Contact My Oracle Support.
- BEA-320938
- SNMP Agent does not support setting values for MBean attributes through SNMP.
- Category:
- SNMP
- Cause:
- You attempted to set an MBean attribute using SNMP.
- Action:
- Use JMX APIs to update the WLS configuration MBeans.
- BEA-320939
- An error occurred while adding a row to the SNMP table for MBean {1} of type {0}.
- Category:
- SNMP
- Cause:
- This could be due to a row already existing in the SNMP Agent for the MBean or an error condition in the SNMP Agent.
- Action:
- Take appropriate action based on additional information in the error stack trace.
- BEA-320940
- An error occurred while deleting the row from the SNMP table for MBean {0}.
- Category:
- SNMP
- Cause:
- The specified MBean instance was not registered in SNMP or it could be due to an error condition in the SNMP Agent.
- Action:
- Take appropriate action based on additional information in the error stack trace.
- BEA-320941
- An SNMP message was received over the default channel instead of the dedicated SNMP channel.
- Category:
- SNMP
- Cause:
- This occurs when a dedicated Network Access Point for SNMP traffic has been configured and activated and an SNMP request is received over the default server channel.
- Action:
- Direct the SNMP request to the configured channel.
- BEA-320942
- The specified type name {0} is invalid.
- Category:
- SNMP
- Cause:
- The specified name is not recognized as a valid WebLogic Server MBean type.
- Action:
- Please specify the correct name for a WebLogic Server Configuration or Runtime MBean type.
- BEA-320943
- The specified attribute name {1} is not valid for the given type {0}.
- Category:
- SNMP
- Cause:
- The specified attribute name that is not valid was specified as part of the configuration.
- Action:
- Please specify the correct attribute name for the WebLogic Server Configuration or Runtime MBean type.
- BEA-320944
- The SecurityName attribute is not specified for the SNMPTrapDestination {0}.
- Category:
- SNMP
- Cause:
- The SNMP Agent's trap version is set to V3 and the SecurityName is not specified for the given SNMPTrapDestination.
- Action:
- Please specify the SecurityName attribute for which the SNMP Agent will issue V3 traps.
- BEA-320945
- The SNMP Agent''s TrapVersion needs to be V2 or higher to be able to send INFORM notifications.
- Category:
- SNMP
- Cause:
- The SNMPAgentMBean's SNMPTrapVersion attribute is set to V1.
- Action:
- Set the SNMPTrapVersion to V2 or higher in the configuration.
- BEA-320946
- The SNMP Agent {0} is already deployed to server {1}.
- Category:
- SNMP
- Cause:
- An attempt was made to target multiple SNMPAgentDeploymentMBeans to the same WebLogic Server instance.
- Action:
- Ensure that only one SNMPAgentDeploymentMBean is targeted to any Server in the domain.
- BEA-320947
- The AuthenticationProtocol for SNMP Agent {0} cannot be noAuth when PrivacyProtocol {1} is specified.
- Category:
- SNMP
- Cause:
- An invalid combination of authentication and privacy protocols was configured.
- Action:
- Specify either MD5 or DES as the AuthenticationProtocol in combination with Privacy.
- BEA-320948
- The SNMPTrapDestinationMBean {0} has a higher SecurityLevel {1} than the SNMPAgent''s SecurityLevel {2}.
- Category:
- SNMP
- Cause:
- An invalid combination of authentication and privacy protocols on the SNMPAgentMBean and security level on the SNMPTrapDestinationMBean has been configured.
- Action:
- Specify the valid security level for the users and the trap destinations.
- BEA-320949
- SNMPAgent {0} is configured with a security level of {1}; the security level of {3} for proxy {2} must not exceed that of the SNMP agent.
- Category:
- SNMP
- Cause:
- A security level on the SNMP proxy was configured that exceeds the security level of the SNMP agent that corresponds to its configured authentication and privacy protocols.
- Action:
- Configure a level of security on the proxy that is lower than the security level of the SNMP agent. For example, if the SNMP agent is configured with authentication but no privacy, configure the security level of NOAUTH_NOPRIV or AUTH_NOPRIV on the proxy.
- BEA-320950
- Failed to start the SNMP agent. If it failed to bind to the port, check if the port is available or the process has permission to bind to the port.
- Category:
- SNMP
- Cause:
- Binding to specified UDP and agentX ports is a common problem. The ports to which the agent binds may not be available. Also, on UNIX platforms, ports up to 1023 are protected and can be bound only by processes owned by root.
- Action:
- Check whether the specified ports are available. On UNIX, the default UDP port (161) and master AgentX port (705) are protected to be used by processes owned by root. In that case, either start the server as root, or configure the SNMP agent to use port numbers higher than 1023.
- BEA-320951
- Failed to initalize the SNMP AgentX master subagent. One possible cause is the failure to bind the Master agentX port. If this is the case, check to see if the specified AgentX port is available, or ensure that the process has permissions to bind to the desired port.
- Category:
- SNMP
- Cause:
- A common problem is with binding to the specified agentX port. The port to which the agent binds may not be available. Also, on UNIX platforms, ports up to 1023 are protected and can be bound only by processes owned by root.
- Action:
- Check whether the specified port is available. On UNIX, the default master AgentX port (705) is protected to be used by processes owned by root. In that case, either start the server as root, or configure the SNMP agent to use port numbers higher than 1023.
- BEA-320952
- Failed to send the SNMP trap or inform notification for trap OID {2}. Number of send attempts = {0}. Number of errors encountered = {1}. The detailed error message from the SNMP toolkit is {3}.
- Category:
- SNMP
- Cause:
- The SNMPTrapDestination(s) could be incorrectly configured or the SNMP Manager might not be running at the configured location.
- Action:
- Ensure that the SNMP Manager is available at the configured SNMP TrapDestinations.
- BEA-320953
- The SNMP Agent has been started on port {0}.
- Category:
- SNMP
- Cause:
- The SNMP Agent tries to bind to the configured port. If this port is not available due to another SNMP Agent being deployed to the same machine on another WebLogic Server instance then the SNMP Agent tries to find the nearest port and binds to it.
- Action:
- No action is needed. The port number is also reflected in the UDPListenPort attribute of the SNMPAgentRuntimeMBean interface on this Server.
- BEA-320954
- The SNMP Agent encountered an error while discovering Extensions {0}.
- Category:
- SNMP
- Cause:
- The SNMPAgent Extension provider implementations could not be loaded successfully.
- Action:
- Take corrective action based on the exception details.
- BEA-320955
- SNMP agent has been shut down.
- Category:
- SNMP
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-320956
- Error registering trap destination {0} for address {1}:{2}.
- Category:
- SNMP
- Cause:
- The host name specified in the SNMPTrapDestination configuraiton is not valid.
- Action:
- Correct the configuration and start the SNMP agent again.
- BEA-320957
- Community prefix value cannot be empty or "public" or "private"
- Category:
- SNMP
- Cause:
- The SNMP agent is enabled and the community prefix attribute is empty or set to either public or private.
- Action:
- Correct the configuration and start the SNMP agent again.
- BEA-340450
- Descriptor {1} has no configuration-support in the weblogic-extension.xml file for application module {0}. JSR-88 updates will not be supported.
- Category:
- CustomModule
- Cause:
- The configuration-support stanza was missing or has XML errors.
- Action:
- Correct the weblogic-extension.xml file and redeploy the application.
- BEA-340451
- URI mismatch for base-URI ({2}) in the weblogic-extension.xml file for descriptor {1} in module {0}. Unpredictable results from JSR-88 updates are likely.
- Category:
- CustomModule
- Cause:
- The custom-module URI does not match the configuration-support base-URI.
- Action:
- Correct the base-URI in the configuration-support stanza of the weblogic-extension.xml file to match the custom-module URI and redeploy the application.
- BEA-340452
- Prepare to deploy descriptor {1} in application module {0}.
- Category:
- CustomModule
- Cause:
- This is normal behavior.
- Action:
- No action is required.
- BEA-340454
- Prepare update for descriptor {1} in application module {0}.
- Category:
- CustomModule
- Cause:
- This is normal behavior.
- Action:
- No action is required.
- BEA-400000
- Initializing message interception service.
- Category:
- messaging.interception
- Cause:
- WebLogic Server starts the message interception service.
- Action:
- No action is required.
- BEA-400200
- Incorrect arguments. Expects 2 arguments.
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400201
- Migrating old security provider JARS from {0}
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400204
- No security provider JARs have been upgraded.
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400205
- Copying the upgraded security provider JAR to {0}
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400206
- Completed upgrading of {0} old security provider JARs.
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400207
- Skipped converting {0} since it is a security provider JAR built with 9.0.
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400208
- No MDFs (.xmls) found in the old security provider JAR with name {0}
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400209
- Created new security provider JAR {0} from {1}
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400210
- The XML file {0} is not a valid MDF, hence the upgrade tool will ignore this file.
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400211
- Not upgrading {0} because either this is an out-of-the-box Oracle security provider JAR or this security provider JAR is already upgraded or this is not a valid archive file (may not be a .jar).
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400212
- Now processing {0}
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400213
- Could not convert from MDF {0}. This file may not be a valid MDF file; verify.
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400214
- Running the first phase of Security Provider Upgrade process on {0}
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-400215
- First phase successful, now running the second and last phase of security provider upgrade process on {0}
- Category:
- Upgrade-SecurityProviders
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-420000
- The message interception service cannot bind "{0}" to the local JNDI.
- Category:
- MIExceptions
- Cause:
- The JNDI name was already used.
- Action:
- Avoid using JNDI names starting with weblogic. Correct this problem then try again.
- BEA-420002
- The addAssociation method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the addAssociation API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420003
- The addAssociation method encounters some usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The interception point type is unknown either due to typo or the registerInterceptionPointNameDescription method didn't register the expected interception point type first.
- Action:
- If this is caused by an external application then fix the related code. Otherwise, contact the customer support.
- BEA-420004
- The removeAssociation method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the removeAssociation API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420005
- The registerInterceptionPointNameDescription method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an llegal usage of the registerInterceptionPointNameDescription API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420006
- The registerInterceptionPoint method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the registerInterceptionPoint API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420007
- The registerInterceptionPoint method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The interception point type is unknown either due to a typo or the registerInterceptionPointNameDescription method did not register the expected interception point type first.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420008
- The unRegisterInterceptionPoint method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the unRegisterInterceptionPoint API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420009
- The registerProcessorType method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the registerProcessorType API.
- Action:
- If this is caused by an external application, then fix the related code; Otherwise, contact My Oracle Support.
- BEA-420010
- The addProcessor method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the addProcessor API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420011
- The addProcessor method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The processor type is unknown either due to a typo or the registerProcessorType method did not register the expected processor type first.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420012
- The removeProcessor method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the removeProcessor API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420013
- The getAssociationHandle method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of getAssociationHandle API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420014
- The getProcessorHandles method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the getProcessorHandles API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420015
- The getProcessorHandle method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the getProcessorHandle API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420016
- The registerInterceptionPointNameDescriptionListener method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the registerInterceptionPointNameDescriptionListener API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420017
- The removeAssociation method encountered an input error due to "{0}".
- Category:
- MIExceptions
- Cause:
- There was an illegal usage of the removeAssociation API.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420019
- The process method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The required processor for the given association was not created at the time. To send a message to a target that has the given association defined, the processor specified in the association needs to be added beforehand.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420020
- The process method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The processor generated an illegal error.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420021
- The process method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The processor generated an illegal runtime exception.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420025
- The addAssociation method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The added association already exists.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420026
- The unregisterInterceptionPoint method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The interception point has already been removed.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420027
- The interception point name argument is invalid due to "{0}".
- Category:
- MIExceptions
- Cause:
- The interception point name argument is invalid for several possible reasons. For example, the total number of name element differs from what is being registered with the interception service or one name element is invalid by itself.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420028
- The removeProcessor method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The processor has been removed.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420029
- The registerProcessorType method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The processor factory class cannot be instantiated.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420030
- The registerProcessorType method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The processor factory class cannot be instantiated.
- Action:
- If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
- BEA-420031
- The process method encountered a usage error due to "{0}".
- Category:
- MIExceptions
- Cause:
- The processor is currently processing more intercepted messages than that the association's depth allows.
- Action:
- Increase the depth on the association using the association handle object.
- BEA-2004000
- An error occurred while loading the Kodo-Oracle message dictionary.
- Category:
- Kodo Integration
- Cause:
- This can happen if the Kodo-Oracle message dictionary is not available. This dictionary should be located at {0}.
- Action:
- Contact My Oracle Support.
- BEA-2004001
- The Kodo-Oracle message dictionary was not found.
- Category:
- Kodo Integration
- Cause:
- This can happen if the Kodo-Oracle message dictionary is not available. This dictionary should be located at {0}.
- Action:
- Contact My Oracle Support.
- BEA-2004003
- Kodo localization key {0} has already been registered in the Kodo-Oracle message ID dictionary. Original value: {1}. New value: {2}. New definition from URL: {3}. The original value will be used.
- Category:
- Kodo Integration
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-2011000
- The bundle {0} has started successfully.
- Category:
- HarvesterAPI
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2011099
- The bundle {0} has been successfully stopped.
- Category:
- HarvesterAPI
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2011100
- The bundle {0} has successfully started.
- Category:
- HarvesterJMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2011101
- An unexpected Exception occurred in harvester {0}. Logging it here and continuing processing... Context: {1}, Exception: {2}
- Category:
- HarvesterJMX
- Cause:
- An unexpected exception occurred during the harvesting process.
- Action:
- You should attempt to uncover the reason for the underlying Exception.
- BEA-2011102
- An unexpected condition was encountered in harvester {0}. Logging it here and continuing processing... Context: {1}
- Category:
- HarvesterJMX
- Cause:
- An unexpected condition occurred during the harvesting process.
- Action:
- The user should attempt to uncover the reason for the problem.
- BEA-2011103
- Service with name: {0} has been prepared.
- Category:
- HarvesterJMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2011104
- Service with name: {0} has been acivated.
- Category:
- HarvesterJMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2011105
- Service with name: {0} has been deactivated.
- Category:
- HarvesterJMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2011199
- The bundle {0} has successfully been stopped.
- Category:
- HarvesterJMX
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2011300
- The bundle {0} has successfully started.
- Category:
- HarvesterUtils
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2011399
- The bundle {0} has successfully been stopped.
- Category:
- HarvesterUtils
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2012300
- The bundle {0} has successfully started.
- Category:
- MBeanTypingUtil
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2012301
- Processing {0} MBeans.
- Category:
- MBeanTypingUtil
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2012302
- Processed {1} MBeans for MBean utility {0}.
- Category:
- MBeanTypingUtil
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2012303
- The MBeanTypeUtil cannot process an MBean instance due to excp {0} on MBeanServer: {1} and MBean: {2} stack trace: {3} --- Retrying once...
- Category:
- MBeanTypingUtil
- Cause:
- The MBeanTypeUtil has failed while trying to access a registered MBean.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-2012304
- The MBeanTypeUtil failed for a second time to process an MBean instance due to excp: {0} on MBeanServer: {1} and MBean: {2} stack trace: {3} --- Skipping this MBean...
- Category:
- MBeanTypingUtil
- Cause:
- The MBeanTypeUtil has failed to access a registered MBean in two tries.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-2012305
- The MBeanTypeUtil failed to process two distinct MBeans in a row. The most recent problem was on MBeanServer: {0} and MBean: {1} stack trace: {2} --- No further MBeans will be processed.
- Category:
- MBeanTypingUtil
- Cause:
- The MBeanTypeUtil has failed to access two consecutive different MBeans.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-2012306
- {1} Unable to process the {2} of MBean: {0} . The managed process might be shutting down. Stack trace: {3}
- Category:
- MBeanTypingUtil
- Cause:
- The process is most likely shutting down, so it is safe to ignore this.
- Action:
- If the process is known to be active, contact My Oracle Support to determine why the MBean cannot be processed. Setting the module debug flag will cause stack traces to be printed.
- BEA-2012307
- {1} Unable to process the {2} of MBean: {0} . The managed process appears to be shutting down. Stack trace: {3}
- Category:
- MBeanTypingUtil
- Cause:
- The process is most likely shutting down, so it is safe to ignore this.
- Action:
- If the process is known to be active, contact My Oracle Support to determine why the MBean cannot be processed. Setting the module debug flag will cause stack traces to be printed.
- BEA-2012308
- An uexpected error occurred while scheduling work for MBeanTypeUtil instance {0} with work manager {1}: {2}
- Category:
- MBeanTypingUtil
- Cause:
- Possibly no work manager was set, or the work manager was unable to queue the request.
- Action:
- If the problem persists, contact My Oracle Support.
- BEA-2012309
- An uexpected error occurred while communicating with the MBeanServer: {0}
- Category:
- MBeanTypingUtil
- Cause:
- The MBeanServer or host process may no longer be available. If the MBeanServer is remote, there may be network issues.
- Action:
- If the problem persists, contact My Oracle Support.
- BEA-2012399
- The bundle {0} has been successfully stopped.
- Category:
- MBeanTypingUtil
- Cause:
- This is a normal operation.
- Action:
- No action is required.
- BEA-2145000
- Unable to fire asynchronous listeners. Associated stack trace follows:
- Category:
- BEA Cache
- Cause:
- An error condition was reported.
- Action:
- Check the Work Manager configuration for work scheduling problems.
- BEA-2145001
- Could not configure cache with write policy of {0} because no store has been configured for the cache.
- Category:
- BEA Cache
- Cause:
- The configuration is invalid.
- Action:
- Either remove the write policy configuration or specify a custom store along with it.
- BEA-2150001
- Validation of weblogic-pubsub.xml descriptor file failed. The error is {0}
- Category:
- HTTP Pubsub Server
- Cause:
- There are errors in the weblogic-pubsub.xml descriptor file.
- Action:
- Correct the error in weblogic-pubsub.xml according to the schema.
- BEA-2150002
- No permission on channel operation: User {0} has no permission to create channel {1}
- Category:
- HTTP Pubsub Server
- Cause:
- There are not sufficient privileges to create a channel.
- Action:
- Check the PubSub server configuration security settings.
- BEA-2150003
- No permission on channel operation: User {0} has no permission to delete channel {1}
- Category:
- HTTP Pubsub Server
- Cause:
- There are not sufficient privileges to delete a channel.
- Action:
- Check the PubSub server configuration security settings.
- BEA-2150005
- Invalid persistent-client-timeout-secs: {0}.
- Category:
- HTTP Pubsub Server
- Cause:
- The persistent-client-timeout-secs must be greater than the timeout-secs.
- Action:
- Check the persistent-client-timeout in the PubSub server configuration
- BEA-2150006
- Invalid transport type: {0}
- Category:
- HTTP Pubsub Server
- Cause:
- An invalid transport type was configured in the PubSub server configuration.
- Action:
- Check the PubSub server configuration.
- BEA-2150007
- Cannot find configuration for referenced message filter {0}; check message-filter in the PubSub server configuration.
- Category:
- HTTP Pubsub Server
- Cause:
- There is a mismatch between the message filter name referenced in the channel setting and the message-filter setting.
- Action:
- Check the PubSub server configuration.
- BEA-2150008
- There is no message filter configured in the PubSub server configuration, but there is a message filter named {0} referenced in the channel setting.
- Category:
- HTTP Pubsub Server
- Cause:
- The channel setting is requesting a message filter but the message filter was not specified in the PubSub server.
- Action:
- Either specify the message-filter setting or remove the message-filter reference from the channel setting.
- BEA-2150009
- Invalid message-filter configured: message-filter {0} is configured in PubSub server configuration, but its associated class {1} cannot be initialized correctly.
- Category:
- HTTP Pubsub Server
- Cause:
- Class {1} associated with message filter {0} is incorrect.
- Action:
- Check the message-filter-name and message-filter-class in the PubSub server configuration.
- BEA-2150011
- Action {1} on channel {0} is not allowed for any client.
- Category:
- HTTP Pubsub Server
- Cause:
- The PubSub server configuration constraints do not allow this action on this channel. This is an informational message.
- Action:
- No action is required.
- BEA-2150012
- Client {0} is an anonymous user but channel {1} requests login.
- Category:
- HTTP Pubsub Server
- Cause:
- Login is requested to perform this action. This is an informational message.
- Action:
- No action is required.
- BEA-2150013
- Client {0} is not allowed to perform action {2} on channel {1}.
- Category:
- HTTP Pubsub Server
- Cause:
- The PubSub server configuration does not allow this action on this channel. This is an informational message.
- Action:
- No action is required.
- BEA-2150014
- Client {0} is allowed to perform action {2} on channel {1}
- Category:
- HTTP Pubsub Server
- Cause:
- The PubSub server configuration is allowing this action to be performed on this channel. This is an informational message.
- Action:
- No action is required.
- BEA-2150015
- Client {0} has no permission to subscribe channel {1}
- Category:
- HTTP Pubsub Server
- Cause:
- Client {0} has no permission to subscribe channel {1}, either because the client configuration does not allow the client to access the channel, or the client is anonymous and the channel configuration only allows specific clients to access the channel.
- Action:
- Check the PubSub server security constraint configuration.
- BEA-2150016
- Client {0} has no permission to publish on channel {1}
- Category:
- HTTP Pubsub Server
- Cause:
- The client is not configured to publish on the channel or the client is anonymous and the channel is configured to only allow access to specific clients.
- Action:
- Check the PubSub server security constraint configuration.
- BEA-2150017
- Failed to register MBean for Channel {0}
- Category:
- HTTP Pubsub Server
- Cause:
- An exception occurred while registering the ChannelRuntimeMBean.
- Action:
- Check the stack trace for more detailed information.
- BEA-2150018
- Failed to unregister MBean for Channel {0}
- Category:
- HTTP Pubsub Server
- Cause:
- An exception occurred while unregistering the ChannelRuntimeMBean.
- Action:
- Check the stack trace for more detailed information.
- BEA-2150019
- Initialize PubSub server {0}
- Category:
- HTTP Pubsub Server
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2150020
- Duplicate initialize PubSub server {0}
- Category:
- HTTP Pubsub Server
- Cause:
- There are multiple servlet and servlet-mapping definitions for com.bea.httppubsub.servlet.ControllerServlet in the web.xml file.
- Action:
- Check the web.xml file.
- BEA-2150021
- Cannot initialize service channel {0}
- Category:
- HTTP Pubsub Server
- Cause:
- An exception occurred when initializing the service channel.
- Action:
- Check the PubSub server configuration.
- BEA-2150024
- Unknown meta channel found from Bayeux message: {0}
- Category:
- HTTP Pubsub Server
- Cause:
- An incoming message specifies a channel other than /meta/handshake, /meta/connect, /meta/reconnect, /meta/disconnect, /meta/subscribe, or /meta/unsubscribe.
- Action:
- Check the Bayeux client and the incoming Bayeux message.
- BEA-2150025
- System property {0} is not set to specify an MBeanManagerFactory implementation.
- Category:
- HTTP Pubsub Server
- Cause:
- System property {0} is not set.
- Action:
- Ensure that runtime MBeans are not necessary; otherwise, set system property {0} to a proper implementation of MBeanManagerFactory.
- BEA-2150026
- Can not initialize instance of MBeanManagerFactory with class {0}
- Category:
- HTTP Pubsub Server
- Cause:
- An exception occurred while initializing MBeanManagerFactory.
- Action:
- Check the stack trace for more detailed information.
- BEA-2150027
- Failed to register WebPubSubRuntimeMBean for PubSub server; the ContextPath is {0}
- Category:
- HTTP Pubsub Server
- Cause:
- An exception occurred while registering WebPubSubRuntimeMBean.
- Action:
- Check the stack trace for more detailed information.
- BEA-2150028
- Failed to unregister WebPubSubRuntimeMBean for PubSub server; the ContextPath is {0}
- Category:
- HTTP Pubsub Server
- Cause:
- An exception occurred while unregistering WebPubSubRuntimeMBean.
- Action:
- Check the stack trace for more detailed information.
- BEA-2150029
- ControllerServlet initialization failed: {0}
- Category:
- HTTP Pubsub Server
- Cause:
- An exception occurred when ControllerServlet was initialized.
- Action:
- Check the exception stack trace for details.
- BEA-2150030
- Cannot fetch JSON message from incoming request
- Category:
- HTTP Pubsub Server
- Cause:
- For long-polling request messages, messages are sent to the server as the body of a POST, encoded either as "application/x-www-form-urlencoded" or as "text/json". If sent as form encoded, the Bayeux messages are sent as the "message" parameter. For callback-polling request messages, messages are sent to the server either using POST requests as per long-polling transport or as the "message" URL parameter of a GET request.
- Action:
- Check the incoming HTTP request and the Bayeux protocol specification.
- BEA-2150031
- Cannot load properties from {0} in classpath.
- Category:
- HTTP Pubsub Server
- Cause:
- The property file does not exist in the classpath.
- Action:
- Check the classpath.
- BEA-2150032
- Cannot find persistent store {0} specified to channel {1}; will use the default store.
- Category:
- HTTP Pubsub Server
- Cause:
- The persistent store may not be configured properly.
- Action:
- Check the configuration of the persistent store.
- BEA-2150033
- Invalid client-timeout-secs: {0}.
- Category:
- HTTP Pubsub Server
- Cause:
- Either a negative or a zero value was set for client-timeout-secs.
- Action:
- Check the PubSub server configuration.
- BEA-2150034
- Invalid interval-millisecs: {0}.
- Category:
- HTTP Pubsub Server
- Cause:
- A negative value was set for interval-millisecs.
- Action:
- Check the PubSub server configuration.
- BEA-2150035
- Invalid multi-frame-interval-millisecs: {0}.
- Category:
- HTTP Pubsub Server
- Cause:
- A negative value wass set for multi-frame-interval-millisecs.
- Action:
- Check tue PubSub server configuration.
- BEA-2150036
- Invalid persistent-client-timeout-secs: {0}.
- Category:
- HTTP Pubsub Server
- Cause:
- Either a negative value or zero was set for persistent-client-timeout-secs.
- Action:
- Check the PubSub server configuration.
- BEA-2150037
- Invalid max-persistent-message-duration-secs: {0}.
- Category:
- HTTP Pubsub Server
- Cause:
- Either a negative value or zero was set for max-persistent-message-duration-secs.
- Action:
- Check the PubSub server configuration.
- BEA-2150038
- Initializing channel authorization manager: {0}
- Category:
- HTTP Pubsub Server
- Cause:
- This channel authorization manager will be used for authorizing channel actions.
- Action:
- No action is required.
- BEA-2150039
- Error initializing channel authorization manager.
- Category:
- HTTP Pubsub Server
- Cause:
- The initialization of channel authorization manager failed.
- Action:
- See the exception stack trace for details.
- BEA-2150041
- Invalid channel {0}, cause is {1}.
- Category:
- HTTP Pubsub Server
- Cause:
- An invalid channel field was found.
- Action:
- Check the Bayeux client.
- BEA-2150042
- A role {0} is being deployed implicitly without a pricipal mapping in the corresponding weblogic.xml.
- Category:
- HTTP Pubsub Server
- Cause:
- There is no security-role-assignment for role {0}
- Action:
- Create a security-role-assignment in weblogic.xml for role {0}
- BEA-2150043
- Security authorization has been disabled for the PubSub server.
- Category:
- HTTP Pubsub Server
- Cause:
- PubSub server security has been disabled by an undocumented system property.
- Action:
- If this property has not been set deliberately, verify all the system properties that begin with com.bea.httppubsub.security.
- BEA-2150044
- Invalid connection-timeout-secs: {0}.
- Category:
- HTTP Pubsub Server
- Cause:
- Either a negative or a zero value was set for connection-timeout-secs.
- Action:
- Check the PubSub server configuration.
- BEA-2150045
- Incoming Bayeux message does not contain 'channel' field.
- Category:
- HTTP Pubsub Server
- Cause:
- Incoming Bayeux message did not contain the 'channel' field.
- Action:
- Turn on Bayeux message debug flag to check the Bayeux message sent by the client.
- BEA-2150046
- Invalid JSON format of a Bayeux message
- Category:
- HTTP Pubsub Server
- Cause:
- A Bayeux message could not be recognized by the JSON parser.
- Action:
- Turn on the Bayeux message debug flag to check the Bayeux message and exception for details.
- BEA-2154000
- Enabling FastSwap on application "{0}".
- Category:
- FastSwap
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-2154001
- Starting FastSwap operation on application "{0}".
- Category:
- FastSwap
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-2154002
- Finished FastSwap operation on application "{0}" with status {1}.
- Category:
- FastSwap
- Cause:
- This message is for informational purposes only.
- Action:
- No action is required.
- BEA-2154003
- FastSwap operation on application "{0}" failed: {1}.
- Category:
- FastSwap
- Cause:
- One or more classes could not be redefined.
- Action:
- Redeploy the application for updates to classes to take effect.
- BEA-2156001
- "config-root" {0} is not a directory.
- Category:
- WebLogicDescriptorWL
- Cause:
- The "config-root" may not have been set properly.
- Action:
- Verify that the "config-root" is correct.
- BEA-2156002
- Attribute "{0}": duration value "{1}" is not valid: {2}
- Category:
- WebLogicDescriptorWL
- Cause:
- The provided duration value was not a valid duration lexical representation.
- Action:
- See the lexical rules for a javax.datatype.Duration, and ensure that the provided duration value is valid according to these rules.
- BEA-2156003
- Attribute "{0}": logical store name value "{1}" is not valid.
- Category:
- WebLogicDescriptorWL
- Cause:
- The provided logical store name value was not a valid name. Logical store names must be valid Java identifiers.
- Action:
- See the lexical rules for a Java identifier, and ensure that the logical store name follows these rules.
- BEA-2156004
- Attribute "{0}": JNDI name value "{1}" is not valid.
- Category:
- WebLogicDescriptorWL
- Cause:
- The provided JNDI name value was not a valid name. JNDI names must be non-null and non-empty and meet the rules of the J2EE platform's JNDI implementation.
- Action:
- See the lexical rules for a JNDI name, and ensure that the JNDI name follows these rules.
- BEA-2156200
- Unable to load descriptor {1} of module {0}. The error is {2}.
- Category:
- Munger
- Cause:
- The descriptor is not valid.
- Action:
- Correct the descriptor.
- BEA-2156201
- An error occurred while parsing descriptors: {0}.
- Category:
- Munger
- Cause:
- Check the stack trace.
- Action:
- Check the stack trace.
- BEA-2156202
- References were found in the deployment plan for module "{0}" with URI, "{1}". The plan was merged.
- Category:
- Munger
- Cause:
- The plan contained variable overrides.
- Action:
- No action is required. This is an informational message.
- BEA-2156203
- A version attribute was not found in element "{0}" in the deployment descriptor {1}. A version attribute is required, but this version of the WebLogic Server will assume that the latest version is used. Future versions of WebLogic Server will reject descriptors that do not specify the Java EE version. To eliminate this warning, add an appropriate "version=" to element "{0}" in the deployment descriptor.
- Category:
- Munger
- Cause:
- The required version attribute was missing.
- Action:
- Add the version attribute with the appropriate JEE version value.
- BEA-2156204
- The root element {0} is missing in the descriptor file {1}.
- Category:
- Munger
- Cause:
- The required root element was missing in the descriptor file.
- Action:
- Add the root element to the descriptor file.
- BEA-2156205
- Updating the configuration with the deployment plan overrides for module "{0}" with URI, "{1}".
- Category:
- Munger
- Cause:
- A deployment plan was specified for the application.
- Action:
- No action is required. This is an informational message.
- BEA-2156206
- No module overrides were found in the deployment plan for module "{0}" with URI, "{1}". If overrides were expected for this module, verify the deployment plan.
- Category:
- Munger
- Cause:
- The plan contained no matching variable overrides.
- Action:
- No action is required. This is an informational message. It may be an expected action.
- BEA-2156207
- The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.
- Category:
- Munger
- Cause:
- The plan contained matching variable overrides.
- Action:
- No action is required. This is an informational message used to troubleshoot deployment plan overrides.
- BEA-2156208
- The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.
- Category:
- Munger
- Cause:
- The plan contained matching variable overrides.
- Action:
- No action is required. This is an informational message used to troubleshoot deployment plan overrides.
- BEA-2156209
- Applying the overrides from the deployment plan for module "{0}" with URI, "{1}".
- Category:
- Munger
- Cause:
- A deployment plan was specified for the application.
- Action:
- No action is required. This is an informational message.
- BEA-2156210
- Applying the override for variable "{0}" with XPath "{1}" and operation "{2}".
- Category:
- Munger
- Cause:
- A deployment plan was specified for the application.
- Action:
- No action is required. This is an informational message.
- BEA-2156211
- After applying the overrides from the deployment plan, the descriptor "{0}" is: "{1}".
- Category:
- Munger
- Cause:
- A deployment plan was specified for the application. The descriptor was updated.
- Action:
- No action is required. This is an informational message.
- BEA-2156212
- An error occurred while parsing the specifed XPath "{0}" : {1}.
- Category:
- Munger
- Cause:
- The specified XPath value was invalid.
- Action:
- Check the associated exception to determine the cause, and correct the XPath value.
- BEA-2156213
- An error occurred while parsing the specifed XPath "{0}" : {1}.
- Category:
- Munger
- Cause:
- The specified XPath value was invalid.
- Action:
- Check the associated exception to determine the cause, and correct the XPath value.
- BEA-2156214
- The XPath "{0}" specifies a key selection but the bean "{1}" does not have any keys defined.
- Category:
- Munger
- Cause:
- The specified XPath value was invalid because no keys were defined for this element.
- Action:
- Check the associated schema, and ensure that the element has the corresponding key.
- BEA-2156215
- Removed the value matched by the deployment plan variable "{0}" with element name "{1}".
- Category:
- Munger
- Cause:
- A deployment plan was specified for the application, and an element has been removed.
- Action:
- No action is required. This is an informational message.
- BEA-2156216
- The deployment plan operation failed because there was no method named "{0}" on the bean "{1}" corresponding to the element "{2}".
- Category:
- Munger
- Cause:
- A deployment plan operation requires a corresponding destroy, remove, or set method. This method was not present.
- Action:
- Contact My Oracle Support.
- BEA-2156217
- An error occurred while performing the plan operation for variable "{0}" with element name "{1}" : {2}.
- Category:
- Munger
- Cause:
- An unexpected exception occurred during the deployment plan operation.
- Action:
- Check the associated exception to determine the cause, and correct the issue.
- BEA-2156218
- Updated the element matched by the deployment plan variable "{0}" with element name "{1}" to have value "{2}".
- Category:
- Munger
- Cause:
- A deployment plan was specified for the application, and a matching element has been updated.
- Action:
- No action is required. This is an informational message.
- BEA-2156219
- Created the element matched by the deployment plan variable "{0}" with element name "{1}".
- Category:
- Munger
- Cause:
- A deployment plan was specified for the application, and a matching element has been created.
- Action:
- No action is required. This is an informational message.
- BEA-2156220
- Created the element matched by the deployment plan variable "{0}" with element name "{1}" to have name "{2}".
- Category:
- Munger
- Cause:
- A deployment plan was specified for the application, and a matching element has been created.
- Action:
- No action is required. This is an informational message.
- BEA-2156221
- The remove operation for the deployment plan variable "{0}" with element name "{1}" specified an array index of "{2}" but the array was smaller, so no elements were removed.
- Category:
- Munger
- Cause:
- The specified array index was larger than the size of the array.
- Action:
- No action is required. This is an informational message.
- BEA-2156222
- The variable "{0}" specifies a property "{1}" that is a primitive array but no index is specified in the XPath.
- Category:
- Munger
- Cause:
- The specified XPath value was invalid since no array index was defined for this element.
- Action:
- Check the XPath, and specify an index.
- BEA-2156223
- The variable "{0}" for the add operation does not specify a property in the XPath "{1}". This variable assignment has been ignored.
- Category:
- Munger
- Cause:
- The specified XPath value was invalid since no property was specified for the add operation.
- Action:
- Check the XPath, and specify a property.
- BEA-2156224
- Added the element matched by the deployment plan variable "{0}" with element name "{1}" with value "{2}".
- Category:
- Munger
- Cause:
- A deployment plan was specified for the application, and a matching element has been added.
- Action:
- No action is required. This is an informational message.
- BEA-2156225
- The XPath "{0}" contains a trailing invalid "/". It has been ignored. Remove it from the XPath expression.
- Category:
- Munger
- Cause:
- The specified XPath value was invalid because it contained a trailing slash.
- Action:
- Remove the trailing slash.
- BEA-2156226
- Skipping the override for the deployment plan variable "{0}" and XPath "{1}" since the value is not set in the deployment plan.
- Category:
- Munger
- Cause:
- A deployment plan did not contain a value for the variable.
- Action:
- Add a variable value if one is desired, or remove the variable assignment if it is not needed.
- BEA-2156227
- The "{0}" deployment descriptor for the "{1}" module is in DTD format. Overrides from the deployment plan will NOT be applied since only deployment descriptors in XML Schema format are supported.
- Category:
- Munger
- Cause:
- A deployment descriptor in DTD format exists in the application archive.
- Action:
- Convert the deployment descriptor to an XML Schema format.
- BEA-2156228
- Updating the configuration with the resource deployment plan overrides for resource "{0}".
- Category:
- Munger
- Cause:
- A resource deployment plan was specified for the application.
- Action:
- No action is required. This is an informational message.
- BEA-2156229
- References were found in the resource deployment plan for resource "{0}". The plan was merged.
- Category:
- Munger
- Cause:
- The plan contained variable overrides.
- Action:
- No action is required. This is an informational message.
- BEA-2156230
- No resource overrides were found in the resource deployment plan for resource "{0}". If overrides were expected for this resource, verify the resource deployment plan.
- Category:
- Munger
- Cause:
- The plan contained no matching variable overrides.
- Action:
- No action is required. This is an informational message. It may be an expected action.
- BEA-2156231
- Applying the overrides from the resource deployment plan for resource "{0}".
- Category:
- Munger
- Cause:
- A resource deployment plan was specified for the application.
- Action:
- No action is required. This is an informational message.
- BEA-2156250
- The value {1} is illegal for {0}. Legal value for this attribute is >= -1. Although the current release of WebLogic Server is accepting this value, future releases may reject the configuration.
- Category:
- WebLogicJavaEEDescriptorValidator
- Cause:
- The current WebLogic Server version accepts this value to support prior releases that allowed arbitrary negative values.
- Action:
- Fix the configuration to specify a value for this parameter in the valid legal range.
- BEA-2156300
- Coherence JAR is in the system classpath and there is more than one instance of CoherenceClusterSystemResourceMBean defined using {0}
- Category:
- CacheProvider
- Cause:
- Multiple instances of CoherenceClusterSystemResourceMBean were targeted.
- Action:
- When the Coherence JAR is in the system classpath, only one CoherenceClusterSystemResourceMBean should be targeted to the server.
- BEA-2156301
- Failed to shut down application {0} due to {1}
- Category:
- CacheProvider
- Cause:
- Failed to shut down application {0} due to {1}
- Action:
- Examine the exception details and take corrective actions.
- BEA-2156302
- Only one server can be a management proxy in a Coherence cluster. {0} has {1} and {2} set as management proxies
- Category:
- CacheProvider
- Cause:
- Only one server can be a management proxy in a Coherence cluster. {0} has {1} and {2} set as management proxies.
- Action:
- Examine the CoherenceMemberConfig management proxy setting for each server.
- BEA-2156303
- Invoking {0} on node {1} resulted in {2}.
- Category:
- CacheProvider
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-2156304
- MBeanServerConnector not available at: {0}
- Category:
- CacheProvider
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-2156400
- The validation.xml file, located at {0}, does not conform to the JSR 303 specifications.
- Category:
- Weblogic-Validation
- Cause:
- The file does not conform to the JSR 303 specification. This maybe because the file is intended to configure another validation framework or because of a typo in the file.
- Action:
- JSR 303 specifies the location of the validator descriptor as either WEB-INF for web application or META-INF for all other cases. A validation.xml file at that location should only be used for the purpose of configuring javax.validation. If the purpose of the file is to configure another validation framework, consider using a different name or placing the file in a different location.
- BEA-2156401
- Invalid URL, {0}, because {1}.
- Category:
- Weblogic-Validation
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-2156402
- Unable to process URL, {0}. Is from jar: {1} resourceDir: {2} resourcePath: {3}.
- Category:
- Weblogic-Validation
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-2156403
- Unable to process URL, {0}, because {1}.
- Category:
- Weblogic-Validation
- Cause:
- The cause of the error is contained in the error message.
- Action:
- Carefully examine the error message to determine the cause of the error and determine the best way to fix it.
- BEA-2156404
- Unable to find a Validation Context. {0}
- Category:
- Weblogic-Validation
- Cause:
- See the message body.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-2156405
- Unable to read resource, {0}, because {1}
- Category:
- Weblogic-Validation
- Cause:
- An IOException has occurred.
- Action:
- Insure that the resource is available for read.
- BEA-2159000
- An exception occurred while the listener {1} processed event {0}. The error is {1}.
- Category:
- InternalEventBus
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Fix the issue related to the embedded root exception. If the listener associated with the exception is an Oracle class, contact My Oracle Support.
- BEA-2159001
- An exception occurred while initializing WLS internal event bus {0}. The error is {1}.
- Category:
- InternalEventBus
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- This is an internal WebLogic Server error and should be reported as a bug to My Oracle Support.
- BEA-2159002
- An exception occurred while loading the listener class {0}. The error is {1}. This listener will not be registered.
- Category:
- InternalEventBus
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Fix the issue related to the embedded root exception. If the listener associated with the exception is an Oracle class, contact My Oracle Support.
- BEA-2159003
- An exception occurred while instantiating an instance of listener class {0}. The error is {1}. This listener will not be registered.
- Category:
- InternalEventBus
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Fix the issue related to the embedded root exception. If the listener associated with the exception is an Oracle class, contact My Oracle Support.
- BEA-2159004
- An exception occurred while registering listeners defined as resources. The error is {1}.
- Category:
- InternalEventBus
- Cause:
- Refer to the embedded exception information for more details as to the probable cause of this error.
- Action:
- Fix the issue related to the embedded root exception. If the listeners associated with the exception are Oracle listeners, contact My Oracle Support.
- BEA-2159005
- An error occurred while processing the WebLogic internal events "{0}". The error is {1}.
- Category:
- InternalEventBus
- Cause:
- See the embedded root exception.
- Action:
- Fix the issue related to the embedded root exception.
- BEA-2159700
- {0}
- Category:
- REST
- Cause:
- REST logs informational messages about REST usage.
- Action:
- No action is required.
- BEA-2159701
- {0}
- Category:
- REST
- Cause:
- REST has encountered an error that is potentially harmful.
- Action:
- Review the warning message text to determine the appropriate action.
- BEA-2159702
- REST encountered the following error: {0}
- Category:
- REST
- Cause:
- REST has encountered an error, but may continue to run.
- Action:
- Review the error message text to determine the appropriate action.
- BEA-2159703
- REST encountered the following error: {0}
- Category:
- REST
- Cause:
- REST has encountered a critical error.
- Action:
- Review the message text to determine the appropriate action.
- BEA-2160000
- Context "{0}" is not a web context. Spring runtime MBeans cannot be created.
- Category:
- WeblogicSpring
- Cause:
- The WeblogicSpringApplicationListener bean was added to (or registered as a listener on) an ApplicationContext that is not a web application context.
- Action:
- Use WeblogicSpringApplicationListener only with a WebApplicationContext.
- BEA-2160001
- WebAppComponentRuntimeMBean not found. Spring runtime MBeans cannot be created.
- Category:
- WeblogicSpring
- Cause:
- See the message detail.
- Action:
- Check for other log messages that give more information about the failure.
- BEA-2160002
- "{0}" is not a registered scope name.
- Category:
- WeblogicSpring
- Cause:
- The scope name supplied to a runtime mbean operation is not registered.
- Action:
- Supply a registered scope name to the runtime mbean operation.
- BEA-2162200
- No Main-Class defined in the manifest file of Java Module: {0}. This module will be treated as a utility JAR and subsequent initialization steps will be skipped.
- Category:
- Application Client
- Cause:
- See the message body.
- Action:
- No action is required unless you believe that this should be a Java client module. In this case, you should specify Main_Class for this module in MANIFEST.MF.
- BEA-2162206
- Warning: Could not find an entry for javax.transaction.UserTransaction in the root context.
- Category:
- Application Client
- Cause:
- There is no entry for javax.transaction.UserTransaction in the root context.
- Action:
- Contact My Oracle Support.
- BEA-2162210
- No persistence unit named ''{0}'' is available in scope.
- Category:
- Application Client
- Cause:
- See the message body.
- Action:
- No action is required.
- BEA-2162224
- No {0} was specified in your client-jar file: {1}.
- Category:
- Application Client
- Cause:
- This is a retired message.
- Action:
- No action is required.
- BEA-2162231
- Warning: Could not bind java:comp/DefaultJMSConnectionFactory due to the following exception - {0}.
- Category:
- Application Client
- Cause:
- Binding java:comp/DefaultJMSConnectionFactory to the application client container failed.
- Action:
- Contact My Oracle Support.
- BEA-2162500
- Class, {0}, was compiled with an incompatible version of Java. Ensure that all the classes needed by the application have been compiled with a compatible java version. {1}
- Category:
- Class Loaders
- Cause:
- This error occurred while attempting to use a class that was compiled with a java compiler version that is not compatible with the JVM used by the application server.
- Action:
- Ensure that this and other classes are compiled with a compiler that is compatible with the JVM used by the application server.
- BEA-2162501
- Class bytes found, but could not define class, {0} due to the following error: {1}
- Category:
- Class Loaders
- Cause:
- The cause of this is unknown.
- Action:
- Contact My Oracle Support for assistance.
- BEA-2162502
- Ignoring manifest file for classpath entry {0}.
- Category:
- Class Loaders
- Cause:
- An error occurred while reading the manifest file for the classpath entry.
- Action:
- Inspect the exception stack trace and correct the problem.
- BEA-2162503
- Not adding pre-processor class {0}.
- Category:
- Class Loaders
- Cause:
- The pre-processor class was not found.
- Action:
- Inspect the exception stack trace and correct the problem.
- BEA-2162504
- Not adding pre-processor class {0}.
- Category:
- Class Loaders
- Cause:
- The pre-processor class could not be intialized.
- Action:
- Inspect the exception stack trace and correct the problem.
- BEA-2162505
- Skipping pre-processing using pre-processor {0} with description: {1}
- Category:
- Class Loaders
- Cause:
- An error was encountered while pre-processing.
- Action:
- Inspect the exception stack trace and correct the problem.
- BEA-2162506
- Ignoring manifest during definition of class {0}.
- Category:
- Class Loaders
- Cause:
- An error occurred while reading the manifest for the jar file. The manifest declaration will be ignored during class definition.
- Action:
- To fix this problem, inspect the exception stack trace, and correct the problem
- BEA-2162507
- Aborting annotation processing due to a symlink cycle. The following directory has been visited already. Path: {0} Cannonical Path: {1}.
- Category:
- Class Loaders
- Cause:
- Symlink cycles in a classes directory tree are causing the directory traversal to repeat the traversal of part of the directory tree indefinitely.
- Action:
- Inspect the classes directory that is related to the reported path for symlink. Ensure that the symlinks do not cause cycling. Differences between the Path and Cannonical Path may suggest where the troublesome symlink lies.
- BEA-2162508
- corrupted jar found. file:{0} ,md5sum:{1}, lastModified:{2}.
- Category:
- Class Loaders
- Cause:
- An error occurred while reading jar file. This means archive corruption.
- Action:
- To fix this problem, inspect the exception stack trace, and correct the problem
- BEA-2162600
- Creating ManagedThreadFactory "{2}" (partition="{3}", module="{0}", application="{1}")
- Category:
- CONCURRENCY
- Cause:
- The application is being initialized.
- Action:
- No action is required.
- BEA-2162601
- Creating ContextService "{2}" (partition="{3}", module="{0}", application="{1}")
- Category:
- CONCURRENCY
- Cause:
- The application is being initialized.
- Action:
- No action is required.
- BEA-2162602
- {0} is still running, create another timer {1}.
- Category:
- CONCURRENCY
- Cause:
- A timer with the same name in ManagedScheduledExecutorService has already been created.
- Action:
- No action is required.
- BEA-2162603
- The value {1} of parameter {0} is illegal.
- Category:
- CONCURRENCY
- Cause:
- The provided parameter value is illegal.
- Action:
- Provide a valid value.
- BEA-2162604
- Unable to create runtime MBean for concurrent managed object {0}. {1}
- Category:
- CONCURRENCY
- Cause:
- A fatal error occurred while creating the runtime MBeans.
- Action:
- Contact My Oracle Support and provide them with the server logs.
- BEA-2162605
- ManagedThreadFactory {0} rejected newThread request as current length reached max capacity {1}, limit type {2}.
- Category:
- CONCURRENCY
- Cause:
- A newThread request was rejected as the capacity was reached.
- Action:
- Configure the MaxConcurrentNewThreads attribute to limit running threads created by ManagedThreadFactory.
- BEA-2162606
- Managed(Scheduled)ExecutorService {0} rejected newThread request as current length reached max capacity {1}, limit type {2}.
- Category:
- CONCURRENCY
- Cause:
- A newThread request was rejected as the capacity was reached.
- Action:
- Configure the MaxConcurrentLongRunningThreads attribute to limit running threads created by Managed(Scheduled)ExecutorService.
- BEA-2162607
- Out-of-date thread {1} is still running when ManagedThreadFactory {0} is restarted.
- Category:
- CONCURRENCY
- Cause:
- A thread was shut down and interrupted when the ManagedThreadFactory was stopped but it was still running when the ManagedThreadFactory was restarted.
- Action:
- No action is required. The thread will be still running in a shutdown and interrupted state.
- BEA-2162608
- ManagedTaskListener registered for task {0} throws exception in method {1}: {2}
- Category:
- CONCURRENCY
- Cause:
- A user-provided ManagedTaskListener implementation may have a defect.
- Action:
- Check your ManagedTaskListener implementation.
- BEA-2162609
- An attempt to process user a transaction failed:{0}
- Category:
- CONCURRENCY
- Cause:
- Transaction processing failed.
- Action:
- No action is required.
- BEA-2162610
- Creating ManagedExecutorService "{4}" (partition="{0}", module="{2}", application="{1}", workmanager="{3}")
- Category:
- CONCURRENCY
- Cause:
- The application is being initialized.
- Action:
- No action is required.
- BEA-2162611
- Creating ManagedScheduledExecutorService "{4}" (partition="{0}", module="{2}", application="{1}", workmanager="{3}")
- Category:
- CONCURRENCY
- Cause:
- The application is being initialized.
- Action:
- No action is required.
- BEA-2162612
- ManagedThreadFactory {0} rejected newThread request as it is in an illegal state such as stopped.
- Category:
- CONCURRENCY
- Cause:
- A newThread request was rejected with an IllegalStateException as the ManagedThreadFactory was in an illegal state such as stopped.
- Action:
- No action is required.
- BEA-2162613
- The invocation of method {0} of a proxy object failed because of the exception: {1}.
- Category:
- CONCURRENCY
- Cause:
- The invocation of method {0} of proxy object failed because of the exception: {1}.
- Action:
- No action is required.
- BEA-2162614
- Workmanager {0} in application {1} could not be found, using default.
- Category:
- CONCURRENCY
- Cause:
- The dispatch-policy attribute is not correct.
- Action:
- Correct the dispatch-policy attribute.
- BEA-2162615
- Concurrent object {2} in application {0} module {1} could not be found, using default.
- Category:
- CONCURRENCY
- Cause:
- The resource-link or mappedName attribute of the resource reference is not correct.
- Action:
- Correct the resource-link or mappedName attribute of the resource reference.
- BEA-2162616
- Proxy is created by a different ContextService object.
- Category:
- CONCURRENCY
- Cause:
- This occurred while trying to get the execution properties on a contextual object proxy that was created by a different ContextService.
- Action:
- No action is required.
- BEA-2162617
- ContextObject is not a valid contextual object proxy created with the createContextualProxy method.
- Category:
- CONCURRENCY
- Cause:
- This occurred while trying to get the execution properties on an invalid contextual object proxy by calling the getExecutionProperties() method of ContextService.
- Action:
- No action is required.
- BEA-2162618
- The instance parameter of createContextualProxy method cannot be null.
- Category:
- CONCURRENCY
- Cause:
- This occurred while trying to create a new contextual object proxy by calling the createContextualProxy method of ContextService but the input object instance was null.
- Action:
- No action is required.
- BEA-2162619
- The interfaces parameter of createContextualProxy method cannot be null.
- Category:
- CONCURRENCY
- Cause:
- This occurred while trying to create a new contextual object proxy by calling the createContextualProxy method of ContextService but no interface was specified.
- Action:
- No action is required.
- BEA-2162620
- Class does not implement at least one of the provided interfaces.
- Category:
- CONCURRENCY
- Cause:
- This occurred while trying to create a new contextual object proxy by calling the createContextualProxy method of ContextService, but the instance does not implement at least one of the provided interfaces.
- Action:
- No action is required.
- BEA-2162621
- Lifecycle related method is not supported.
- Category:
- CONCURRENCY
- Cause:
- An attempt was made to invoke an unsupported lifecycle related method.
- Action:
- No action is required.
- BEA-2162622
- Task list is empty.
- Category:
- CONCURRENCY
- Cause:
- An empty task list was passed to invokeAll/invokeAny.
- Action:
- No action is required.
- BEA-2162623
- Task submission was rejected because executor {0} has been stopped.
- Category:
- CONCURRENCY
- Cause:
- A task was submitted to a stopped executor.
- Action:
- No action is required.
- BEA-2162624
- Task was canceled because concurrent managed object {0} is stopped.
- Category:
- CONCURRENCY
- Cause:
- A task was submitted to a stopped concurrent managed object.
- Action:
- No action is required.
- BEA-2162625
- ManagedExecutorService {0} rejected a newThread request as it is in an illegal state such as stopped.
- Category:
- CONCURRENCY
- Cause:
- A newThread request was rejected with an IllegalStateException as the ManagedExecutorService was in an illegal state such as stopped.
- Action:
- No action is required.
- BEA-2162626
- Task {0} was canceled by user.
- Category:
- CONCURRENCY
- Cause:
- A task was canceled by a user.
- Action:
- No action is required.
- BEA-2162627
- Contextual object proxy deserialization error: {0} is expected but current object is {1}.
- Category:
- CONCURRENCY
- Cause:
- An attempt was made to deserialize a contextual object proxy but the context was not as expected.
- Action:
- No action is required.
- BEA-2162628
- Save contexts failed: {0}.
- Category:
- CONCURRENCY
- Cause:
- An exception occurred while saving the current contexts. The context's setup in the executing thread will be ignored.
- Action:
- No action is required.
- BEA-2162629
- Setup contexts failed: {0}.
- Category:
- CONCURRENCY
- Cause:
- An exception occurred while setting up contexts in the executing thread. The contexts will be rolled back.
- Action:
- No action is required.
- BEA-2162630
- Reset contexts failed: {0}.
- Category:
- CONCURRENCY
- Cause:
- An exception occurred while resetting the current contexts in the executing thread.
- Action:
- No action is required.
- BEA-2162631
- Concurrent managed objects are used before the concurrent service is started. {0}
- Category:
- CONCURRENCY
- Cause:
- Concurrent managed objects were used before the concurrent service was started.
- Action:
- No action is required.
- BEA-2162632
- New thread request was rejected by ManagedThreadFactory {0} because {1}.
- Category:
- CONCURRENCY
- Cause:
- A new thread request was rejected by the limit of maximum new threads or the serialize-deserialize check.
- Action:
- No action is required.
- BEA-2162633
- Contextual object proxy deserialization error: cannot get the expected {0} from cache with key {1}.
- Category:
- CONCURRENCY
- Cause:
- An attempt was made to deserialize a contextual object proxy but no related context can be found in cache. Check the status of the corresponding application to see if the context was released.
- Action:
- No action is required.
- BEA-2162634
- Override {0} is not allowed.
- Category:
- CONCURRENCY
- Cause:
- A task is canceled by a user
- Action:
- No action is required.
- BEA-2162635
- Override is is not allowed.
- Category:
- CONCURRENCY
- Cause:
- The JNDI name was not correct.
- Action:
- No action is required.
- BEA-2162636
- Task {1} submitted to {0} skip partition class loader check.
- Category:
- CONCURRENCY
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-2162637
- Unable to create ConcurrentManagedObjectsRuntimeMBean for partition {0}. {1}
- Category:
- CONCURRENCY
- Cause:
- An exception occurred while creating the ConcurrentManagedObjectsRuntimeMBean.
- Action:
- Contact My Oracle Support and provide them with the server logs.
- BEA-2162638
- Unable to destroy ConcurrentManagedObjectsRuntimeMBean for partition {0}. {1}
- Category:
- CONCURRENCY
- Cause:
- An exception occurred while destroying the ConcurrentManagedObjectsRuntimeMBean.
- Action:
- Contact My Oracle Support and provide them with the server logs.
- BEA-2162639
- Context setup failed because {0} is not started.
- Category:
- CONCURRENCY
- Cause:
- Context setup failed because {0} is not started.
- Action:
- Check the state of the corresponding partition, application or module.
- BEA-2162640
- Unable to create the partition level concurrent manangement object.
- Category:
- CONCURRENCY
- Cause:
- The partition level concurrent manangement object could not be created.
- Action:
- Contact My Oracle Support and provide them with the server logs.
- BEA-2162641
- Trying to unbind a non-existent {0} factory named {1}: {2}
- Category:
- CONCURRENCY
- Cause:
- An attempt was made to unbind a non-existent factory.
- Action:
- Contact My Oracle Support and provide them with the server logs.
- BEA-2162642
- Roll back transaction {0} because it was begun but has not been committed by task {1}.
- Category:
- CONCURRENCY
- Cause:
- The transaction was not committed by the task after it had begun.
- Action:
- Contact My Oracle Support and provide them with the server logs.
- BEA-2162643
- Trigger used for task {0} throws exception in method {1}: {2}
- Category:
- CONCURRENCY
- Cause:
- A Trigger implementation may have a defect.
- Action:
- Check the Trigger implementation.
- BEA-2162644
- {0} belonging to ManagedExecutorService {1}, application {2} was released as the ManagedExecutorService was shutting down.
- Category:
- CONCURRENCY
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-2162645
- {0} belonging to ManagedExecutorService {1}, WorkManager {2}, application {3} was released as the WorkManager was shutdown and the task was not submitted by an administrator.
- Category:
- CONCURRENCY
- Cause:
- This is an information message.
- Action:
- No action is required.
- BEA-2162646
- {0} cannot be used outside of its partition in {1}: {2}
- Category:
- CONCURRENCY
- Cause:
- A concurrent managed object was used outside of its partition.
- Action:
- Check all code that is submitting tasks to the concurrent managed object.
- BEA-2162647
- Application Level {0} cannot be used outside of its application in {1}: {2}
- Category:
- CONCURRENCY
- Cause:
- An application-level concurrent managed object was used outside of its application.
- Action:
- Check all code that is submitting tasks to the concurrent managed object.
- BEA-2162648
- {0} rejected the task because the submitting component {1} was not started: {2}
- Category:
- CONCURRENCY
- Cause:
- A concurrent managed object was used by another component and that component was not started.
- Action:
- Check the state of the submitting component.
- BEA-2162649
- {0} rejected createContextualProxy because it was not started.
- Category:
- CONCURRENCY
- Cause:
- createContextualProxy was rejected with an IllegalArgument exception as the ContextService was not started.
- Action:
- Check the state of the ContextService.
- BEA-2162650
- Context setup failed because the submitting component {0} is not started.
- Category:
- CONCURRENCY
- Cause:
- Context setup failed because the submitting component {0} is not started.
- Action:
- Check the state of the submitting component.
- BEA-2162651
- {0} belonging to ManagedExecutorService {1}, application {2} was released as the submitting application {3} was shutting down.
- Category:
- CONCURRENCY
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2162652
- Long running task was canceled because the submitting application {0} is stopped.
- Category:
- CONCURRENCY
- Cause:
- A long running task was canceled because the submitting application {0} is stopped.
- Action:
- No action is required.
- BEA-2162700
- {0}: Cluster {1} contains {2} running Managed Servers which meets or exceeds the maximum number of allowed servers ({3}). The cluster will not be scaled up.
- Category:
- Elasticity
- Cause:
- The cluster size has already reached the configured Maximum Elastic Cluster Size.
- Action:
- If possible, for example, if additional capacity exists, increase the Maximum Elastic Cluster Size.
- BEA-2162701
- {0}: Cluster {1} contains a sufficient number of available Managed Servers. Cluster will be scaled by {2} servers.
- Category:
- Elasticity
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-2162702
- {0}: Proposed size ({2}) for cluster {1} will exceed the configured maximum size. Limiting cluster size to {3}.
- Category:
- Elasticity
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-2162703
- {0}: Cluster {1} will be expanded by {2} servers.
- Category:
- Elasticity
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-2162704
- {0}: Cluster {1} contains only {2} running Managed Servers which is less or equal to the minimum number of servers ({3}). The cluster will not be scaled down.
- Category:
- Elasticity
- Cause:
- Cluster size has already reached the configured Minimum Elastic Cluster Size.
- Action:
- No action is required.
- BEA-2162705
- {0}: Cluster {1} will be scaled down by {2} servers.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162706
- {0}: Cluster {1} has only {2} running servers. The cluster will be scaled down by {3} servers instead of the requested scaling size {4} since the minimum size of the cluster is {5}.
- Category:
- Elasticity
- Cause:
- There are fewer running servers than what may be necessary to satisfy the request to shut down the specified number of servers.
- Action:
- No action required.
- BEA-2162707
- A suitable Lifecycle Management end point was not found while performing a scaling operation on cluster {0}. The scaling operation will be attempted without Lifecycle Management capabilities.
- Category:
- Elasticity
- Cause:
- A suitable Lifecycle Management end point was not found while performing a scaling operation on the cluster.
- Action:
- No action is required.
- BEA-2162708
- {0}: Unable to scale cluster {1} by the requested amount of {2}, adjusting scaling request to {3} instances.
- Category:
- Elasticity
- Cause:
- The requested capacity likely exceeded the MaxDynamicClusterSize setting for the cluster.
- Action:
- If necessary, increase the MaxDynamicClusterSize on the DynamicServersMBean for the cluster. This may, however, also require that you provision additional hardware capacity.
- BEA-2162709
- {0}: Scaling operation failed to start server {2} for cluster {1}.
- Category:
- Elasticity
- Cause:
- Server startup failed. Check the server log to determine why the startup failed.
- Action:
- Determine what caused the startup to fail, and take corrective action.
- BEA-2162710
- {0}: Cluster {1} scale up, server {2} successfully started.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2162711
- {0}: Scale up work for cluster {1} completed, started {2} new instances.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162712
- {0}: The workflow operation status for the scale-up work was null.
- Category:
- Elasticity
- Cause:
- The scale-up work may not be configured correctly, or this could be a product defect.
- Action:
- Check the server log and contact My Oracle Support if necessary.
- BEA-2162713
- Current size of dynamic cluster {0} is already at maximum: {1}
- Category:
- Elasticity
- Cause:
- The dynamic cluster size maximum was reached.
- Action:
- No action is required.
- BEA-2162714
- Updating max servers count for {0} by {1} to {2}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2162715
- Failed to perform forced shutdown on server {0} during scaledown operation on cluster {1}. {2}
- Category:
- Elasticity
- Cause:
- There may be an environmental problem.
- Action:
- Check other log messages in the log for details.
- BEA-2162716
- Unable to locate ServerLifecycleRuntimeMBean instance for {0}.
- Category:
- Elasticity
- Cause:
- This can result when the cluster size was not successfully adjusted to meet the requested capacity, but the scale-up was attempted.
- Action:
- Check the scaling action and DynamicServersMBean configuration for problems. If a defect is suspected, contact My Oracle Support.
- BEA-2162717
- {0}: Scale down of server {1} completed successfully for cluster {2}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162718
- An unexpected exception occurred trying to start server {0} in cluster {1}. {2}
- Category:
- Elasticity
- Cause:
- An unexpected exception occurred.
- Action:
- Check the server log for other messages for more details.
- BEA-2162719
- Adjusting maximum servers count by requested amount {1} for cluster {0}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162720
- {0}: Scaling operation failed to stop server {2} for cluster {1}.
- Category:
- Elasticity
- Cause:
- Server shutdown failed, check the server log to determine why the startup failed.
- Action:
- Determine what caused the shutdown to fail, and take corrective action.
- BEA-2162721
- {0}: Scale down work for cluster {1} completed, stopped {2} instances.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162722
- {0}: The workflow operation status for the scale-down work was null.
- Category:
- Elasticity
- Cause:
- The scale down work may be misconfigured, or this could be a product defect.
- Action:
- Check the server log and contact My Oracle Support if necessary.
- BEA-2162723
- {0}: Graceful shutdown of server {1} in cluster {2} failed. Performing a forceful shutdown on the server.
- Category:
- Elasticity
- Cause:
- Graceful shutdown may not finish due to reasons such as sessions that may not have migrated within the specified timeout period.
- Action:
- If more time will be needed for quiescing the server before shutdown, increase the value of the DynamicClusterShutdownTimeoutSeconds attribute in the DynamicServersMBean for the cluster.
- BEA-2162724
- {0}: ScriptExecutorCommand executing pre-processor script {1} as configured in script MBean {2} while performing scale up operation for cluster {3}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162725
- {0}: ScriptExecutorCommand executing pre-processor script {1} as configured in script MBean {2} while performing scale down operation for cluster {3}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162726
- {0}: ScriptExecutorCommand executing post-processor script {1} as configured in script MBean {2} while performing scale up operation for cluster {3}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162727
- {0}: ScriptExecutorCommand executing post-processor script {1} as configured in script MBean {2} while performing scale down operation for cluster {3}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162728
- {0}: Pre-processor script {1} as configured in script MBean {2} completed with exit code {4} while performing scale up operation for cluster {3}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162729
- {0}: Pre-processor script {1} as configured in script MBean {2} completed with exit code {4} while performing scale down operation for cluster {3}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162730
- {0}: Post-processor script {1} as configured in script MBean {2} completed with exit code {4} while performing scale up operation for cluster {3}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162731
- {0}: Post-processor script {1} as configured in script MBean {2} completed with exit code {4} while performing scale-down operation for cluster {3}.
- Category:
- Elasticity
- Cause:
- This is an informational message..
- Action:
- No action required.
- BEA-2162732
- ScriptInterceptor adding workflow item for pre-processor script {0} as configured in script MBean {1} for performing scale-up operation for cluster {2}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162733
- ScriptInterceptor adding workflow item for pre-processor script {0} as configured in script MBean {1} for performing scale-down operation for cluster {2}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162734
- ScriptInterceptor adding workflow item for post-processor script {0} as configured in script MBean {1} for performing scale-up operation for cluster {2}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162735
- ScriptInterceptor adding workflow item for post-processor script {0} as configured in script MBean {1} for performing scale-down operation for cluster {2}.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2162736
- {0}: Script interceptor {2} timed out after {4} seconds while executing script {1} for cluster {3}.
- Category:
- Elasticity
- Cause:
- The script did not complete within the specified timeout. The script may be hung or executing slower than expected.
- Action:
- Investigate if the script is hung or depending on resources that may not be responding. Adjust the timeout settings if necessary.
- BEA-2162737
- {0}: Script interceptor {2} failed with exit status {4} while executing script {1} for cluster {3}.
- Category:
- Elasticity
- Cause:
- One or more commands executed by the script failed. In addition, the script may have errors or the interceptor may not be configured correctly.
- Action:
- Check the configuration of the script interceptor and check for errors in the script or its configuration.
- BEA-2162738
- {0}: An unexpected exception occurred while trying to cancel the scale-up operation for server {2} in cluster {1}: {3}
- Category:
- Elasticity
- Cause:
- An unexpected exception occurred.
- Action:
- Check the server log.
- BEA-2162739
- {0}: An unexpected exception occurred while trying to cancel the scale-down operation for server {2} in cluster {1}: {3}
- Category:
- Elasticity
- Cause:
- An unexpected exception occurred.
- Action:
- Check the server log.
- BEA-2162740
- {0}: Server {1} cannot participate in scaling operation because its NodeManager is either not configured correctly or not reachable.
- Category:
- Elasticity
- Cause:
- NodeManager for the server is either not configured correctly or is unreachable.
- Action:
- Check the Machine and NodeManager configuration for the server and ensure that the NodeManager is running properly.
- BEA-2162741
- {0}: Aborting execution of script {1} due to cancel or timeout.
- Category:
- Elasticity
- Cause:
- The script executed by a ScriptInterceptor was aborted due to a cancel operation or timeout.
- Action:
- No action required.
- BEA-2162742
- Scaling operation with Lifecycle Management endpoint {0} failed. Please check endpoint configuration and ensure that the lifecycle runtime service is running.
- Category:
- Elasticity
- Cause:
- The lifecycle management endpoint may be misconfigured, or the lifecycle runtime service may not be running or is accessible.
- Action:
- Ensure that the url and credential information of the lifecycle management endpoint is correct. Ensure also that the lifecycle runtime service is running and accessible from the Administration Server.
- BEA-2162743
- An unexpected exception occurred trying to shut down server {0} in cluster {1}. {2}
- Category:
- Elasticity
- Cause:
- An unexpected exception occurred.
- Action:
- Check the server log for other messages for more details.
- BEA-2162744
- An error occurred while trying to update size for cluster {0}. {2}
- Category:
- Elasticity
- Cause:
- The configuration update failed. It may be due to several factors such as locked down configuration, timeouts, or another issue.
- Action:
- Check the server log for other messages for more details.
- BEA-2162745
- {0}: An error occurred trying to scale cluster {1}. Scaling operation failed because there is another scaling activity occurring on cluster {1} .
- Category:
- Elasticity
- Cause:
- The scaling operation failed because there is another scaling activity occurring on the same cluster.
- Action:
- Initiate the scaling activity after the current activity finishes.
- BEA-2162746
- {0}: An error occurred while trying to scale cluster {1}. Scaling operation failed because the cluster {1} is in cool-off period and cannot be scaled for another {2} seconds.
- Category:
- Elasticity
- Cause:
- The scaling operation failed because the cluster cannot be scaled during the cool-off period.
- Action:
- Initiate the scaling activity after the specified cool-off period.
- BEA-2162747
- {0}: Scale-up operation on cluster {1} started.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2162748
- {0}: Scale-down operation on cluster {1} started.
- Category:
- Elasticity
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2163000
- OSGi system {2} could not install bundle from file {0} due to {1}
- Category:
- OSGi
- Cause:
- The OSGi system failed to install a bundle from a file.
- Action:
- Fix the problem that is indicated in the error message and then restart the server.
- BEA-2163001
- OSGi system {2} could not advertise data source {0} due to {1}
- Category:
- OSGi
- Cause:
- The OSGi system failed to advertise a data source.
- Action:
- Fix the problem that is indicated in the error message and then restart the server.
- BEA-2163002
- OSGi system {0} could not install bundles from $WL_HOME/server/osgi-lib.
- Category:
- OSGi
- Cause:
- At least one bundle from the $WL_HOME/server/osgi-lib directory could not be installed.
- Action:
- Examine the bundles that failed to install, fix them, and then restart the server.
- BEA-2163003
- Started OSGi system {0}.
- Category:
- OSGi
- Cause:
- An OSGi system has started.
- Action:
- Write modular code and deploy it onto your OSGi system.
- BEA-2163004
- OSGi system {2} could not advertise work manager {0} due to {1}
- Category:
- OSGi
- Cause:
- The OSGi system failed to advertise a work manager
- Action:
- Fix the problem that is indicated in the error message and then restart the server.
- BEA-2163005
- An application could not be deployed because it had conflicting OSGi framework names in its metadata. The OSGi framework names {0} and {1} were found.
- Category:
- OSGi
- Cause:
- More than one OSGi system was referenced in the application metadata files.
- Action:
- Modify the metadata files of the application such that the application references only one framework.
- BEA-2163006
- An application could not be deployed because it had conflicting OSGi bundle symbolic names in its metadata. The bundle symbolic names {0} and {1} were found.
- Category:
- OSGi
- Cause:
- More than one OSGi bundle was referenced in the application metadata files.
- Action:
- Modify the metadata files of the application such that the application references only one bundle.
- BEA-2164000
- The specified partition "{0}" does not exist in the domain.
- Category:
- Deployer
- Cause:
- A partition needs to exist in the domain before deploying to it.
- Action:
- Create the specified partition before deploying to it.
- BEA-2164001
- Start and stop operations are not supported for resources at the resource group template level.
- Category:
- Deployer
- Cause:
- Start and stop operations are not supported for resources at the resource group template level.
- Action:
- Start and stop resources at the referencing resource group level.
- BEA-2164002
- The specified resource group "{0}" does not exist in the specified partition "{1}".
- Category:
- Deployer
- Cause:
- A resource group needs to exist before deploying to it.
- Action:
- Create the specified resource group before deploying to it.
- BEA-2164003
- The specified resource group template "{0}" does not exist in the domain.
- Category:
- Deployer
- Cause:
- A resource group template needs to exist before deploying to it.
- Action:
- Create the specified resource group template before deploying to it.
- BEA-2164004
- The resource group name cannot be derived in this case. Specify the resource group option along with the partition option.
- Category:
- Deployer
- Cause:
- A resource group option must be specified with the partition option in cases where it cannot be derived.
- Action:
- Specify the resource group option with the partition option.
- BEA-2164005
- A resource group template option cannot be specified with a resource group option.
- Category:
- Deployer
- Cause:
- A resource group template option and resource group option were specified together.
- Action:
- Either specify the resource group template option or specify the resource group option.
- BEA-2164007
- The specified resource group "{0}" does not exist in the domain.
- Category:
- Deployer
- Cause:
- A resource group needs to exist before you can deploy to it.
- Action:
- Create the specified resource group before deploying to it.
- BEA-2164008
- The override of the deployment plan was already removed.
- Category:
- Deployer
- Cause:
- The override of the plan cannot be removed because it was already removed.
- Action:
- No action is required.
- BEA-2164009
- A resource group template option cannot be specified in a partition context.
- Category:
- Deployer
- Cause:
- A partition administrator cannot operate on a resource group template.
- Action:
- Operate on a resource group template outside of the partition context.
- BEA-2164011
- A resource group option cannot be specified in this operation.
- Category:
- Deployer
- Cause:
- A resource group option was specified but is not supported in this operation.
- Action:
- Retry the operation without the resource group option.
- BEA-2164012
- Unable to perform the {1} request for application "{0}". Either the application does not exist, or it is deployed to a resource group template referenced by resource group "{2}".
- Category:
- Deployer
- Cause:
- The application name was likely misspelled, or it is deployed to a resource group template but no resourceGroupTemplate option value was provided.
- Action:
- Verify that the application is correctly named, or provide a resource group template name using the resourceGroupTemplate option if application is deployed to a resource group template, or remove the reference to the resource group template from the resource group.
- BEA-2164013
- Unable to perform the {1} request for application "{0}". Operation cannot be performed until the server is restarted. Either the application does not exist, or it is deployed to a resource group template referenced by resource group "{2}".
- Category:
- Deployer
- Cause:
- The application name was either misspelled, was created after non-dynamic changes were activated, or it is deployed to a resource group template but no resourceGroupTemplate option value is provided. The server needed to be restarted.
- Action:
- Verify that the application is correctly named, or provide a resource group template name using the resourceGroupTemplate option if the application is deployed to a resource group template, or remove the reference to the resource group template from the resource group. Then restart the server and start the application. In the future, start the application before making non-dynamic changes to the configuration.
- BEA-2164014
- The deployment task "{0}" for application "{1}" was canceled.
- Category:
- Deployer
- Cause:
- The deployment task was canceled by the adminstrator or due to an error.
- Action:
- No action is required if the the task was explicitly canceled.
- BEA-2164015
- Application or library version must be specified during undeployments from a resource group template if more than one version exists.
- Category:
- Deployer
- Cause:
- It is not possible to find our the active version given a resource group template because the state of an application is defined in the context of a partition, not by a resource group template alone.
- Action:
- If the intent it to undeploy the application or library from all partitions that refer to this resource group template, provide version information for this application or library.
- BEA-2164016
- Cannot start an application which is in a shutdown partition {0} or resource group {1}.
- Category:
- Deployer
- Cause:
- An administrator is trying to start an application which is in a shutdown partition or resource group.
- Action:
- An application will be started when the partition or resource group is started.
- BEA-2164017
- Implicitly retiring {0} during managed server startup
- Category:
- Deployer
- Cause:
- A newer version of the application could have been deployed since this server was last booted
- Action:
- No action needs to be taken
- BEA-2164018
- More than one non-retiring app ids found on server startup: {0}
- Category:
- Deployer
- Cause:
- The older version might not have been retired yet
- Action:
- No action needs to be taken
- BEA-2164019
- More than one retiring app ids found on server startup: {0}
- Category:
- Deployer
- Cause:
- A newer version of the application could have been deployed since this server was last booted
- Action:
- More than one production redeploy might have been performed
- BEA-2164020
- There is no application named "{0}" in the system. However, there is a pending configuration change which does have an application named "{0}". The user must decide to either delete the pending transaction or commit the pending transaction before the {1} operation can be performed.
- Category:
- Deployer
- Cause:
- It is either because the user has started a configuration edit transaction but has not yet committed it yet, or it is possible that an existing edit transaction was underway and the admin server has rebooted. In either case some user must decide to either abandon the existing user transaction or commit the existing user transaction to perform the operation given in the message.
- Action:
- Some administrative user must decide to either abandon the existing configuration transaction or to commit the existing configuration transaction before issuing this command to the given application.
- BEA-2164021
- Application {0} is marked for retirement at {1} in future. This app will not be implicitly retired at this time {2}
- Category:
- Deployer
- Cause:
- The reiterment time is valid but set to some time in the future
- Action:
- No action needs to be taken
- BEA-2164022
- Entry for module {1} is being removed from app runtime state of application {0} during server startup
- Category:
- Deployer
- Cause:
- Applciation source could have changed while the server was shutdown
- Action:
- No action needs to be taken
- BEA-2164023
- Failed to deploy new version {1} of configured application {0} {3}
- Category:
- Deployer
- Cause:
- Underlying exception in deployment {4}
- Action:
- Address the underlying exception. If the exception is because of the new version, fix it and introduce it as a new version
- BEA-2164024
- Failed to properly retire old version {1} of configured application {0} {2}
- Category:
- Deployer
- Cause:
- Underlying exception in deployment {3}
- Action:
- No action needs to be taken
- BEA-2164025
- Failed to read deployment-config-overrides.xml file at path {0} {1}
- Category:
- Deployer
- Cause:
- Underlying exception in deployment {2}
- Action:
- Address the underlying exception and fix the problem with file system
- BEA-2164026
- Initiating deployment of new version of configured application {0}. The new generated version is {1} and it will be deployed from {2}
- Category:
- Deployer
- Cause:
- The new version of application must have been specified in a the updated deployment-config-overrides.xml
- Action:
- No action needs to be taken at this time
- BEA-2164027
- Completed deployment of new generated version {1} of configured application {0}
- Category:
- Deployer
- Cause:
- The new version of application must have been specified in a the updated deployment-config-overrides.xml
- Action:
- No action needs to be taken at this time
- BEA-2164028
- Scheduling retirement for generated version {1} of configured application {0} in {2} seconds
- Category:
- Deployer
- Cause:
- The new version of application must have been specified in a the updated deployment-config-overrides.xml. That version must have successfully deployed, so the old version is being retired
- Action:
- No action needs to be taken at this time
- BEA-2164029
- Initiating retirement of old generated version {1} of configured application {0}
- Category:
- Deployer
- Cause:
- The new version of application must have been specified in a the updated deployment-config-overrides.xml. That version must have successfully deployed, so the old version is being retired
- Action:
- No action needs to be taken at this time
- BEA-2164030
- Completed retirement of old generated version {1} of configured application {0}
- Category:
- Deployer
- Cause:
- The new version of application must have been specified in a the updated deployment-config-overrides.xml. That version must have successfully deployed, so the old version is being retired
- Action:
- No action needs to be taken at this time
- BEA-2164031
- Ignoring a modified deployment-config-overrides.xml because previous processing started at {0} has not completed yet
- Category:
- Deployer
- Cause:
- Changes to deployment-config-overrides.xml from a previous poll are still being processed. So the current poll will be ignored
- Action:
- No action needs to be taken at this time
- BEA-2164032
- Cancelling {2} for generated version {1} of {0} since MSID infrastructure is being torn down
- Category:
- Deployer
- Cause:
- MSID infrastructure is being torn down, most likely due to server shutdown. All in-flight work will be cancelled.
- Action:
- No action needs to be taken at this time
- BEA-2164033
- Invalid value of retire-timeout {2} found in deployment-config-overrides.xml for generated version {1} of {0}. This value must be a non-negative integer. This value is being ignored, domain wide default {3} will be used instead
- Category:
- Deployer
- Cause:
- Retire timeout configuration cannot be processed if it is not a number, or if it is negative.
- Action:
- Correct the value of retire-timeout in deployment-config-overrides.xml
- BEA-2164034
- The processing of the MSID application [{0}] is blocked. Current count of old app version [{1}] reaches the maxiumum number of old app versions [{2}] threshold.
- Category:
- Deployer
- Cause:
- The current count of old app version reaches max old app versions threshold. Processing of the next MSID application is blocked till the count drops below the threshold.
- Action:
- You can wait for the count of old app version drops below the threshold, or configure the max-old-app-versions property in DeploymentConfigOverridesMBean to increase the threshold.
- BEA-2164035
- The processing of the MSID application is unblocked. Current count of old app version [{0}] drops below the maximum number of old app versions [{1}] threshold.
- Category:
- Deployer
- Cause:
- The current count of old app version drops below max old app versions threshold. Processing of the next MSID application is now unblocked.
- Action:
- No action needs to be taken at this time
- BEA-2164036
- An attempt was made to execute the "{0}" operation on an application named "{1}" that is not currently available. The application may have been created after non-dynamic configuration changes were activated; or this server has gone out-of-sync with the admin server so it is unaware of the application. Allow the "{0}" operation to pass through so it does not affect "{0}" operation performed on other in-sync server instances. Please restart this server at earliest convenience to get things back in sync.
- Category:
- Deployer
- Cause:
- The application may have been created after non-dynamic changes were activated, or this server has gone out-of-sync with the admin server so it is unaware of the application.
- Action:
- Restart the server at earliest convenience to get things back in sync.
- BEA-2165000
- Resource Consumption Management service initialization started.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165001
- Resource Consumption Management service initialization completed.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165002
- Resource Consumption Management resource class was not found. An error occurred during initialization: {0}
- Category:
- RCM
- Cause:
- A resource class name was not found.
- Action:
- Check the "config.xml" file. Verify the resource class name or the configuration.
- BEA-2165003
- Resource Consumption Management resource runtime MBean is not registered. An error occurred during initialization of runtime MBeans: {0}
- Category:
- RCM
- Cause:
- There was an error while registering runtime MBeans.
- Action:
- Check the exception for the exact error message.
- BEA-2165004
- Trigger value is updated for an Resource Consumption Management resource.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165005
- New trigger is added to an Resource Consumption Management resource.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165006
- Trigger is removed for an Resource Consumption Management resource.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165007
- Resource Consumption Management resource is added to Resource Manager.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165008
- Resource Consumption Management Resource is removed from Resource Manager.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165009
- Resource Consumption Management resource manager is added to Resource Management.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165010
- Resource Consumption Management resource manager is removed from Resource Management.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165011
- Resource Consumption Management resource manager is added to the partition.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165012
- Resource Consumption Management resource manager is removed from the partition.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165013
- Updating resource manager reference at the partition.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165014
- Updating resource manager reference at the partition, moving current usage to the new resource manager.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165015
- Trying to update a resource manager reference at the partition but can not proceed as Current Usage is more than the new value specified at the Trigger level.
- Category:
- RCM
- Cause:
- Current Usage was more than the new value specified at the Trigger level.
- Action:
- Increase the Trigger value for a shutdown or fail action.
- BEA-2165016
- FairShare is removed for the Resource Consumption Management resource.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165017
- New FairShare is added to the Resource Consumption Management resource.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165018
- Resource Consumption Management Notification Withdraw Message: Notification action has been withdrawn because the quota has been reached below the given trigger value.
- Category:
- RCM
- Cause:
- This is an informational message for a withdrawal notification action under Resource Consumption Management.
- Action:
- This is a log message based on a "notify" trigger specified for the resource under Resource Consumption Management. If you want, you can use the WebLogic Diagnostic Framework(WLDF) to define different rules for this notification.
- BEA-2165019
- "ResourceManagement" is not supported in this JDK. Use Oracle JDK 8u40 or later which supports "ResourceManagement", to use the WebLogic Server "Resource Consumption Management" feature.
- Category:
- RCM
- Cause:
- "ResourceManagement" is not supported in the JDK used to start the WebLogic Server.
- Action:
- Use Oracle JDK 8u40 or later.
- BEA-2165020
- FairShare was updated to the Resource Consumption Management resource.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165021
- "ResourceManagement" is not enabled in this JVM. Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature. To enable "ResourceManagement", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.
- Category:
- RCM
- Cause:
- "ResourceManagement" is not enabled in this JVM.
- Action:
- Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature.
- BEA-2165022
- The process of creating the Resource Consumption Management Diagnostic Image has been timed out by the Diagnostic Framework. The resulting image may be incomplete.
- Category:
- RCM
- Cause:
- The process of creating the Resource Consumption Management Diagnostic Image has been timed out by the Diagnostic Framework.
- Action:
- Investigate the contents of the log and Diagnostic Images for more information.
- BEA-2165023
- Resource Consumption Management Fail Withdraw Message: Fail action has been withdrawn because the quota dropped below the given trigger value.
- Category:
- RCM
- Cause:
- This is an informational message for a withdrawal fail action under Resource Consumption Management.
- Action:
- This is a log message based on a fail trigger specified for the resource under Resource Consumption Management. If you want, you can use WebLogic Diagnostic Framework(WLDF) to define different rules for this notification.
- BEA-2165024
- "ResourceManagement" is not supported in this JDK, but found a "Resource Consumption Management" policy configuration in the WebLogic Server for partition "{0}". Use Oracle JDK 8u40 or later which supports "ResourceManagement", to use the WebLogic Server "Resource Consumption Management" feature.
- Category:
- RCM
- Cause:
- "ResourceManagement" is not supported in the JDK used to start the WebLogic Server.
- Action:
- Use Oracle JDK 8u40 or later.
- BEA-2165025
- "ResourceManagement" is not enabled in this JVM, but found a "Resource Consumption Management" policy configuration in the WebLogic Server for partition "{0}". Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature. To enable "ResourceManagement", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.
- Category:
- RCM
- Cause:
- "ResourceManagement" is not enabled in this JVM.
- Action:
- Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature.
- BEA-2165026
- System Accounting flag is turned on. All resources consumed for performing System work by a Partition are tracked separately and not included in the Partition''s resource consumption values. If there are any Resource Consumption Management Policies(Triggers) configured, they will not be accounting system context based resource consumption. Similarly, Partition Resource Metrics will not include system context based resource consumption.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- When "System Accounting" feature is enabled, Resource Consumption Management policies established for a Partition would not include the resources consumed for a Partition to execute System work. If the Resource Consumption Management policies established for a Partition must track all resources used for a Partition, disable the "System Accounting" feature.
- BEA-2165027
- "Resource Consumption Management" policy for "Heap Retained" resource is defined in the WebLogic Server for partition "{0}". However "Heap Retained Metric" is not available in WebLogic Server.Resource Consumption Management" policy for "Heap Retained" resource can not be activated if "Heap Retained Metric" is not available. "Heap Retained Metric" is unavailable if "G1 Garbage Collector" is not enabled in the WebLogic Server JVM. Please enable "G1 Garbage Collector" to use "Heap Retained Metric" in WebLogic Server. To enable "G1 Garbage Collector", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UseG1GC.
- Category:
- RCM
- Cause:
- "Heap Retained Metric" is not available in WebLogic Server but found a "Resource Consumption Management" policy configuration for "Heap Retained" resource in the WebLogic Server for partition "{0}"
- Action:
- Enable "G1 Garbage Collector", Please specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UseG1GC.
- BEA-2165028
- "Heap Retained Metric" is not available in WebLogic Server."Resource Consumption Management" support for "Heap Retained" resource is not available. "Heap Retained" resource is available only with "G1 Garbage Collector".
- Category:
- RCM
- Cause:
- "Heap Retained Metric" is not available in WebLogic Server.
- Action:
- If "Resource Consumption Management" support for "Heap Retained" resource is needed , please enable "G1 Garbage Collector" by specifying the following JVM options in the WebLogic Server instance in which the JVM runs:-XX:+UseG1GC.
- BEA-2165029
- Resource Consumption Management Restart Message: Given quota has been reached for the partition and a "restart" action has been executed.
- Category:
- RCM
- Cause:
- Given quota for the resource under Resource Consumption Management was reached for the partition and a "restart" action was executed. The partition was restarted due to this action.
- Action:
- No action is required.
- BEA-2165030
- Resource Consumption Management Restart Message: Partition has been restarted the maximum number of times as a result of resource consumption management "restart" action, in the duration, as specified in the partition config. Partition can not be restarted anymore, and is being shutdown.Partition would have to be started manually.
- Category:
- RCM
- Cause:
- There are many attempts to "restart" the partition in configured duration.In order to prevent restart action going in a loop ,a "shutdown" action is executed.
- Action:
- There are many attempts to "restart" the partition in configured duration. You can reconfigure max-restart-allowed and max-restart-allowed-interval with higher value if this is expected behaviour .
- BEA-2165031
- Resource Consumption Management : Partition restart is unsuccessful. It failed with an error : {0}
- Category:
- RCM
- Cause:
- There was an error while restarting the partition.
- Action:
- Check the exception for the exact error message.
- BEA-2165032
- Restart Loop Protection updated for a Resource Consumption Management Resource Manager.
- Category:
- RCM
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2165799
- Resource Consumption Management Notification Message: Given quota has been reached for the partition and a "notify" action has been executed.
- Category:
- RCM
- Cause:
- Given quota for the resource under Resource Consumption Management was reached for the partition and a "notify" action was executed.
- Action:
- This is a log message based on a "notify" trigger specified for the resource under Resource Consumption Management. If you want, you can use the WebLogic Diagnostic Framework(WLDF) to define different rules for this notification.
- BEA-2165800
- Resource Consumption Management Slow Message: Given quota has been reached for the partition and a "slow" action has been executed.
- Category:
- RCM
- Cause:
- Given quota for the resource under Resource Consumption Management was reached for the partition and a "slow" action was executed.The partition was slowed down due to this action.Once the resource consumption drops below the specified quota, partition would be un-slowed.
- Action:
- No action is required.
- BEA-2165801
- Resource Consumption Management Shutdown Message: Given quota has been reached for the partition and a "shutdown" action has been executed.
- Category:
- RCM
- Cause:
- Given quota for the resource under Resource Consumption Management was reached for the partition and a "shutdown" action was executed. The partition was stopped due to this action.
- Action:
- The partition has been stopped. Restart the partition manually. Use the Administration Console or WebLogic Diagnostic Framework(WLST) to start the partition.
- BEA-2165802
- Resource Consumption Management Fail Message: Given quota has been reached for the partition and a "fail" action has been executed.
- Category:
- RCM
- Cause:
- Given quota for the resource under Resource Consumption Management was reached for the partition and a "fail" action was executed. The resource consumption request failed due to this action.
- Action:
- Reissue the request.
- BEA-2165803
- Resource Consumption Management Un-slow Message: Slow action is "withdraw" as quota has been reached below the given trigger value.
- Category:
- RCM
- Cause:
- Slow action was withdrew as quota reached below the given trigger value for the resource under Resource Consumption Management .
- Action:
- No action is required.
- BEA-2165804
- Resource Consumption Management : Unable to successfully execute action {0}. It failed with an error : {1}
- Category:
- RCM
- Cause:
- There was an error while executing the indicated action.
- Action:
- Check the exception for the exact error message.
- BEA-2165805
- Resource Consumption Management : Unable to successfully withdraw action {0}. It failed with an error : {1}
- Category:
- RCM
- Cause:
- There was an error while withdrawing the indicated action.
- Action:
- Check the exception for the exact error message.
- BEA-2166001
- Message "{0}" Exception: {1}
- Category:
- LCM
- Cause:
- This message displays output from the script.
- Action:
- No action is required.
- BEA-2166002
- Exception Loading Plugins during LCM bootstrap: {0}
- Category:
- LCM
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Ensure LCM Plugins are in Plugin directory.
- BEA-2166003
- Exception getting the LCM Configuration File: {0}
- Category:
- LCM
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Ensure LCM Configuration file is present in Domain Config Directory.
- BEA-2166004
- Exception Setting up File Watcher for LCM Configuration File: {0}
- Category:
- LCM
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Ensure LCM Configuration file is present in Domain Config Directory.
- BEA-2166005
- Exception reloading LCM Configuration File: {0}
- Category:
- LCM
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Ensure LCM Configuration file is present in Domain Config Directory.
- BEA-2166201
- Could not shutdown server {0}
- Category:
- LCM_WLS_Plugin
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Take appropriate action based on the details provided in the exception.
- BEA-2166202
- Could not shutdown server {0}
- Category:
- LCM_WLS_Plugin
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Take appropriate action based on the details provided in the exception.
- BEA-2166203
- Could not get server mbean details for {0}
- Category:
- LCM_WLS_Plugin
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Take appropriate action based on the details provided in the exception.
- BEA-2190000
- {0} ERROR DATA recv on CLOSED messageId {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}
- Category:
- BuzzMessageBus
- Cause:
- Data was received after the message was closed.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190001
- {0} ERROR DATA recv on zero messageId {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}
- Category:
- BuzzMessageBus
- Cause:
- Data was received with an illegal messageId.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190002
- {0} ERROR INIT recv after INIT, releasing endpoint {1} peer: {2}/{3} local: {4}/{5}
- Category:
- BuzzMessageBus
- Cause:
- An INIT was received after a previous INIT.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190003
- {0} ERROR INIT recv frame too short {1}
- Category:
- BuzzMessageBus
- Cause:
- An INIT frame was received that is not long enough.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190004
- {0} ERROR INIT recv version mismatch {1} peer: {2}/{3} local: {4}/{5}
- Category:
- BuzzMessageBus
- Cause:
- An INIT frame was received with version information that cannot be matched.
- Action:
- Verify that the correct versions of all software are installed. If the problem persists, contact My Oracle Support and provide them with the logs.
- BEA-2190005
- {0} ERROR message received before connection initialized {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}
- Category:
- BuzzMessageBus
- Cause:
- A message was received before the connection was initialized.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190006
- {0} ERROR recv message too short {1} bytes: {2}
- Category:
- BuzzMessageBus
- Cause:
- A received message was too short.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190007
- {0} START recv for existing messageId {1} flags: {2} subprotocol: {3} messageId: {4}
- Category:
- BuzzMessageBus
- Cause:
- A START frame was received for an existing messageId.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190008
- {0} ERROR ignoring START message received on endpoint in GRACEFUL_SHUTDOWN state {1} flags: {2} subprotocol: {3} messageId: {4} connectionState: {5}
- Category:
- BuzzMessageBus
- Cause:
- A START frame was received but the endpoint is shutting down.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190009
- {0} ERROR START recv on messageId zero {1} flags: {2} subprotocol: {3}
- Category:
- BuzzMessageBus
- Cause:
- A START was received with an illegal messageId.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190010
- {0} ERROR recv subprotocol mismatch {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} subprotocol of previous message {6}
- Category:
- BuzzMessageBus
- Cause:
- A message was received with a subprotocol that does not match the previous subprotocol for the same messageId.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190011
- {0} ERROR recv unknown error code {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} errorCode: {6}
- Category:
- BuzzMessageBus
- Cause:
- A message was received with an unknown error code.
- Action:
- Verify that the correct versions of all software are installed. If the problem persists, contact My Oracle Support and provide them with the logs.
- BEA-2190012
- {0} ERROR recv unknown frame type {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}
- Category:
- BuzzMessageBus
- Cause:
- A message was received with an unknown frame type.
- Action:
- Verify that the correct versions of all software are installed. If the problem persists, contact My Oracle Support and provide them with the logs.
- BEA-2190013
- {0} ERROR INTERNAL open or close admin receiver threw exception (ignored) {1} adminReceiver: {2}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzAdminReceiver threw an exception in its #close or #open method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190014
- {0} ERROR INTERNAL graceful shutdown ack received admin receiver threw exception (ignored) {1} adminReceiver: {2}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzAdminReceiver threw an exception in its #gracefulShutdown method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190015
- {0} ERROR INTERNAL graceful shutdown ack admin receiver threw exception (ignored) {1} adminReceiver: {2}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzAdminReceiver threw an exception in its #gracefulShutdown method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190016
- {0} ERROR INTERNAL connect or release receiver threw exception (ignored) {1} subprotocol: {2} subprotocolReceiver: {3} eventType: {4}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzSubprotocolReceiver threw an exception in its #connect or #release method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190017
- {0} ERROR INTERNAL receipt receiver threw exception (ignored) {1} subprotocol: {2} subprotocolReceiver: {3} receiptCookie: {4}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzSubprotocolReceiver threw an exception in its #receipt method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190018
- {0} ERROR INTERNAL backlog receiver threw exception (ignored) {1} subprotocol: {2} subprotocolReceiver: {3} isExcessive: {4}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzSubprotocolReceiver threw an exception in its #backlog method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190019
- {0} ERROR INTERNAL graceful shutdown ack sent done receiver threw exception (ignored) {1} subprotocol: {2} subprotocolReceiver: {3}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzSubprotocolReceiver threw an exception in its #gracefulShutdown method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190020
- {0} ERROR INTERNAL subprotocol receiver threw exception (ignored) {1} frameType: {2} flags: {3} subprotocol: {4} messageId {5} subprotocolReceiver: {6}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzSubprotocolReceiver threw an exception in its #receive method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190021
- {0} ERROR INTERNAL graceful shutdown receiver threw exception (ignored) subprotocol: {1} subprotocolReceiver: {2} gracefulShutdownState: {3}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzSubprotocolReceiver threw an exception in its #gracefulShutdown method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190022
- {0} ERROR INTERNAL subprotocol internal receiver threw exception (ignored) {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} subprotocolReceiver: {6}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzSubprotocolReceiverInternalApi threw an exception in its #receiveRstInternal method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190023
- {0} ERROR INTERNAL graceful shutdown internal receiver threw exception (ignored) {1} subprotocol: {2} errorCode: {3} subprotocolReceiver: {4}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzSubprotocolReceiverInternalApi threw an exception in its #receiveGsdInternal method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190024
- {0} ERROR INTERNAL EventCollector exception (ignored) {1}
- Category:
- BuzzMessageBus
- Cause:
- Collector.add threw an exception which will be ignored.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190025
- {0} ERROR exception in tryRelase (ignored) {1} extra: msg
- Category:
- BuzzMessageBus
- Cause:
- An exception occurred in TryRelease (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190026
- {0} ERROR INTERNAL POTENTIAL RDMA MEMORY LEAK no subprotocol receiver for receipt cookie {1} receiptCookie: {2}
- Category:
- BuzzMessageBus
- Cause:
- There is no subprotocol receiver for the receipt cookie. This may be due to an RDMA memory leak.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190027
- {0} ERROR INTERNAL incorrect event type in connect release receiver {1} eventType: {2}
- Category:
- BuzzMessageBus
- Cause:
- There is an INTERNAL incorrect event type in the connect release receiver.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190028
- {0} ERROR INTERNAL POTENTIAL RDMA MEMORY LEAK unknown receipt type {1} receiptCookie: {2}
- Category:
- BuzzMessageBus
- Cause:
- An unknown receipt type was encountered. This may be due to an RDMA memory leak.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190029
- {0} ERROR INTERNAL recv exception reading BufferSequenceInputStream {1} bytes: {2}
- Category:
- BuzzMessageBus
- Cause:
- An exception occurred while reading BufferSequenceInputStream.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190030
- {0} ERROR INTERNAL POTENTIAL RDMA MEMORY LEAK forceCloseIdAux message info is null {1} messageId {2}
- Category:
- BuzzMessageBus
- Cause:
- INTERNAL MessageInfo is null. This may be due to an RDMA memory leak.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190031
- {0} ERROR INTERNAL no ConnectionInfo {1}
- Category:
- BuzzMessageBus
- Cause:
- No connection info was provided for the endpoint.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190032
- {0} ERROR INTERNAL no epToMessageMap entry {1}
- Category:
- BuzzMessageBus
- Cause:
- The epToMessageMap entry for the endPoint was missing.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190033
- {0} ERROR INTERNAL recv no subprotocol receiver {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5}
- Category:
- BuzzMessageBus
- Cause:
- No subprotocol receiver was provided for the messageId.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190034
- {0} ERROR INIT INTERNAL recv connection in wrong state, should be CONNECTED {1} peer: {2}/{3} local: {4}/{5} connectionState: {6}
- Category:
- BuzzMessageBus
- Cause:
- An INIT frame was received but the endpoint is in the wrong state.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190035
- {0} ERROR INTERNAL INIT recv error ConnectionInfo should not be null {1}
- Category:
- BuzzMessageBus
- Cause:
- An INTERNAL INIT was received but ConnectionInfo is null.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190036
- {0} ERROR INTERNAL POTENTIAL RDMA MEMORY LEAK recv unknown messageId scope for RST {1} flags: {2} subprotocol: {3} messageId: {4} errorCode: {5}
- Category:
- BuzzMessageBus
- Cause:
- An RST frame was received with an unknown messageId scope. This may be due to an RDMA memory leak.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190037
- {0} ERROR INTERNAL send incorrect message state - should be HALF_CLOSED {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} messageState: {6}
- Category:
- BuzzMessageBus
- Cause:
- An attempt was made to send a message but the message is in an incorrect state.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190038
- {0} ERROR INTERNAL send incorrect message state - should be OPEN {1} frameType: {2} flags: {3} subprotocol: {4} messageId: {5} messageState: {6}
- Category:
- BuzzMessageBus
- Cause:
- An INTERNAL attempt was made to send a message but the message is in an incorrect state.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190039
- {0} ERROR INTERNAL send existing endPoint to ConnectionInfo during INIT {1}
- Category:
- BuzzMessageBus
- Cause:
- An error of type INTERNAL occurred during initialization.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190040
- {0} ERROR INTERNAL send exception when sending RST {1} subprotocol: {2} messageId: {3} errorCode: {4} extra: {5}
- Category:
- BuzzMessageBus
- Cause:
- An exception of type INTERNAL occurred when sending RST.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190041
- {0} ERROR INTERNAL flush receiver threw exception (ignored) subprotocol: {1} subprotocolReceiver: {2}: {3}
- Category:
- BuzzMessageBus
- Cause:
- A BuzzSubprotocolReceiver threw an exception in its #flush method (ignored).
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190042
- {0} ERROR close time out extra: waited for {1} {2}
- Category:
- BuzzMessageBus
- Cause:
- An internal close timeout occurred.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190043
- Unexpected DummyBuzzChannel usage by App Container with stack trace: {0}.
- Category:
- BuzzMessageBus
- Cause:
- There was an unexpected usage of DummyBuzzChannel by the Application Container.
- Action:
- Contact My Oracle Support and provide them with the logs.
- BEA-2190044
- Buzz Message Bus is initialized at {0}.
- Category:
- BuzzMessageBus
- Cause:
- This is an informational message.
- Action:
- No action required.
- BEA-2191000
- {0} Invalid HTTP header length in Buzz frame: {1}
- Category:
- BuzzMessageBusHttp
- Cause:
- The HTTP header length in the Buzz frame is invalid.
- Action:
- Contact My Oracle Support and provide them the logs.
- BEA-2191001
- {0} Incomplete HTTP header in Buzz frame
- Category:
- BuzzMessageBusHttp
- Cause:
- The HTTP header in the Buzz frame is incomplete.
- Action:
- Contact My Oracle Support and provide them the logs.
- BEA-2191002
- {0} Invalid message type for HTTP BuzzSubprotocolHandler: {1}
- Category:
- BuzzMessageBusHttp
- Cause:
- The message type received by the HTTP BuzzSubprotocolHandler is invalid.
- Action:
- Contact My Oracle Support and provide them the logs.
- BEA-2191003
- {0} The BuzzSubprotocolRecieverHttpWLSImpl#receipt method should not be invoked. There may be a memory leak: {1}
- Category:
- BuzzMessageBusHttp
- Cause:
- The Http BuzzSubprotocolHandler encountered an internal receipt error.
- Action:
- Contact My Oracle Support and provide them the logs.
- BEA-2191004
- {0} Internal receive error in Http BuzzSubprotocolHandler: {1}
- Category:
- BuzzMessageBusHttp
- Cause:
- The Http BuzzSubprotocolHandler encountered an internal receive error.
- Action:
- Contact My Oracle Support and provide them the logs.
- BEA-2191005
- {0} A complete message could not be read on socket: '{1}', in the configured timeout period of '{2}' secs.
- Category:
- BuzzMessageBusHttp
- Cause:
- A complete HTTP message could not be read on the socket within the configured timeout.
- Action:
- Contact My Oracle Support and provide them the logs.
- BEA-2191006
- {0} BuzzSubprotocolRecieverHttpWLSImpl#closeYourId({1}) should not be invoked because WLS/Buzz/HTTP does not initiate messages.
- Category:
- BuzzMessageBusHttp
- Cause:
- BuzzSubprotocolRecieverHttpWLSImpl#closeYourId was invoked.
- Action:
- Contact My Oracle Support and provide them the logs.
- BEA-2192000
- Workflow {0} failed in step <{1}> during {2} operation without a specified reason. Requested resolution is {3}
- Category:
- MgmtOrchestration
- Cause:
- {0}
- Action:
- Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
- BEA-2192001
- Workflow {0} failed in step <{1}> during {2} operation. Requested resolution is {3}. Reason: {4}
- Category:
- MgmtOrchestration
- Cause:
- {0} - {2}
- Action:
- Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
- BEA-2192002
- Workflow {0} - the saved workflow is corrupted, there are missing work units.
- Category:
- MgmtOrchestration
- Cause:
- The workflow could not be loaded properly from persistent storage.
- Action:
- Review the server configuration or create a new workflow.
- BEA-2192003
- Workflow {0} - the saved workflow is corrupted, checksum errors were detected.
- Category:
- MgmtOrchestration
- Cause:
- The workflow could not be loaded properly from persistent storage.
- Action:
- Review the server configuration or create a new workflow.
- BEA-2192004
- Workflow {0} Running: {1} / {2}
- Category:
- MgmtOrchestration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192005
- Workflow {0} finished successfully. {1} steps completed.
- Category:
- MgmtOrchestration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192006
- Workflow {0} failed and the revert process has been initiated.
- Category:
- MgmtOrchestration
- Cause:
- See getError for details of the failure.
- Action:
- Allow the workflow to revert automatically, then diagnose the failure with the information reported by getError before attempting the process again.
- BEA-2192007
- Workflow {0} failed and the revert process was not initiated. The failure was: {1}
- Category:
- MgmtOrchestration
- Cause:
- See getError for details of the failure.
- Action:
- Diagnose the failure with the information reported by getError and address it.
- BEA-2192008
- Workflow {0} failed, the revert process was initiated and completed successfully. The failure that triggered the revert process was: {1}
- Category:
- MgmtOrchestration
- Cause:
- See getError for details of the failure.
- Action:
- Diagnose the failure with the informatipn reported by getError and address it. Then try running the procedure again.
- BEA-2192009
- Workflow {0} failed, the revert process was initiated, but it failed as well. The failure that triggered the revert process was: {1}
- Category:
- MgmtOrchestration
- Cause:
- See getError for details of the cause.
- Action:
- Review the cause details from getError and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
- BEA-2192010
- Workflow {0} was canceled.
- Category:
- MgmtOrchestration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192011
- Workflow {0} cannot create directory to store workflow: {0}
- Category:
- MgmtOrchestration
- Cause:
- The requested directory could not be created.
- Action:
- Ensure that the parent directory is writable and the hard drive has sufficient free space.
- BEA-2192012
- Workflow {0} could not delete a file during the workflow storage cleaning process. {1}
- Category:
- MgmtOrchestration
- Cause:
- {1}
- Action:
- Unlock the file and check the user's privileges.
- BEA-2192013
- Workflow {0} - found unexpected or invalid structures in the storage directory:{1}
- Category:
- MgmtOrchestration
- Cause:
- This is usually caused by external changes to the directory contents.
- Action:
- Create a new workflow for this procedure.
- BEA-2192014
- Workflow {0} could not move the temporary workflow file ({0}) to the permanent destination ({1}).
- Category:
- MgmtOrchestration
- Cause:
- The cause is unknown.
- Action:
- Ensure that the parent directory is writable and that the temporary workflow file is writable. You will likely need to start a new workflow for this procedure.
- BEA-2192015
- Workflow {0} is starting the revert process.
- Category:
- MgmtOrchestration
- Cause:
- There was a previously reported error with the workflow and the revert process is starting.
- Action:
- No action is required.
- BEA-2192016
- Workflow {0} is already completed and cannot be started again.
- Category:
- MgmtOrchestration
- Cause:
- You attempted to start a completed workflow.
- Action:
- To run the process again, start a new workflow.
- BEA-2192017
- Workflow {0} is already running.
- Category:
- MgmtOrchestration
- Cause:
- You attempted to start a running workflow.
- Action:
- No action is required.
- BEA-2192018
- Could not delete a file or directory: {0}
- Category:
- MgmtOrchestration
- Cause:
- Either the file is locked or the user has insufficient privileges.
- Action:
- Unlock the file and check the user's privileges.
- BEA-2192019
- Workflow {0} is not running, so it cannot be canceled.
- Category:
- MgmtOrchestration
- Cause:
- Only a running workflow can be canceled.
- Action:
- No action is required.
- BEA-2192034
- {0} {1} {2}-{3} (duration: {4})
- Category:
- MgmtOrchestration
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-2192035
- {0} {1} {2}-{3} (duration: {4}) - ERROR {5}
- Category:
- MgmtOrchestration
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-2192036
- {0} {1} {2}-{3} (duration: {4}) - ERROR Unknown error
- Category:
- MgmtOrchestration
- Cause:
- See the message body.
- Action:
- No action required.
- BEA-2192037
- Failure performing {1} of {0}
- Category:
- MgmtOrchestration
- Cause:
- See the cause of the exception.
- Action:
- Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
- BEA-2192038
- Workflow {0} was never executed. Cannot revert.
- Category:
- MgmtOrchestration
- Cause:
- You attempted to revert a new workflow.
- Action:
- This operation is valid only for stopped workflows, not for completed but already executed workflows, for example, failed workflows.
- BEA-2192039
- Service is blocked. It was used too early or was not used on the Administration Server.
- Category:
- MgmtOrchestration
- Cause:
- The server is not in a state where the orchestration framework can act.
- Action:
- Check the status of the Administration Server.
- BEA-2192040
- Workflow instance {0} is running. Cannot delete.
- Category:
- MgmtOrchestration
- Cause:
- A running workflow instance cannot be deleted.
- Action:
- Wait for the workflow to complete.
- BEA-2192041
- It is not possible to execute the workflow instance in its current state.
- Category:
- MgmtOrchestration
- Cause:
- The current state of the workflow is not compatible with this operation.
- Action:
- Check the state of the workflow instance.
- BEA-2192042
- It is not possible to revert the workflow instance in its current state.
- Category:
- MgmtOrchestration
- Cause:
- The current state of the workflow is not compatible with this operation.
- Action:
- Check the state of the workflow instance.
- BEA-2192043
- Cannot execute the workflow instance. Not all required shared state objects are defined. ({0})
- Category:
- MgmtOrchestration
- Cause:
- The workflow instance cannot be constructed because of missing shared state objects.
- Action:
- Ensure that you have defined all necessary attributes.
- BEA-2192044
- Failure performing {1} of {0}, caused by {2}
- Category:
- MgmtOrchestration
- Cause:
- See the cause of the exception.
- Action:
- Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
- BEA-2192045
- Debug Message: {0}
- Category:
- MgmtOrchestration
- Cause:
- Used for capturing debug information during testing.
- Action:
- No action is required.
- BEA-2192046
- Workflow {0} failed in step <{1}> during {2} operation. Requested resolution is {3}. Reason: {4}
- Category:
- MgmtOrchestration
- Cause:
- {0} - {2}
- Action:
- Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
- BEA-2192047
- Workflow {0} failed to store step <{1}> during {2} operation. Reason: {4}
- Category:
- MgmtOrchestration
- Cause:
- {0} - {2}
- Action:
- Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details.
- BEA-2192048
- Unable to load stored progress object of type: {0} from {1} due to {2}.
- Category:
- MgmtOrchestration
- Cause:
- {0} - {2}
- Action:
- Check that the file store is still valid and that the workflow information is not lost.
- BEA-2192049
- Unable to initialize progress object from persistence: {0} due to {1}.
- Category:
- MgmtOrchestration
- Cause:
- {0} - {1}
- Action:
- Check that the file store is still valid and that the workflow information is not lost.
- BEA-2192050
- Error initializing progress for workflow {0} from path {1}, due to {2}.
- Category:
- MgmtOrchestration
- Cause:
- {2}
- Action:
- Check that the file store is still valid and that the workflow information is not lost.
- BEA-2192051
- Error starting workflow {0}, due to {1}.
- Category:
- MgmtOrchestration
- Cause:
- {1}
- Action:
- Check the exception that caused the failure for more information.
- BEA-2192052
- Error setting type {1} on workflow {0}, {2}.
- Category:
- MgmtOrchestration
- Cause:
- {2}
- Action:
- Check the exception that caused the failure for more information.
- BEA-2192053
- Error setting target type {1} on workflow {0}, {2}.
- Category:
- MgmtOrchestration
- Cause:
- {2}
- Action:
- Check the exception that caused the failure for more information.
- BEA-2192054
- Error setting target {1} on workflow {0}, {2}.
- Category:
- MgmtOrchestration
- Cause:
- {2}
- Action:
- Check the exception that caused the failure for more information.
- BEA-2192055
- Error cleaning up workflows on Partition {0} deletion.
- Category:
- MgmtOrchestration
- Cause:
- {1}
- Action:
- Check the exception that caused the failure for more information.
- BEA-2192056
- Unable to get workflow for Partition {0} and workflowid {1}.
- Category:
- MgmtOrchestration
- Cause:
- Action:
- BEA-2192057
- Unable to delete workflowfiles for for Partition {0} and workflowid {1} as workflow was in state {2}.
- Category:
- MgmtOrchestration
- Cause:
- Action:
- BEA-2192058
- Found a workflow with state = null for Partition {0} and workflowid {1}.
- Category:
- MgmtOrchestration
- Cause:
- Action:
- BEA-2192059
- Error attempting to create workflow orchestration directory {0}.
- Category:
- MgmtOrchestration
- Cause:
- Action:
- BEA-2192100
- Script "{0}" output: {1}
- Category:
- Patching
- Cause:
- This message displays output from the script.
- Action:
- No action is required.
- BEA-2192101
- Timeout polling ready application URL for server: {0}.
- Category:
- Patching
- Cause:
- The system failed to perform a ready check on applications within the stipulated time.
- Action:
- Check the server log to determine which applications or applications failed to load. You may need to increase the readyCheckAppsTimeoutInMin value depending on how long the application or applications take to load.
- BEA-2192102
- Failed to construct URL for server: {0}.
- Category:
- Patching
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Take appropriate action based on the details provided in the exception.
- BEA-2192103
- Error opening URL.
- Category:
- Patching
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Take appropriate action based on the details provided in the exception.
- BEA-2192104
- Failed to get ServerLifeCycleRuntimeMBean for server {0}
- Category:
- Patching
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Take appropriate action based on the details provided in the exception.
- BEA-2192105
- Server lifecycle operation error for server {0}: {1}
- Category:
- Patching
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Take appropriate action based on the details provided in the exception.
- BEA-2192106
- Cannot unregister deleted MBean: {0}
- Category:
- Patching
- Cause:
- A workflow was deleted but it was not possible to unregister the relevant MBean.
- Action:
- No action is required.
- BEA-2192107
- Workflow {0} is executing {1} on {2}.
- Category:
- Patching
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192108
- Workflow {0} is retyring {1} on {2}.
- Category:
- Patching
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192109
- Workflow {0} is reverting {1} on {2}.
- Category:
- Patching
- Cause:
- This is an informational message.
- Action:
- No action isrequired.
- BEA-2192110
- Workflow {0} successfully completed {1} on {2}.
- Category:
- Patching
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192111
- Workflow {0} successfully completed revert of {1} on {2}.
- Category:
- Patching
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192112
- Workflow {0} failed to complete {1} on {2}.
- Category:
- Patching
- Cause:
- Use getError for details of the failure.
- Action:
- Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details and take appropriate action.
- BEA-2192113
- Workflow {0} failed to complete {1} on {2} due to error {3}.
- Category:
- Patching
- Cause:
- Use getError for details of the failure.
- Action:
- Workflow failures are handled according to their failure plan. Check the log messages or the workflow results for additional details and take appropriate action.
- BEA-2192114
- Workflow {0} failed to revert {1} on {2}.
- Category:
- Patching
- Cause:
- See the log for details of the failure.
- Action:
- Review the cause details from getError and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
- BEA-2192115
- Workflow {0} failed to revert {1} on {2} due to error {3}.
- Category:
- Patching
- Cause:
- See the log for details of the failure.
- Action:
- Review the cause details from getError and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
- BEA-2192116
- Unable to enable session handling features on restarted server: {0}.
- Category:
- Patching
- Cause:
- See the log for details of the failure.
- Action:
- Review the cause and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
- BEA-2192117
- Targeted application redeploy for "{0}" on server "{1}" during patching failed with an exception {2}.
- Category:
- Patching
- Cause:
- See the log for details about the cause of the failure.
- Action:
- Review the cause in the logs and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
- BEA-2192118
- Workflow {0} skipped {1} on {2}.
- Category:
- Patching
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192119
- The user path input "{0}" was translated to "{1}".
- Category:
- Patching
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192120
- Error using the NodeManager to verify local paths on machine {0}. The last lines of script output (full script output in the log): {1}.
- Category:
- Patching
- Cause:
- This is usually caused by a file not being found at the specified path.
- Action:
- Confirm that the specified paths are correct.
- BEA-2192121
- Error from ZDT agent invocation on node manager: [{0}] Message: {1}
- Category:
- Patching
- Cause:
- Operation failed while executing on node manager.
- Action:
- Review the cause based on the error message.
- BEA-2192122
- Warning from ZDT agent invocation on node manager: [{0}] Message: {1}
- Category:
- Patching
- Cause:
- Warning generated while executing on node manager.
- Action:
- Review the warning message.
- BEA-2192123
- Info from ZDT agent invocation on node manager: [{0}] Message: {1}
- Category:
- Patching
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192124
- Info message from ZDT agent local invocation: {0}
- Category:
- Patching
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192125
- Warning message from ZDT agent local invocation: {0}
- Category:
- Patching
- Cause:
- Warning generated while executing ZDT agent.
- Action:
- Review the warning message.
- BEA-2192126
- Error message from ZDT agent local invocation: {0}
- Category:
- Patching
- Cause:
- Operation failed while executing ZDT agent.
- Action:
- Review the cause based on the error message.
- BEA-2192127
- Exception message from ZDT agent local invocation: {0}
- Category:
- Patching
- Cause:
- Details of the cause are provided in the exception.
- Action:
- Take appropriate action based on the details provided in the exception.
- BEA-2192128
- Targeted application redeploy for "{0}" on partition "{1}"on server "{2}" during patching failed with an exception {3}.
- Category:
- Patching
- Cause:
- See the log for details about the cause of the failure.
- Action:
- Review the cause in the logs and address the reported issue. The partial completion of this operation may have left affected targets in an inconsistent state.
- BEA-2192129
- Rollout is being started on Coherence cluster "{0}" , but the cluster has only 2 managed servers or 2 machines. This can lead to probable data loss if during the rollout, the other server which is running fails.
- Category:
- Patching
- Cause:
- There are only 2 managed server belonging to the Coherence cluster.
- Action:
- The Coherence cluster must have atleast 3 managed servers, ideally belonging to 3 different machines, to prevent data loss during rollout.
- BEA-2192130
- ElasticitySyncCounter.loadCounterFromDisk caught an exception while trying to load persisted counter file from disk at [{0}]. Message: {1}
- Category:
- Patching
- Cause:
- An exception occurred while trying to load persisted file from disk
- Action:
- Review the cause in the logs and address the reported issue. The Elasticity service may remain enabled and affect the rollout operation.
- BEA-2192300
- The partition lifecycle operation "{0}" failed for partition "{1}".
- Category:
- Partition Lifecycle
- Cause:
- The partition lifecycle operation "{0}" failed for partition "{1}" with exception "{2}".
- Action:
- Try restarting the partition.
- BEA-2192301
- The resource group lifecycle operation "{0}" failed for resourceGroupName "{2}" of partition "{1}".
- Category:
- Partition Lifecycle
- Cause:
- The resource group lifecycle operation "{0}" failed for resourceGroupName "{2}" of partition "{1}" with exception "{2}".
- Action:
- Try restarting the resource group
- BEA-2192302
- The partition lifecycle operation "{0}" failed for partition "{1}".
- Category:
- Partition Lifecycle
- Cause:
- The partition lifecycle operation "{0}" failed for partition "{1}" with exception "{2}".
- Action:
- Check whether the targets for partition "{1}" are running.
- BEA-2192303
- The partition lifecycle operation "{0}" for partition "{1}" is initiated.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192304
- The partition lifecycle operation "{0}" for partition "{1}" was successful.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192305
- The partition lifecycle operation "{0}" for the untargeted partition "{1}" was successful.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192306
- The resource group lifecycle operation "{0}" for resourceGroupName "{2}" of partition "{1}" was initiated.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192307
- The resource group lifecycle operation "{0}" for resourceGroupName "{2}" of partition "{1}" was successful.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192308
- The resource group lifecycle operation "{0}" for untargeted resourceGroupName "{2}" of partition "{1}" was successful.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192309
- The partition "{0}" is already in the "{1}" state.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192310
- The resource group "{0}" of partition "{1}" is already in the "{2}" state.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192311
- The partition lifecycle operation "{1}" is in progress for partition "{0}".
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192312
- The resource group lifecycle operation "{2}" for resource group "{0}" belonging to partition "{1}" is in progress.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192313
- The partition lifecycle operation "{1}" on partition "{0}" is incompatible with the current state "{2}".
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192314
- The resource group lifecycle operation "{2}" for resource group "{0}" belonging to partition "{1}" is incompatible with the current state "{3}".
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192315
- The partition operation "{1}" for partition "{0}" failed with exception "{2}".
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192316
- Performing an automatic HALT on partition "{1}" after operation "{0}" because there are no targeted active admin resource groups.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192317
- Skipping BOOT for partition "{0}" because there are no targeted active admin resource groups.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192318
- Graceful operation "{0}" on partition "{1}" timed out; converting to "{2}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192319
- Partition lifecycle operation "{0}" initiated using partitionLifeCycleRuntimeMbean for partition "{1}" on servers "{2}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192320
- The status of partition lifecycle sub task "{0}" for partition "{1}" is "{2}" on server "{3}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192321
- The partition lifecycle sub task "{0}" for partition "{1}" failed on server "{2}" with exception "{3}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192322
- The status of partition lifecycle task "{0}" for partition "{1}" is "{2}" on servers "{3}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192323
- The partition lifecycle task "{0}" for partition "{1}" failed with exception "{2}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192324
- The partition lifecycle operation "{0}" for the partition "{1}" is a no-op since the partition is already in expected state "{2}" in all the targeted servers
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192325
- The resource group lifecycle operation "{0}" for the resource group "{1}" is a no-op since the resource group is already in expected state "{2}" in all the targeted servers
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192326
- Resource group lifecycle operation "{0}" initiated using resourceGroupLifeCycleRuntimeMbean for resource group "{1}" on servers "{2}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192327
- The status of resource group lifecycle sub task "{0}" for resource group "{1}" is "{2}" on server "{3}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192328
- The resource group lifecycle sub task "{0}" for resource group "{1}" failed on server "{2}" with exception "{3}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192329
- The status of resource group lifecycle task "{0}" for resource group "{1}" is "{2}" on servers "{3}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192330
- The resource group lifecycle task "{0}" for resource group "{1}" failed with exception "{2}"
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192331
- A partition forceRestart operation halted the partition "{0}" on this server but the corresponding runtime MBean remains.
- Category:
- Partition Lifecycle
- Cause:
- This is a warning message.
- Action:
- Monitor the system for unexpected behavior of the partition on this server.
- BEA-2192332
- Partition "{0}" is in state "{2}". The resource group "{1}" can not be transitioned to "{3}" state.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192333
- Performing an automatic HALT on partition "{1}" after operation "{0}" because SHUTDOWN_TO_HALTED flag is True.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192334
- An inconsistent state "{0}" and substate "{1}" were found; continuing with substate "{2}".
- Category:
- Partition Lifecycle
- Cause:
- The system uses separate remote messages to obtain the state and substate of a partition on a remote server. If between those two messages the state of the server or partition changes or the underlying network connection falters, the retrieved state and substate might be inconsistent with each other.
- Action:
- Make sure that the system actions following the substate substitution are what was intended.
- BEA-2192335
- Performing a RESUME instead of a START on partition "{0}" as the partition is in ADMIN state.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192336
- Performing a RESUME instead of a START on resource group "{0}" of partition "{1}" as the resource group is in ADMIN state.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192337
- Performing a RESUME instead of a START on resource group "{0}" as the resource group is in ADMIN state.
- Category:
- Partition Lifecycle
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192338
- The partition lifecycle operation for partition "{0}" failed during server "{1}" start-up
- Category:
- Partition Lifecycle
- Cause:
- The partition lifecycle operation for partition "{0}" failed during server "{1}" start-up with exception "{2}"
- Action:
- Try invoking lifecycle operation on partition "{0}" to bring it back to correct state.
- BEA-2192339
- The partition lifecycle operation for partition "{0}" failed during server "{1}" shutdown
- Category:
- Partition Lifecycle
- Cause:
- The partition failed operation for partition "{0}" during server "{1}" shutdown with exception "{2}"
- Action:
- Try invoking lifecycle operation on partition "{0}" to bring it back to correct state.
- BEA-2192400
- JAX-RS OWSM configuration may not work: {0}
- Category:
- JAXRSClient
- Cause:
- This problem may be caused by an incorrect WebLogic class path.
- Action:
- No action is required.
- BEA-2192500
- Application MBean not initialized for application ''{0}''.
- Category:
- JAXRSIntegration
- Cause:
- The application was destroyed.
- Action:
- No action is required.
- BEA-2192501
- Cannot find URI for {0} resource class.
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192502
- Do not call JaxRsApplicationRuntimeMBean.setApplicationEnabled(boolean).
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message. This is a deprecated API with no replacement.
- Action:
- Enable 'DebugRestJersey2Integration' to get the caller stack trace.
- BEA-2192503
- InitialContext not found. JAX-RS EJB support is not available.
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192504
- EJB component provider has not been initialized properly.
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192505
- An instance of EJB class {0} could not be looked up using a simple form name. Attempting to look up using the fully-qualified form name.
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192506
- Exception thrown when trying to look up actual handling method {0} for EJB type {1} using interface {2}.
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192507
- Class {0} has been bound by Jersey EJB component provider.
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192508
- The failure was: {0}
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192509
- Changing servlet class from {0} (web.xml) to {1}.
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192510
- Cannot add Jersey servlet for application class {0} because ApplicationPath annotation is not set on it.
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2192511
- The list of resource packages: {0}
- Category:
- JAXRSIntegration
- Cause:
- This is an informational message.
- Action:
- No action is required.
- BEA-2194500
- Initializing a Coherence cluster scoped to classloader {0} using {1}
- Category:
- CoherenceIntegration
- Cause:
- Initializing a Coherence cluster scoped to classloader {0} using {1}
- Action:
- No action is required.
- BEA-2194501
- Failed to initialize a Coherence cluster due to {0}
- Category:
- CoherenceIntegration
- Cause:
- Failed to initialize a Coherence cluster due to {0}
- Action:
- Take corrective action based on the exception details.
- BEA-2194502
- Shutting down a Coherence cluster scoped to classloader {0}
- Category:
- CoherenceIntegration
- Cause:
- Shutting down a Coherence cluster scoped to classloader {0}
- Action:
- No action is required.
- BEA-2194503
- Failed to shut down a Coherence cluster due to {0}
- Category:
- CoherenceIntegration
- Cause:
- Failed to shut down a Coherence cluster due to {0}
- Action:
- Take corrective action based on the exception details.
- BEA-2194504
- Deployed a GAR ({0}) without a CoherenceClusterSystemResourceMBean definition on this server. In most of the scenarios, a Coherence cluster must be created for applications to work properly.
- Category:
- CoherenceIntegration
- Cause:
- Deployed a GAR ({0}) without a CoherenceClusterSystemResourceMBean definition on this server.
- Action:
- Create a CoherenceClusterSystemResourceMBean appropriately and associate it with the server, or the cluster of which this server is a member. Only in some special cases, for example using Coherence Extend with TCMP disabled, a Coherence cluster may not be associated with a managed server.
- BEA-2194505
- Server {0} is configured with 'localhost' as the Unicast Listen Address. A generated Coherence WKA list will not operate correctly across multiple machines. This will result in an error if Coherence is run in Production mode.
- Category:
- CoherenceIntegration
- Cause:
- Server {0} is configured with 'localhost' as the Unicast Listen Address. When using Coherence WKA and not explicitly defining a WKA list, the configuration may not operate correctly across multiple machines. This will result in an error if Coherence is run in Production mode.
- Action:
- Explicitly define a Well Known Address (WKA) list for the Coherence cluster.
- BEA-2194506
- Could not find the JNDI resource [{0}] referenced by {1}.
- Category:
- CoherenceIntegration
- Cause:
- The JNDI resource [{0}] referenced by {1} could not be found.
- Action:
- Define the JNDI resource [{0}] referenced by {1}.
- BEA-2194507
- The Coherence cluster service failed to start or failed to join cluster due to {0} using {1}.
- Category:
- CoherenceIntegration
- Cause:
- The Coherence cluster service failed to start or failed to join cluster due to {0} using {1}.
- Action:
- Review the Coherence configuration for the cause of the exception.
- BEA-2194508
- Coherence configuration failed due to {0} using {1}.
- Category:
- CoherenceIntegration
- Cause:
- The Coherence configuration failed due to {0} using {1}.
- Action:
- Review the Coherence configuration for the cause of the exception.
- BEA-2194509
- The WeblogicCoherenceBean and CoherenceClusterParamsBean are not defined for the CoherenceClusterSystemResourceMBean {0}.
- Category:
- CoherenceIntegration
- Cause:
- The CohererenceClusterSystemResourceBean {0} needs to have an association with valid WeblogicCoherence and CoherenceCluster Beans.
- Action:
- Create a CoherenceClusterSystemResource MBean with the required associations.
- BEA-2194510
- While configuring the Coherence Cluster Service, the Server MBean or Server CoherenceMemberConfig MBean or both were not defined.
- Category:
- CoherenceIntegration
- Cause:
- The Server MBean or Server CoherenceMemberConfig MBean or both were not defined and thus will not be used when configuring the Coherence Cluster Service.
- Action:
- No action is required.
- BEA-2194511
- Server {0} is configured with 'localhost' as the Unicast Listen Address which is an error in Coherence Production mode. A generated Coherence WKA list will not operate correctly across multiple machines.
- Category:
- CoherenceIntegration
- Cause:
- Server {0} is configured with 'localhost' as the Unicast Listen Address resulting in an error when Coherence is in Production mode. When using Coherence WKA and not explicitly defining a WKA list, the configuration may not operate correctly across multiple machines.
- Action:
- Explicitly define a Well Known Address (WKA) list for the Coherence cluster.
- BEA-2194512
- While undeploying a GAR, the deployment module received an exception when closing files {0}.
- Category:
- CoherenceIntegration
- Cause:
- While undeploying a GAR, one or more files could not be closed due to {0}.
- Action:
- Review the exception and determine if there any file system issues for the referenced files.
- BEA-2194513
- Deployed an application ({0}) with Coherence*Web as session persistence type without a CoherenceClusterSystemResourceMBean definition on this server. Typically, a Coherence cluster must be created for this scenario to work properly.
- Category:
- CoherenceIntegration
- Cause:
- Deployed an application ({0}) with Coherence*Web as session persistence type without a CoherenceClusterSystemResourceMBean definition on this server.
- Action:
- Create a CoherenceClusterSystemResourceMBean appropriately and associate it with the server, or the cluster of which this server is a member. Only in some special cases, for example using Coherence Extend with TCMP disabled, a Coherence cluster may not be associated with a managed server.
- BEA-2194514
- There was an error creating Timer Manager for the Managed Server Level Coherence*Web Session Reaping Manager.
- Category:
- CoherenceIntegration
- Cause:
- TBD
- Action:
- TBD
- BEA-2194515
- There was an error during the Session Reaping process of the Coherence*Web Session Reaping Manager.
- Category:
- CoherenceIntegration
- Cause:
- TBD
- Action:
- TBD
- BEA-2194801
- The archive file name {0} specified for importPartition is null
- Category:
- DomainToPartition
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Specify a valid archive file for importPartition
- BEA-2194802
- Partition name cannot be null, please specify a partition name.
- Category:
- DomainToPartition
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Specify a name for the partition
- BEA-2194803
- A Path Service targeted to a cluster requires High Availability Policies set on that Cluster, so MigrationBasis must be set in the Cluster "{0}". If database is chosen as MigrationBasis, then DataSourceForAutomaticMigration must be set. When consensus leasing is chosen as MigrationBasis, all servers that belong to the cluster must have a machine set and node manager configured for that machine.
- Category:
- DomainToPartition
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Configure the High Availability Policies for the Cluster "{0}".
- BEA-2194804
- A domain partition with the name "{0}" already exists. Please specify a name for the partition which is not already configured in the given domain.
- Category:
- DomainToPartition
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Specify a name for the domain partition which is not already configured.
- BEA-2194805
- The domain archive "{0}" is empty, specify a valid domain archive for import operation.
- Category:
- DomainToPartition
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Specify a valid domain archive for import operation.
- BEA-2194806
- The domain archive "{0}" and/or the associated json file is not compatible with the current version of importPartition. Please generate the archive using the current Domain To Partition Conversion Tool. If the generated json file is modified to remove the resource-group entries please correct it.
- Category:
- DomainToPartition
- Cause:
- This is an internal WebLogic Server error.
- Action:
- Supply a compatible domain archive for import partition operation.
- BEA-2194807
- Cannot find realm "{0}" in the domain configuration.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194808
- The exiting virtual-target {0} is not for target {1}.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194809
- Cannot create a virtual target with the name "{0}" as the server "{1}" is a member of the cluster "{2}"!
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194810
- Cannot add "{0}" to available targets of the domain partition as the server "{1}" is a member of the cluster "{2}".
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194811
- The target "{0}" of virtual-target "{1}" does not exist in the target domain.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194812
- Cannot find Virtual Target "{0}" to add as an available target.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194813
- Cannot find Virtual Target "{0}" to add as the default target.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194814
- Virtual Target with the name "{0}" is not available, to set as target for the resource group "{1}"!
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194815
- Virtual Target with the name "{0}" is not one of the available targets in the partition "{1}"!
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194816
- Resource Group Template "{0}" already exists in the domain.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194817
- JMS Server "{0}" is referencing a persistence store "{1}" with distribution policy 'Singleton', as it is hosting one or more standalone destinations. However the same persistence store is referenced by SAF Agent "{2}", which requires the persistence store to have distribution policy 'Distributed'. This conflict is not allowed, so JMS Server and SAF Agent should not refer the same persistence store.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194818
- The "{0}" element in the json generated by the Domain TO Partition Conversion Tool is not an JSON Array. If the json file is modified before import, please correct the issue and try import again.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194819
- Cannot add the Virtual Target "{0}" to available targets of the domain partition as the server "{1}" is a member of the cluster "{2}".
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194820
- The destination for writing the imported application "{0}" already exists at {1}.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194821
- The imported zip file does not contain the application plan at "{0}".
- Category:
- DomainToPartition
- Cause:
- TBD
- Action:
- TBD
- BEA-2194822
- The imported zip file does not contain the application/library source at "{0}".
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194823
- The destination for writing the imported plan for application "{0}" already exists at {1}.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194824
- Import of "{1}" of type "{0}" is excluded in the json file, an excluded resource won't be available in the partition.
- Category:
- DomainToPartition
- Cause:
- The resource is excluded in the json file generated by Domain To Partition Conversion Tool, before importing to the partition.
- Action:
- Manually configure the resource appropriately.
- BEA-2194825
- Partition "{0}" already contains a default target with the name "{1}".
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194826
- Cannot find/set JDBCStore "{0}" to JMS Server "{1}".
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194827
- Removing the target "{1}" from the subdeployment "{0}", to retain the first target for the subdeployment.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194828
- Modifying the distribution policy to 'Singleton' and the migration policy to 'Always' of the persistent store "{0}" referenced by the Path Service "{1}".
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194829
- Path Service "{0}" in the source domain was pointing to default store. So creating a file store with the name "{1}" under Resource Group / Resource Group Template "{2}" as a path service without a valid store is not supported in a partitioned environment.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194830
- The importPartition operation failed to create the report.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194832
- The activation of importPartition failed with the error - {0}
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194833
- Error creating the JDBC Store "{0}", cannot find and set JDBC SystemResource "{1}"
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194834
- The JDBC Store "{0}" in the source domain does not have an associated JDBC System Resource. So this JDBC Store won't be created in the target domain partition. Any reference to this JDBC Store by a JMS Server or a SAF Agent or a Path Service will result in a validation exception due to unresolved reference in the configuration (config.xml).
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194835
- The Uniform Distributed Topic "{0}" in JMS Module "{1}" is configured to use the forwarding policy 'Replicated'(the default). This configuration is not supported when importing this domain to a partition, so the forwarding policy will be changed to 'Partitioned'.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194836
- The subdeployment "{0}" in JMS Module "{1}" is targeted to "{2}" of type "{3}". This configuration is not supported. Subdeployments when not targeted to a JMS Server or a SAF Agent, will be left untargeted and any resources that reference that subdeployment will not be deployed.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194837
- The subdeployment "{0}" in JMS Module "{1}" is targeted to "{2}" of type "{3}" and "{2}" is associated with a specific server in cluster "{4}" via a target of "{5}" of type "{6}". Partition scoped JMS destinations do not support targeting a particular Server or Migratable Target, so, after import, this subdeployment will be targeted to a JMS Server or a SAF Agent with an effective target of a Cluster, the destination runtime will therefore be hosted on a single random server in the cluster, or across all members of the cluster depending on its distribution policy and the server hosting the destination may change after failures or restarts.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194838
- The subdeployment "{0}" in JMS module "{1}" does not have any valid target. After import, any JMS destination that refer this subdeployment will not be deployed.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194839
- Unable to undo the changes which are not activated. Cause: {0}
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194840
- JMS Server "{0}" is found to be hosting one or more standalone destinations as well as Uniform Distributed Destinations using subdeployments. As the required Distribution Policy to host these destinations conflict, this is not allowed by Domain To Partition Conversion Tool(D-PCT).
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194841
- JMS Server "{0}" is found to be hosting one or more standalone destinations as well as Foregin Server using subdeployments. As the required Distribution Policy to host these destinations conflict, this is not allowed by D-PCT.
- Category:
- DomainToPartition
- Cause:
- Action:
- BEA-2194842
- The library file "{0}" available at "{1}" is used; the source library is ignored.
- Category:
- DomainToPartition
- Cause:
- The require-exact-version attribute available at the json file was set to "false" for the library "{0}" and hence the version of the library available at the target domain is being used.
- Action:
- Set the require-exact-version attribute in the json need to be set to "true" to get the same source file library before import.