7 BEA-000001 to BEA-2163006
- BEA-000005: Deployed a GAR ({0}) without a CoherenceClusterSystemResourceMBean definition on this server.
-
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.
Level: 1
Type: WARNING
Impact: weblogic-coherence-integration
- BEA-000006: Using localhost as the ListenAddress when generating a Coherence WKA list will not operate correctly across multiple machines.
-
Cause: Server {0} is configured with 'localhost' as the ListenAddress. When using Coherence WKA and not explicitly defining a WKA list, the configuration may not operate correctly across multiple machines.
-
Action: Specify an appropriate hostname as the ListenAddress for this server.
Level: 1
Type: NOTIFICATION
Impact: weblogic-coherence-integration
- BEA-000104: Cluster members are running incompatible versions. Local version: {0}. Remote version ({1}): {2}
-
Cause: This server is a different version than other servers in this cluster.
-
Action: Ensure that all members of this cluster are running the same version.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000105: The server is leaving the cluster because it is an incompatible version.
-
Cause: This server is running a different version of WebLogic Server.
-
Action: Set a different multicast address for this cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-000107: Failed to install {0} in place of those currently installed due to {1}.
-
Cause: An error occurred while resolving non-local conflicting offers for a node in the JNDI tree.
-
Action: Check the preceding conflict start message in the logs. Try to avoid the conflict by taking one of the suggested actions. If the problem persists, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000109: An error occurred while sending multicast message: {0}.
-
Cause: An error occurred while trying to send a message over multicast.
-
Action: WebLogic Server will try to recover from this error. If the problem continues to persist, make sure that the network infrastructure and NIC are functioning properly. If you believe no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000110: Multicast socket receive error: {0}.
-
Cause: An error occurred while trying to receive a message over the multicast.
-
Action: Ensure that the NIC is functioning properly. If it appears that no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000112: Removing {0} from cluster view due to timeout.
-
Cause: Removing {0} from cluster as it failed to send heartbeats over the multicast in the past 30 seconds.
-
Action: If a server has been shut down or suspended, no action is required. If the remote server {0} appears to be hung, take thread dumps and send them to My Oracle Support.
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-000113: Removing {0} from cluster view due to PeerGone.
-
Cause: The TCP/IP connection to server {0} was lost.
-
Action: If a server has been shut down or suspended, no action is required. If the remote server {0} appears to be hung, take thread dumps and send them to My Oracle Support.
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-000115: Lost {0} multicast message(s).
-
Cause: This is an informational message. When a server joins a stable cluster, this message will appear since multicast messages sent out by servers in the cluster were not received.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-000116: Failed to join cluster {0} at address {1} due to: {2}.
-
Cause: This happens if you specify an incorrect multicast address for the cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.
-
Action: Set a valid multicast address and try again.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000117: Received a stale replication request for object {0}.
-
Cause: This happens when a network problem exists, or one of the servers is taking a long time to collect garbage, causing the virtual machine to freeze.
-
Action: Tune garbage collection so that it does not pause. If the problem still persists, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000118: Lost {0} replication updates of object {1}.
-
Cause: If the secondary failed to receive some of the updates, it indicates this to the primary server by causing a NotFoundException to the primary so that the primary server can recreate the session state.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-000119: Missing multicast address for cluster: {0}. Set the MulticastAddress="a.b.c.d" property for the cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. Avoid the reserved range 224.0.0.0 - 224.0.1.255.
-
Cause: The cluster does not have a defined multicast address.
-
Action: Specify a valid multicast address.
Level: 1
Type: INTERNAL_ERROR
Impact: Cluster
- BEA-000121: Two domains in the same LAN should not use the same multicast address. Domains in conflict are {0} and {1}.
-
Cause: Two clusters on the local area network are using the same multicast address.
-
Action: Change the multicast address of either domain {0} or {1}.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000123: Conflict start: You tried to bind an object under the name {0} in the JNDI tree. The object {1} is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.
-
Cause: The cluster is not homogeneous. Two servers in the cluster are providing different services under the same name {0}. If the object is non-clusterable, only one server in the cluster can provide this service.
-
Action: There are various options. 1. Make the object clusterable. 2. Change the JNDI name of the object under which it is bound. 3. Make sure the object gets deployed only on one server. 4. Deploy the service on all the servers. However, binding it into the JNDI tree, set the replicate bindings property to false.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000124: Conflict start: The object {1} you tried to bind under the name {0} in the JNDI tree is clusterable but is incompatible. Ensure that all the servers in the cluster use an identical copy of the object.
-
Cause: The object {1} is clusterable. However, it implements different or incompatible interfaces on different servers.
-
Action: Ensure that all the servers in the cluster use an identical copy of the object.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000126: All session objects should be serializable to replicate. Check the objects in the session. Failed to replicate a non-serializable object.
-
Cause: Objects in the session are not serializable or externalizable.
-
Action: Ensure that all user-defined objects in the HTTP session are serializable.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000139: There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name {0} and they are using the same address {1} and port {2}.
-
Cause: There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name {0} and they are using the same address {1} and port {2}.
-
Action: Change either the multicast address or the multicast port.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000140: Failed to deserialize statedump from server {0} with {1}.
-
Cause: The server failed to deserialize an object since it does not have the class definition. This usually happens if the application classes are not deployed on all the nodes in the cluster. It is preferable to deploy beans to all the nodes of the cluster.
-
Action: Ensure that all the classes are available on all the nodes of the cluster.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000141: TCP/IP socket failure occurred while fetching state dump over HTTP from {0}.
-
Cause: An IOException occurred in the operating system.
-
Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support with the stack trace for further analysis.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000145: Managed Server {0} is tagged as a migratable server. A cluster that has migratable servers should configure a JDBC data source to ensure that the migratable server is highly available.
-
Cause: The cluster is misconfigured.
-
Action: Configure the DataSourceForAutomaticMigration property.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000148: Migratable server "{0}" is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should have at least a couple of machines assigned to it for automatic migration.
-
Cause: The migratable server is misconfigured.
-
Action: Ensure that the server is targeted to a machine and restart the migratable server.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-000149: Server failed to get a connection to the {1} during {0}.
-
Cause: The database or the consensus leasing basis appears to be down.
-
Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis the server is in the minority partition and the leasing basis is in some other partition that is not reachable.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000150: Server failed to get a connection to the {1} in the past {0} seconds for lease renewal. Server will shut itself down.
-
Cause: The database or consensus leasing basis appears to be down.
-
Action: Ensure that the database is accessible to the cluster. In the case of consensus leasing basis, the server is in the minority partition and the leasing basis is in some other partition that is not reachable.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000153: Cluster is misconfigured. For automatic migration, a pool of machines should be assigned to the cluster or each migratable server in the cluster should at least have a couple of machines assigned to it for automatic migration.
-
Cause: The cluster is misconfigured.
-
Action: Assign a pool of machines for automatic migration and refer to WebLogic Server documentation for more details.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000154: Cluster is misconfigured. The remote cluster address {0} is not a valid URL.
-
Cause: The server is misconfigured.
-
Action: Set the correct remote cluster address and restart the servers. If it is not clear on how to set remote ClusterAddress, refer to WebLogic Server documentation.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000155: Configured cluster address is invalid : {0}. Constructing cluster address dynamically.
-
Cause: The cluster configuration is invalid.
-
Action: Ensure that the cluster address contains either a DNS name or a comma-separated host list (or IP list) or a comma-separated host:port list (or IP:port list).
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-000158: Server has stopped sending cluster heartbeats and announcements. It is still receiving heartbeats and announcements from other cluster members.
-
Cause: The server is going out of the cluster as a result of the suspend or shutdown operation.
-
Action: No action is required
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-000159: The clocks of the machines hosting local server and remote server "{0}" are off by {1} seconds
-
Cause: The clocks of the machines hosting servers in the cluster are not synchronized.
-
Action: Ensure that all the machines are synchronized to the same time.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-000160: A request to synchronize the JNDI tree has been made over an insecure channel. Configure a secure HTTP channel for all of the servers in the cluster.
-
Cause: The cluster was configured to encrypt multicast data but the request to synchronize the JNDI tree was done on a non-secure channel (HTTP). To secure the cluster completely, configure a secure HTTP channel for all of the servers in the cluster.
-
Action: Configure a secure HTTP channel on all of the servers in the cluster.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000165: Some other domain has a cluster that is configured to use the same multicast address and port as a cluster in {0}. Two domains in the same LAN should not use the same multicast address.
-
Cause: Two clusters on the local area network are using the same multicast address.
-
Action: Change the multicast address of either domain.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000166: Some other cluster in this domain is configured to use the same multicast address as {0}. Clusters cannot use the same multicast address.
-
Cause: Multiple clusters in the same domain are using the same multicast address.
-
Action: For efficiency purposes, use two different multicast addresses.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000167: Some services failed to roll back successfully when trying to abort the migration: {0}.
-
Cause: An exception caused the rollback to fail: {0}.
-
Action: It would be safest to shut down this server so that any lingering services will stop. They will not be automatically restarted upon reboot. Once the cause of the rollback has been fixed, attempts to migrate to this server should be successful.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000170: The server {0} did not receive the multicast packets that it sent.
-
Cause: Each WebLogic Server instanec is expected to receive the messages it multicast to its multicast group. Since the server does not receive its own messages, the multicast address configuration in the cluster configuration or the interface address specification may be wrong.
-
Action: Ensure that the cluster configuration and server interface configuration are valid
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000171: Failed to load the custom Singleton Services SQL Query Helper: {0}, because of {1}.
-
Cause: The most likely cause for failing to load the named class is either a typo in the name of the class or that the class is missing from the server classpath.
-
Action: Ensure that the provided classname is valid and that the class exists in the classpath of the server.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000172: TCP/IP socket failure occurred while fetching state dump over HTTP from {0}. Error message received: {2}. The request was generated by {3}. {1}
-
Cause: An IOException occurred in the operating system.
-
Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support with the stack trace for further analysis.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000176: {0} does not specify a machine.
-
Cause: {0}'s configuration does not specify the machine on which it is running. Machines must be specified if scripts are to be executed when migrations happen.
-
Action: Specify the machine on which {0} is running in the server's console page.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000180: Unable to retrieve Job {0} from the database. The retrieval failed with {1}
-
Cause: An error occurred while reading a job from the database.
-
Action: ENsure that the classes corresponding to the job are present in the server classpath and are of the correct version.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000184: This server did not attempt to renew its lease for {0} seconds. The server may need to be restarted or migrated.
-
Cause: The thread that is supposed to regularly renew the lease has become blocked for some reason.
-
Action: Ensure that the server is not overloaded with work and that there are enough system resources available on the machine.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-000185: Despite the delay in the lease-renewing thread, the server has successfully renewed its lease. It is no longer in imminent risk of being migrated or restarted.
-
Cause: The thread that is supposed to regularly renew the lease became blocked, but is running properly again and has successfully renewed the lease.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-000192: A running server was not found to host {0}. The server will retry in a few seconds.
-
Cause: All running servers failed when asked to activate {0}.
-
Action: Ensure that there is at least one active candidate server for this service and that there is no bug in the activate() method. The service will be tried on all running servers in another few seconds.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-000193: The JTA service for {0} has failed, but {0} is still running. JTA cannot be migrated from a running server.
-
Cause: The JTA service failed.
-
Action: Check the logs of {0}; {0} should be restarted once the cause of the error has been determined and fixed. Upon restart, the JTA service will be migrated and running transactions recovered.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-000194: An error was encountered while trying to report a migration event: {0}.
-
Cause: The most likely cause is the Administration Server being unavailable. If this is intended, this message can be ignored.
-
Action: If monitoring information is desired, the Administration Server should be running and reachable.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-000195: An error was encountered while trying to save a migration event. The error was: {0}.
-
Cause: An internal error occurred while trying to create a runtime MBean to encapsulate this data.
-
Action: Contact My Oracle Support and provide the stack trace for further analysis.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-000196: Received data about a migration of type {0}, but no such type is recognized by the Administration Server.
-
Cause: If the Managed Servers have been upgraded to a newer version of WebLogic Server, they may be reporting data that the Administration Server does not know how to handle.
-
Action: Upgrade the Administration Server to the same version as the cluster members.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-000220: Cannot shut down the server because the request was from a null user (Principal).
-
Cause: The server refused to shut down since the command came from an unauthorized user.
-
Action: Only users within the Administrators group can shut down the server. Retry the command with a user who has administrator credentials.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000221: Cannot shut down the server because the request was from a nameless user (Principal).
-
Cause: The server refused to shut down since the command came from an unauthorized user.
-
Action: Only users within the Administrators group can shut down the server. Retry the command with a user who has administrator credentials.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000222: Cannot disable server logins because the request was from a null user (Principal).
-
Cause: The server refused to lock itself since the command came from an unauthorized user.
-
Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000223: Cannot disable server logins because the request was from a nameless user (Principal).
-
Cause: The server refused to lock itself since the command came from an unauthorized user.
-
Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000224: Cannot enable server logins because the request was from a null user (Principal).
-
Cause: The server refused to unlock itself since the command came from an unauthorized user.
-
Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000225: Cannot enable server logins because the request was from a nameless user (Principal).
-
Cause: The server refused to unlock itself since the command came from an unauthorized user.
-
Action: Retry the command with a user who has the privileges necessary to perform this operation.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000231: Waiting {0} seconds for server shutdown.
-
Cause: A shutdown command was issued with a wait time. The server will wait the specified number of seconds before starting shutdown.
-
Action: A cancel shutdown command can be issued during the wait time to cancel the shutdown process. Otherwise no action is needed.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000240: Cannot cancel the server shutdown because the request was from a null user (Principal).
-
Cause: Server shutdown could not be canceled because the user account that was used to issue the cancel command does not have the appropriate privileges.
-
Action: The command can only be executed by a user from the administrator group. Retry the command with a user account that has administrator privilieges.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000241: Cannot cancel the server shutdown because the request was from a nameless user (Principal).
-
Cause: Server shutdown could not be canceled because the user account that was used to issue the cancel command does not have the appropriate privileges.
-
Action: The command can only be executed by a user from the administrator group. Retry the command with a user account that has administrator privilieges.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000242: Cannot cancel server shutdown because there is no shutdown in progress.
-
Cause: The server shutdown cannot be canceled as the server is not in the state 'Shutdown in Progress'.
-
Action: No action is needed. Check the Administration Console for the state of the server.
Level: 1
Type: INTERNAL_ERROR
Impact: WebLogicServer
- BEA-000249: Because the weblogic.ConsoleInputEnabled property is set to true, the server can only be shut down from the command line. Type the command "shut" in the window in which the server was started.
-
Cause: The weblogic.ConsoleInputEnabled property was set true on the server startup command line.
-
Action: To shut down the server, type the command "shut" in the window in which the server was started.
Level: 1
Type: INTERNAL_ERROR
Impact: WebLogicServer
- BEA-000261: The system user is not permitted to shut down, {0}.
-
Cause: The server was not shut down because the user is not authorized to shut down the server.
-
Action: See the exception text in {0} for more information on diagnosing the problem. See the previous log messages for more information on authorization failure. If the user does not have permission to shut down the server, but should, use the Administration Console to define a policy for this server that allows the user to shut down.
Level: 1
Type: INTERNAL_ERROR
Impact: WebLogicServer
- BEA-000286: Failed to invoke startup class "{0}", {1}.
-
Cause: An exception occurred in a startup class.
-
Action: Determine the error in the startup class code and restart the server. To work around the problem, set the "abort on startup failure" property to false.
Level: 1
Type: INTERNAL_ERROR
Impact: WebLogicServer
- BEA-000306: Cannot use SSL because no certificates have been specified in the WebLogic Server configuration.
-
Cause: No certificates can be found for use by SSL.
-
Action: If using a keystore for the server certificate, set the ServerPrivateKeyAlias in the SSL MBean. If using the Server Certificate File, ensure that valid certificates are contained within the file.
Level: 1
Type: INTERNAL_ERROR
Impact: WebLogicServer
- BEA-000329: Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in production mode.
-
Cause: The production mode of the server is enabled.
-
Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000330: Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in production mode.
-
Cause: The production mode of the server is enabled.
-
Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script file to change the server mode.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000331: Started the WebLogic Server Administration Server "{0}" for domain "{1}" running in development mode.
-
Cause: The production mode of the server is disabled (default).
-
Action: Set the weblogic.ProductionModeEnabled property of the domain in the configuration script to change the server mode.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000332: Started the WebLogic Server Managed Server "{0}" for domain "{1}" running in development mode.
-
Cause: The production mode of the server is disabled (default).
-
Action: Set the weblogic.ProductionModeEnabled property of the domain in the startup script to change the server mode.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000333: Queue usage is greater than QueueLengthThresholdPercent "{0}%" of the maximum queue size. An attempt will be made to allocate ThreadsIncrease "{1}" thread(s) to help.
-
Cause: The server is under high load.
-
Action: Review the execute queue settings.
Level: 1
Type: WARNING
Impact: WebLogicServer
- BEA-000337: {0} has been busy for "{1}" seconds working on the request "{2}", which is more than the configured time (StuckThreadMaxTime) of "{3}" seconds in "{4}". Stack trace: {5}
-
Cause: The server is extremely busy or the thread is hung.
-
Action: Monitor the method that the hung thread is running. Use the Administration Console monitor execute request feature or take a thread dump (weblogic.Admin THREAD_DUMP).
Level: 1
Type: ERROR
Impact: WebLogicServer
- BEA-000358: Started WebLogic Server independent Managed Server "{0}" for the domain "{1}" running in production mode.
-
Cause: The production mode of the server is enabled.
-
Action: Set the ProductionModeEnabled property of the domain in the configuration file to change the server mode.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000382: A critical service failed. The server will automatically transition to the ADMIN state.
-
Cause: A server lifecycle operation or a critical service failed.
-
Action: The server logs contain information about the failure. If the error is not application related, contact My Oracle Support.
Level: 1
Type: NOTIFICATION
Impact: WebLogicServer
- BEA-000384: A fatal configuration failure occurred during startup. Check if the config.xml file contains invalid entries. Reason: {0}
-
Cause: The server failed to start due to invalid configuration.
-
Action: Check if the config.xml file contains invalid entries. Contact My Oracle Support for more information.
Level: 1
Type: INTERNAL_ERROR
Impact: WebLogicServer
- BEA-000398: WebLogic Server "{0}" for domain "{1}" is running with class caching enabled in production mode. Class caching is not supported in production mode. Disable class caching by setting CLASS_CACHE to "false" in the startWeblogic script and then restarting the server.
-
Cause: Class caching is turned on by default when server production mode is enabled.
-
Action: Set the CLASS_CACHE to false in the startWeblogic script and then restart the server.
Level: 1
Type: INTERNAL_ERROR
Impact: WebLogicServer
- BEA-000402: There are: {0} active sockets, but the maximum number of socket reader threads allowed by the configuration is: {1}. The configuration may need altered.
-
Cause: When non-native I/O is used, I/O is performed in a blocking manner. Therefore, if the number of socket reader threads is less than the number of active sockets, performance may degrade significantly.
-
Action: Optimally, increase the ThreadPoolPercentSocketReaders, or the ThreadPoolSize, or both. Optimally, decrease the SocketReaderTimeoutMinMillis, or the SocketReaderTimeoutMaxMillis, or both.
Level: 1
Type: WARNING
Impact: Socket
- BEA-000409: Problem on socket: {0} {1}
-
Cause: An exception occurred while registering the socket with the muxer. It is possible that the file descriptor cannot be obtained from the socket.
-
Action: Capture the errors and send the server log files to My Oracle Support.
Level: 1
Type: ERROR
Impact: Socket
- BEA-000414: Could not initialize the POSIX performance pack.
-
Cause: The shared library for the POSIX performance pack could not be loaded.
-
Action: Ensure that the muxer shared library (libmuxer.so) exists in a directory that is in the LD_LIBRARY_PATH. If the situation persists, contact My Oracle Support.
Level: 1
Type: INTERNAL_ERROR
Impact: Socket
- BEA-000431: Accepted connection: filtering is set to: "{0}", remote address: "{1}", remote port: "{2,number,0}", local address: "{3}", local port: "{4,number,0}", protocol: "{5}"
-
Cause: This is an informational message for the administrator.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Socket
- BEA-000432: Unable to load performance pack. Using Java I/O instead. {0}
-
Cause: The native library for the performance pack was unable to be loaded.
-
Action: Ensure that the classpath and the environment is set up properly. If the situation persists, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Socket
- BEA-000440: Unable to initiate I/O for {0} {1}.
-
Cause: The initiation of the I/O operation failed, which could have been caused by the network, I/O or other problems. It could also have been an internal error.
-
Action: Correct any conditions as suggested by the error message, if applicable. If the situation persists, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Socket
- BEA-000442: The connection attempt was rejected because the incoming protocol is not enabled on channel "{0}".
-
Cause: The connection attempt was rejected because a protocol was not enabled for this server, as determined by the ServerMBean, or was not enabled on this particular channel.
-
Action: Enable the protocol on the channel.
Level: 1
Type: WARNING
Impact: Socket
- BEA-000443: The connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.
-
Cause: The connection attempt was rejected because the {1} protocol was not enabled for this server, as determined by the ServerMBean, or was not enabled on this particular channel.
-
Action: Enable the {1} protocol on the channel.
Level: 1
Type: WARNING
Impact: Socket
- BEA-000444: Could not load the performance pack that can take advantage of the /dev/(e)poll device due to: {0}. Will attempt to use the performance pack that does not depend on the /dev/(e)poll device.
-
Cause: The operating system does not support the /dev/(e)poll or the device is not initialized.
-
Action: Ensure that the operating system supports the /dev/(e)poll device.
Level: 1
Type: WARNING
Impact: Socket
- BEA-000448: Socket channel support has been enabled for a JVM on which the feature is unsupported.
-
Cause: This error is caused by turning on a feature that is not supported on the underlying JVM.
-
Action: Either disable socket channel support or use a JVM version on which this feature is supported.
Level: 1
Type: ERROR
Impact: Socket
- BEA-000449: Closing the socket, as no data read from it on {1}:{2} during the configured idle timeout of {0} seconds.
-
Cause: The WebLogic Server instance or the network may be overloaded, which is causing the socket to idle timeout.
-
Action: Capacity tuning of the server is required.
Level: 1
Type: WARNING
Impact: Socket
- BEA-000451: Closing the socket, as end of file is encountered while reading from the socket to the ONS server at {0}.
-
Cause: The connection to the remote Oracle Notification Server (ONS) process might have been disconnected.
-
Action: Check the status of the remote ONS process.
Level: 1
Type: WARNING
Impact: Socket
- BEA-000452: An exception occurred on the socket to the ONS server at {0}: {1}.
-
Cause: An exception occurred while reading from the socket. The connection to the remote Oracle Notification Server (ONS) process might have been disconnected.
-
Action: Check the network connectivity to the remote ONS process. If the situation persists after environmental issues are resolved, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: Socket
- BEA-000454: Unable to establish connection to the remote ONS process at {0}:{1}. Exception occurred while doing handshake: {2}
-
Cause: An exception occurred while doing handshake with the remote ONS process.
-
Action: Check the exception and ONS log file for additional details.
Level: 1
Type: ERROR
Impact: Socket
- BEA-000455: Attempting to remove unregistered HandshakeCompletedListener: class={0}, instance={1}.
-
Cause: The unregistered HandshakeCompletedListener: class={0}, instance={1}, is attempting to be removed.
-
Action: The unregistered HandshakeCompletedListener: class={0}, instance={1}, is attempting to be removed.
Level: 1
Type: ERROR
Impact: Socket
- BEA-000456: Unable to load performance pack. Using Java I/O instead.
-
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.
Level: 1
Type: ERROR
Impact: Socket
- BEA-000457: NIOInputStream received error while closing java.nio.channels.Selector: : {0} {1}.
-
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.
Level: 1
Type: WARNING
Impact: Socket
- BEA-000503: Incoming message header or abbreviation processing failed. {0}
-
Cause: While processing an incoming message an error was encountered. It is likely that the message was corrupted.
-
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1
Type: ERROR
Impact: RJVM
- BEA-000504: Unmarshal exception: received illegal command code: {0}
-
Cause: A message containing an invalid command code was received. This message cannot be processed. One of the possible reasons is that the message was corrupted in transit.
-
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1
Type: ERROR
Impact: RJVM
- BEA-000505: Peer did not send us a valid heartbeat interval; using the default heartbeat specified as a property.
-
Cause: The incoming message has an invalid heartbeat interval. This is either due to message corruption in transit or to an invalid choice for the heartbeat interval on the peer that is attempting to establish communication with this JVM.
-
Action: If the peer that is attempting to establish communication is overriding the default heartbeat interval, ensure that a valid interval is used. If not, contact My Oracle Support with the server logs and configuration.
Level: 1
Type: ERROR
Impact: RJVM
- BEA-000506: Closing: {0} because of {1}
-
Cause: This JVM has received an incoming message that is incompatible with the way the protocols are supposed to work.
-
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1
Type: ERROR
Impact: RJVM
- BEA-000507: Could not create/send request to close duplicate connection message. {0}
-
Cause: Creation or sending of the message to request closing a connection caused an I/O error.
-
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1
Type: WARNING
Impact: RJVM
- BEA-000510: Unsolicited response: {0}
-
Cause: A duplicate response has been received for a request that has already received its response.
-
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1
Type: WARNING
Impact: RJVM
- BEA-000511: Unsolicited error response for: {0}
-
Cause: A duplicate error response was received for a request that has already received its response or its error response.
-
Action: This is most likely a temporary situation. No action is necessary. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1
Type: WARNING
Impact: RJVM
- BEA-000514: openConnection() failed. {0}
-
Cause: Possible causes are an invalid target address or the target not being active or reachable.
-
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1
Type: ERROR
Impact: RJVM
- BEA-000515: execute failed {0}
-
Cause: A failure was encountered when handling the incoming HTTP message.
-
Action: This is most likely a temporary situation. No action is required. If this situation continues, contact My Oracle Support with the server logs and configuration.
Level: 1
Type: ERROR
Impact: RJVM
- BEA-000572: The server rejected a connection attempt {0} probably due to an incorrect firewall configuration or administrative command.
-
Cause: The incoming connection attempt was probably made through an address translating firewall. WebLogic Server needs to be correctly configured for this to work. This message can also occur if an administration connection attempt, requiring administrator level security, is made on a non-administrative port.
-
Action: Configure the public and private addresses for this WebLogic Server instance to reflect the configuration of the firewall. The private address is the actual address the server is running. The public address is the address that external clients use to connect.
Level: 1
Type: ERROR
Impact: RJVM
- BEA-000611: No resources in the pool {0} will be tested, as the specified MaxUnavailable {1} has been reached.
-
Cause: The application MaxUnavailable attribute for this pool has been configured. Since the number of unavailable resources in the pool has reached or exceeded the configured limit, no more resources will be tested. Resources become unavailable to the application during the testing.
-
Action: Tune the MaxUnavailable attribute for the pool if so desired.
Level: 1
Type: NOTIFICATION
Impact: Common
- BEA-000612: All {1} resource instances currently available in the pool {0} are being tested.
-
Cause: This is a warning indicating that all currently available resources in the pool are being tested, and therefore some or all of them may become unavailable to the application for a short time.
-
Action: Reduce the current setting of the MaxUnavailable attribute for the pool.
Level: 1
Type: NOTIFICATION
Impact: Common
- BEA-000619: Unable to forcibly release resource "{1}" back into the pool "{0}". Received exception: {2}.
-
Cause: As part of the InactiveResourceTimeout feature, resources that are found to be inactive for the configured period of time are forcibly released back into the pool. The operation could not be performed for the indicated reason.
-
Action: Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Common
- BEA-000620: Forcibly releasing inactive resource "{1}" back into the pool "{0}".
-
Cause: The resource was found to be unused by the application for the specified duration and is being forcibly released back into pool.
-
Action: Check application code for leakages of resource objects or tune the configured value of the relevant pool attribute.
Level: 1
Type: WARNING
Impact: Common
- BEA-000622: Ignoring an attempt to release resource "{1}" to pool "{0}" after the pool has been shut down.
-
Cause: Application is trying to release a resource to a pool after the pool has been shut down.
-
Action: Check application behavior. All resources should be closed before the application is shut down.
Level: 1
Type: WARNING
Impact: Common
- BEA-000623: Setting CapacityIncrement for pool "{0}" to 1. The specified value of "{1}" is not valid.
-
Cause: The application had specified an invalid value for CapacityIncrement.
-
Action: Check and correct the specified value for CapacityIncrement for the indicated pool.
Level: 1
Type: WARNING
Impact: Common
- BEA-000624: Setting frequency of testing of free resources in pool "{0}" to five seconds since the specified value of "{1}" is not valid.
-
Cause: The application had specified an invalid value for the test frequency.
-
Action: Check and correct the specified value for TestFrequencySeconds for the indicated pool.
Level: 1
Type: WARNING
Impact: Common
- BEA-000629: Recreated "{2}" out of "{1}" resources for pool "{0}".
-
Cause: As part of forcibly suspending a pool, all resources currently in use are destroyed and recreated. This message indicates that not all required resources were recreated.
-
Action: Contact My Oracle Support.
Level: 1
Type: WARNING
Impact: Common
- BEA-000630: Unable to create "{1}" resources for pool "{0}".
-
Cause: As part of the ConnectionCreationRetry feature, pools periodically attempt to create unavailable resources. This message indicates that, in the current attempt, the indicated number of resources could not be created.
-
Action: Check if the failure condition that prevents the resources from being created (for example, database server or downed network connectivity to it) is still persisting.
Level: 1
Type: WARNING
Impact: Common
- BEA-000631: Unknown resource "{1}" being released to pool "{0}": {2}
-
Cause: The application is trying to release a resource to a pool that is no longer part of the pool. This could happen if the pool was forcibly suspended (which results in all borrowed resources being closed and replaced with new ones) while the resource was borrowed by the application.
-
Action: Check the application behavior.
Level: 1
Type: WARNING
Impact: Common
- BEA-000632: Resource Pool "{0}" shutting down, ignoring {1} resources still in use by applications.
-
Cause: The administrator is shutting down the pool while applications are still using resources they have obtained from the pool. It is possible that these resources may have been leaked by the applications.
-
Action: Check the application behavior.
Level: 1
Type: WARNING
Impact: Common
- BEA-000633: Resource Pool "{0}" suspending due to consecutive number of resource creation failures exceeding threshold of {1}
-
Cause: Resource creation or resource tests have repeatedly failed.
-
Action: Determine the cause of resource failures and take corrective action.
Level: 1
Type: NOTIFICATION
Impact: Common
- BEA-000634: Resource hang detected for pool "{0}", group "{1}". Waited {2} milliseconds where a typical test has been taking {3}.
-
Cause: Resource tests have been taking longer than expected.
-
Action: Correct the condition that causes the resource tests to block for extended periods of time.
Level: 1
Type: NOTIFICATION
Impact: Common
- BEA-000635: Resource Pool "{0}", group "{1}" disabled due to number of resource creation or test failures exceeding threshold of {2}.
-
Cause: Resource creation or resource tests have repeatedly failed.
-
Action: Determine the cause of resource failures and correct.
Level: 1
Type: NOTIFICATION
Impact: Common
- BEA-000801: ExecuteRequest: {0} cancelled.
-
Cause: This only happens when WebLogic Server is used in conjunction with an IDE, which uses JVMDI to cancel in-flight requests. If this occurs in normal operation, contact My Oracle Support.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Kernel
- BEA-000803: The Class {0} has a setter {1} for attribute {2} which does not have a constructor that could be initialized from a String value of {3}.
-
Cause: No constructor that takes a String argument was found for the declared attribute type.
-
Action: Provide a constructor with a String argument.
Level: 1
Type: ERROR
Impact: Kernel
- BEA-000808: The executing thread is a non-WebLogic Server thread. Modify the application to use the Commonj Work Manager API.
-
Cause: The use of an application spawned a Java thread instead of the Commonj Work Manager API.
-
Action: Modify the application to use the Commonj Work Manager APIs.
Level: 1
Type: WARNING
Impact: Kernel
- BEA-000902: A duplicate expression was found in the system property {0}.nonProxyHosts: {1}.
-
Cause: The system property {0}.nonProxyHosts contains a pipe character delimited list of hosts, which should be connected to directly and not through the proxy server.
-
Action: Check the system property {0}.nonProxyHosts. The value can be a list of hosts, each separated by a |. In addition, a wildcard character (*) can be used for matching. For example: -D{0}.nonProxyHosts="*.foo.com|localhost".
Level: 1
Type: ERROR
Impact: Net
- BEA-000903: Failed to communicate with proxy: {0}/{1}. Will try connection {2}/{3} now.
-
Cause: An IOException was received while communicating with the proxy server.
-
Action: Check the exception for more information. Check if the proxy is running by pinging the proxy: {0}/{1} from the same machine.
Level: 1
Type: ERROR
Impact: Net
- BEA-000904: {0} initializing the URL stream handler with custom factory: {1}.
-
Cause: The factory class that was specified against the system property weblogic.net.http.URLStreamHandlerFactory failed to load or invoke.
-
Action: Check the system property weblogic.net.http.URLStreamHandlerFactory. This property is used to set a custom URLStreamHandlerFactory.
Level: 1
Type: ERROR
Impact: Net
- BEA-001064: Ignoring the property "enableTwoPhaseCommit" for JDBCTxDataSource "{0}". This property is used only for those drivers that do not natively support XA.
-
Cause: The property EnableTwoPhaseCommit was configured to "true" for an XADataSource and will be ignored.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001066: Delaying {0,number} seconds before making a {1} pool connection.
-
Cause: Some databases cannot handle a tight loop of making multiple connections from one application. If this is the case and the delay is more than 2 seconds, this message will be printed.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001074: A JDBC pool connection leak has been detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the data source connection pool. The following stack trace at create shows where the leaked connection was created. {0}
-
Cause: A JDBC pool connection leak was detected. A connection leak occurs when a connection obtained from the pool was not closed explicitly by calling close() and then was disposed by the garbage collector and returned to the data source connection pool. A stack trace is printed indicating where the leaked connection was created.
-
Action: Close the connection appropriately.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001076: An attempt has been made to release a connection that belongs to a non-existing pool. Ensure that the pool "{0}" has been destroyed by intent.
-
Cause: An attempt was made to release a connection that belongs to a non-existing pool.
-
Action: Correct the destroy operation to specify a valid pool name.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001104: A globally scoped data source connection pool named ({0}) already exists.
-
Cause: When adding or referencing a JDBC data source connection pool that is an application-scoped pool, a globally scoped data source connection pool with the same name already exists. The locally scoped pool has precedence over the global pool.
-
Action: If you want to reference the global pool in your application, the name of the global pool or the application-scoped pool must be changed to be unique.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001105: Referenced global pool ({0}) has the same name as a locally defined data source connection pool or data source ({1}).
-
Cause: When deploying a JDBC data source connection pool (not application-scoped) an application (locally) scoped data source connection pool with the same name already exists. The locally scoped pool has precedence over the global pool.
-
Action: If you want to reference the global pool in your application, the name of the global pool or the application-scoped pool must be changed to be unique.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001107: There is a globally defined data source ({0}) with the same JNDI name ({1}) as a locally defined data source.
-
Cause: It is possible to use a resource descriptor with application-scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name that is specified in the resource descriptor, it is assumed that this is a pool that the application meant to use and it is bound into comp/env. However, a check in the global namespace indicates that there is also a global pool with the same JNDI name.
-
Action: If you want to reference the global pool in your application, the JNDI name of the global pool or the application-scoped pool must be changed to be unique.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001108: A locally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).
-
Cause: It is possible to use a resource descriptor with application-scoped pools. If the local JNDI lookup reveals that there is a pool with the JNDI name specified in the resource-descriptor, it is assumed that this is the pool that the application meant to use and it is bound into comp/env.
-
Action: No action is required. If this association is not desired, specify a unique JNDI name in the resource descriptor.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001109: A globally scoped pool ({0}) was bound into comp/env with the JNDI name ({1}).
-
Cause: It is possible to use a resource descriptor with global data source connection pools. If the JNDI lookup reveals that there is a pool with the JNDI name that is specified in the resource descriptor, it is assumed that this is the pool that the application was meant to use and it is bound into comp/env.
-
Action: No action is required. If this association is not desired, specify a unique JNDI name in the resource descriptor.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001110: No test table set up for pool "{0}". Connections will not be tested.
-
Cause: TestConnectionsOnReserve, TestConnectionsOnRelease, TestConnectionsOnCreate, TestFrequencySeconds were configured but TestTableName was not configured.
-
Action: Configure a valid TestTableName for the data source connection pool.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001111: Unable to verify the test "{1}" set up for pool "{0}". Connections will not be tested. The test will not be used by isValid either.
-
Cause: While creating a data source connection pool with the attributes specified to test the pool connections, a test is run during the pool initialization. This test failed with the printed error.
-
Action: Check the SQL error that occurred and correct the problem. The specified TestTableName might not exist.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001112: Test "{1}" set up for pool "{0}" failed with exception: "{2}".
-
Cause: The specified data source connection pool has been configured with one or more attributes to test the pool connections. One of those test attempts failed. The associated error is printed.
-
Action: Check the associated error to see what the problem is and correct it. Normally, this indicates that a connection was lost to the database (the database is down). This needs to be corrected by the database administrator.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001116: Disable and freeze users called on data source connection pool "{0}" by "{1}".
-
Cause: An operation to disable and freeze users on the specified data source connection pool has been started, as requested by the application.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001117: Disable and drop users called on data source connection pool "{0}" by "{1}".
-
Cause: An operation to disable and drop users on the specified data source connection pool has been started, as requested by the application.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001118: Unable to register for receiving MBean notifications of dynamic configurations changes for data source connection pool "{0}": "{1}". Pool will not be dynamically reconfigured.
-
Cause: The server was unable to register for receiving MBean notifications of dynamic configurations changes for the specified data source connection pool. The connection pool will not be dynamically reconfigured.
-
Action: Check the exception that is printed along with this message to see what the cause of the failure was.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001119: Unable to delete configuration MBean for pool "{0}": "{1}"
-
Cause: While doing a forced shutdown, the data source connection pool was removed but the associated MBean for the connection pool was not removed.
-
Action: Check the exception that is printed along with this message to see what the cause of the failure was.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001130: Disabled statement caching for connection in pool "{0}" as it is using the WebLogic Type-2 XA driver.
-
Cause: Statement caching was disabled for the specified data source connection pool because it is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when the XAResource.end is called, causing all prepared statements to be no longer valid.
-
Action: No action is required. Use a different driver if you want to use the prepared statement cache with the driver.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001131: Received an exception when closing a cached statement for the pool "{0}": {1}.
-
Cause: When closing a prepared statement in the prepared statement cache for the specified data source connection pool, an error occurred.
-
Action: Check the associated error that is printed and, if possible, correct the problem.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001132: Initialized statement cache of size "{1}" for connection in pool "{0}".
-
Cause: A prepared statement cache has been enabled for a connection in the specified data source connection pool.
-
Action: No action is required. If you do not want statement caching turned on for the pool, do not configure or disable it.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001133: Statement caching is not enabled for connection in specified data source connection pool "{0}".
-
Cause: A configured data source connection pool has been started without statement caching being enabled.
-
Action: No action is required. If you want statement caching turned on for the pool, configure and enable it.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001134: Statement caches of connections in the data source connection pool "{0}" have been cleared by "{1}".
-
Cause: The statement caches for connections in the specified data source connection pool have been cleared, as requested by the application.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001152: Cannot enable statement caching for connection in pool "{0}", because it is using the WebLogic Type-2 XA driver.
-
Cause: Statement caching has been disabled for the specified data source connection pool because the connection pool is using the WebLogic Type-2 XA driver. This driver has a limitation based on the implementation using the ORACLE OCI interface. Cursors are closed when XAResource.end is called, causing all prepared statements to no longer be valid.
-
Action: No action is required. Use a different driver if you want to use the prepared statement cache with the driver.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001153: Forcibly releasing inactive/harvested connection "{1}" back into the data source connection pool "{0}", currently reserved by: {2}.
-
Cause: The connection was found to be unused by the application for the specified duration (configured using InactiveConnectionTimeoutSeconds attribute of the pool MBean), and therefore is being forcibly released back into pool. Alternatively, the connection was harvested and the application callback did not close the connection.
-
Action: Check the application code for leakages of connection objects, or tune the configured value of the specifed connection pool attribute.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001154: Disabling statement caching for connection in pool "{0}".
-
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.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001155: The following exception has occurred:
-
Cause: An error condition has occurred.
-
Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001165: Invalid statment cache size "{1}" specified for connection in pool "{0}".
-
Cause: An invalid value has been specified for statement cache size for connections in the indicated data source connection pool.
-
Action: Check the allowed limits for statement cache size for this data source connection pool and fix the specified value.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001250: Unable to load application configured callback {1} for multi data source {0}, got error: {2}. Application control of multi data source failover behaviour will not work.
-
Cause: This is most likely because the application-defined class location has not been added to the CLASSPATH environment varible.
-
Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001251: Application configured callback {1} for multi data source {0} does not implement required interface {2}. Application control of multi data source failover behaviour will not work.
-
Cause: The configured callback {1} does not implement the required interface {2}.
-
Action: Refer to the WebLogic Server documentation.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001503: Creating application-scoped data source connection pool {0} for Application {1}, Module {2}, URL = {3}, Properties = {4}.
-
Cause: A request was made to create the data source connection pool, either implicitly or explicitly.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001526: Unable to load class "{0}", got exception : {1}. Driver Interception feature disabled.
-
Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.
-
Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001547: The "{0}" field value "{1}" in table reference "{2}" format [[[catalog.]schema.]table) is too long. The database supports a maximum length of "{3}" for this field.
-
Cause: This is a configuration error.
-
Action: When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001548: Empty field value in table reference "{0}" (format [[[catalog.]schema.]table).
-
Cause: This is a configuration error.
-
Action: Ensure that the entire table reference is blank, or that the table field is not blank. If there is no schema, ensure that there are no periods "." in the table reference. Do not start the table reference with a period ".". Note that JDBC stores automatically append "WLStore" to table references.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001549: An old style WebLogic driver URL {0} is used. Because the WebLogic driver URL auto-convert switch is turned on, it is converted to {1}.
-
Cause: An old style WebLogic driver URL is used and the WebLogic driver URL auto-convert switch is turned on.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JDBC
- BEA-001550: WebLogic Oracle driver is being used. The driver URL is {0}. WebLogic Server no longer supports the WebLogic Oracle driver.
-
Cause: The WebLogic Oracle driver has been deprecated and removed.
-
Action: Stop using the WebLogic Oracle driver, use the Oracle Thin driver instead.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001551: Application context for member data source {1} not found for standalone multi data source module {0}. Ensure that multi data source standalone modules have a higher deployment order than member data source standalone modules.
-
Cause: The deployment order of the multi data source is the same or lower than one of its member datasources.
-
Action: Change the deployment order of the standalone multi data source to be greater than each member data source's deployment order.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001552: The logging last resource (LLR) data source {0} will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.
-
Cause: Remote JDBC access over RMI is disabled.
-
Action: Either configure the data source to use an XA-capable driver, or enable remote JDBC on all servers.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001553: Unable to deploy JDBC data source {0}. No credential mapper entry found for password indirection user {1}
-
Cause: No credential mapper entry was found for user {1} on data source {0}
-
Action: Ensure that a credential mapper entry is defined for the data source {0} that maps the specified user name {1} to a password. The WebLogic Server administration console provides support for managing data source credential mapper entries.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001555: Invalid member data source {1} specified for multi data source {0}. GridLink data source may not be used in multi data source configurations.
-
Cause: A GridLink data source was specified as a multi data source member.
-
Action: Either use a single GridLink data source or define generic data sources for use in a multi data source configuration.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001570: Attempt to enable Fast Application Notification (FAN) support for a non-GridLink data source {0}, which is not supported.
-
Cause: Subscribing to FAN events is only supported by GridLink data sources.
-
Action: Either set the FAN enabled attribute to false or configure a GridLink data source.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001571: Unable to load the connection labeling callback class "{0}", got exception : {1}.
-
Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.
-
Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001574: Unable to load the connection Initialization callback class "{0}", got exception : {1}.
-
Cause: This is most likely because the application-defined class' location has not been added to the CLASSPATH environment varible.
-
Action: Please check that you specified the correct class name and that your CLASSPATH includes this class.
Level: 1
Type: ERROR
Impact: JDBC
- BEA-001586: EndRequest failed: {0}
-
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.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-001587: For LLR RAC DataSource {0} Member of MultiDataSource, test-on-reserve is disabled, and the health of the DataSource can not be verified.
-
Cause: Test on Reserve is disabled in the DataSource configuration.
-
Action: Enable Test on Reserve in the DataSource configuration. If all memeber DataSources are marked as unhealthy and the WLS admin server fails to boot use WLST to change configuration.
Level: 1
Type: WARNING
Impact: JDBC
- BEA-002001: Received an unknown message type.
-
Cause: This should not occur. This indicates that the client is sending garbaged messages. It might also indicate that malicious third parties are trying to access the server using IIOP.
-
Action: Contact My Oracle Support.
Level: 1
Type: NOTIFICATION
Impact: IIOP
- BEA-002002: Failed to parse method name {0}.
-
Cause: This can happen for a variety of reasons. Normally, it is because the caller made a request for a non-existent method. Alternatively, the IDL mangling of the method name may be ambiguous, so WebLogic Server cannot decide which method to call.
-
Action: If the IDL mangling is causing a problem, try changing the name of the method. In particular, names such as getSomedata() (where somedata is also the name of an attribute or method) can cause problems. Also, some bugs with name mangling exist in JDK 1.3.1. Try using a JDK 1.4 client.
Level: 1
Type: NOTIFICATION
Impact: IIOP
- BEA-002003: Unable to send the message: {0}.
-
Cause: Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.
-
Action: Verify that the client-server network connection is working.
Level: 1
Type: ERROR
Impact: IIOP
- BEA-002005: OutOfMemoryError in adapter: {0}.
-
Cause: This is often caused by marshalling mismatches between the client and the server and is generally a bug in either the client or the server or both.
-
Action: Restart the server and contact My Oracle Support.
Level: 1
Type: INTERNAL_ERROR
Impact: IIOP
- BEA-002006: Cannot scavenge idle connections, {0}
-
Cause: The server was unable to schedule a trigger to watch for idle IIOP connections. The fact that it was unable to do so indicates some core failure in the server.
-
Action: Restart the server. If this occurs again, contact Oracle Customer Support.
Level: 1
Type: ERROR
Impact: IIOP
- BEA-002008: Failed to export {0}. The following exception occurred: {1}.
-
Cause: This is most often caused by the server being unable to find or generate an IIOP stub for the remote object. Ensure that the Common Object Request Broker API (CORBA) objects have corresponding _Stub classes in the server classpath. RMI-IIOP object stubs should be generated automatically.
-
Action: For CORBA objects, ensure that the idlj was run on the server class. For RMI-IIOP objects, contact My Oracle Support.
Level: 1
Type: NOTIFICATION
Impact: IIOP
- BEA-002011: Failed to marshal exception {0}: {1}.
-
Cause: The server could not find the appropriate exception definitions in its classpath. For Common Object Request Broker API (CORBA) exceptions, the application must contain the exception helper classes as well as the exception classes.
-
Action: Add missing exception classes to the application.
Level: 1
Type: ERROR
Impact: IIOP
- BEA-002013: Complete failure to send exception {0}: {1}.
-
Cause: Some sort of communication failure has occurred. This could be because the target closed the IIOP connection or because of some transient network fault.
-
Action: Verify the client-server network connection.
Level: 1
Type: ERROR
Impact: IIOP
- BEA-002015: Using javax.rmi.CORBA.UtilClass {0}; The IIOP subsystem requires a WebLogic Server-compatible UtilClass.
-
Cause: Some application code, or a foreign object request broker (ORB), set the system property javax.rmi.CORBA.UtilClass or tried accessing javax.rmi.CORBA.Util functions before the IIOP subsystem had initialized.
-
Action: The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.
Level: 1
Type: ERROR
Impact: IIOP
- BEA-002016: Using javax.rmi.CORBA.PortableRemoteObjectClass {0}, the IIOP subsystem requires a WebLogic Server-compatible PortableRemoteObjectClass.
-
Cause: Some application code, or a foreign object request broker (ORB), set the system property javax.rmi.CORBA.PortableRemoteObjectClass or tried accessing javax.rmi.PortableRemoteObject functions before the IIOP subsystem had initialized.
-
Action: The IIOP subsystem will not function correctly in this scenario. Correct the application code and restart the server.
Level: 1
Type: ERROR
Impact: IIOP
- BEA-002028: An OTS error occurred: {0}, {1}.
-
Cause: OTS errors are generally not bugs but always result in exception information being lost when propagated to the caller. Thus, the root cause is always logged, so that system administrators can determine the real cause. OTS errors are generally caused by some transaction subsystem operation (for instance, a transaction being rolled back).
-
Action: Ensure that this is an expected error.
Level: 1
Type: WARNING
Impact: IIOP
- BEA-002041: Connection attempt was rejected because IIOP is not enabled on this channel.
-
Cause: The connection attempt was rejected because IIOP is not enabled at all for this server, as determined by the ServerMBean, or is not enabled on this particular channel.
-
Action: Enable IIOP.
Level: 1
Type: WARNING
Impact: IIOP
- BEA-002606: The server is unable to create a server socket for listening on channel "{3}". The address {0} might be incorrect or another process is using port {1,number,0}: {2}
-
Cause: The address was incorrect or another process was using the port.
-
Action: Use ipconfig or ifconfig to check if the listen address is valid, and use netstat to check that the specified port is not in use by another process.
Level: 1
Type: ERROR
Impact: Server
- BEA-002608: The ListenThread failed because of an error: {0}
-
Cause: An exception occurred when the server socket was unable to accept client connections.
-
Action: Check the file descriptor limit. Tune the operating system parameters that handle socket creation using ServerSocket.
Level: 1
Type: ERROR
Impact: Server
- BEA-002612: Channel "{2}", listening on {0}:{1,number,0}, did not start did not start properly.
-
Cause: Some of the listen ports did not open or failed within the configured grace period.
-
Action: Ensure that none of the configured listen ports are in use by other processes.
Level: 1
Type: NOTIFICATION
Impact: Server
- BEA-002615: After having failed to listen, the server is now listening on channel "{2}" on {0}:{1,number,0}.
-
Cause: The server backed off because a socket exception occurred while accepting client connections. The server is now ready to accept connections.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Server
- BEA-002616: Failed to listen on channel "{2}" on {0}:{1,number,0}, failure count: {3}, failing for {4} seconds, {5}
-
Cause: An exception occurred while trying to accept client connections. The server will try to back off to aid recovery.
-
Action: The operating system (OS) limit for the number of open file descriptors (FD limit) needs to be increased. Tune the OS parameters that might help the server to accept more client connections (for example, TCP accept back log).
Level: 1
Type: INTERNAL_ERROR
Impact: Server
- BEA-002617: Attempting to close and reopen the server socket on channel "{2}" on {0}:{1,number,0}.
-
Cause: The server listener could not accept a socket connection and failed after several simple retries. It has closed and reopened the server socket.
-
Action: Check if the file decriptor limit needs to be increased. Tune the operating system parameters that might help the server accept more client connections.
Level: 1
Type: INTERNAL_ERROR
Impact: Server
- BEA-002621: The connection was rejected because the server license only allows connections from {0} unique IP addresses.
-
Cause: Clients tried to connect from more distinct addresses than the license allows.
-
Action: Use a server license that allows for more clients to connect.
Level: 1
Type: NOTIFICATION
Impact: Server
- BEA-002623: Connection rejected, the server is in the {0} state. Starting service {1}, {2} of {3}. Last service {4} took {5} milliseconds.
-
Cause: Clients tried to connect to the server before it was in the RUNNING state.
-
Action: Connect to the server after it has started.
Level: 1
Type: NOTIFICATION
Impact: Server
- BEA-002627: The domain configuration must have at least one administration channel on every server or no administration channels at all.
-
Cause: The server was contacted by a server that did not reflect the same administration state as itself.
-
Action: Modify the domain configuration so that all servers have administration channels, or enable the domain-wide administration port.
Level: 1
Type: ERROR
Impact: Server
- BEA-002631: Max threshold reached for open sockets [total open sockets: {0}, allowed max: {1}]. No more connections allowed.
-
Cause: The MaxOpenSocketCount attribute of the server configuration defines the upper bound of the number of open sockets.
-
Action: Increase the MaxOpenSocketCount attribute of the server configuration. Use the server tuning tab in the Administration Console.
Level: 1
Type: WARNING
Impact: Server
- BEA-002633: A port conflict was detected in the server configuration. The server is configured to listen on two ports that have the same port number and IP address. Channel "{0}" address "{1}" conflicts with channel "{2}" address "{3}".
-
Cause: The server is configured to listen on two ports that have the same port number and IP address.
-
Action: Ensure that the address identities [ListenAddress and ListenPort combinations] are distinct and unique.
Level: 1
Type: INTERNAL_ERROR
Impact: Server
- BEA-002637: Failed to register a disconnect listener because of {0}
-
Cause: This can happen during server startup when the incoming network connection is not suitable for callbacks and the booting server does not yet have a listen port open.
-
Action: No action is required. The server should eventually be connected properly.
Level: 1
Type: WARNING
Impact: Server
- BEA-002641: -DserverType is set to an unrecognized value: {0}. The server will start with all services enabled.
-
Cause: An undefined server type was specified or a typographical error was made.
-
Action: See the WebLogic Server documentation for valid values for -DserverType.
Level: 1
Type: WARNING
Impact: Server
- BEA-002648: Could not obtain the relevant ServerRuntimeMBean for server {0}.
-
Cause: The remote server runtime object for server {0} could not be obtained. This can happen if the server has already been shut down or is otherwise unavailable.
-
Action: If the server is active when this error occurs, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: Server
- BEA-002649: A port conflict was detected in the server configuration. Both TCP and SDP channels are configured to listen on the same port number and IP address. Channels "{0}" and "{1}" on address "{2}".
-
Cause: Both TCP and SDP channels are configured to listen on the same port number and IP address.
-
Action: Ensure that the channels with the same [ListenAddress and ListenPort combinations] either all support SDP or do not support SDP.
Level: 1
Type: INTERNAL_ERROR
Impact: Server
- BEA-002918: Server detected execute queue(s) in self-tuning mode. Execute queues will not be self-tuned. They retain their behavior from earlier releases. Consider using Work Managers to take advantage of self-tuning.
-
Cause: The execute queues were detected in the self-tuning server.
-
Action: Consider removing the execute queues. The server automatically adjusts the thread pool size for optimal performance. Work Managers can be used to change the default behavior where needed.
Level: 1
Type: WARNING
Impact: WorkManager
- BEA-002919: Unable to find a Work Manager with name {0}. Dispatch policy {0} will map to the default Work Manager for the application {1}
-
Cause: There is no Work Manager with the given name.
-
Action: This could indicate a configuration error. Check the dispatch-policy and ensure that it matches the name of a Work Manager defined either within the same application or globally.
Level: 1
Type: WARNING
Impact: WorkManager
- BEA-002939: The maximum thread constraint {0} has been reached {1} times for the last {2} seconds.
-
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.
Level: 1
Type: NOTIFICATION
Impact: WorkManager
- BEA-002940: Shutting down work manager "{0}" according to the configured work manager shutdown trigger.
-
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.
Level: 1
Type: NOTIFICATION
Impact: WorkManager
- BEA-003102: There was a failure in the execution of the post script {0} while deactivating MigratableTarget {1}. Since post script failure is marked as fatal, the MigratableTarget will not be automatically migrated. To enable automigration, fix the post script failure and manually migrate the failed migratable target or disable the post script failure fatal flag.
-
Cause: The execution ofthe post deactivation script failed.
-
Action: Fix the post deactivation script and migrate the MigratableTarget manually.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-003104: Failed to notify the execution failure of the post script {1} for {0} to the SingletonServiceStateManager because of {2}. This may affect its automatic migration behavior.
-
Cause: An exception occurred: {2}.
-
Action: Ensure that the network is working properly.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-003105: The asynchronous replication request timed out while attempting to add object {0} to the replication queue. This session has not been replicated to any backup at this point.
-
Cause: The asynchronous replication request timed out while attempting to add object {0} to the replication queue. Once full, the queue waits until it has space for the object. This wait took longer than the ClusterMBean specified AsyncSessionQueueTimeout, thus the session object was not put into the queue and will not be replicated at this time.
-
Action: This could be due to the secondary server or persistent store slowing down the replication process. To better handle this, the SessionFlushInterval and the SessionFlushThreshold can be reduced to replicate less at a time and to replicate more often. Checking the performance of the secondary server or persistent store is advised.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-003106: An unexpected exception occured during replication: {0}. Future session updates should replicate as expected.
-
Cause: An unexpected runtime exception occured during replication probably from the Remote Management Interface (RMI) stub. Future session updates should replicate as expected.
-
Action: Ensure that no problems exist in the network. If the problem persists, contact My Oracle Support. with the stack trace for further analysis.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-003107: Lost {0} unicast message(s).
-
Cause: This is an informational message. When a server joins a stable cluster, this message will appear since the server did not receive unicast messages sent out by other servers in the cluster.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-003108: Unicast receive error : {0}
-
Cause: An error occurred while trying to receive a message over the cluster broadcast.
-
Action: Ensure that the NIC is functioning properly. If it appears that no environment problems exist, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-003109: Cluster {0} uses a database as the migration basis but no data source for migration has been configured.
-
Cause: Cluster {0} uses a database as the migration basis but no data source for migration has been configured.
-
Action: Ensure that the data source is created and set for database migration basis.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-003110: Connection attempt was rejected because the incoming protocol {1} is not enabled on channel {0}.
-
Cause: The connection attempt was rejected because the {1} protocol is not enabled at all for this server, as determined by the ServerMBean, or is not enabled on this particular channel.
-
Action: Enable the {1} protocol on the channel.
Level: 1
Type: WARNING
Impact: Cluster
- BEA-003115: Failed to synchronize a secondary session due to missing updates.
-
Cause: The Work Manager queue might be full and as a result update messages were dropped.
-
Action: Either increase the number of servers in the cluster (preferred) or add more replication channels (requires server re-start).
Level: 1
Type: ERROR
Impact: Cluster
- BEA-003122: {0} : A cluster that has migratable servers could not create/execute SQL statement when validating the database connection. The cluster is misconfigured. Check the leasing table on the database and connection configuration.
-
Cause: The cluster is misconfigured.
-
Action: Check the leasing table on the database and connection configuration.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-003501: The migration of server {0} from machine {1} has failed. No suitable candidate machines could be found.
-
Cause: No candidate machines are available, or the server {0} has encountered an error on booting independent of its location.
-
Action: Further migration of server {0} has been disabled. When the cause of the problem has been determined and fixed, the server {0} should be started by the user, at which point it will resume standard automatic migration behavior.
Level: 1
Type: ERROR
Impact: Cluster
- BEA-003502: Beginning the migration of server {0} from machine {1} to machine {2}
-
Cause: The failure of server {0} has provoked a migration attempt to a new machine, machine {2}.
-
Action: No action is required, but the logs of server {0} should be examined to determine why it crashed and could not successfully restart on machine {1}.
Level: 1
Type: NOTIFICATION
Impact: Cluster
- BEA-010001: While deploying EJB "{0}", class {1} was loaded from the system classpath. As a result, this class cannot be reloaded while the server is running. To prevent this behavior in the future, make sure the class is not located in the server classpath.
-
Cause: The specified class is located in the server classpath.
-
Action: Remove this class from the server classpath. It should only be located in the packaged application.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010003: Exception occurred while loading _WL_TIMESTAMP FILE.
-
Cause: The container generates the _WL_GENERATED file, which stores the server version of the appc compiler. If the current server version is different from the version specified in the _WL_GENERATED file, appc recompiles the beans. There was an error reading this file.
-
Action: The container will automatically recompile the beans.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010006: Error occurred while saving ejb deployment timestamps. {0}
-
Cause: The container generates the _WL_GENERATED file, which stores the server version of the appc compiler. if the current server version is different from the version specified in the _WL_GENERATED file, appc recompiles the beans. There was an error writing this file.
-
Action: Please check the exception for the exact error message. The container will recompile the beans if this file is not found.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010020: EJB-20 - MessageDriven - Could not start the JMS connection: {0}
-
Cause: The JMS provider may not be available, or the Message-Driven Bean deployment descriptors or annotation or both may not be correct.
-
Action: Verify that the JMS provider is running and accessible through the network. Verify that the deployment descriptors or annotation or both specify the correct configuration information for the JMS provider.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010052: An exception occurred while creating the free pool for EJB {0}. Since this occurred during server startup, when a dependent resource may be unavailable, the error will be ignored and deployment will proceed. The EJB container will instead attempt to create the bean instances on demand. The exception was: {1}
-
Cause: An exception occurred while the EJB container was initializing the free pool of bean instances. The root exception should be printed as part of the warning message issued by the EJB container. Check the server log for further details.
-
Action: If you believe the root exception is due to a temporary condition that will automatically be resolved, no action is required. If this exception was not due to a temporary condition, fix the cause of the root exception. If changes to your application are required to fix this issue, redeploy the updated application.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010058: The EJB deployment named {0} is being recompiled within the WebLogic Server instance. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a standalone tool to generate the required classes.
-
Cause:
-
Action:
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-010061: The Message-Driven EJB {0} is unable to connect to the JMS destination {1}. The Error was: {2}
-
Cause: The JMS destination is not available due to a network problem or a problem with the JMS provider, or the configuration information in the MDB deployment descriptor or annotation or both is incorrect. This warning may also occur during WebLogic cluster startup if the JMS destination is located on another server.
-
Action: Check that the JMS provider is running and that network connectivity is available. Also check that the configuration information in the MDB deployment descriptor and/or annotation is correct.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010065: MessageDrivenBean threw an Exception in onMessage(). The exception is: {0}.
-
Cause: The onMessage method of the MDB may have generated an exception for a legitimate reason, such as the loss of a database connection. If that is not the case, then the MDB may have a programming error that causes it to generate an unchecked Java exception, such as a NullPointerException.
-
Action: Unless you are sure that the MDB has generated the exception on purpose, check the source code to ensure that it does not contain any programming errors that might cause it to generate an unchecked Java exception such as a NullPointerException or IndexOutOfBoundsException.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010073: Unable to add the {0} interface "{1}" and any dependent classes to the client-jar since it was loaded from the classpath.
-
Cause: EJB interface and other dependent classes exist in the system classpath.
-
Action: Please remove the classes from the system classpath.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010074: Unable to create the client-jar file due to classes being loaded from the classpath rather than the input JAR. Please modify your classpath so that it does not contain these classes and try again.
-
Cause: EJB interface and other dependent classes exist in the system classpath.
-
Action: Please modify your classpath so it does not contain these classes and try again.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010079: An error occurred while attempting to receive a message from JMS for processing by a Message-Driven Bean: {0} The exception is : {1}
-
Cause: The JMS provider for the MDB may have been shut down or has crashed, or network connectivity may have been lost.
-
Action: Check that the JMS provider is available and accessible through the network.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010080: An error occurred while attempting to process a message inside a Message-Driven Bean: {0} Exception is : {1}
-
Cause: This error usually occurs if the onMessage method of the MDB throws an exception.
-
Action: Check that the MDB is able to process messages by ensuring that any resources it uses (such as database connections) are available. Check the MDB source code to ensure that it does not have any bugs that cause an exception (such as a NullPointerException) to be generated.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010081: The Message-Driven Bean {0} was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.
-
Cause: The nature of the JMS API does not permit this in a standard way.
-
Action: No action is required. However, if you require better performance for a foreign JMS provider and do not need exactly-once transactional semantics, redeploy the MDB so that it has a transaction mode of NotSupported.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010086: The deployment unit {0} that contains Message-Driven Beans is undeployed already. The server cannot start the Message-Driven Beans that are part of undeployed unit.
-
Cause: The beans were started after having been undeployed.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-010087: The EJB deployment named {0} is being recompiled within the WebLogic Server instance. Please consult the server logs if there are any errors. It is also possible to run weblogic.appc as a standalone tool to generate the required classes. The generated source files will be placed in {1}.
-
Cause:
-
Action:
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-010096: The Message-Driven EJB {0} is unable to connect to the JMS destination or bind to JCA resource adapter {1}. The onnection failed after {2} attempts. The MDB will attempt to reconnect/rebind every {3} seconds. This log message will repeat every {4} seconds until the condition clears.
-
Cause: The JMS provider or JCA resource adapter is not available, or the configuration is incorrect and WebLogic Server is not able to connect.
-
Action: Ensure that the JMS provider is running and is reachable using the network, or the JCA resource adapter is deployed. Also ensure that the configuration information in the MDB deployment descriptor or the annotation or both are correct.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010098: The database type {0} mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver {1}.
-
Cause: The database type {0} mentioned in weblogic-cmp-rdbms-jar.xml does not match the database type returned by the driver {1}.
-
Action: Check the database-type tag inside weblogic-cmp-rdbms-jar.xml.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010100: This server is not part of a cluster. Therefore the InMemory replication feature for StatefulSession EJB {0} will have no effect on this server.
-
Cause: The bean has been deployed on a server, which is not a part of cluster. Hence the InMemory replication feature will be ignored.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010124: Method SecurityHelper.{0} returned a NULL principal. The CallerPrincipal stack has been corrupted.
-
Cause: One cause of corruption might be that a bean has created its own threads. Note that this would be in violation of EJB2.0 Final Spec Chapter: Runtime Management 24.1.2.
-
Action: Review your code about thread safety. If a bean does not create its own thread, this is likely a bug in the EJB subsystem and you should probably contact My Oracle Support.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010127: Incorrect data source type detected. The data source with JNDI name {0}, specified in the RDBMS deployment descriptor for the EJB {1}, does not support global transactions.
-
Cause: The EJB container requires that a data source which supports global transactions be specified for transactions to be managed correctly.
-
Action: Specify the correct data source for the EJB.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010128: Error during deployment of EJB {0}. The EJB references an application-level cache, {1}, that is not defined in the weblogic-application.xml descriptor.
-
Cause: The weblogic-ejb-jar.xml descriptor for the EJB refers to an unknown application-level cache.
-
Action: Ensure that the application-level cache is defined in the weblogic-application.xml descriptor and ensure the cache name defined in the weblogic-ejb-jar.xml is correct.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010129: Error during deployment of EJB {0}. The EJB references a MultiVersion application-level cache {1}, but it must use an Exclusive cache instead. EJBs with a concurrency-strategy of Exclusive must use an Exclusive cache.
-
Cause: An incorrect concurrency strategy is specified. The concurrency-strategy you specify for the bean must be compatible with the caching-strategy specified in weblogic-application.xml.
-
Action: Specify the correct concurrency strategy.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010130: An error occurred during deployment of EJB {0}. The EJB references an Exclusive application level cache {1}, but it must use a MultiVersion cache instead. EJBs with a concurrency-strategy of Database, ReadOnly, or Optimistic must use a MultiVersion cache.
-
Cause: An incorrect concurrency strategy is specified. The concurrency-strategy you specify for the bean must be compatible with the caching-strategy specified in weblogic-application.xml.
-
Action: Specify the correct concurrency strategy.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010132: Error during deployment of EJB {0}. The EJB has been deployed with use-select-for-update set to true. The database indicates it does not support SELECT ... FOR UPDATE.
-
Cause: The database indicates it does not support SELECT ... FOR UPDATE.
-
Action: Modify use-select-for-update to false, or use a different database that supports SELECT ... FOR UPDATE.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010141: Creation of Many-To-Many relationship for primary key: {0} and {1} effected {2} rows in {3}, instead of just 1.
-
Cause: JoinTable contains a non-unique row for specified primary keys, indicating a Many-To-Many relationship.
-
Action: Check the JoinTable to remove the duplicate row.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010144: The setXXX method for a primary key field may only be called during ejbCreate.
-
Cause: The setXXX method for a primary key field may only be called during ejbCreate.
-
Action: Remove the setXXX method call (for a primary key field) from places other than ejbCreate.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010147: The setXXX method for a cmr-field may not be called during ejbCreate. The setXXX method should be called during ejbPostCreate instead.
-
Cause: The setXXX method should be called during ejbPostCreate instead.
-
Action: Move the setXXX method call for a cmr-field to ejbPostCreate.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010152: Illegal value for concurrency-strategy. Value was {0}, but must be one of ReadOnly, Exclusive, Database, or Optimistic.
-
Cause: An illegal value was used for concurrency-strategy.
-
Action: Specify a correct value for concurrency-strategy. It must be one of ReadOnly, Exclusive, Database, or Optimistic
Level: 1
Type: ERROR
Impact: EJB
- BEA-010155: Only instances of beans with container-managed transaction demarcation can use getRollbackOnly().
-
Cause: See the error message body.
-
Action: Remove the getRollbackOnly() method call if container-managed transaction is not used, or enable container-managed transaction for EJB.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010157: Only instances of beans with container-managed transaction demarcation can use setRollbackOnly().
-
Cause: See the error message body.
-
Action: Remove the setRollbackOnly() method call if container-managed transaction is not used, or enable container-managed transaction for EJB.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010159: To support the use of Handles and HomeHandles, an EJB must be deployed with a JNDI name. This EJB, {0}, was deployed without specifying a JNDI name. To specify a JNDI name for this EJB, add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.
-
Cause: This EJB, {0}, was deployed without specifying a JNDI name.
-
Action: To specify a JNDI name for this EJB, add a jndi-name element to the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010194: Only instances of beans with bean-managed transaction demarcation can use getUserTransaction().
-
Cause: An illegal invocation was made to the getUserTransaction() method on a Container Managed Bean.
-
Action: Remove the getUserTransaction() method call from EJBs that are using container-managed transaction.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010197: The entity bean {0} uses optimistic concurrency with read-verification enabled. The database indicates that exclusive row locks are not supported. Read-verification will not guarantee data integrity if the isolation level of the transaction is lower than repeatable read.
-
Cause: This is a mismatch problem between the concurrency strategy and the transaction isolation level.
-
Action: If data integrity should be guaranteed under a read-verification enabled configuration, use the appropriate transaction isolation level.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010199: EJB {0} with run as role {1} has no run-as-principal-name specified in its deployment descriptor or annotation. The EJB container has chosen principal-name {2} from the security-role-assignment list for role {1} to be the run as principal name.
-
Cause: The specified EJB with the specified run as role has no run-as-principal-name specified in its deployment descriptor or annotation.
-
Action: Specify run-as-principal-name explicitly if the chosen principal-name is not the appropriate one.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010201: The Message-Driven Bean {0} encountered an error while recovering a JMS session. This is a secondary error. The original error occurred while the Message-Driven Bean was processing a message. The recover action was taken in an attempt to recover from the original error, which will be logged separately.
-
Cause: The Message-Driven Bean may have generated an exception, or there may be a problem with the JMS provider.
-
Action: Check that the JMS provider is running and accessible through the network. In addition, check that the Message-Driven Bean onMessage method does not generate any unchecked Java exceptions such as NullPointerException or IndexOutOfBoundsException.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010202: Call-by-reference is not enabled for EJB {0}. The server will have better performance if it is enabled. To enable call-by-reference, set the enable-call-by-reference element to True in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB.
-
Cause: Call-by-reference is not enabled.
-
Action: If appropriate, enable call-by-reference in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for the EJB.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010204: The EJB component, {0}, will be rolled back and redeployed to update class {1}. This class is not a bean implementation class. Only bean implementation classes can be updated without redeploying the entire module, and only when enable-bean-class-redeploy is set to True in weblogic-ejb.jar.xml.
-
Cause: A command was issued to update the specified class.
-
Action: No action is necessary. This is just an informative message indicating why the EJB module is being redeployed, since this can cause disruption to clients using an EJB in this EJB module.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-010205: The EJB module, {0}, will be rolled back and redeployed to update the class {1}. Bean implementation classes, such as this, can be updated without redeploying the entire EJB module. However, this can only be done if enable-bean-class-redeploy is set to True in weblogic-ejb.jar.xml or the corresponding annotation. If this is the behavior you want, set this value to True and redeploy.
-
Cause: A command was issued to update the specified class.
-
Action: No action is necessary. This is just an informative message indicating why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-010206: The EJB module, {0}, will be rolled back and redeployed to update the class {1}. This bean implementation class could not be updated without redeploying the entire EJB module because it was changed incompatibly. Incompatible changes are any changes that cause the EJB compiler to be run. This includes modifying a public variable name or a public method signature.
-
Cause: A command was issued to update the specified class.
-
Action: No action is necessary. This is just an informative message to let the user know why the EJB module is being redeployed since this can cause disruption to clients using an EJB in this EJB module.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-010212: The EJB {0} contains at least one method without an explicit transaction attribute setting. The default transaction attribute of {1} will be used for the following methods: {2}.
-
Cause: The ejb-jar.xml deployment descriptor or corresponding annotation does not contain transaction attribute settings for the specified EJB methods.
-
Action: Assign transaction attributes for all methods of your EJB.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010214: Error starting MDB {0}.
-
Cause: This error itself does not provide the cause of the error. The log file will contain an exception stack indicating the root cause of the failure.
-
Action: Inspect the log file for indications of the root cause of the failure.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010215: The durable subscription store with jms-client-id equal to {0} is deleted when MDB {1} is removed from the server.
-
Cause: The durable subscription store is deleted when the MDB is removed from the server and its durable-subscription-deletion is set to true.
-
Action: This is an informational message. No action is needed.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-010216: The Message-Driven EJB: {0} is generating an exception when processing the messages. Delivery failed after {1} attempts. The EJB container will suspend the message delivery for {2} seconds before retry.
-
Cause: The Message-Driven Bean is generating an exception.
-
Action: Check the message delivery methods and resolve the exception condition.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010221: The Message-Driven EJB: {0} is unable to bind to the JCA resource adapter: {1}. The Error was: {2}
-
Cause: The JCA resource adapter is not deployed, or the configuration information in the MDB deployment descriptor or corresponding annotation is incorrect.
-
Action: Check that the JCA resource adapter is deployed and the configuration information in the MDB deployment descriptor or corresponding annotation is correct.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010222: The aggregate query {0} has a primitive return type but the query returned null because there were no values to which to apply the aggregate function.
-
Cause: There were no values to which to apply the aggregate function
-
Action: Handle ObjectNotFoundException correctly on the application side.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010224: The EJB Timer: {0} has failed to successfully time out in {1} consecutive attempts. The container will delay the timeout for {2} milliseconds as configured for the timer.
-
Cause: This was caused by a failed ejbTimeout.
-
Action: It is possible that no action needs to be taken. However, it may be good to investigate why the original ejbTimeout failed.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-010225: The EJB Timer: {0} has failed to successfully time out in {1} consecutive attempts. Since no retry delay was configured for this timer, the container will automatically delay the timeout for {2} seconds.
-
Cause: This was caused by a failed ejbTimeout.
-
Action: It is possible that no action needs to be taken. However, it may be good to investigate why the ejbTimeout has consecutively failed.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-010226: Error executing clustered EJB timer for EJB {0} of module {1} of application {2}. While executing, the timer was unable to find a necessary internal resource required to execute. The most likely cause of this issue is that the EJB is no longer configured to use the clustered EJB timer service but timers still exist in the database.
-
Cause: The most likely cause of this error is that the EJB associated with this timer is no longer configured to use the clustered EJB timer service.
-
Action: If the EJB in question is no longer configured to use EJB timers, the timers associated with it should be removed from the database. This can be achieved by re-enabling clustered EJB timers for the EJB and then undeploying the EJB. This will cause any timers associated with the EJB to be removed from the database.
Level: 1
Type: ERROR
Impact: EJB
- BEA-010230: EJB {0} : method name {1} and method name {2} are equal under case-insensitive comparison but both methods have declarative security settings. Declarative security checks are case-insensitive.
-
Cause: Both of the specified methods have declarative security settings.
-
Action: Avoid case-insensitive method name conflicts if method permissions are configured.
Level: 1
Type: WARNING
Impact: EJB
- BEA-010232: The version of EJB in Module "{0}" is "{1}". However, the deprecated "enable-bean-class-redeploy" feature is not supported in EJB 3.
-
Cause: See error message body.
-
Action: Use the FastSwap feature instead and remove the "enable-bean-class-redeploy" settings in the weblogic-ejb-jar.xml.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011047: In ejb-jar.xml or annotation, EJB {0} has container-transactions set when the EJB has a transaction-type of Bean. The container-transaction settings will be ignored.
-
Cause: The specified EJB has container-transactions set when the EJB has a transaction-type of Bean.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011057: The table {0} was created by the user. The container does not drop or alter user-created tables. The container would verify the table in this case.
-
Cause: The table was already created by the user.
-
Action: Drop the table if the existing table is not correct. The container will then be able to create the table.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011059: The container was unable to create the DDL file.
-
Cause: This error does not provide the cause of the error. The log file will contain an exception stack indicating the root cause of the failure.
-
Action: Inspect the log file for indications of the root cause of the failure.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011061: Stack trace associated with message {0} follows:
-
Cause: An error condition was reported.
-
Action: Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help with debugging an existing problem.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-011063: Stateless session beans with bean-managed transactions must commit or roll back their transactions before completing a business method. The method {0} of EJB {1} either returned or generated an Exception without properly completing a transaction.
-
Cause: A transaction started by the stateless session bean method did not complete before the method completed.
-
Action: Check the bean code to determine what caused the transaction to not commit or roll back, and fix code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011070: In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <field-group>(s) are defined but are not used in any <weblogic-query>, <weblogic-relationship-role> or <relationship-caching> <caching-element>s. The <group-name>(s) of the unreferenced <field-group>(s) are: {1}
-
Cause: Some field group definitions are not referenced in any query or relationship.
-
Action: Remove the field groups listed in the logged message from the descriptor or include its usage appropriately.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011071: In the <weblogic-rdbms-bean>, for <ejb-name> {0}, some <relationship-caching>(s) are defined but are not used in any <weblogic-query>. The <caching-name>(s) of the unreferenced <relationship-caching>(s) are: {1}
-
Cause: There are unused relation cachings defined in the weblogic-rdbms descriptor.
-
Action: Remove the unused relationship cachings listed in the logged message from the descriptor or include its usage appropriately.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011073: An error occurred while the EJB container was attempting to obtain information about the table {0} from the database. This information is necessary to validate the mapping between the fields of the EJB {1} and the table. The exception is: {2}
-
Cause: The most likely cause is an error communicating with the database. The error message should include the specific error message.
-
Action: The action depends on the specific error that occurred. Actions may range from retrying the failed deployment to seeking help from your database administrator. Also, ensure that you are using a supported database.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011077: The EJB deployment contains settings for automatically creating or altering database tables. However, the server is in production mode, so no database tables will be created or altered.
-
Cause: The server is in production mode so the create-default-dbms-tables settings are being ignored.
-
Action: No action is required. To suppress the warning, remove the create-default-dbms-tables setting from your EJB deployment.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011082: Error: The message-destination-link {0} for the Message-Driven Bean {1} in the application module {2} could not be resolved. The target message-destination for the Message-Driven Bean could not be found. Ensure that the link is correct.
-
Cause: The target of the message-destination-link could not be found in the application.
-
Action: Fix the message-destination-link to point to a valid message-destination.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011083: The EJB specification prohibits stateful session beans from using the TimerService.
-
Cause: An illegal call was made to the getTimerService() method on the stateful session beans SessionContext.
-
Action: Correct the stateful session bean code so that it does not call the getTimerService() method from the bean class.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011084: This EJB class does not support EJB timers and therefore is prohibited from using the TimerService. To use EJB timers, the bean class must implement javax.ejb.TimedObject or have a method that is annotated with @Timeout.
-
Cause: An illegal call to the getTimerService() method on the EJBContext.
-
Action: Correct the EJB class so it either implements the javax.ejb.TimedObject interface or ensure that it does not call the getTimerService() method on the EJBContext.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011087: This TimerHandle is being invoked outside of the context of the application in which it was created. Since timers are local objects, they can only be called from within the same application in which they were created.
-
Cause: This TimerHandle is being invoked outside of the context of the application in which it was created.
-
Action: Ensure that your application does not pass any TimerHandle references outside of the scope of the application.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011088: The following error occurred while invoking the ejbTimeout(javax.ejb.Timer) method of EJB {0}.
-
Cause: This could be caused by erroneous code in the ejbTimeout method or by the failure of a dependent resource.
-
Action: All exceptions that occur while invoking or attempting to invoke the ejbTimeout method should be investigated and resolved. If the ejbTimeout method is non-transactional, that is, has a transaction attribute of NotSupported, or if the bean uses bean-managed transactions, the ejbTimeout method may not be retried, leading to missed timeout notifications.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011089: The following error occurred while attempting to remove an EJB timer from the persistent store for EJB {0}.
-
Cause: This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.
-
Action: This cause of this error should be investigated and resolved promptly.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011090: The following error occurred while preparing to invoke the ejbTimeout(javax.ejb.Timer) method of EJB {0}.
-
Cause: This is an unexpected error so the cause is unknown. The accompanying exception and stack trace should provide information as to the cause of the error.
-
Action: All exceptions that occur while attempting to invoke the ejbTimeout method should be investigated and resolved.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011091: The table {0} cannot be dropped or created since it uses a trigger to update the optimistic column of the EJB. The container will only verify the existence of the table.
-
Cause: The table uses a trigger to update the optimistic column of the EJB.
-
Action: To suppress this warning, set the create-default-dbms-tables value in the RDBMS deployment descriptor to Disabled.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011092: In production mode, the DropAndCreate, DropAndCreateAlways, and AlterOrCreate options are ignored. The container will only attempt to verify the existence and increment value of the sequence {0}.
-
Cause: Options that apply only to development mode are ignored in production mode.
-
Action: Do not use these values for Automatic Oracle SEQUENCE Generation in production mode.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011093: The SEQUENCE named {0} with INCREMENT {1} was not found in the database. This SEQUENCE was specified in the CMP deployment descriptor to be used for automatic primary key generation.
-
Cause: The SEQUENCE was not found.
-
Action: Examine the <automatic-key-generation> tag in the CMP deployment descriptor. In particular, re-examine the <generator-name> and verify that this is the correct name of the SEQUENCE. Also, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011094: The SEQUENCE named {0} does not have INCREMENT value of {1} in the database as specified in the CMP deployment descriptor. Either modify the key-cache-value for this SEQUENCE in the deployment descriptor or update the SEQUENCE in the database.
-
Cause: The SEQUENCE named {0} does not have an INCREMENT value of {1} in the database as specified in the CMP deployment descriptor.
-
Action: In the <automatic-key-generation> tag of the CMP deployment descriptor, re-examine the <key-cache-size> and verify that this is the correct size of the SEQUENCE INCREMENT value.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011095: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}. {2}
-
Cause: During EJB deployment, error(s) were encountered while attempting to CREATE the SEQUENCE named {0} with INCREMENT value {1}.
-
Action: The message contains the cause of the error. See the message body and resolve the reported error.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011096: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}. {2}
-
Cause: During EJB deployment, error(s) were encountered while setting up The SEQUENCE named {0} with INCREMENT value {1}.
-
Action: The message contains the cause of the error. See the message body and resolve the reported error.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011097: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}. {2}
-
Cause: During EJB deployment, error(s) were encountered while attempting to ALTER the SEQUENCE named {0} with INCREMENT value {1}.
-
Action: The message contains the cause of the error. See message body and resolve the reported error.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011098: No generated primary key was returned from the database insert statement as expected. Verify that the primary key database column for this EJB is an IDENTITY column as declared in the CMP deployment descriptor for this EJB.
-
Cause: This is most likely caused by a database configuration error. It may also be caused by a JDBC driver that 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).
Level: 1
Type: ERROR
Impact: EJB
- BEA-011099: Multiple generated keys were returned from the database insert statement. The EJB container is unable to determine which generated key corresponds to the primary key column. To use the IDENTITY primary key generator, you must only have a single automatically generated database column per EJB.
-
Cause: This is most likely caused by a database configuration error. Each EJB may only have a single automatically generated database column.
-
Action: Verify that the database table corresponding to the EJB only has a single generated column.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011110: The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database. This may generate missing keys.
-
Cause: The SEQUENCE named {0} has key-cache-size set to {1}, which is less than the INCREMENT_BY value for the sequence in the database.
-
Action: In the <automatic-key-generation> tag, re-examine the <key-cache-size> and verify that it is set correctly.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011111: The SEQUENCE named {0} has key-cache-size set to {1} which is greater than the INCREMENT_BY value for the sequence in the database. This is not allowed as it may generate duplicate keys.
-
Cause: The key-cache-set size for the SEQUENCE is not valid.
-
Action: in the <automatic-key-generation> tag, re-examine the <key-cache-size> and set it to a value less than or equal to the INCREMENT_BY value for the sequence in the database.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011120: The CMP EJB {0} has enable-batch-operations set to true. The update queries, however, are not suitable for batching. Batched operations are turned off for this batch and the queries will be executed with multiple update statements.
-
Cause: Batching is turned off for update queries.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: EJB
- BEA-011124: Error in Message-Driven Bean EJB {0}. The plugin-class {1} does not implement weblogic.ejb.spi.SecurityPlugin.
-
Cause: The plugin-class does not implement weblogic.ejb.spi.SecurityPlugin.
-
Action: Make the plugin-class implement weblogic.ejb.spi.SecurityPlugin.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011125: An unexpected error was encountered while attempting to remove any EJB timers from the persistent store for the EJB {0}.
-
Cause: An unexpected error occurred while attempting to remove EJB timers from the persistent store.
-
Action: See the particular error message for details about the error. If your application is failing to deploy because of this error, it may be necessary to manually remove the timers from the store.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011126: The same exception has consecutively caused the expiration to fail for EJB timer {0}. Consecutive errors of this type will no longer be logged for the current timer expiration.
-
Cause: The same exception has consecutively caused expiration of an EJB timer to fail.
-
Action: Investigate what caused the ejbTimeout method to fail. The original exception will be logged in a previous error message.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-011127: Error deserializing one or more EJB timers from the persistent store for the EJB deployment {0}. An incompatible change to the class of a Serializable object associated with the timer may be the cause. If this is the case, you can either undeploy your application entirely to remove the EJB timers from the persistent store or revert the incompatible changes to the Serializable class so the EJB timer can be deserialized. The error was: {1}
-
Cause: A common cause of this error is an incompatible serializable class change in your application.
-
Action: If the error is due to an incompatible serializable class change in your application, there are two options for dealing with the serialization errors. The first option is to completely undeploy the EJB. which will cause all of the EJB timers in the persistent store to be permanently removed. The second option is to revert changes to the serializable class that is associated with the EJB timer and redeploy the application. This allows the EJB timer to be deserialized.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011128: Error creating an instance of the EJB {0}: {1}
-
Cause: See the reported error message for the cause. This error may be due to a configuration issue or a bug in the EJB container.
-
Action: See the specific error message for details and take appropriate action.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011129: Error deploying EJB {0} to server {1}. This EJB is configured to use the clustered EJB Timer implementation but this server is not part of a cluster.
-
Cause: It is illegal to deploy an EJB that uses clustered EJB timers to a server that is not part of a cluster.
-
Action: You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or ensure that any servers to which you deploy the EJB are part of a cluster.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011130: Error deploying EJB {0}. This EJB is configured to use the clustered EJB timer implementation but the data-source-for-job-scheduler cluster attribute is not configured.
-
Cause: While deploying this EJB, the EJB container determined the data-source-for-job-scheduler cluster attribute has not been set.
-
Action: You must either set the timer-implementation attribute of your weblogic-ejb-jar.xml descriptor to Local or configure the data-source-for-job-scheduler attribute for your cluster.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011132: Error deploying EJB {0}. While binding a business interface to the JNDI name {1}, the following error occurred: {2}
-
Cause: See the specific error for details.
-
Action: The action to take depends on the specific error that occurred. If the error was a JNDI naming conflict, you may need to choose a different JNDI name for the interface.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011138: Singleton session beans with bean-managed transactions must commit or rollback their transactions before completing a business method. The method {0} of EJB {1} either returned or generated an exception without properly completing a transaction.
-
Cause: A transaction started by the singleton session bean method did not complete before the method completed.
-
Action: Check the bean code to determine what caused the transaction to not commit or roll back and fix the code. Pay special attention to any exceptions that may be generated by the method, causing commit or rollback calls to be skipped. Blocks can be used to ensure transactions are properly completed in all situations.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011148: Singleton {0} not initialized as Singleton {1} from the DependsOn transitive, closure failed initialization.
-
Cause: A singleton was not initialized as a Singleton from the DependsOn transitive, closure failed initialization.
-
Action: Check the server log for the cause of the dependent Singleton initialization error and resolve it.
Level: 1
Type: ERROR
Impact: EJB
- BEA-011278: The following dependency that was declared by {0} is not a Singleton Session Bean: {1}.
-
Cause: A dependency that was specified by a Singleton Session Bean must also be a Singleton Session Bean.
-
Action: Remove the illegal dependency from the dependency list or replace it with a Singleton Session Bean.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-012031: The EJB {0} has a finder {1} for which the sql-select-distinct attribute has been specified. This attribute has been deprecated and will not be supported in future releases.
-
Cause: The deprecated sql-select-distinct attribute was used.
-
Action: Use the EJB-QL DISTINCT clause instead. The container will automatically filter duplicates if necessary.
Level: 1
Type: WARNING
Impact: EJB
- BEA-012032: For EJB {0}, a weblogic-query element in the CMP deployment descriptor has no matching query element in the ejb-jar.xml descriptor. The settings specified in the weblogic-query element will be ignored. The EJB method referred to by the weblogic-query element is {1}.
-
Cause: The weblogic-query element references a wrong or non-existent query method for this entity EJB.
-
Action: Remove the weblogic-query element or update it so that it references the correct query method.
Level: 1
Type: WARNING
Impact: EJB
- BEA-012033: Compiling generated EJB classes produced the following Java compiler output: {0}
-
Cause: While compiling EJB generated classes, the Java compiler produced output.
-
Action: Typically, there is no action to take. The Java compiler output is printed for informational purposes. If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact support.
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-012035: The Remote interface method: {0} in EJB {1} contains a parameter of type {2} which is not serializable. Though the EJB {1} has call-by-reference set to false, this parameter is not serializable and hence will be passed by reference. A parameter can be passed using call-by-value only if the parameter type is serializable.
-
Cause: The EJB has call-by-reference set to false. A parameter can be passed using call-by-value only if the parameter type is serializable. As this parameter is not serializable, the parameter will be passed by reference.
-
Action: The parameter should implement the java.io.Serializable interface for it to be passed by value.
Level: 1
Type: WARNING
Impact: EJB
- BEA-012036: Compiling generated EJB classes produced the following Java compiler error message: {0}
-
Cause: While compiling EJB generated classes, the Java compiler produced output.
-
Action: If the Java compiler is unable to successfully compile the generated classes, this is likely a bug in the EJB subsystem and you should probably contact My Oracle Support.
Level: 1
Type: ERROR
Impact: EJB
- BEA-012037: In weblogic-ejb-jar.xml or annotation, a singleton-session-descriptor element was found for EJB {0}. This EJB was not declared as a singleton session bean in ejb-jar.xml or annotation.
-
Cause: There is an incompatible configuration between weblogic-ejb-jar.xml and ejb-jar.xml.
-
Action: Modify weblogic-ejb-jar.xml or ejb-jar.xml to keep configuration consistency whether singleton or non-singleton.
Level: 1
Type: ERROR
Impact: EJB
- BEA-014000: Problem, encountered illegal value for transaction-isolation {0}.
-
Cause: See the error message body.
-
Action: Specify one of the following legal values: TransactionSerializable, TransactionReadCommitted, TransactionReadCommittedForUpdate, TransactionReadCommittedForUpdateNoWait, TransactionReadUncommitted, or TransactionRepeatableRead.
Level: 1
Type: ERROR
Impact: EJB
- BEA-014001: RDBMS descriptor {0} contains transaction-isolation settings. These settings may conflict with isolation-level settings in your weblogic-ejb-jar.xml descriptor and will be lost if you edit this descriptor in the console.
-
Cause: The specified RDBMS descriptor contains transaction-isolation settings.
-
Action: Move the isolation-level settings to the weblogic-ejb-jar.xml descriptor.
Level: 1
Type: ERROR
Impact: EJB
- BEA-014003: EJB {0} uses optimistic concurrency and contains a finder or select method, {1}, for which include-updates is true. This combination of features does not work properly with database {2}.
-
Cause: Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks, unless Oracle is used as the database. Oracle read consistency does not hold read locks, so in this case reads are performed using the current JTA transaction. When reads are performed in a local transaction updates that have been flushed prior to commit of the transaction are not visible.
-
Action: Set include-updates for the query to false to avoid this warning message, or if you are using Oracle as your database, set the database-type to Oracle in weblogic-cmp-jar.xml.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014004: In EJB {0}, <generator-type> is set to {1}. It is incompatible with Batch Operations due to database limitations. Both order-database-operations and enable-batch-operations are turned off by EJB container.
-
Cause: These are database limitations.
-
Action: Turn off automatic-key-generation in order to use batch operations.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014005: The configured dispatch policy {1} for Message-Driven Bean (MDB) {0} will be ignored: the MDB is not running in a WebLogic thread.
-
Cause: The queue MDB is driven asynchronously by a non-WebLogic JMS implementation and runs in a non-WebLogic thread mechanism, so the MDBs application thread pool is not configurable.
-
Action: To disable this warning, remove the dispatch-policy setting from the MDBs WebLogic descriptor file.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014006: The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown execute queue thread pool. The default execute thread pool will be used instead.
-
Cause: The specified MDB named has a dispatch policy that refers to an unknown execute queue thread pool.
-
Action: Create an execute thread queue pool for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing execute queue thread pool.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014007: The bean named {0} contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified. This may result in corruption of BLOB and CLOB data.
-
Cause: The specified bean contains BLOB or CLOB fields or both, and uses Optimistic Concurrency but no version or timestamp column has been specified.
-
Action: Specify "version" or "timestamp" in the <table-map> <verify-columns> element and specify the name of the <version> or <timestamp> column in the <optimistic-column> element.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014008: In EJB {0}, {1} references an SqlShape element {2} that is not defined. The list of SqlShape elements that are defined for this EJB is: {3}.
-
Cause: An undefined SqlShape element was referenced.
-
Action: Use an existing SqlShape or create the SqlShape that you wish to use.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014010: The Message-Driven Bean {0} of application {1} will now be suspended, as it listens to global JMS topic {2} and a new application version {3} is being redeployed. Note also that the current Message-Driven Bean is not a durable subscriber to the topic, and messages published by the topic after the currently active version of the Message-Driven Bean is suspended may not be received by the new application version.
-
Cause: The specified Message-Driven Bean listens to the specified global JMS topic and a new application version is being redeployed.
-
Action: To ensure that the new application version will receive all messages published while the Message-Driven Bean was suspended, set the activation config property "subscriptionDurability" to "durable" in the deployment descriptor or annotation.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014011: EJB {0} uses optimistic-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. This combination of features is incompatible. The use-select-for-update is turned off by the EJB container in this case.
-
Cause: Optimistic concurrency is implemented by reading data in a local transaction to avoid holding database locks. The element use-select-for-update in the RDBMS deployment descriptor when set to true, will cause SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the table. This conflicts with the Optimistic Concurrency strategy.
-
Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014012: EJB {0} uses optimistic-concurrency and disables cluster invalidation, but does not have verify-rows set to Read. This combination will prevent detection of stale data if the bean is never modified in a transaction.
-
Cause: Optimistic concurrency beans verify consistency of data only if the bean has been modified, unless verify-rows is set to Read. If some other member of a cluster modifies a bean, other members will not be notified of this modification and will continue to store stale data unless the other members also attempt to modify the bean.
-
Action: Set either of the elements verify-rows to Read or cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014013: EJB {0} does not have a concurrency-strategy of either optimistic or readOnly and disables cluster invalidation. Cluster invalidation is relevant only for these concurrency strategies.
-
Cause: When an EJB is using either optimistic or readOnly concurrency-strategy and is deployed to a cluster, the container invalidates such beans on modification to avoid throwing OptimisticConcurrencyExceptions. This invalidation can be turned off by setting the cluster-invalidation-disabled to true in the RDBMS deployment descriptor.
-
Action: Set cluster-invalidation-disabled to false in the RDBMS deployment descriptor to avoid this warning message.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014014: The Message-Driven Bean (MDB) named {0} has a dispatch policy {1} that refers to an unknown work manager. The default work manager will be used instead.
-
Cause: The specified MDB has a dispatch policy that refers to an unknown work manager.
-
Action: Create a work manager for the server named {1}, or modify the dispatch-policy attribute in the MDBs WebLogic descriptor file to the name of an already existing work manager.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014016: EJB {0} uses readonly-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is read-only, select-for-update is unnecessary.
-
Cause: Read-only beans cannot be updated. Therefore, use-select-for-update is unnecessary.
-
Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014017: EJB {0} uses exclusive-concurrency and has the use-select-for-update element in the RDBMS deployment descriptor set to true. As the bean is locked at the server level during a transaction, select-for-update on the database is unnecessary.
-
Cause: Exclusive concurrency is implemented by locking the bean at the server level when the bean participates in a transaction. Setting the element use-select-for-update in the RDBMS deployment descriptor to true causes SELECT ... FOR UPDATE to be used whenever the bean is loaded from the database, thus locking the row in the database too. This may be unnecessary, as the bean is locked by the container.
-
Action: Set use-select-for-update element in the RDBMS deployment descriptor to false to avoid this warning message.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014018: EJB {0} uses a verify-columns element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.
-
Cause: verify-columns is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.
-
Action: Remove verify-columns element in the RDBMS deployment descriptor to avoid this warning message.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014019: EJB {0} uses a verify-rows element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.
-
Cause: verify-rows is applicable only for optimistic concurrency beans. As the bean does not use optimistic concurrency, this element will be ignored.
-
Action: Remove the verify-rows element in the RDBMS deployment descriptor to avoid this warning message.
Level: 1
Type: WARNING
Impact: EJB
- BEA-014020: EJB {0} uses an optimistic-column element in the RDBMS deployment descriptor. This element is applicable only for optimistic concurrency beans. Since this bean does not use optimistic concurrency, this element will be ignored.
-
Cause: optimistic-column element is applicable only for optimistic concurrency beans. If the bean does not use optimistic concurrency, this element will be ignored.
-
Action: Remove the optimistic-column element in the RDBMS deployment descriptor to avoid this warning message.
Level: 1
Type: WARNING
Impact: EJB
- BEA-015027: The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.
-
Cause: The Message-Driven EJB is transactional, but the JMS connection factory referenced by the JNDI name {0} is not a JMS XA connection factory.
-
Action: Make the Message-Driven EJB non-transactional, or use a different connection factory that supports XA.
Level: 1
Type: ERROR
Impact: EJB
- BEA-015028: The EJB {0} contains an illegal value for the activation config property DistributedDestinationConnection. The specified value is {1} but the legal values are EveryMember and LocalOnly.
-
Cause: See the error message body.
-
Action: Correct the activation config property.
Level: 1
Type: ERROR
Impact: EJB
- BEA-015029: The EJB {0} contains an illegal value for the activation config property TopicMessagesDistributionMode. The specified value is {1} but the legal values are Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application.
-
Cause: See the error message body.
-
Action: Correct the activation config property.
Level: 1
Type: ERROR
Impact: EJB
- BEA-015030: The EJB {0} has an illegal permutation on distributed topic type and topicMessagesDistributionMode. Replicated distributed topics work with Compatibility, One-Copy-Per-Server, or One-Copy-Per-Application, but partitioned distributed topics only work with One-Copy-Per-Server or One-Copy-Per-Application. The EJB is configured to partitioned distributed topic and Compatibility.
-
Cause: See the error message body.
-
Action: Review the compatibility of distributed topic types and topicMessagesDistributionMode and fix them.
Level: 1
Type: ERROR
Impact: EJB
- BEA-015031: The EJB {0} has a distributedDestinationConnection configured but the EJB is configured to connect to a remote cluster. Since the distributedDestinationConnection configuration is only valid in a local cluster, the setting will be ignored.
-
Cause: See the error message body.
-
Action: Connect to a local cluster, or remove the distributedDestinationConnection configuration.
Level: 1
Type: WARNING
Impact: EJB
- BEA-015032: The EJB {0} is configured with the activation config property topicMessagesDistributionMode but the EJB is configured to connect to a JMS Queue. The topicMessagesDistributionMode is valid only for JMS Topic destinations.
-
Cause: See the error message body.
-
Action: Correct the activation config property.
Level: 1
Type: ERROR
Impact: EJB
- BEA-015033: The EJB {0} has an invalid value configured for the activation config property {1}. Only WebLogic JMS server 10.3.4 or later versions support the values One-Copy-Per-Server or One-Copy-Per-Application. Prior to 10.3.4.0 Weblogic JMS server or other non-Weblogic JMS vendors, only the Compatibility value is supported.
-
Cause: See the error message body.
-
Action: Correct the activation config property.
Level: 1
Type: ERROR
Impact: EJB
- BEA-015034: This destinaiton {1} is a remote replicated distribution topic which does not support durable subscriptions when the Message-Drive Bean {0} works in Compatibility mode.
-
Cause: See the error message body.
-
Action: Review and fix the compatibility of the activation config property SubscriptionDurability and topicMessagesDistributionMode.
Level: 1
Type: ERROR
Impact: EJB
- BEA-015035: The EJB {0} is configured to support One-Copy-Per-Server mode but the partitioned topic is configured as LocalOnly. To support One-Copy-Per-Server mode, the LocalOnly setting will be overridden with EveryMember.
-
Cause: See the error message body.
-
Action: Change distributed-destination-connection to EveryMember to remove the warning.
Level: 1
Type: WARNING
Impact: EJB
- BEA-015036: In the EJB {0}, the value for the activation config property {1} will be ignored since it is overridden with the value {2}.
-
Cause: See the error message body.
-
Action: To remove this warning, remove the duplicated configuration from the activation config property.
Level: 1
Type: WARNING
Impact: EJB
- BEA-015037: In EJB {0}, the throws clause for method {1} in the bean class contains exceptions that are NOT in the throws clause of the corresponding {2} interface method.
-
Cause: See the error message body.
-
Action: Correct the throws clause. Implementation methods must have all exceptions that are provided by the corresponding interfaces.
Level: 1
Type: WARNING
Impact: EJB
- BEA-015043: A concurrent-call attempt failed on a stateful session bean instance because the lock was held by another thread or transaction, either because concurrent-access is prohibited or access could not be granted in a specific time period. You may change the concurrent-access behavior using the @AccessTimeout annotation or a corresponding element in deployment descriptor.
-
Cause:
-
Action:
Level: 1
Type: NOTIFICATION
Impact: EJB
- BEA-015044: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.
-
Cause: @JNDIName is specified on multiple classes for the same business interface {0} but the value is different. Class: {1}; Class: {2}.
-
Action: Remove @JNDIName from either {1} or {2}.
Level: 1
Type: ERROR
Impact: EJB
- BEA-015045: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.
-
Cause: @JNDIName on the bean implementation class does not provide the class of the client view, but more than one client view exists. Class: {0}.
-
Action: Remove @JNDIName from {0} or provide the class name of each client view.
Level: 1
Type: ERROR
Impact: EJB
- BEA-040010: JMSServer "{0}" configured {1,choice,0#no session pools|1#1 session pool|2#{1} session pools}.
-
Cause: This message indicates the number of session pools that were configured or deployed for the JMSServer while processing the configuration file.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040017: JMSServer "{0}" connection factory JNDI binding failed, {1}. JMS is shutting down.
-
Cause: An error was found when binding the connection factory to a JNDI name during configuration.
-
Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040018: Could not obtain a replicated or non-replicated InitialContext from the default provider, {0}.
-
Cause: An error was encountered when binding a JMS Server to a JNDI name during configuration.
-
Action: Modify the configuration and restart the server file. Then reboot the server.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040090: Deployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.
-
Cause: This message indicates the number of default connection factories deployed while processing the configuration file.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040107: Undeployed {0,choice,0#no default connection factories|1#1 default connection factory|2#{0} default connection factories}.
-
Cause: This message indicates the number of default connection factories that were undeployed.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040113: JMSServer "{0}", Opening file store "{1}" in directory "{2}". Starting scan of {3,choice,0#0 files|1#1 file|2#{3} files} totaling {4} bytes.
-
Cause: A JMS server has opened its persistent file store and is about to scan its contents for messages.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040119: Failed to deploy a JMS connection factory "{0}" due to {1}.
-
Cause: The JMS connection factory failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new connection factory.
-
Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040122: Failed to deploy JMS Server "{0}" due to {1}.
-
Cause: The JMS server failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server.
-
Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040123: Failed to start JMS Server "{0}" due to {1}.
-
Cause: A JNDI failure occurred, or there was a failure when starting destinations, server session pools and/or connection consumers.
-
Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040124: JMSServer "{0}". Failed to create JMS server session pool "{1}" due to {2}.
-
Cause: The JMS server session pool failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server session pool.
-
Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040125: JMSServer "{0}". Failed to create JMS connection consumer "{1}" due to {2}.
-
Cause: The JMS connection consumer failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS connection consumer.
-
Action: Modify the configuration and restart the server file. Then reboot the system.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040307: JMS service is suspending gracefully.
-
Cause: The JMS service has started the suspension phase. No new work will be accepted and JMS Service will attempt to complete all existing work before it brings itself to standby mode.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040308: JMS service is suspending.
-
Cause: The JMS service has started the suspension phase. No new work will be accepted and all the existing work will be terminated immediately before the JMS service brings itself to standby mode.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040371: JMSServer "{0}" JMS server session pool is invalid and has not been started "{1}". Exception is "{2}".
-
Cause: The server session pool is invalid because it has an invalid Connection Factory or Listener.
-
Action: Edit the JMS session pool, verify that it has valid attributes, and reboot the server. Alternatively, delete the session pool and add a new valid JMS session pool.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040409: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} {2} </FailedJMSMessage
-
Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040410: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage
-
Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040411: FailedJMSMessage for store-and-forward: JMSMessageID={0} > {1} </FailedJMSMessage
-
Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log the message header fields and messages properties so that they are printed.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040412: FailedJMSMessage for store-and-forward: JMSMessageID={0} > </FailedJMSMessage
-
Cause: A message was expired before it was successfully forwarded by the SAF agent, and the policy is to log only the MessageId. Alternatively, there are no matching message header fields or message properties.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040421: An administrative request to commit the JMS transaction branch {1} on destination {0} failed with the following exception. {2}
-
Cause: The cause of the failure may be indicated by the exception provided in the error message.
-
Action: The transaction may be in an invalid state to allow commit processing. Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040423: An administrative request to rollback the JMS transaction branch {1} on destination {0} failed with the following exception. {2}
-
Cause: The cause of the failure may be indicated by the exception provided in the error message.
-
Action: Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040430: The "UserTransactionsEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.
-
Cause: A deprecated attribute was used.
-
Action: Use the XAConnectionFactoryEnabled attribute instead.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040431: The "XAServerEnabled" attribute on the JMSConnectionFactory "{0}" has been deprecated and replaced by the "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.
-
Cause: A deprecated attribute is used.
-
Action: Use the XAConnectionFactoryEnabled attribute instead.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040442: While attempting to bind JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI.
-
Cause: Some other entity has already bound this JNDI name globally.
-
Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040443: While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer globally bound into JNDI under any name.
-
Cause: Some other entity has already bound this JNDI name globally.
-
Action: Determine the owner the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040444: While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised globally.
-
Cause: A network connection between the local server and the Administration Server may have gone down.
-
Action: Make sure that network connectivity is working properly and that the Administration Server is reachable.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040445: While attempting to change the JNDI name from {0} to {1} for destination {2} in module {3}, a JNDI name conflict was found. This destination is no longer locally bound into JNDI under any name.
-
Cause: Some other entity has already bound this JNDI name locally.
-
Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040446: While attempting to unadvertise the JNDI name {0} for destination {1} in module {2}, an error occurred. The name may or may not be unadvertised locally.
-
Cause: A network connection between the local server and the Administration Server may have gone down.
-
Action: Make sure that network connectivity is working properly and that the Administration Server is reachable.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040447: While attempting to bind the JNDI name {0} for destination {1} in module {2}, a JNDI name conflict was found. This destination has not been bound into JNDI locally.
-
Cause: Some other entity has already bound this JNDI name locally.
-
Action: Determine the owner of the currently bound JNDI name and remove it if it should not be there, or change the JNDI name of this destination so that it does not conflict with the existing one.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040448: JMSFileStoreMBean has been deprecated, and has been replaced with FileStoreMBean. The JMSFileStoreMBean "{0}" has been replaced in the configuration with a FileStoreMBean with the same name.
-
Cause: A deprecated MBean was replaced in the configuration.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040449: JMSJDBCStoreMBean has been deprecated, and has been replaced with JDBCStoreMBean. The JMSJDBCStoreMBean "{0}" has been replaced in the configuration with a JDBCStoreMBean with the same name.
-
Cause: A deprecated MBean was replaced in the configuration.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040450: The "PagingStore" attribute on the JMSServerMBean "{0}" has been deprecated. It is being replaced in the configuration with the new "PagingDirectory" attribute.
-
Cause: A deprecated MBean attribute was replaced in the configuration.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040451: The PagingStore attribute on the JMSServerMBean {0} has been deprecated. Since it currently refers to a JMSJDBCStoreMBean, and paging to a JDBC store is not supported, the JMS server will page messages to its local working directory.
-
Cause: A deprecated MBean attribute was replaced in the configuration.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040452: The server session pool feature has been deprecated, and it will be removed in an upcoming release. New applications should use message-driven beans (MDBs) instead.
-
Cause: A deprecated feature was detected in the configuration.
-
Action: Plan to replace use of server session pools in your application.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040453: The BytesPagingEnabled and MessagesPagingEnabled parmeters on the JMSServer {0} have been deprecated. These parameters are now ignored. The MessageBufferSize parameter should be used to configure paging in this release.
-
Cause: A deprecated parameter was encountered.
-
Action: Plan to use the new MessageBufferSize to control paging.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040455: Flow control has been enabled on JMS server "{0}" because memory is low
-
Cause: Too much memory is being used.
-
Action: Either increase the amount of memory available to the server, or decrease the MessageBufferSize parameter on the JMS server so that fewer messages remain in memory.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040456: An entity of type "{3}" with name "{2}" in JMS module "{0}" is not targeted. There is no subdeployment with name "{1}" in the configuration repository (config.xml). Therefore, this entity will not exist anywhere in the domain.
-
Cause: The entity of the given name and type in the given JMS module does not have a corresponding subdeployment in the configuration repository (config.xml). In order for this entity to exist in the domain, it must be targeted with a sub-deployment element.
-
Action: Add a sub-deployment stanza to the appropriate deployment descriptor in config.xml. This will either be a jms-system-resource for a system module, or an app-deployment for a stand-alone JMS deployable module. If the JMS module is inside a J2EE application (an EAR file), then you must add the sub-deployment stanza to the subdeployment that represents this JMS module in the J2EE application. You do not necessarily have to target the subdeployment yet. Simply adding the subdeployment with no targets will remove this warning. However, if you wish for this entity to exist somewhere in your domain you must target the sub-deployment.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040457: The Template named "{1}" element of Distributed Destination "{0}" is not supported and hence ignored. Please consider using a Uniform Distributed Destination.
-
Cause: An unsupported attribute JMSTemplate is used in a Distributed Destination.
-
Action: Use a Uniform Distributed Destination instead.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040475: The destination {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.
-
Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases, a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
-
Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040476: The destination {0} does not have an associated quota object. The setting of messagesMaximum to {1} will have no effect.
-
Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
-
Action: Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040477: An error occurred while unbinding a remote JNDI object from local JNDI name "{0}". The exception encountered was {1}.
-
Cause: There may be an error in the JNDI subsystem. See the exception for more information.
-
Action: Check the exception message for more detail.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040490: {0} {1} has a conflicting name attribute value, which is now changed to have a unique name with its JMSServer name. The new destination-name attribute now holds the original name value.
-
Cause: A name conflict has been detected during upgrade for JMS destinations, maybe because in WebLogic Server versions prior to 9.2, more than one destination was allowed to have the same name, as long as the destinations belonged to different JMS servers.
-
Action: Ensure that destinations are created with their name decorated with the target JMS server name to avoid conflict.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040491: A {0} {1} with multiple targets has been split into multiple deployments one for each unique target.
-
Cause: A JMS Deployment found with multiple unique targets configured.
-
Action: In WebLogic Server versions prior to 9.2, both JMSConnectionFactory and ForeignJMSServer were allowed to be targeted to more than one server, cluster, or both. During upgrade of this configuration to WebLogic Server 9.2, these configuration entities are split into more than one entity, one for each unique target.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040496: The template {0} does not have an associated quota object. The setting of bytesMaximum to {1} will have no effect.
-
Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
-
Action: Please consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040497: The template {0} does not have an associated quota object. The setting of MessagesMaximum to {1} will have no effect.
-
Cause: Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
-
Action: Consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040502: While attempting to change the targeting of JMS module "{0}", an error occurred while activating the change. The exception returned is: {1}
-
Cause: The JMS module failed to activate a prepared change during a targeting update.
-
Action: More information may be available from the exception.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040503: The delivery mode override value of destination "{0}" hosted on JMS server "{1}" has been changed from {2} to {3}.
-
Cause: During the upgrade process, a configuration was detected that would force all messages through the given destination to be non-persistent. Therefore, the upgrade process made that override explicit.
-
Action: Review your application code and configuration. If you need a behavior other than the one that the upgrade process chose, you can modify the resulting configuration using the DeliveryMode parameter of the OverridesParams of the destination, or with the HasStore or AllowsPersistentDowngrade parameters of the JMS server on which the destination is targeted.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040504: While attempting to add an entity with name "{0}", an error occurred while trying to convert the old style entity to the new style entity. The error was "{1}".
-
Cause: See the description of the exception that occurred for more information on the cause of this failure.
-
Action: Take appropriate action based on the determined cause.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040505: The JMS module named "{0}" inside application "{1}" does not have a sub-deployment stanza named "{0}". Without such a stanza, no entities inside the module will be deployed, since the subdeployments inside of the sub-deployment stanza named "{0}" control where JMS entities inside this module are targeted.
-
Cause: When a JMS module is inside an EAR file, the targeting information for entities inside that module are nested within a sub-deployment named after the name of the JMS module found in the weblogic-application.xml file of the EAR file. If no sub-deployment exists with the name of the JMS module, then no targeted entities inside the module will become available. This is usually an oversight on the part of the administrator.
-
Action: Add a sub-deployment stanza with the name of the JMS module as specified in the weblogic-application.xml file to the app-deployment stanza. Nested inside that sub-deployment, you can target the entities in the module as you normally would.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040507: The JMS store-and-forward (SAF) forwarder failed to connect to the remote destination "{0}", because of {1}.
-
Cause: This is either due to a configuration error, a network failure, or the remote destination being temporarily unavailable.
-
Action: Check the configuration, network connection, or remote destination.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040508: BridgeDestinationMBean has been deprecated. The BridgeDestination "{0}" has been replaced in the configuration with a JMSBridgeDestination with the same name.
-
Cause: A deprecated MBean is being replaced in the configuration.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040510: While attempting to rename a connection factory named "{0}", an error occurred while attempting to establish a JNDI listener. The cause was {1}.
-
Cause: There was an error while attempting to establish a JNDI listener. The description of the cause may provide more information about the true cause of the error.
-
Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040511: The system is waiting to unbind connection factory "{0}". An attempt is being made to change the JNDI name of this connection factory from "{1}" to "{2}".
-
Cause: An attempt is being made to unbind a connection factory from a JNDI name in order to dynamically change the JNDI from one name to another. This message will repeat every twenty seconds for five minutes.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: JMS
- BEA-040512: An attempt is being made to change the JNDI name of connection factory "{0}" from "{1}" to "{2}". The system has waited to unbind "{1}" for five minutes. The new JNDI name "{2}" may or may not be bound properly.
-
Cause: The connection factory was not fully unbound after five minutes. Some error may have occurred while attempting to unbind this connection factory.
-
Action: In order to maintain the integrity of the connection factory it is recommended you untarget and retarget the connection factory that failed. Otherwise, the connection factory is in an indeterminate state.
Level: 1
Type: ERROR
Impact: JMS
- BEA-040513: While attempting to rename a connection factory named "{0}", an error occurred while attempting to remove a JNDI listener. The cause was {1}.
-
Cause: There was an error while attempting to remove a JNDI listener. The description of the cause may provide more information about the true cause of the error.
-
Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040514: While attempting to rename a connection factory named "{0}" an error occurred in the JNDI listener. The error was {1}
-
Cause: While attempting to dynamically change the JNDI name of a connection factory, a JNDI error occurred. The error itself will tell more about the cause of this failure.
-
Action: The cause of this problem may give an indication of the source of this problem and the action to take. If this problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040515: A failured occured while attempting to unregister an InterceptionPoint, {0}.
-
Cause: An exceptoin coccurred while attempting to unregister an InterceptionPoint. The error will provide more details about the cause of this failure.
-
Action: The cause of this problem may give an indication of the source of this problem. If this problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040520: One or more Weighted Distributed Destination (WDD) resources were detected in JMS configuration module "{1}": {0}. This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.
-
Cause: Deprecated resource was used.
-
Action: Use the Uniform Distributed Destination instead.
Level: 1
Type: WARNING
Impact: JMS
- BEA-040521: The JMS resource "{0}" that you are trying to create in module "{1}" is a Weighted Distributed Destination (WDD). This resource type was deprecated as of WebLogic Server 10.3.4.0. Consider using a Uniform Distributed Destination (UDD) instead. If you want to suppress this warning, set system property "weblogic.jms.WDD.SuppressDeprecationWarnings" to true when starting each WebLogic Server instance.
-
Cause: A deprecated resource is trying to create.
-
Action: Use the Uniform Distributed Destination instead.
Level: 1
Type: WARNING
Impact: JMS
- BEA-045029: The messages threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.
-
Cause: The messages threshold of the JMS server was exceeded.
-
Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1
Type: WARNING
Impact: JMSExceptions
- BEA-045031: The bytes threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server.
-
Cause: The bytes threshold of the JMS server was exceeded.
-
Action: Verify that the messages are being consumed and that sufficient memory is available.
Level: 1
Type: WARNING
Impact: JMSExceptions
- BEA-045032: While attempting to create destination {1} in module {2} the JMS server {0} could not be found.
-
Cause: The JMS server may be shutting down or may not have completed startup.
-
Action: Deploy the module again once the JMS server has completed startup.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045040: While attempting to add a {1} named {2} in module {0}, an error occurred.
-
Cause: A linked ModuleException will contain more detail about the cause of the failure.
-
Action: Examine the linked exception, which will contain more information about the cause of this failure.
Level: 1
Type: WARNING
Impact: JMSExceptions
- BEA-045047: The SubDeploymentMBean {0} in deployment {1} can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue, topic or quota) has a sub-deployment-name element with value {0}
-
Cause: The SubDeploymentMBean of the given name cannot be targeted to anything but a single JMS server because an element of the JMS module that points to that subdeployment can only be targeted to a single JMS server.
-
Action: Modify the target of the subdeployment so that it only contains a single JMS server.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045048: The JMS server named {0} has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is {1}, and the template name is {2}. However, a JMSSystemResourceMBean of name {1} could not be found. The JMS server {0} will not boot until this problem has been fixed.
-
Cause: The temporary template for a JMS server must come from a JMSSystemResourceMBean. A common mistake is to put the temporary template into an AppDeployment. However, because the temporary template must be owned by the administrator, all temporary templates must come from JMSSystemResourceMBeans, not AppDeployments.
-
Action: Put the temporary template into a JMSSystemResource.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045049: JMS server {0} does not have a configured temporary template. However an attempt was made to create a temporary destination. This is not allowed.
-
Cause: A JMS server without a configured temporary template was used to create a temporary destination. This usage is not allowed.
-
Action: Create a JMSSystemResource that contains a template. Use that template as the temporary template for this JMS server.
Level: 1
Type: WARNING
Impact: JMSExceptions
- BEA-045050: A destination named {3} has a jms-create-destination-identifier named {1}. However, another destination named {2} has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot both be located on the JMS server named {0}.
-
Cause: Two destinations cannot both have the same jms-create-destination-identifier on the same JMS server, even if the two destinations are from different modules.
-
Action: Either deploy the destination with the offending jms-create-destination-identifier to a different JMS server, or change the value of the jms-create-destination-identifier attribute.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045051: Two destinations with name {1} were deployed to the JMS server {0}.
-
Cause: Two destinations with the same fully qualified name cannot be deployed to the same JMS server. This error should have been caught during the validation phase of the JMS module.
-
Action: Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045052: An attempt was made to change the target of a JMS entity that cannot have its target changed. The entity has name "{0}". The original target has name "{1}". The proposed target has name "{2}"
-
Cause: An attempt was made to change the target of an entity that cannot have its target changed dynamically.
-
Action: Untarget a subdeployment and then retarget that subdeployment elsewhere. However, by doing so, the persistent state maintained for entities retargeted in this fashion will not be kept on the old target and may or may not be removed by the system.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045061: An attempt was made to create a durable subscription on a queue named "{3}". The client identifier is "{0}", the subscriptionName is "{1}" and the selector is "{2}". Durable subscriptions may only be created on topics.
-
Cause: An attempt was made to create a durable subscription on a queue.
-
Action: Do not attempt to create a durable subscription on a queue.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045062: There can be no more than one jms-interop-module element in the config.xml file.
-
Cause: More than one jms-interop-module element was found in the config.xml file.
-
Action: Do not attempt to define more than one jms-interop-module element in the config.xml file.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045063: The jms-interop-module must have name interop-jms and a descriptor file name jms/interop-jms.xml. This has name "{0}".
-
Cause: An attempt was made to use a jms-interop-module with a name other than interop-jms.
-
Action: Do not attempt to define a jms-interop-module element in the config.xml file with a name other than interop-jms.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045064: The target named "{1}" of a JMS module inside a deployment named "{0}" must be a WebLogic Server instance or a cluster. Instead, it is of type "{2}".
-
Cause: An attempt was made to target a JMS module to an invalid type of target.
-
Action: Do not attempt to target a JMS module to anything other than WebLogic Server instances or clusters. Any other type of target is not understood.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045065: A JMS module with fully qualified name "{1}" in an application named "{0}" does not have the proper hierarchy of targets. In particular, the subdeployment named "{2}" has a target "{3}" that is not a subtarget of any of the targets of "{0}". For example, the target "{3}" is not a subtarget of "{4}".
-
Cause: A target of a subdeployment of a JMS module was not contained within the targets of the whole JMS module.
-
Action: Ensure that the JMS module is targeted to a super-set of all the targets of the subdeployment, or retarget the subdeployment within the set of targets for the JMS module.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045066: The target named "{1}" of a JMS subdeployment named "{3}" inside a deployment named "{0}" must be a JMS server, WebLogic Server instance, or a cluster. Instead, it is of type {2}.
-
Cause: An attempt was made to target a JMS subdeployment to an invalid type of target.
-
Action: Do not attempt to target a JMS subdeployment to anything other than JMS servers, WebLogic Server instances or clusters. Any other type of target is not understood.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045067: The field "destination-name" was set to "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}". The destination-name field of a distributed destination may only be set in the interop module.
-
Cause: An attempt was made to set the destination-name field of a distributed destination member type. This is only allowed in the interop module in order to accommodate older clients.
-
Action: Change the name of the distributed destination member to the name of the physical queue or topic being referenced, and unset the destination-name field.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045068: The physical destination named "{3}", in the distributed destination member "{2}", in the distributed destination "{1}", in the module "{0}" does not exist.
-
Cause: An attempt was made by a distributed destination member to reference a destination that does not exist. The physical destination referenced to by a distributed destination must already exist.
-
Action: Create the physical destination before referring to it, or create the physical destination in the same edit session as the creation of the distributed destination member.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045069: The JMS module entity named "{2}" of type "{1}" does not exist in the JMSSystemResource "{0}".
-
Cause: An attempt was made to reference a JMS module entity that does not exist in the specified JMSSytemResource.
-
Action: Create the JMS module entity in the specified JMSSystemResource before referring to it.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045070: The configuration entity named "{2}" of type "{1}" does not exist in the domain "{0}".
-
Cause: An attempt was made to reference a configuration entity that does not exist in the specified domain.
-
Action: Create the configuration entity in the specified domain before referring to it.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045071: The JMS module entity named "{2}" of type "{1}" cannot be created in JMSSystemResource "{0}".
-
Cause: The JMS module entity creation using the the JMSModuleHelper API failed. See the accompanying exception for details.
-
Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045072: The configuration entity named "{2}" of type "{1}" cannot be created in domain "{0}".
-
Cause: The configuration entity creation using the JMSModuleHelper API failed. See the accompanying exception for details.
-
Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045073: The JMS module entity named "{2}" of type "{1}" cannot be deleted from JMSSystemResource "{0}".
-
Cause: The JMS module entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.
-
Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045074: The configuration entity named "{2}" of type "{1}" cannot be deleted from the domain "{0}".
-
Cause: The configuration entity deletion using the JMSModuleHelper API failed. See the accompanying exception for details.
-
Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045075: The JMS module managed entity named "{2}" of type "{1}" cannot be found in the JMSSytemResource "{0}" for modification.
-
Cause: The JMS module entity modification using the JMSModuleHelper API failed. See the accompanying exception for details.
-
Action: Resolve the problem identified by the accompanying exception, and retry the operation.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045076: An attempt was made to find and modify a JMS module entity named "{2}", of type "{1}", from the JMSSystemResource "{0}" using a null modifier.
-
Cause: The JMSEntityModifier argument for the findAndModifyEntity() helper API cannot be null.
-
Action: Use a valid weblogic.jms.extensions.JMSEntityModifer implementation as the modifier argument.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045077: The destination named "{0}" on the JMS server "{1}" would have caused the JMS server not to boot because the destination StoreEnabled value is true, but the JMS server does not have a store.
-
Cause: This configuration does not work in older releases because the destination StoreEnabled value is true, but the JMS server does not have a store.
-
Action: Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the StoreEnabled parameter on the destination.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045078: The destination named "{0}" on the JMS server "{1}" has a DeliveryParamsOverrides.DeliveryMode parameter set to persistent, but the JMS server does not have a store.
-
Cause: Messages cannot be made persistent on this JMS server because it does not have a store.
-
Action: Modify the configuration to remove this discrepency, and re-run the upgrade process. Either add a store to the JMS server or change the value of the DeliveryParamsOverrides.DeliveryMode parameter.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045079: An attempt was made to send a persistent message to the destination "{0}" hosted on the JMS server "{1}". This JMS server does not have a store, so the quality of service requested is not available.
-
Cause: An attempt was made to send a persistent message to a destination hosted by a JMS server that does not have a store. Since the message cannot be persisted, this message cannot be sent at the required quality of service.
-
Action: There is a parameter on the JMS server called "AllowsPersistentDowngrade". If this parameter is set to true, then persistent messages sent to this JMS server will be downgraded to non-persistent.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045080: The flow steps value {1} is larger than the flow interval value {2} in the connection factory "{0}". The flow steps value must be less than or equal to the flow interval value.
-
Cause: This is an invalid configuration. The flow steps value must be less than the entire flow interval.
-
Action: Modify the configuration of the connection factory to have the flow steps value be less than or equal to the flow interval.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045082: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}".
-
Cause: The naming exception should contain more information about why this operation failed.
-
Action: See the attached naming exception message, which should have more information about why this operation failed.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045083: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the local JNDI context.
-
Cause: The naming exception should contain more information about why this operation failed.
-
Action: See the attached naming exception, which should have more information about why this operation failed.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045084: An unexpected naming exception occurred while binding the destination "{0}" to the JNDI name "{1}" to the application JNDI context.
-
Cause: The naming exception should contain more information about why this operation failed.
-
Action: See the attached naming exception, which should have more information about why this operation failed.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045086: The jms-system-resource cannot have the name interop-jms.
-
Cause: An attempt was made to define a jms-system-resource with the name interop-jms.
-
Action: Do not attempt to define a jms-system-resource element in the config.xml file with the name interop-jms.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045087: The JMS deployment "{0}" has the descriptor file name "{1}", which is reserved for internal use only.
-
Cause: An attempt was made to define a JMS deployment with the reserved file name "interop-jms.xml". This name is reserved by the system for use as the interop module.
-
Action: Do not attempt to define a JMS deployment with the reserved name "interop-jms.xml" as its file name.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045088: The JMS module descriptor file "{1}" used by the JMS system resource "{0}" is illegal. Either the descriptor file name does not end with -jms.xml or the descriptor is being used by another JMS system resource in the configuration.
-
Cause: An attempt was made to define a JMS system resource with the illegal descriptor file name.
-
Action: Do not attempt to define a jms-system-resource element in the config.xml file with the illegal descriptor file name.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045093: A UDQ named "{0}" was found in the JMS interop module. UDQs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDQ in that module.
-
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
-
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045094: A UDT named "{0}" was found in the JMS interop module. UDTs were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the UDT in that module.
-
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
-
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045095: An SAF imported destinanation named "{0}" was found in the JMS interop module. SAF imported destinations were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF imported destinations in that module.
-
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
-
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045096: An SAF remote context named "{0}" was found in the JMS interop module. SAF remote contexts were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF remote context in that module.
-
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
-
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045097: An SAF error handlings named "{0}" was found in the JMS interop module. SAF error handlings were not available prior to the 9.0 release of WebLogic Server, and therefore cannot be in the JMS interop module. Create another JMS module and put the SAF error handlings in that module.
-
Cause: An invalid entity type was found in the JMS module that handles interoperating clients. This element should be placed into a different JMS module.
-
Action: Place the entity into another JMS module, and either deploy that module as a system resource or as a deployable resource.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045098: There is a JMS system resource and an application deployment both named "{0}". The names of all JMS system resources and all application deployments must be different.
-
Cause: Both a JMS system resource and an application deployment have the same name. This would cause similarly named resources in a JMS module descriptor file to have conflicting runtime names, and therefore is not allowed.
-
Action: Change the name of either the JMS system resource or application deployment so that there is no name conflict.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045099: An attempt was made to create a temporary destination. However, no JMS server in the cluster is able to host temporary destinations. Ensure that at least one of the JMS servers in the cluster has the HostingTemporaryDestinations parameter set to true (which is the default).
-
Cause: None of the JMS servers in the cluster are available for hosting temporary destinations.
-
Action: Modify the HostingTemporaryDestinations parameter on at least one JMS server in the cluster. Note that in releases prior to 9.0, the default for the ability to host temporary destinations was false, while in 9.0 and beyond, the default for the ability to host temporary destinations is true.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045100: The createQueue or createTopic call was made with a null or zero length destination name.
-
Cause: The createQueue or createTopic call must be made with the name of a destination to find.
-
Action: Do not pass a null or zero length string to createQueue or createTopic.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045101: The destination name passed to the createTopic or createQueue "{0}" is invalid. If the destination name does not contain a "/" character, then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character, then the string before the "/" must be the name of a JMS server or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WebLogic Server instance will be returned.
-
Cause: Either a distributed destination of the given name does not exist in the cluster to which the client is attached or the destination name passed to createTopic or createQueue does not contain a "/" character, or there is nothing before the "/" character.
-
Action: Ensure that the distributed destination is available on the same cluster where the client is located, or format the destination name string properly.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045102: A destination named "{0}" was not found on WebLogic Server instance "{1}".
-
Cause: An attempt was made to find a destination of a given name on a particular WebLogic Server instance. No destination of that name could be found on that WebLogic Server instance.
-
Action: It is possible that the createTopic or createQueue call was routed to a WebLogic Server instance that does not contain a destination with the given name. The set of WebLogic Server instances where this request can be routed can be controlled by using a connection factory that is only targeted to WebLogic Werver instances that have destinations of the desired name.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045103: While trying to find a topic or a queue, the specific JMS server requested could not be found. The linked exception may contain more information about the reason for failure.
-
Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.
-
Action: The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045104: While trying to find a topic or a queue, the specific JMS server requested could not be found.
-
Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not locate the JMS server of that name.
-
Action: Ensure that the JMS server requested exists in the configuration of the cluster to which the client is attached.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045105: While trying to find a topic or a queue, communication failed with the specific JMS server requested. The linked exception may contain more information about the reason for failure.
-
Cause: A specific JMS server was requested by a call to createTopic or createQueue. However, the system could not communicate with the JMS server of that name.
-
Action: The WebLogic Server instance on which that JMS server is targeted may be down. The JMS server may be suspended. Check on the status of the JMS server and also on the status of the communication between the servers in the cluster. Check the linked exception for more information about the cause of this failure.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045106: A destination named "{0}" was found. However, the requested destination was of type "{1}", and the destination found was not of that type.
-
Cause: Either the user called createTopic and the destination found was a queue or the user called createQueue and the destination found was a topic.
-
Action: Ensure that the destination name requested is of the correct type.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045107: A communication failure occurred while attempting to remove a durable subscription. The linked exception may contain more details about the cause of the failure.
-
Cause: While attempting to remove a durable subscription a communication failure occurred.
-
Action: Check on the status of WebLogic Server instance where the destination which the durable subscription refers to resides. Check the linked exception for more information about the cause of this failure.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045109: A foreign server named "{0}" was found which does not have a connection URL specified. However, it contains a "{2}" named "{1}" that has the same local and remote JNDI name value "{3}". This is an invalid configuration and is not allowed.
-
Cause: The user has configured a foreign server without a connection URL and has either a foreign connection factory or a foreign destination with both the local and remote JNDI name matching.
-
Action: Ensure that either the foreign server has a connection URL to the foreign server or that the local and remote JNDI names are different.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045110: The JMS resource named "{0}" has incorrect targeting information. This resource has the default-targeting-enabled attribute set to true and has a valid sub-deployment-name value specified.
-
Cause: A JMS resource cannot have both default targeting enabled and a subdeployment name specified.
-
Action: Ensure that either the default targeting is enabled or that the valid subdeployment name is specified.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045111: The JMS resource named "{0}" has incorrect targeting information. A JMS physical destination cannot have the default-targeting-enabled attribute set.
-
Cause: A JMS physical destination cannot have the default-targeting-enabled attribute set.
-
Action: Ensure that the default-targeting-enabled attribute is not set for the physical destinations.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045112: The flow minimum value {1} is larger than or equal to the flow maximum value {2} in connection factory "{0}". The flow minimum value must be less than the flow maximum value.
-
Cause: This is an invalid configuration. The flow minimum value must be less than the flow maximum value.
-
Action: Modify the configuration of the connection factory to have the flow minimum value be less than the flow maximum value.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045113: JMS distributed destination forward request denied for the destination named "{1}". Reason "{0}".
-
Cause: JMS distributed destinations may not have been fully initialized.
-
Action: If forwarding does not begin after a few minutes, contact My Oracle Support.
Level: 1
Type: NOTIFICATION
Impact: JMSExceptions
- BEA-045114: Failed to unsubscribe the subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription without a topic object.
-
Cause: An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a client ID policy of UNRESTRICTED.
-
Action: Use the weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a client ID policy of UNRESTRICTED. If using a pre-AS11gR1PS3 Java client, upgrade to a AS11gR1PS3 client. If using a non-Java client, clean up the durable subscription from the Administration Console or use WebLogic Scripting Tool (WLST) commands or scripts.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045115: The SubDeploymentMBean {0} in JMS Module {1} can only be targeted to a single non-clustered JMSServer as it contains a standalone queue, topic or quota that can only be targeted to a single non-clustered JMSServer.
-
Cause: The SubDeploymentMBean of the given name cannot be targeted to anything but a single non-clusterd JMSServer.
-
Action: Modify the target of the subdeployment so that it contains only a single non-clustered JMSServer.
Level: 1
Type: ERROR
Impact: JMSExceptions
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045117: An SAFAgent (store-and-forward agent) cannot be targeted to cluster {0} which has dynamic servers enabled (dynamic servers exist in clusters where the MaximumDynamicServerCount is greater than zero). Instead of using cluster targeting, SAFAgents can be targeted directly to one or more of non-dynamic WebLogic Servers or any one of their migratable target counterparts.
-
Cause: An SAFAgent cannot be targeted to cluster {0} which has dynamic servers enabled (dynamic servers exist in clusters where the MaximumDynamicServerCount is greater than zero). Instead of using cluster targeting, SAFAgents can be targeted directly to one or more of non-dynamic WebLogic Servers or any one of their migratable target counterparts.
-
Action: Modify the target of the SAFAgent such that it is either targeted directly to one or more non-dynamic WebLogic Servers or any one of their migratable target counterparts.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045118: MaximumDynamicServerCount cannot be set higher than 0 for the DynamicServers {0} in cluster {1}. One or more SAFAgents (store-and-forward agents) are currently targeted to the same cluster, and SAFAgents are not supported for a cluster in which dynamic servers are enabled. Instead of using cluster targeting, SAFAgents can be targeted directly to one or more non-dynamic WebLogic Servers or any one of their migratable target counterparts.
-
Cause: MaximumDynamicServerCount cannot be set higher than 0 for the DynamicServers {0} in cluster {1}. One or more SAFAgents are currently targeted to the same cluster, and SAFAgents are not supported for a cluster in which dynamic servers are enabled. Instead of using cluster targeting, SAFAgents can be targeted directly to one or more non-dynamic WebLogic Servers or any one of their migratable target counterparts.
-
Action: Modify the target of the SAFAgent or SAFAgents that are targeted to this cluster such that they are either targeted directly to one or more of non-dynamic WebLogic Servers or any one of their migratable target counterparts.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-045119: A JMS message send request failed for distributed destination {0}. Neither Unit-of-Order (UOO) nor Unit-of-Work (UOW) messages are supported for distributed destinations that have a member hosted by a clustered JMS Server. Distributed destination {0} has one or more of its members hosted by a clustered JMS server.
-
Cause: A JMS message send request failed for distributed destination {0}. Neither Unit-of-Order (UOO) nor Unit-of-Work (UOW) messages are supported for distributed destinations that have a member hosted by a clustered JMS Server. Distributed destination {0} has one or more of its members hosted by a clustered JMS server.
-
Action: To produce either UOO or UOW messages on a distributed destination, either use a distributed destination that is hosted only on one or more non-dynamic JMS servers, or send messages directly to a member of the distributed destination. Note that when an application sends messages directly to a distributed destination member, the application is responsible for making sure that all messages with the same UOO/UOW string are sent to the same distributed destination. This ensures strictly ordered message processing for the given UOO/UOW.
Level: 1
Type: ERROR
Impact: JMSExceptions
- BEA-050001: WLContext.close() was called in a different thread than the one in which it was created.
-
Cause: The threads used to create and close the context are different. As a result, the context entries associated with the creating thread might not be cleaned up.
-
Action: Close the context in the creating thread.
Level: 1
Type: WARNING
Impact: JNDI
- BEA-050002: Cannot replicate the object that is bound in the JNDI under the name {0}.
-
Cause: A non-serializable object cannot be serialized.
-
Action: If the object was not intended to be replicated, set the replicate bindings to false. If the object should be replicated to all nodes in the cluster, ensure that the object is serializable or externalizable.
Level: 1
Type: ERROR
Impact: JNDI
- BEA-050006: An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.
-
Cause: An attempt was made to look up the versioned object "{0}" from an external client or another application. This can potentially cause in-flight work of the application version not being tracked properly, and thus, be retired prematurely.
-
Action: Ensure that the possibility of premature retirement of the application version is either tolerated or handled properly. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_EXTERNAL_LOOKUP to "true" when performing lookup of the versioned object.
Level: 1
Type: WARNING
Impact: JNDI
- BEA-050007: An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.
-
Cause: An attempt was made to look up the non-versioned global resource "{0}" from an application version "{1}". This can potentially cause conflict of the global resource usages among multiple application versions.
-
Action: Ensure that usages of the global resource by multiple application versions do not conflict. To disable this check, set the JNDI environment property as specified by weblogic.jndi.WLContext.ALLOW_GLOBAL_RESOURCE_LOOKUP to "true" when performing lookup of the global resource.
Level: 1
Type: WARNING
Impact: JNDI
- BEA-055014: Error sending message
-
Cause: The linked exception will contain more details concerning the failure to send the message.
-
Action: The action will depend on the error that occurred. More information about the specific error that occurred can be found in the linked exception.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055030: This topic does not support durable subscriptions.
-
Cause: Durable subscribers are not supported on Distributed Topics and no subscribers at all are supported on SAF topics
-
Action: Avoid attempting to create a durable subscriber on a distributed topic or do not create a subscriber on an SAF topic.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055032: An attempt was made to create a named consumer ({0}) on a connection with no clientID.
-
Cause: An attempt was made to create a named consumer on a connection with no clientID.
-
Action: Avoid attempting to create a named consumer on a connection with no clientID.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055035: Cannot open multicast socket, {0}.
-
Cause: An attempt was made to open a multicast socket and failed. The reason for the failure may be in the exception
-
Action: For more details, check the printed exception on the failure to open the multicast socket.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055036: Cannot join multicast group ({0}) {1}
-
Cause: An attempt was made to join a multicast group and failed. The reason for failure may be in the exception.
-
Action: For more details, check the printed exception on the failure to join the multicast group.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055041: Cannot leave multicast group ({0}) {1}
-
Cause: An attempt was made to leave a multicast group and failed. The reason for failure may be in the exception.
-
Action: For more details, check the printed exception on the failure to leave the multicast group.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055048: Multicast selectors are not supported in the thin client.
-
Cause: Multicast selectors are not supported in the thin client.
-
Action: If selectors are required, avoid using the JMS thin client. If selectors are not required, avoid using them while using the thin client.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055072: Wrong connection for this temporary destination
-
Cause: An attempt was made to call createConsumer on an invalid connection from a temporary destination.
-
Action: Create consumers using the same connection that was used to create the temporary destination.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055075: It is possible that the client is malfunctioning: a RuntimeException was thrown from its onMessage method.
-
Cause: The onMessage method of the client threw a RuntimeException.
-
Action: Modify the code such that the RuntimeException does not occur from within the body of the user code. This warning is required by section 4.5.2 of the JMS Specification.
Level: 1
Type: WARNING
Impact: JMSClientExceptions
- BEA-055077: Cannot override producer destination.
-
Cause: A call to send with a non-null destination was made on a producer that is already bound to a destination.
-
Action: Avoid calling send with a non-null destination on a producer that is already bound to a destination.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055078: Cannot override producer destination
-
Cause: A call to send with a non-null destination was made on a producer that is already bound to a destination.
-
Action: Avoid calling send with a non-null destination on a producer that is already bound to a destination.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055084: A connection consumer works only on the server.
-
Cause: A connection consumer can be created only in the same JVM in which the server is running.
-
Action: Avoid attempting to create a connection consumer on a JVM that is not running the server.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055087: The session already has a message listener.
-
Cause: A consumer may not have an individual message listener if its parent session already has one defined.
-
Action: Avoid attempting to set a message listener for a consumer if the session already has a listener defined.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055108: Read past end of message
-
Cause: An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information
-
Action: Avoid attempting to read past the end of a StreamMessage. See the linked EOFException for more information.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055114: There was an eeror when deserializing an object. Some typical reasons for failure are: missing application class, application class version mismatch, or Java objects not being supported.
-
Cause: There was an error deserializing an object. A linked IOException may have more details.
-
Action: See the linked IOException for more details.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055125: Unknown underlying stream type, cannot convert 6.0 class.
-
Cause: While attempting to read a message created by an older version of WebLogic Server, a failure occurred.
-
Action: It may not be possible to read the older version of the message. Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055126: Stream is corrupted. Possible older version
-
Cause: While attempting to read a message created by an older version of WebLogic Server, a failure occurred.
-
Action: It may not be possible to read the older version of the message. Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055133: Could not deserialize message.
-
Cause: The system could not deserialize a MapMessage. The linked IOException should contain more information about the nature of the error.
-
Action: Examine the linked exception to discover what caused the failure.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055134: Unsupported class version {0}. Expected a value between {1} and {2} inclusive.
-
Cause: While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {1} then it is possible an attempt was made to access a newer JMS version than the current version. Otherwise a possible attempt has been made to interoperate with an unsupported older version of JMS.
-
Action: Ensure that the versions of Oracle products that are interoperating are supported. If the versions should be supported, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055137: JMSProducerSendResponse versions {0}, {1} not compatible with peer: {2}
-
Cause: An interoperability error occurred.
-
Action: Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055138: Peer not compatible with DistributedDestinationImpl version {0}. Peer Major Version is less than 6.
-
Cause: An interoperability error occurred.
-
Action: Only use versions of Oracle products that can interoperate with each other. If the versions being used should interoperate, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055146: The stream cannot handle raw objects.
-
Cause: The stream is probably from an unintended source, such as a Web browser.
-
Action: Only connect to the Oracle product TCP port with a proper client. If the client is a proper client, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055149: Attempt to read past end of message ({0})
-
Cause: The end of the BytesMessage was reached, but an attempt was made to read past it. {0} indicates where the attempt was made and will only be significant to My Oracle Support.
-
Action: Avoid attempting to read past the end of the BytesMessage.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055152: length ({0}) is greater than the length of the array ({1}).
-
Cause: In a call to readBytes, the length parameter is larger than the size of the bytes array to fill.
-
Action: Fix the code to ensure the length passed to readBytes is less than or equal to the length of the output array.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055165: The following exception has occurred: {0}.
-
Cause: An error condition has occurred.
-
Action: Look for the associated exception in the log or the program to see what the results are. In general, this stack trace will help in debugging an existing problem.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055168: Synchronous message-prefetching consumer cannot support user transaction.
-
Cause: Synchronous message-prefetching consumer cannot support user transaction.
-
Action: Disable the user transaction or the synchronous message-prefetching consumer in the jms connection factory setting.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055169: Network connection to server was lost.
-
Cause: The network connection to the server was lost.
-
Action: This is usually a recoverable error when the JMS client is using the auto-reconnect/failover feature. This error is exposed to the user (JMS client code developer) when the auto-reconnect feature cannot make a decision without user input on a particular course of action after failover. The user can consciously code to continue to use relevant refreshed JMS objects with a potential lowered quality of service such as duplicate/lost/out-of-order messages, or decide to close the relevant JMS object.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055171: Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe() API.
-
Cause: An attempt was made to unsubscribe a durable subscription using the standard javax.jms.Session.unsubscribe(String name) method from a connection that has a Client ID policy of UNRESTRICTED.
-
Action: Use weblogic.jms.extensions.WLSession.unsubscribe(Topic topic, String name) API to unsubscribe a durable subscription from a connection that has a Client ID policy of UNRESTRICTED.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055172: Failed to unsubscribe subscription "{0}", client ID "{1}". This connection has a Client ID policy of UNRESTRICTED and cannot unsubscribe a durable subscription with a null topic or distributed topic instance.
-
Cause: An attempt was made to unsubscribe a durable subscription with a null Topic object or a distributed topic object from a connection that has a Client ID policy of UNRESTRICTED.
-
Action: Provide a standalone topic object or a member of a distributed topic when calling weblogic.jms.extensions.WLSession.unsubscribe(String topic, String name).
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055173: Read past end of message ({0})
-
Cause: An attempt was made to read past the end of a StreamMessage. A linked EOFException may contain more information
-
Action: Do not attempt to read past the end of a StreamMessage. See the linked EOFException for more information
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-055176: Active transaction detected during send, publish, or receive while using a non-XATransaction Resource Adapter.
-
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.
Level: 1
Type: ERROR
Impact: JMSClientExceptions
- BEA-080005: An exception was generated by the RMI server: {0} {1}.
-
Cause: The error response could not be sent to the client. The underlying socket caused an IOException while dispatching the error response.
-
Action: The associated stack trace contains information about the error.
Level: 1
Type: WARNING
Impact: RMI
- BEA-080006: Failed to associate the transaction context with the response while marshalling an exception to the client: {0}.
-
Cause: An IOException occurred while associating a transaction context with the response. This happened when marshalling an exception in the response. Most likely, the socket has been torn down or an error occurred in the stream.
-
Action: Check the server logs for more details.
Level: 1
Type: WARNING
Impact: RMI
- BEA-080009: An error was generated by the RMI server: {0} invoking: {1}.
-
Cause: A java.lang.Error occurred while invoking method {1} on {0}. A ServerError occurred due to the server side RMI method call.
-
Action: Check the nested exception in the ServerError for more details.
Level: 1
Type: WARNING
Impact: RMI
- BEA-080011: Empty workingSet found while assembling the heartbeat for {0}.
-
Cause: An empty set of references for {0} was found while assembling the deterministic garbage collector (DGC) heartbeats for all remote virtual machines that are referenced from this virtual machine.
-
Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support.
Level: 1
Type: NOTIFICATION
Impact: RMI
- BEA-080012: No workingSet found for {0} residing in {1}.
-
Cause: An empty working set for {0} was found while periodically scanning the list of finalized references and decrementing the count for any reference found. This is related to the deterministic garbage collector (DGC).
-
Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1
Type: ERROR
Impact: RMI
- BEA-080013: Reference for {0} not found in working set.
-
Cause: Did not find {0} in the working set while attempting to decrement the reference count. This is related to the deterministic garbage collector (DGC).
-
Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1
Type: ERROR
Impact: RMI
- BEA-080016: No connection available to: {0}. References to objects hosted by it are in jeopardy.
-
Cause: The client lost connection to the server {0}. If the server does not receive lease renewal messages on the server, RMI runtime removes the remote objects whose leases are not renewed.
-
Action: If the server {0} has been shut down or crashed, no action is required. Otherwise, ensure that the network is healthy.
Level: 1
Type: WARNING
Impact: RMI
- BEA-080020: An exception occurred in the DGC server sweep {0}.
-
Cause: A runtime error occurred while the DGC server (host of remote objects) requested a sweep to periodically clean up server references.
-
Action: Provide the log files to My Oracle Support for further analysis of the problem.
Level: 1
Type: ERROR
Impact: RMI
- BEA-080022: Tried to enroll lost reference: {0}.
-
Cause: This message is logged when an attempt is made to increment the reference count of a lost reference. The reference may have already been released.
-
Action: If a java.rmi.NoSuchObjectException occurs, contact My Oracle Support for further analysis of the error.
Level: 1
Type: NOTIFICATION
Impact: RMI
- BEA-080026: Exporting remote object {0} with ID {1}.
-
Cause: When a remote object is exported into RMI, RMI runtime assigns an object ID to it, thus setting up the environment for remote invocation.
-
Action: This is an informational message. No action is required.
Level: 1
Type: NOTIFICATION
Impact: RMI
- BEA-090001: Failed to broadcast LoginFailureRecord to the other cluster servers, {0}.
-
Cause: An I/O exception occurred.
-
Action: For more information on how the invalid login attempts are handled, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090002: Failed to broadcast unlock user {0} to the other clustered servers. {1}
-
Cause: An I/O exception occurred.
-
Action: For more information on how locked user account lockouts are handled, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090040: The File realm contains more users than the specified maximum. Maximum = {0}, currently have {1}.
-
Cause: The File realm sets a limit on the maximum number of supported users. The system has exceeded that limit.
-
Action: Raise the value of the Max Users attribute.
Level: 1
Type: WARNING
Impact: Security
- BEA-090041: The File realm contains more groups than the specified maximum. Maximum = {0}, currently have {1}.
-
Cause: The File realm sets a limit on the maximum number of supported groups. The system has exceeded that limit.
-
Action: Raise the value of the Max Groups attribute.
Level: 1
Type: WARNING
Impact: Security
- BEA-090042: The File realm contains more ACLs than the specified maximum. Maximum = {0}, currently have {1}.
-
Cause: The File realm sets a limit on the maximum number of supported ACLs. The system has exceeded that limit.
-
Action: Raise the value of the Max ACLs attribute.
Level: 1
Type: WARNING
Impact: Security
- BEA-090051: Error creating security runtime management.
-
Cause: During initialization, the security runtime registers with the OAM infrastructure. If this process fails, a management exception occurs.
-
Action: Verify that the user booting the server is a member of the Administrator group.
Level: 1
Type: ERROR
Impact: Security
- BEA-090052: Server installed as Windows NT service with incorrect password for user {0}. The password may have been changed since the server was installed as a Windows NT Service. Contact the Windows NT system administrator.
-
Cause: The server is incorrectly configured as a Windows NT service.
-
Action: Contact the Windows NT system administrator.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090056: User {0} had{1,choice,1# one invalid login attempt|2# {1,number} invalid login attempts}, locking account for {2} minutes.
-
Cause: User exceeded the value of Lockout Threshhold attempts within the period of time specified in the Lockout Reset Duration attribute. The user account is locked.
-
Action: For more information about protecting user accounts, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090067: User lockout expired, unlocking user {0} in security realm {1}.
-
Cause: The period of time specified for the Lockout Duration attribute has expired for this user account. The user account was locked for exceeding the number of invalid login attempts specified in the Lockout Threshold attribute within the period of time specified in the Lockout Reset Duration attribute.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090070: Failed to broadcast unlock user {0} in security realm {1} to the other cluster servers, {2}.
-
Cause: An IOException occurred.
-
Action: For more information about unlocking user accounts, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090074: Initializing {0} provider using LDIF template file {1}.
-
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 of the LDIF information for this security provider.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090077: A failure occurred while attempting to create {1} for the {0} provider had been loaded. The exception is {2}.
-
Cause: Read the exception to determine the cause.
-
Action: Take appropriate action to keep the exception from happening again. The marker file can be created manually.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090078: User {0} in security realm {1} has had {2,choice,1# one invalid login attempt|2# {2,number} invalid login attempts}, locking account for {3} minutes.
-
Cause: User exceeded the number of invalid login attempts specified in the Lockout Threshhold attribute within the period of time specified in the Lockout Reset Duration attribute. The user account is locked.
-
Action: For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090079: Failed to broadcast LoginFailureRecord for security realm {0} to the other cluster servers, {1}.
-
Cause: An I/O exception occurred.
-
Action: For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090087: Server failed to bind to the configured administrator port. The port may already be in use by another process.
-
Cause: Most likely another process opened the administrator port, thus causing a port conflict.
-
Action: Inspect the log file for messages that identify the reason why none of the listen ports could be opened.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090088: Private Key keystore alias is not specified in the SSL configuration of server {0}, security realm {1}. Assuming 6.x private key configuration. Loading the private key from a file.
-
Cause: The keystore alias is not specified in the Server Private Key Alias attribute.
-
Action: Set the Server Private Key Alias attribute with the alias used to load the private key of the server into the keystore.
Level: 1
Type: WARNING
Impact: Security
- BEA-090089: SSL did not find the passphrase for the private key of the server on server {0} for security realm {1}. This may cause an error when SSL attempts to load the private key of the server.
-
Cause: Either the Server Private Key PassPhrase attribute is not set or the Identity PassPhrase attribute is not set.
-
Action: If a passphrase is required to retrieve the private key from a keystore, set the Server Private Key PassPhrase attribute.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090091: SSL was unable to get a required Security Service.
-
Cause: A security service was requested, but no value was returned.
-
Action: It is likely that the server's configuration has been corrupted. Restore the configuration files from backup. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090093: No pre-WLS 8.1 Keystore providers are configured for server {0} for security realm {1}.
-
Cause: This is an informational message.
-
Action: To use pre-WLS 8.1 keystores with the SSL configuration, at least one Keystore Provider must be configured.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090095: SSL cannot instantiate the keystore {1} on server {0}.
-
Cause: An exception occurred while creating the keystore. This exception caused the create to fail.
-
Action: Most likely, the keystore was not configured correctly. Ensure that the keystore provider has been configured on the named server. Review the server log for subsequent messages that contain the exception from the keystore provider.
Level: 1
Type: ERROR
Impact: Security
- BEA-090096: The MBeans configured for the keystore provider on server {0} for security realm {1} are not Keystore MBeans.
-
Cause: The MBeans passed to the WebLogic Server key management initialization method are not Keystore MBeans.
-
Action: Most likely, the keystore provider was not configured correctly. Check that the keystore provider has been configured on the named server.
Level: 1
Type: ERROR
Impact: Security
- BEA-090097: The KeyManager class for private keys server {0} for security realm {1} could not be instantiated.
-
Cause: The Key Manager Security service is null.
-
Action: There was a problem with the installation of WebLogic Server because the KeyManager is an internal class that supports the WebLogic Security service.
Level: 1
Type: ERROR
Impact: Security
- BEA-090101: A keystore exception was returned when the server {1} attempted to load trusted CAs from the keystore file {0}.
-
Cause: The keystore JDK method threw a keystore exception.
-
Action: There is a problem with the keystore file. Verify that the file is intact and valid. Use the JDK keytool utility to display the contents of the file. If the file is corrupt, down load a new file from the JavaSoft web site or configure a trusted CA keystore. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090108: The server was unable to retrieve the private key aliased by {2} from the configured keystore on server {0} for security realm {1}. Private key password might be invalid.
-
Cause: An exception was returned by the keystore getKey method.
-
Action: Check that a private key keystore is configured on the server. Verify that the private key keystore exists. Ensure that the keystore is valid and contains the private key necessary to use SSL on the server. Verify that the passphrase configured for the private key was the one used to load the private key into the keystore when the private key was created. This exception most often occurs when the passphrase is invalid. Check the log for subsequent messages that contain the key store exception. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090109: The server was unable to find the configured private key on server {0} in the file specified by the SSL Server Key File Name attribute.
-
Cause: The server looks at the Server Key File Name attribute to load the private key of the server when it cannot find the private key in a configured keystore using the alias that is specified in the Server Private Key Alias attribute as the alias string. One possible cause of this error is that server is not configured with a private key keystore or the server is configured to use the pre-7.0 SSL attribute Server Key File Name.
-
Action: A pre-7.0 configuration is being used for SSL connections, however that configuration does not specify a value for the Server Key File Name attribute. Either provide a value for the Server Key File Name attribute or configure a keystore for the server. SSL will not be able to initialize until the configuration is corrected. For more information, see the security documentation available at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090110: The server was unable to find the configured certificate on server {0} in the file specified by the Server Certificate File Name attribute {1}.
-
Cause: The server looks at the Server Certificate File Name attribute to load the certificate for the server. One possible cause of this error is that the server is not configured with a certificate, or there is a problem with the file configured as the server's certificate.
-
Action: Verify that a certificate file is configured for the server and that the certificate contained in the file is valid. For more information, see the security documentation available at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090112: SSL is configured to require clients to present their certificates, however, no trusted certificates have been loaded. The trusted certificates are necessary for validating client certificates.
-
Cause: Either the "Client Certificates Enforced" option was set by mistake or the problem is with SSL trusted certificates configuration.
-
Action: Clear the "Client Certificates Enforced" option or specify the location of keystore that contains the trusted certificates.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090118: LDIF template file {1} was empty. The WebLogic provider {0} has been bootstrapped but has not been initialized with any LDIF data.
-
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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090119: LDIF template file {1} not found. The WebLogic Server provider {0} has been bootstrapped but has not been initialized with any LDIF data.
-
Cause: A WebLogic Server 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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090120: Cannot find the file specified by SSL.TrustedCAFileName {0} on server {1}.
-
Cause: The specified file was not found.
-
Action: Verify that the specified file exists in the expected directory and/or that the value of Trusted CA File Name attribute refers to an existing file.
Level: 1
Type: WARNING
Impact: Security
- BEA-090126: Unable to read a valid version number for property {0} from file {1}. Received exception {2}.
-
Cause: The value for the {0} property may have been corrupted.
-
Action: Shut down 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. Restart WebLogic Server.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090127: Encountered a {2} exception while attempting to read from file {1} for WebLogic {0} provider.
-
Cause: The {1} file may have been deleted while it was being accessed.
-
Action: Shut down the server. Attempt to restore the file from a backup. If no backup is available, restart the server. Note that the default WebLogic Server provider might not be correctly initialized.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090129: Updating {0} provider to version {2} using LDIF update template file {1}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090130: Failure {3} while attempting to update the LDIF to version {2} in file {1} for WebLogic {0} provider.
-
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 that 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.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090131: Could not create a {0} JDK keystore instance. Exception: {1}
-
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. Restart the serverr after correcting the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090132: Could not open the keystore file {0} for read access. Exception: {1}
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090133: Could not load a {1} keystore from the file {0}. Exception: {2}
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090134: Could not load a {1} keystore from the file {0}. Exception: {2}
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090135: Could not load a {1} keystore from the file {0}. Exception: {2}
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090136: Could not open the keystore file {0} for write access. Exception {1}
-
Cause: The file may exist but is a directory rather than a regular file, the file does not exist and cannot be created, or the file cannot be opened.
-
Action: Verify that the correct pathname to the keystore was specified and that the parent directory exists. If neither of these problems exist, read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090137: Could not store a {1} keystore in the file {0}. Exception: {2}
-
Cause: There was an I/O problem with the keystore data.
-
Action: Verify that the passphrase is correct. Some JDK keystore implementations require the use of the password for a previous keystore. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090138: Could not store a {1} keystore in the file {0}. Exception: {2}
-
Cause: Some certificates included in the keystore could not be stored.
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090139: Could not store a {1} keystore in the file {0}. Exception: {2}
-
Cause: The data integrity algorithm for the keystore could not 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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090140: Could not store a {1} keystore in the file {0}. Exception: {2}
-
Cause: The keystore has not been initialized (loaded).
-
Action: Make sure to load the keystore before storing it. Read the exception text for more information on diagnosing the problem. Reboot the server after correcting the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090141: The WebLogic keystore provider {1} in security realm {0} cannot be used for private keys because its private key keystore was not configured.
-
Cause: The Private Key Store Location attribute was not specified.
-
Action: To use the WebLogic keystore provider to store private keys, perform the following steps. Create a JDK keystore and load the private keys into the keystore. Use the Administration Console to attributes on the WebLogic keystore provider. Set the Private Key Store Location attribute to the path of the JDK keystore file. Set the Private Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the type of the JDK keystore (the Type attribute may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090142: The WebLogic keystore provider {1} in security realm {0} cannot be used for trusted (root) CAs because its trusted (root) CA keystore was not configured.
-
Cause: The Root Key Store Location attribute was not specified.
-
Action: To use the WebLogic keystore provider to store trusted CAs, perform the following steps. Create a JDK keystore. Load the trusted CA certificates into the keystore. Set attributes on the WebLogic keystore provider. Set the Root Key Store Location attribute to the path of the JDK keystore file. Set the Root Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the JDK keystore type (the type may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090143: The WebLogic keystore provider {1} in security realm {0} cannot be used for private keys because its configured private key keystore file {2} does not exist.
-
Cause: The file {2} does not exist as a global pathname or in the domain directory.
-
Action: To use the WebLogic keystore provider to store private keys, perform the following steps. Create a JDK keystore and load the private keys into the keystore. Use the Administration Console to set attributes on the WebLogic Keystore provider. Set the Private Key Store Location attribute to the path of the JDK keystore file. Set the Private Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the type of the JDK keystore (the Type attribute may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090144: The WebLogic keystore provider {1} in security realm {0} cannot be used for trusted (root) CAs because its configured trusted (root) CA keystore file {2} does not exist.
-
Cause: The file {2} does not exist as a global pathname or in the domain directory.
-
Action: To use the WebLogic keystore provider to store trusted CAs, perform the following steps. Create a JDK keystore. Load the trusted CA certificates into the keystore. Set attributes on the WebLogic keystore provider. Set the Root Key Store Location attribute to the path of the JDK keystore file. Set the Root Key Store Passphrase attribute to the passphrase of the JDK keystore file (some keystore types (for example, JKS) allow an empty passphrase for read-only access). Set the Type attribute to the JDK keystore type (the type may be left empty if the JDK keystore uses the default keystore type configured in the java.security file). Restart the server.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090145: The WebLogic keystore provider {1} in security realm {0} cannot be used for private keys because its private key {3} keystore could not be loaded from the file {2}.
-
Cause: See the error logged before this one for details.
-
Action: Verify that the Root Keystore Location attribute is specified correctly. Verify that the Root Keystore PassPhrase attribute matches the passphrase of the keystore. Some keystore types (for example, JKS) allow an empty passphrase for read-only access. Verify that the Type attribute is correct. The Type attribute may be left empty if the JDK keystore uses the keystore type configured in the java.security file. Verify that the private key keystore exists and is properly configured. Verify that a keystore for the specified type is properly configured. After correcting the problem, restart the server.
Level: 1
Type: ERROR
Impact: Security
- BEA-090146: The WebLogic keystore provider {1} in security realm {0} cannot be used for trusted CAs because its trusted CA {3} keystore could not be loaded from the file {2}.
-
Cause: See the error logged before this one for details.
-
Action: Verify that the Private Keystore Location attribute is correct. Verify that the Private Keystore PassPhrase attribute matches the passphrase of the keystore. Note that some keystore types (for example, JKS) allow an empty passphrase for read-only access. Verify that the Type attribute is correct. The Type attribute may be empty if the JDK keystore uses the keystore type configured in the java.security file. Verify that the private key keystore exists and is properly configured. Verify that a JDK keystore for the type specified is properly configured. After correcting the problem, reboot the server.
Level: 1
Type: ERROR
Impact: Security
- BEA-090152: Demo trusted CA certificate is being used in production mode: {0}. The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.
-
Cause: A trusted CA keystore contains a demo certificate.
-
Action: Remove the demo certificate from the trusted CA keystore.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090153: Demo identity certificate is used in production mode: {0} The system is vulnerable to security attacks, since the server private key is available to the public.
-
Cause: The server is configured with Demo identity and is running in production mode.
-
Action: Configure the server to use a certificate obtained from a reputable certificate authority.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090158: The server was unable to find the private key with alias {0} at location {1} on server {2}, security realm {3}. Ensure that the keystore exists and contains the key entry under the specified alias.
-
Cause: The private key alias {0} was not found at location {1} on server {2}, security realm {3}.
-
Action: Verify that a keystore is configured on the server displayed in the log file. Verify that the keystore for the private key exists, the keystore is a valid, and contains the private key for the server. For more information, see the security documentation at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090161: A failure occurred while attempting to save LDIF for security provider {0} using file {1}.
-
Cause: An exception occurred while attempting to open a temporary file as part of the export process.
-
Action: Examine the exception and correct the cause.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090166: Failed to load identity keystore of type {2} from file {1} on server {0}
-
Cause: File is not a valid keystore file or it is of a different keystore type.
-
Action: Ensure that the keystore file specified in SSL configuration of the server is valid and of the specified keystore type.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090167: Cannot retrieve identity certificate and private key on server {0}, because the keystore entry alias is not specified.
-
Cause: The alias for the private key entry in the identity keystore was not specified.
-
Action: Correct the private key alias in the SSL configuration of the server.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090168: No identity key/certificate entry was found under alias {2} in keystore {1} on server {0}.
-
Cause: The private key entry does not exist in the specified keystore under the specified alias. The wrong alias or keystore was specified or the entry under the specified alias is not a private key.
-
Action: Ensure that the entry for the private key exists in the specified keystore under the specified alias.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090171: Loading the identity certificate and private key stored under the alias {2} from the {1} keystore file {0}.
-
Cause: The server is loading the identity certificate and the corresponding private key from the specified keystore.
-
Action: Verify that the certificate information such as keystore location, alias, and type are correct.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090172: No trusted certificates have been loaded. Server will not trust to any certificate it receives.
-
Cause: Keystores specified in the SSL configuration of the server do not contain certificates or do not exist.
-
Action: Correct the trusted CA information in the SSL configuration of the server.
Level: 1
Type: WARNING
Impact: Security
- BEA-090173: The server's trust keystore configuration (specified on the command line or in boot.properties) is incorrect.
-
Cause: Either TrustKeyStores was set to an illegal value or TrustKeyStores was set to CustomTrust but CustomTrustKeyStoreFileName was not specified.
-
Action: If specifying the server's trust keystore on the command line: To use the trusted CAs in DemoTrust.jks and in the JDK''s cacerts, specify: -Dweblogic.security.TrustKeyStore=DemoTrust defaults to DemoTrust -Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=passphrase defaults to no passphrase which means read-only access to the JDK''s cacerts. To use the trusted CAs in the JDK''s cacerts, specify: -Dweblogic.security.TrustKeyStore=JavaStandardTrust -Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=passphrase defaults to no passphrase which means read-only access to the JDK''s cacerts. To use the trusted CAs from another keystore, specify: -Dweblogic.security.TrustKeyStore=CustomTrust -Dweblogic.security.CustomTrustKeyStoreFileName=filename either an absolute pathname or a pathname relative to the directory in which the server was started. -Dweblogic.security.CustomTrustKeyStoreType=type defaults to the default keystore type specified in the JDK''s java.security file. -Dweblogic.security.CustomTrustKeyStorePassPhrase=passphrase defaults to no passphrase. Some keystore types allow this but only grant read-access (for example, JKS). Other keystore types require a keystore passphrase even for read-access. If specifying the server's trust keystore via boot.properties, set the same properties as for the command line to boot.properties but remove the weblogic.security prefix. For example, set TrustKeyStore=JavaStandardTrust.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090174: The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.
-
Cause: Either the trust keystore type does not match (for example, one specifies CustomTrust and the other specifies JavaStandardTrust) or the configuration values do not match (for example, the CustomTrustKeyStoreFileName values are not the same).
-
Action: To always specify the trusted CA keystore for the server on the command line or the boot.properties file, set the server's Keystores value in the config.xml file to CustomIdentityAndCommandLineTrust. Otherwise, ensure that the trust keystore configuration for this server in config.xml matches the trust keystore configuration specified on the command line or in boot.properties.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090176: Illegal null Subject passed as a parameter.
-
Cause: The Subject parameter cannot be null.
-
Action: Verify that the subject passed as a parameter is not null. If no subject utility methods are being called, this exception indicates an internal coding error in the server. This exception should not normally occur. Check with My Oracle Support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090186: Error: Callback {0} is not available.
-
Cause: The callback handler does not support one of callbacks required by the UsernamePasswordLoginModule. The UsernamePasswordLoginModule requires 3 callbacks: NameCallback, PasswordCallback, and URLCallback.
-
Action: Verify that the callback handler that is specified in the initialize method of UsernamePasswordLoginModule supports the three required callbacks.
Level: 1
Type: ERROR
Impact: Security
- BEA-090190: Error creating {0}
-
Cause: Either 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 the filename. Read the exception text for more information on diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090233: problem with connection filter rules
-
Cause: An exception occurred while setting the connection filter rules. The filter class may not have been loaded or some other error may have caused the exception.
-
Action: Verify the connection filter class and rules. Read the exception text for more information on diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090241: Identity Assertion type of {0} is not a configured active type.
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090242: Client principal {0} is not trusted to assert identity.
-
Cause: Client principal {0} is not in the list of clients trusted to assert identity via CSIv2 identity assertion tokens.
-
Action: Add the client principal to the Trusted Client Principals attribute of the WebLogic Identity Asserter provider or specify asterisk (*) to allow any client to assert any identity.
Level: 1
Type: ERROR
Impact: Security
- BEA-090243: user Name Mapper class not configured - cannot assert identity
-
Cause: No User Name Mapper is configured.
-
Action: Configure a User Name Mapper. Use either the default User Name Mapper or a custom User Name Mapper. To use the default implementation, set the Use Default User Name Mapper attribute for the WebLogic Identity Assertion provider. To use a custom User Name Mapper, set the User Name Mapper Class Name attribute to the name of the custom implementation.
Level: 1
Type: ERROR
Impact: Security
- BEA-090250: Cursor not found {0}
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090314: Entitlement Engine unable to connect to the embedded LDAP server {0}
-
Cause: An exception occurred when initializing the entitlement engine for the WebLogic Authorization provider.
-
Action: Read the exception text in {0} for more information on diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090357: Calling isProtectedResource before the AuthorizationManager is initialized.
-
Cause: The Authorization Manager must be initialized before any method calls.
-
Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090361: Exception: CredentialManager.initialize, Invalid or missing CredentialMapperMBean Mbean
-
Cause: The array of Credential Mapping MBeans was null or empty.
-
Action: Verify the security realm configuration and ensure that a Credential Mapping provider is configured.
Level: 1
Type: ERROR
Impact: Security
- BEA-090402: Authentication denied: Boot identity not valid. The user name or password or both from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
-
Cause: The user name or password or both from the boot identity file may have been changed since the boot identity file was created.
-
Action: Update the boot identity file with the correct username and password for the boot identity.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090404: User {0} is not permitted to start the server. The server policy may have changed in such a way that the user is no longer able to start the server. Restart the server with the administrative user account or contact the system administrator to update the server policy definitions.
-
Cause: The server policy may have changed in such a way that the user is no longer able to boot the server.
-
Action: Reboot the server from the administrative user account or contact the system administrator to update the server policy definitions.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090407: Invalid security configuration, no default security realm found.
-
Cause: A default security realm is not defined.
-
Action: Set one of the configured security realms as the default (active) security realm by setting the Default Realm attribute at the domain.
Level: 1
Type: ERROR
Impact: Security
- BEA-090413: No Realm MBean found. Bad configuration, unable to initialize Security.
-
Cause: A default security realm is not configured.
-
Action: Set one of the configured security realms as the default (active) security realm by setting the Default Realm attribute at the domain.
Level: 1
Type: ERROR
Impact: Security
- BEA-090419: Subject "{0}" is not the kernel identity.
-
Cause: The current subject is not the kernel identity.
-
Action: Verify that the subject in {0} is the correct identity. If so, this exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090420: Security provider error: providerClassName {0} creation exception.
-
Cause: An Instantiation exception or an IllegalAccess exception occurred while creating and initializing the security provider.
-
Action: Read the associated exception text for more information on diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090421: Security provider error: providerClassName {0} not found.
-
Cause: A ClassNotFound exception occurred when loading the security provider {0}.
-
Action: Ensure that the class name in {0} is present. Read the associated exception text for more information on diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090423: The Server {0} was unable to find the server certificate file {1} specified by the SSL ServerCertificateFileName attribute.
-
Cause: The server certificate file was not found.
-
Action: Verify that the Server Certificate File attribute for server is specified correctly.
Level: 1
Type: ERROR
Impact: Security
- BEA-090426: Cannot read private key from file {0}. Ensure that the password specified in environment property {1} is valid. Exception is {2}
-
Cause: A KeyManagement exception occurred when loading the private key.
-
Action: Verify that the password specified in environment property {1}. Verify the format of the private key. Read the exception text in {2} for more information in diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090434: Enumerator returned a null element for a key.
-
Cause: The invalid login information entry is null.
-
Action: Check the list of locked out users and unlock any users manually. Reboot the server if necessary. This exception indicates an internal coding error in the server. Contact Oracle support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090436: Inconsistent hashtable, key exists but not value.
-
Cause: The invalid login information entry is null.
-
Action: Check the list of locked out users and unlock any users manually. Reboot the server if necessary. This exception indicates an internal coding error in the server. Contact Oracle support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090437: Security service is unavailable.
-
Cause: The authentication service is null.
-
Action: If a security realm name is specified in the login method, verify that the name of the security realm is correct. Otherwise, this exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090439: Invalid file parameter {0} specified for adminstrator account creation.
-
Cause: Either the template file does not exist or is not a file, or the output directory does not exist or is not a directory.
-
Action: Pass in a valid template file and a valid output directory.
Level: 1
Type: ERROR
Impact: Security
- BEA-090446: Invalid base template
-
Cause: The file did not contain the appropriate templates for the user or password.
-
Action: If the Domain Configuration wizard was used, this exception indicates an internal coding error in the server. Contact My Oracle Support. If the Domain Configuration wizard is not being used, verify the contents of the specified template file.
Level: 1
Type: ERROR
Impact: Security
- BEA-090462: Illegal access on context wrapper class {0}
-
Cause: An illegal access exception occurred when getting an instance of the wrapper class.
-
Action: Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1
Type: ERROR
Impact: Security
- BEA-090463: Instantiation exception on context wrapper class {0}
-
Cause: An instantiation exception occurred when getting an instance of the wrapper class.
-
Action: Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1
Type: ERROR
Impact: Security
- BEA-090464: Problem accessing private key
-
Cause: A key management exception occurred when adding the private key and certificates to the SSL identity.
-
Action: Verify the private key. Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1
Type: ERROR
Impact: Security
- BEA-090465: Problem with certificate chain {0}
-
Cause: A certificate exception occurred when adding the private key and certificates to the SSL identity.
-
Action: Verify the certificates. Read the exception text in {0} for more information on diagnosing the problem and determining which class was not found.
Level: 1
Type: ERROR
Impact: Security
- BEA-090467: problem with connection filter
-
Cause: An exception occurred while calling the setRules method.
-
Action: Verify that the connection file class is specified correctly and present in the classpath. Verify that the setRules method is implemented correctly. Read the exception text for more information on diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090468: Set the AuditProviderClassName attribute to a valid value
-
Cause: An exception occurred while loading the class.
-
Action: Verify that the class is specified correctly and present in the classpath. Read the exception text from the log message for more information on diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090469: Invalid file format
-
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 an LDIF template file produced by an export operation.
Level: 1
Type: ERROR
Impact: Security
- BEA-090470: Inconsistent security configuration, the {0} security realm has been configured to use security data in deployment descriptors but no {1} has been configured with deployment enabled.
-
Cause: The {0} security realm has been configured to use security data in deployment descriptors but no {1} has been configured with deployment enabled.
-
Action: Either uncheck the "Ignore security data in deployment descriptors" attribute for the security realm to ignore all deployment descriptor security information or configure at least one {1} to have deployment enabled.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090475: Plaintext data for protocol {0} was received from peer {1} instead of an SSL handshake.
-
Cause: A peer is trying to send plaintext data directly instead of using SSL.
-
Action: Check the port and protocol settings on the peer that is trying to connect. It may be pointing to the SSL port by mistake or it may be specifying a plaintext protocol by mistake.
Level: 1
Type: WARNING
Impact: Security
- BEA-090476: Invalid/unknown SSL header was received from peer {0} during SSL handshake.
-
Cause: A peer is either sending invalid data, trying to connect using a newer version of SSL that is incompatible with the version of SSL used by WebLogic Server, or is trying to connect using plaintext data from a protocol for which WebLogic Server does not check.
-
Action: Check the peer that is trying to connect. It may be trying to connect using a plaintext protocol over SSL by mistake, or it may be using some newer incompatible version of SSL.
Level: 1
Type: WARNING
Impact: Security
- BEA-090477: Certificate chain received from {0} was not trusted causing SSL handshake failure.
-
Cause: A peer presented a certificate chain to the server that the server does not trust.
-
Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the server trusted CA configuration to trust the CA certificate that signed the peer certificate chain.
Level: 1
Type: WARNING
Impact: Security
- BEA-090480: SSL alert ({1}) received from {0}. Check the peer SSL configuration, or enable SSL debug tracing on the peer.
-
Cause: The peer determined something was not correct, sent an alert, and ended the SSL session.
-
Action: Check the peer to determine why it sent the alert and what alert it believes it sent. This action may require enabling SSL debug tracing to determine the exact cause.
Level: 1
Type: WARNING
Impact: Security
- BEA-090481: NO_CERTIFICATE alert was received from {0}. Verify that the SSL configuration has a proper SSL certificate chain and private key specified.
-
Cause: The SSL configuration for this server needs to supply a certificate chain.
-
Action: If using one-way SSL, verify that the certificate chain and private key are being specified for the SSL server. If using two-way SSL, verify that the certificate chain and private key are being specified for both the SSL server and the client.
Level: 1
Type: WARNING
Impact: Security
- BEA-090482: BAD_CERTIFICATE alert was received from {0}. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason for which the certificate was rejected.
-
Cause: The certificate chain sent to the peer may not be valid, or the peer may not be configured to accept the certificates.
-
Action: Check the peer configuration to see if the certificate chain was rejected because the certificate was not trusted or because there was a hostname violation. Verify that the certificate chain sent to the peer had valid dates and had the correct issuer ordering. This action may require enabling SSL debug tracing to determine the exact cause.
Level: 1
Type: WARNING
Impact: Security
- BEA-090483: CERTIFICATE_REVOKED alert was received from {0}. The certificate chain sent to the peer was rejected because it was revoked by the certificate authority.
-
Cause: A certificate in the configured certificate chain was revoked by the certificate authority and is no longer valid.
-
Action: A new certificate chain needs to be issued by the certificate authority, the SSL configuration then needs to be updated to use the new certificate chain and the new private key that corresponds to it.
Level: 1
Type: WARNING
Impact: Security
- BEA-090484: CERTIFICATE_EXPIRED alert was received from {0}. A certificate in the certificate chain expired or is not yet valid, or the peer and local machine have a date/time mismatch.
-
Cause: A certificate in the chain is either expired or is not yet valid. Another possible cause is the peer machine date/time is not set properly causing the check to fail.
-
Action: Verify the certificate validity and expiration dates in the certificate chain are correct. If they are not, obtain new certificates issued by the certificate authority and update the SSL configuration with the new certificates and private key. If the dates are valid, check the peer machine date/time setup.
Level: 1
Type: WARNING
Impact: Security
- BEA-090485: CERTIFICATE_UNKNOWN alert was received from {0}. The peer has an unspecified issue with the certificate. SSL debug tracing should be enabled on the peer to determine what the issue is.
-
Cause: The exact cause is unclear. To determine the cause, check messages from the peer to see if they explain the problem.
-
Action: Review the SSL messages from the peer by turning on SSL debug tracing.
Level: 1
Type: WARNING
Impact: Security
- BEA-090486: UNSUPPORTED_CERTIFICATE alert was received from {0}. The peer rejected a certificate in the chain because it was an unsupported type. Verify all certificates in the chain are valid X.509 RSA certificates.
-
Cause: This problem could be caused by an incorrect type of certificate in the certificate chain or the peer not being able to handle certain attributes in a valid certificate.
-
Action: The certificate chain should first be checked to ensure the certificates are all valid X.509 RSA certificates and are using the proper strength. If that is correct, SSL debug tracing may be required on the peer to see if it gives more detail on what was specifically not supported.
Level: 1
Type: WARNING
Impact: Security
- BEA-090487: UNKNOWN_CA alert received from {0}. The peer is rejecting the certificate chain as being untrusted or incomplete.
-
Cause: The peer is not configured to trust the CA that signed the certificate chain.
-
Action: Review the certificate chain and the peer trusted CA configuration to determine whether the peer should be trusting the certificate chain or whether a new certificate chain is required that is trusted by the peer.
Level: 1
Type: WARNING
Impact: Security
- BEA-090488: PROTOCOL_VERSION alert received from {0}. Check that the peer supports the same level of the SSL/TLS protocol being used (SSL V3.0 and TLS V1.0).
-
Cause: The peer may not support the same level of the SSL/TLS protocol, or there was some sort of data corruption occurring with the low-level SSL records.
-
Action: The peer needs to be checked to determine whether it supports SSL V3.0 and TLS V1.0. If it does, SSL debug tracing may be required to see if the SSL record was rejected for another reason.
Level: 1
Type: WARNING
Impact: Security
- BEA-090489: NO_RENEGOTIATION alert was received from {0}. The peer does not support renegotiation.
-
Cause: The peer does not support renegotiation and is responding to a renegotiation request with a warning to indicate it is not supported.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: Security
- BEA-090490: ACCESS_DENIED alert received from {0}. The peer recognizes the certificate chain but a higher-level access control is rejecting it.
-
Cause: The peer is likely doing an authorization check, perhaps above the SSL layer and is rejecting the connection because of an authorization check failure.
-
Action: Check the peer configuration to determine why the authorization check is failing.
Level: 1
Type: WARNING
Impact: Security
- BEA-090491: INSUFFICIENT_SECURITY alert received from {0}. The peer requires stronger ciphers to be supported.
-
Cause: The peer requires stronger ciphers than those specified in the SSL configuration of the server.
-
Action: Determine the ciphers required by the peer and update the SSL configuration. This update may not be possible if the required ciphers are stronger than allowed by the WebLogic Server license.
Level: 1
Type: WARNING
Impact: Security
- BEA-090493: BAD_RECORD_MAC alert received from {0}. The peer indicated it received a record with an invalid MAC.
-
Cause: The certificate does not match the private key or data corruption has occurred.
-
Action: Check the SSL configuration to ensure the certificate and private key match, check the network, and verify the routes between the machines.
Level: 1
Type: WARNING
Impact: Security
- BEA-090494: DECRYPTION_FAILED alert received from {0}. The peer detected errors when decrypting.
-
Cause: A cryptography error or a data corruption error.
-
Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1
Type: WARNING
Impact: Security
- BEA-090495: RECORD_OVERFLOW alert received from {0}. The peer received an invalid record with a length greater than allowed.
-
Cause: A problem in the SSL implementation or a data corruption error.
-
Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1
Type: WARNING
Impact: Security
- BEA-090496: DECOMPRESSION_FAILURE alert received from {0}. The peer was unable to decompress data.
-
Cause: WebLogic Server does not support data compression. This message likely indicates a data corruption problem.
-
Action: Check both sides of the SSL connection for any relevant error information, check the network, and verify the routes between the machines.
Level: 1
Type: WARNING
Impact: Security
- BEA-090497: HANDSHAKE_FAILURE alert received from {0}. Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings.
-
Cause: There is a mismatch in the SSL configurations.
-
Action: Check both sides of the SSL configuration for mismatches in supported ciphers, supported protocol versions, trusted CAs, and hostname verification settings. SSL Debug tracing may be needed on both sides to determine the exact cause.
Level: 1
Type: WARNING
Impact: Security
- BEA-090498: ILLEGAL_PARAMETER alert received from {0}.
-
Cause: This message is most likely caused by a data corruption error.
-
Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1
Type: WARNING
Impact: Security
- BEA-090499: DECODE_ERROR alert received from {0}.
-
Cause: This message is most likely caused by a data corruption error.
-
Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1
Type: WARNING
Impact: Security
- BEA-090500: DECRYPT_ERROR alert received from {0}. A decryption error occurred during the SSL handshake.
-
Cause: This message is most likely caused by a data corruption error.
-
Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1
Type: WARNING
Impact: Security
- BEA-090501: EXPORT_RESTRICTION alert received from {0}.
-
Cause: This message could be caused by an SSL configuration mismatch between the implementations.
-
Action: Check both sides of the SSL connection for relevant error information, check the network, and verify the routes between the machines.
Level: 1
Type: WARNING
Impact: Security
- BEA-090502: INTERNAL_ERROR alert received from {0}. Check for unrelated failures such as insufficient resources.
-
Cause: There may be failures because of an insufficient resource (memory, file descriptors, or other resource).
-
Action: Check both sides of the SSL connection for relevant error information.
Level: 1
Type: WARNING
Impact: Security
- BEA-090503: The public key from the configured server certificate and the configured server private key do not match.
-
Cause: The server SSL configuration is incorrect. Either the certificate, the private key, or both are incorrectly specified.
-
Action: Check the SSL configuration. Check that the server certificate corresponds to the server private key.
Level: 1
Type: WARNING
Impact: Security
- BEA-090504: Certificate chain received from {0} failed hostname verification check. Certificate contained {1} but check expected {2}
-
Cause: A peer presented a certificate chain to the server that did not pass the hostname verification check.
-
Action: Check that the hostname in the peer certificate matches the hostname expected by the hostname verifier.
Level: 1
Type: WARNING
Impact: Security
- BEA-090505: No certificate chain was received from {0}, hostname verification check failed.
-
Cause: The peer is most likely not configured to support a cipher that presents a certificate.
-
Action: Check the supported ciphers on the peer and ensure that it supports a cipher that provides a certificate.
Level: 1
Type: WARNING
Impact: Security
- BEA-090506: Unspecified exception occurred handling hostname verification for {0}.
-
Cause: The hostname verifier failed.
-
Action: Enable SSL debug tracing to determine the exact exception. If this is a custom hostname verifier, there may be coding problems in the implementation.
Level: 1
Type: WARNING
Impact: Security
- BEA-090508: Certificate chain received from {0} was incomplete.
-
Cause: A peer presented a certificate chain to the server that was incomplete (it did not contain a trusted CA).
-
Action: Check the peer certificate chain to determine if it should be trusted or not. If it should be trusted, then update the server trusted CA configuration to trust the CA that signed the certificate chain. If the chain was incomplete, correct the chain.
Level: 1
Type: WARNING
Impact: Security
- BEA-090509: The SSL ListenPort attribute {0} cannot be the same as the non-secure ListenPort for the server.
-
Cause: The same value was specified for the server Listen port and the SSL Listen port.
-
Action: Correct the configuration of the SSL Listen port. The value must be different that than the server Listen port.
Level: 1
Type: ERROR
Impact: Security
- BEA-090511: The following exception has occurred:
-
Cause: An error condition has occurred.
-
Action: Read the associated exception in the log or in the application to determine the problem. In general, the stack trace can be used to debug an existing problem.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090513: ServerIdentity failed validation, downgrading to anonymous.
-
Cause: Trust has not been properly established between two domains. If the domains are not configured properly, a hacker could make an attempt to guess the server identity for this domain.
-
Action: See the documentation on "Enabling Trust Between WebLogic Domains" at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090514: The server certificate chain has settings that might cause it to be rejected by peers during SSL handshaking. No action is required unless peers are rejecting the certificate chain.
-
Cause: The server certificate chain has CA certificates that have BasicConstraints settings which are either missing or set in such a way that a peer may reject it during SSL handshaking.
-
Action: No action is necessarily required. If peers have trouble handshaking, check that the BasicConstraints settings in the CA certificates in the chain are specified correctly.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090515: The certificate chain could not be completely checked for issues that could cause it to be rejected by a peer during SSL handshaking. No action is required unless peers are rejecting the certificate chain.
-
Cause: The configured certificate chain was incomplete.
-
Action: No action is necessarily required. If the entire certificate chain is to be checked, ensure that the entire certificate chain is specified in the configuration.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090518: Could not decrypt the {1} attribute value of {2} from the file {0}. If an encrypted attribute was copied from boot.properties from another domain into {0}, change the encrypted attribute to its clear text value, and then restart the server. The attribute will be encrypted again. Otherwise, change all encrypted attributes to their clear text values, then restart the server. All encryptable attributes will be encrypted again. The decryption failed with the exception {3}.
-
Cause: An invalid encrypted value was found in boot.properties.
-
Action: If an encrypted attribute was copied from boot.properties from another domain into {0}, change the encrypted attribute to its clear text value, and then restart the server. The attribute will be encrypted again. Otherwise, change all encrypted attributes to their clear text values, then restart the server. All encryptable attributes will be encrypted again.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090522: The realm {0} does not have a deployable role mapper configured. To correct the problem, configure a deployable role mapper.
-
Cause: The realm {0} does not have a deployable role mapper configured.
-
Action: To correct the problem, configure a deployable role mapper.
Level: 1
Type: WARNING
Impact: Security
- BEA-090523: None of the deployable role mappers in realm {0} have deployments enabled. To correct the problem, enable deployments in one of the deployable role mappers.
-
Cause: None of the deployable role mappers in realm {0} have deployments enabled.
-
Action: To correct the problem, enable deployments in one of the deployable role mappers.
Level: 1
Type: WARNING
Impact: Security
- BEA-090525: The realm {0} does not have a deployable authorizer configured. To correct the problem, configure a deployable authorizer.
-
Cause: The realm {0} does not have a deployable authorizer configured.
-
Action: To correct the problem, configure a deployable authorizer.
Level: 1
Type: WARNING
Impact: Security
- BEA-090526: None of the deployable authorizers in realm {0} have deployments enabled. To correct the problem, enable deployments in one of the deployable authorizers.
-
Cause: None of the deployable authorizers in realm {0} have deployments enabled.
-
Action: To correct the problem, enable deployments in one of the deployable authorizers.
Level: 1
Type: WARNING
Impact: Security
- BEA-090530: The realm {0} has more than one identity asserter configured with the token type {1} selected as an active type. To correct the problem, decide which of the identity asserters should handle this token type. Set it as an active type in that identity asserter, and unset it as an active type for all the other identity asserters.
-
Cause: The realm {0} has more than one identity asserter configured with the token type {1} selected as an active type.
-
Action: To correct the problem, decide which of the identity asserters should handle this token type. Set it as an active type in that identity asserter, and unset it as an active type for all the other identity asserters.
Level: 1
Type: WARNING
Impact: Security
- BEA-090532: The realm {0} has a realm adapter adjudicator but no realm adapter authorizer. To correct the problem, configure a realm adapter authorizer.
-
Cause: The realm {0} has a realm adapter adjudicator but no realm adapter authorizer.
-
Action: To correct the problem, configure a realm adapter authorizer.
Level: 1
Type: WARNING
Impact: Security
- BEA-090533: The realm {0} has a realm adapter adjudicator but no default authorizer. To correct the problem, configure a default authorizer.
-
Cause: The realm {0} has a realm adapter adjudicator but no default authorizer.
-
Action: To correct the problem, configure a default authorizer.
Level: 1
Type: WARNING
Impact: Security
- BEA-090534: The realm {0} has a realm adapter adjudicator but multiple default authorizers. To correct the problem, remove all the default authorizers except one.
-
Cause: The realm {0} has a realm adapter adjudicator but multiple default authorizers.
-
Action: To correct the problem, remove all the default authorizers except one.
Level: 1
Type: WARNING
Impact: Security
- BEA-090535: The realm {0} has a realm adapter adjudicator but is using an authorizer that is neither a realm adapter authorizer nor a default authorizer. To correct the problem, remove all authorizers except the realm adapter authorizer and the default authorizer.
-
Cause: The realm {0} has a realm adapter adjudicator but is using an authorizer that is neither a realm adapter authorizer nor a default authorizer.
-
Action: To correct the problem, remove all authorizers except the realm adapter authorizer and the default authorizer.
Level: 1
Type: WARNING
Impact: Security
- BEA-090536: The realm {0} has multiple realm adapter authorizers. To correct the problem, remove all the realm adapter authorizers except one.
-
Cause: The realm {0} has multiple realm adapter authorizers.
-
Action: To correct the problem, remove all the realm adapter authorizers except one.
Level: 1
Type: WARNING
Impact: Security
- BEA-090537: The realm {0} has multiple realm adapter authenticators. To correct the problem, remove all the realm adapter authenticators except one.
-
Cause: The realm {0} has multiple realm adapter authenticators.
-
Action: To correct the problem, remove all the realm adapter authenticators except one.
Level: 1
Type: WARNING
Impact: Security
- BEA-090538: The realm {0} has a realm adapter authorizer but no realm adapter authenticator. To correct the problem, configure a realm adapter authenticator.
-
Cause: The realm {0} has a realm adapter authorizer but no realm adapter authenticator.
-
Action: To correct the problem, configure a realm adapter authenticator.
Level: 1
Type: WARNING
Impact: Security
- BEA-090539: The realm {0} has keystore configured that is not a default keystore. To correct the problem, remove the non-default keystore.
-
Cause: The realm {0} has keystore configured that is not a default keystore.
-
Action: To correct the problem, remove the non-default keystore.
Level: 1
Type: WARNING
Impact: Security
- BEA-090540: The realm {0} has more than one default keystore configured for trusted CAs. To correct the problem, ensure that only one default keystore provider has its root CA keystore location configured.
-
Cause: The realm {0} has more than one default keystore configured for trusted CAs.
-
Action: To correct the problem, ensure that only one default keystore provider has its root CA keystore location configured.
Level: 1
Type: WARNING
Impact: Security
- BEA-090541: The realm {0} has more than one default keystore configured for private keys. To correct the problem, ensure that only one default keystore provider has its private key keystore location configured.
-
Cause: The realm {0} has more than one default keystore configured for private keys.
-
Action: To correct the problem, ensure that only one default keystore provider has its private key keystore location configured.
Level: 1
Type: WARNING
Impact: Security
- BEA-090542: Certificate chain received from {0} was not trusted, causing SSL handshake failure. Check the certificate chain to determine whethr or not it should be trusted. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WebLogic Server instance that is using demo certificates (the default WebLogic Server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
-
Cause: A peer presented a certificate chain to the server which the server does not trust.
-
Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
Level: 1
Type: WARNING
Impact: Security
- BEA-090543: Certificate chain received from {0} was incomplete. Check the peer certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA that signed the certificate chain. If the chain was incomplete, correct the chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
-
Cause: A peer presented a certificate chain to the server that was incomplete (it did not contain a trusted CA).
-
Action: Check the peer certificate chain to determine whether or not it should be trusted. If it should be trusted, then update the client trusted CA configuration to trust the CA that signed the certificate chain. If the chain was incomplete, correct the chain. If you are connecting to a WebLogic Server instance that is using demo certificates (the default WebLogic Server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.
Level: 1
Type: WARNING
Impact: Security
- BEA-090546: The server is configured to use custom identity and command line trust, but either demo trust or no trust was specified on the command line or in boot.properties.
-
Cause: The server's KeyStore value in config.xml is CustomIdentityAndCommandLineTrust, but, on the command line to boot the server or in boot.properties, either no trust or DemoTrust was specified.
-
Action: To correct the problem, either specify -Dweblogic.security.TrustKeyStore=JavaStandardTrust or -Dweblogic.security.TrustKeyStore=CustomTrust and -Dweblogic.security.CustomTrustKeyStoreFileName on the command line when booting the server (or specify TrustKeyStore=JavaStandardTrust or TrustKeyStore=CustomTrust and CustomTrustKeyStoreFileName in boot.properties).
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090547: The certificate chain received from {0} contained a V3 CA certificate which had basic constraints that were not marked critical. This is being rejected due to the strict enforcement of basic constraints.
-
Cause: Strict basic constraints checking was explicitly enabled, and a certificate chain received by the peer contained a CA that failed due to the strict check but would have passed the strong check.
-
Action: If strict compliance of RFC 2459 for basic constraints is really required, then the peer certificate chain was correctly rejected and needs to be corrected. If strict compliance is not really required, consider setting the constraints checking back to the default value of strong to accept the certificate chain.
Level: 1
Type: WARNING
Impact: Security
- BEA-090548: The certificate chain received from {0} contained a V3 CA certificate that was missing the basic constraints extension
-
Cause: The certificate chain received by the peer contained a V3 CA certificate that does not contain a basic constraints extension indicating that it really is a CA. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.
-
Action: The peer certificate chain needs to be looked at carefully to determine which CA was missing the basic constraints extension. 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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090549: The certificate chain received from {0} contained a V3 CA certificate that did not indicate it really is a CA.
-
Cause: The certificate chain received by the peer contained a V3 CA certificate that contained a basic constraints extension which was not marked as being a CA. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.
-
Action: The peer certificate chain needs to be looked at carefully to determine which CA 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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090550: The certificate chain received from {0} contained a V3 CA certificate that indicated a certificate chain path length in the basic constraints that was exceeded.
-
Cause: The certificate chain received by the peer contained a V3 CA certificate that specified a path length in the basic constraints that was exceeded. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.
-
Action: The peer certificate chain needs to be looked at carefully to determine which CA indicated the path length limit that was exceeded. The path length, if specified, limits how many CA certificates are allowed to follow a CA certificate in a certificate chain. A path length of 0 indicates only an end entity certificate may follow it in the chain, positive values indicate how many CA certificates may be in the chain between that CA and the end entity certificate. 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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090551: The certificate chain received from {0} contained a V3 CA certificate that could not be converted to be checked for basic constraints.
-
Cause: The certificate chain received by the peer contained a V3 CA certificate that could not be converted to a format which allows the basic constraints to be checked. This is rejected by the basic constraints checking for strong and strict, which protects against a specific certificate chain attack on SSL.
-
Action: The peer certificate chain needs to be looked at carefully to confirm they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact Oracle support. If the certificate can not be processed, you can disable the basic constraints checking as a workaround to allow the certificate chain to be accepted and allows this vulnerability to be exploited
Level: 1
Type: WARNING
Impact: Security
- BEA-090552: The public and private key could not be checked for consistency.
-
Cause: The failure could be due to a keystore being used to hold the private key that does not allow access to private key material. Hardware keystores generally do not give access to the private key material that is needed to perform this operation.
-
Action: If a keystore is being used the warning should be ignored. If handshaking errors occurs with all clients, check that the private key and public key match.
Level: 1
Type: WARNING
Impact: Security
- BEA-090554: Set the RealmClassName attribute of the BasicRealm {0} used by the CachingRealm to a valid value.
-
Cause: The RealmClassName attribute was not properly configured.
-
Action: Verify that the class is specified correctly and is present in the classpath. Read the exception text from the log message for more information on diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090560: Could not load the {0} class named {1}. The exception was {3}. The class was specified via the {2} system property value.
-
Cause: Could not load the {0} class named {1}.
-
Action: Ensure that the {2} system property is set to the proper {0} class. Also ensure that the class is in the classpath.
Level: 1
Type: ERROR
Impact: Security
- BEA-090561: Could not instantiate a {0} of class {1}. The exception received is {3}. The class was specified via the {2} system property value.
-
Cause: Could not instantiate a {0} of class {1}.
-
Action: Ensure that the {2} system property is set to the proper {0} class. Also ensure that the class is a correct {0} implementation.
Level: 1
Type: ERROR
Impact: Security
- BEA-090562: Could not create a {0} of class {1} because it is not assignable as a {2}. The class was specified via the {3} system property value.
-
Cause: Could not create a {0} of class {1} because it is not assignable as a {2}.
-
Action: Ensure that the {3} system property is set to the proper {0} class. Also ensure that the class is a correct {0} implementation.
Level: 1
Type: ERROR
Impact: Security
- BEA-090563: Cannot create instance of Hostname Verifier {0}.
-
Cause: The class {0} was not found, does not have a public constructor without arguments, or has thrown an exception in its constructor.
-
Action: Ensure that the {0} class is in the class path, and has a public constructor without arguments.
Level: 1
Type: ERROR
Impact: Security
- BEA-090564: Specified HostnameVerifier class {0} is invalid. It does not implement weblogic.security.SSL.HostnameVerifier interface.
-
Cause: An invalid HostnameVerifier class specified.
-
Action: Specify a different HostnameVerifier class, or ensure that the {0} class implements weblogic.security.SSL.HostnameVerifier interface.
Level: 1
Type: ERROR
Impact: Security
- BEA-090566: The certificate chain received from {0} contained a V3 certificate with unrecognized critical extension: {1}.
-
Cause: The certificate cannot be validated because it contains an unrecognized critical extension.
-
Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1
Type: WARNING
Impact: Security
- BEA-090567: The certificate chain received from {0} contained a V3 certificate for which key usage constraints forbid its key use by the key agreement algorithm.
-
Cause: Certificate key usage constraints forbid certificate key use in a quality required by the key agreement algorithm.
-
Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1
Type: WARNING
Impact: Security
- BEA-090568: Cannot check key usage constraints of certificate received from {0} because of the failure to determine the key agreement algorithm.
-
Cause: A NoSuchAlgorithmException occurred while trying to obtain the key agreement algorithm.
-
Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1
Type: WARNING
Impact: Security
- BEA-090569: The certificate chain received from {0} contained a V3 CA certificate for which key usage constraints indicate its key cannot be used to sign certificates.
-
Cause: One of certificate in the check cannot pass validation check because its key is used to sign another certificate while key usage constraints indicate that it cannot be used for that.
-
Action: The peer certificate chain needs to be looked at carefully to confirm that they are valid. If the certificates are all valid, this indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1
Type: WARNING
Impact: Security
- BEA-090570: {0} has been specified without enabling the SecurityManager.
-
Cause: The server has been told to boot with a JACC property enabled without also enabling a SecurityManager by setting the java.security.manager property. JACC depends on a SecurityManager being in place.
-
Action: If JACC is desired, then a SecurityManager must be enabled. This can be done by specifying a value for the java.security.manager property. If JACC is not desired then remove the specification of the JACC property.
Level: 1
Type: ERROR
Impact: Security
- BEA-090572: The javax.security.jacc.policy.provider property points to a non-existant {0} class.
-
Cause: JACC has been enabled by setting the javax.security.jacc.policy.provider property but the class it points to cannot be found.
-
Action: Ensure that the class is present or change javax.security.jacc.policy.provider property to point to an existing class.
Level: 1
Type: ERROR
Impact: Security
- BEA-090575: The {0} class is not an instance of java.security.Policy.
-
Cause: An non-Policy object was passed as the value of the javax.security.jacc.policy.provider property.
-
Action: Change javax.security.jacc.policy.provider to point to an instance of a java.security.Policy object.
Level: 1
Type: ERROR
Impact: Security
- BEA-090576: A PolicyConfigurationFactory could not be obtained successfully.
-
Cause: The javax.security.jacc.PolicyConfigurationFactory.provider property may not be set to a valid implementation of PolicyConfigurationFactory.
-
Action: Change javax.security.jacc.PolicyConfigurationFactory.provider to point to an instance of a javax.security.jacc.PolicyConfigurationFactory object.
Level: 1
Type: ERROR
Impact: Security
- BEA-090579: The javax.security.jacc.PolicyConfigurationFactory.provider property points to a non-existant class {0}.
-
Cause: JACC has been enabled by setting javax.security.jacc.PolicyConfigurationFactory.provider property but the class it points to cannot be found.
-
Action: Ensure that the class is present or change javax.security.jacc.PolicyConfigurationFactory.provider property to point to an existing class.
Level: 1
Type: ERROR
Impact: Security
- BEA-090590: The WLSJDKCertPathValidator was passed an illegal CertPathParameters.
-
Cause: The CertPathParameters must be a weblogic.security.pk.CertPathValidatorParameters.
-
Action: Pass a weblogic.security.pk.CertPathValidatorParameters as the CertPathParameters.
Level: 1
Type: ERROR
Impact: Security
- BEA-090591: The realm {0} does not have any Certification Path providers configured. To correct the problem, configure at least one Certification Path provider.
-
Cause: The realm {0} does not have any Certification Path providers configured.
-
Action: To correct the problem, configure at least one Certification Path provider.
Level: 1
Type: WARNING
Impact: Security
- BEA-090592: The realm {0} does not have a Certification Path builder configured. To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.
-
Cause: The realm {0} does not have a Certification Path builder configured.
-
Action: To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.
Level: 1
Type: WARNING
Impact: Security
- BEA-090593: The realm {0} has an illegal Certification Path builder configured. To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.
-
Cause: The realm {0} has an illegal Certification Path builder configured.
-
Action: To correct the problem, select one of the realm"s Certification Path providers as the realm"s Certification Path builder.
Level: 1
Type: WARNING
Impact: Security
- BEA-090598: Unable to update the domain controller list
-
Cause: The most likely cause is that the attempt to lock the domain controller list for update timed out. This may happen if there are concurrent updates occurring to the configuration for the same provider instance, and the updates are taking a while to execute (perhaps a long domain controller list or slow network).
-
Action: If this is an update from the Administration Console, and the domain controller list was modified, apply the changes again.
Level: 1
Type: WARNING
Impact: Security
- BEA-090599: Unable to initialize the domain controller list
-
Cause: The domain controller list was not able to be locked for initialization. This should not occur and was likely caused by an internal coding error.
-
Action: This indicates an internal coding error or limitation in the server. Contact My Oracle Support.
Level: 1
Type: WARNING
Impact: Security
- BEA-090600: Failed to retrieve the local machine name.
-
Cause: There may be a configuration error with either the user account rights required or the local NT machine.
-
Action: Verify that the user running the server has the specific NT account rights that are required to use the NT authentication provider.
Level: 1
Type: ERROR
Impact: Security
- BEA-090601: Cannot access domain controller {0}.
-
Cause: The domain controller name may not be valid, may be down or unavailable on the network, or the user may not have permission to access it.
-
Action: If the domain controller is simply down, or temporarily unavailable, it may be retried later on depending on the domain controller retry settings. If the domain controller is available, check that the user account running the server has permission to access the domain controller. This may require logging into the domain controller that failed and verifying the user has been granted access.
Level: 1
Type: WARNING
Impact: Security
- BEA-090602: The java and native library versions do not match for the WindowsNTAuthenticator.
-
Cause: The native library being found and loaded is not in synch with the java portion of the provider.
-
Action: Verify the correct native library for the WindowsNTAuthenticator is in the PATH and that the correct PATH is being used.
Level: 1
Type: ERROR
Impact: Security
- BEA-090615: A CertPathBuilderParameters or CertPathValidatorParameters object was constructed with a list of trusted CAs that includes a null trusted CA.
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090625: Policy context {0} not in open state.
-
Cause: Policy context must be in open state.
-
Action: Ensure that the policy context is open before attempting an operation on it that requires an open Policy Context. This indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090628: Cannot have circular policy configuration links.
-
Cause: A PolicyConfiguration is linked to another PolicyConfiguration which ultimately is linked back to the original PolicyConfiguration. This means that no PolicyConfiguration actually holds the role to principal mapping.
-
Action: This indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090629: Received a {0} when attempting to use the passed role to principal map for PolicyConfiguration with a ContextID of {1}.
-
Cause: Received a {0} when attempting to use the passed role to principal map for PolicyConfiguration with a ContextID of {1}. The code attempts to do some simple validation the map.
-
Action: This exception indicates an internal coding error in the server. Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090633: Cannot open policy file {0}. Received exception {1}.
-
Cause: If the exception is a FileNotFoundException, the file path name may be too long for the operating system, or the directory may have been deleted before the policy file was written to it.
-
Action: Try to shorten the file path name if it is too long for the operating system. The error may also occur if the directory has been deleted before the file was written to it.
Level: 1
Type: ERROR
Impact: Security
- BEA-090660: Certificate chain received from {0} was not validated by the custom trust manager {1} causing SSL handshake failure.
-
Cause: A peer presented a certificate chain to the server that the custom trust manager did not validate.
-
Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the custom trust manager to trust the peer certificate chain.
Level: 1
Type: WARNING
Impact: Security
- BEA-090661: Certificate chain received from {0} was not validated by the custom trust manager {1} causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the custom trust manager to trust the certificate chain.
-
Cause: A peer presented a certificate chain to the server that the custom trust manager did not validate.
-
Action: Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the custom trust manager to trust the certificate chain.
Level: 1
Type: WARNING
Impact: Security
- BEA-090662: The DeployableAuthorizer "{0}" implements the deprecated {1} interface.
-
Cause: At security provider initialization, a deprecated security interface was detected.
-
Action: No immediate action is required. However, the security provider should be updated.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090663: The DeployableRoleMapper "{0}" implements the deprecated {1} interface.
-
Cause: At security provider initialization a deprecated security interface was detected.
-
Action: No immediate action is required. However, the security provider should be updated.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090668: Ignored deployment of role "{0}" for resource "{1}".
-
Cause: The application has been configured to ignore security data from deployment descriptors.
-
Action: Remove role mapping from the application deployment descriptor or change the security configuration to allow deployment of role mappings.
Level: 1
Type: WARNING
Impact: Security
- BEA-090669: Ignored deployment of policy for resource "{0}".
-
Cause: The application has been configured to ignore security data from deployment descriptors.
-
Action: Remove security policy from the application deployment descriptor or change the security configuration to allow deployment of security policy.
Level: 1
Type: WARNING
Impact: Security
- BEA-090670: Unable to verify user name token for user {0}
-
Cause: The UsernameToken could not be verified.
-
Action: Verify that the user exists in the WebLogic authentication provider, that the authentication provider has the PasswordDigestEnabled attribute set to true, and that the user entry has set the password since the attribute was set to true.
Level: 1
Type: ERROR
Impact: Security
- BEA-090672: Identity assertion object for token type {0} was of type {1} instead of expected type of {2}.
-
Cause: The token object was not an instance of the correct type.
-
Action: If called from an application via the identity assertion public API, then modify the application to pass the expected token. If called from the container, then the container should not be passing a token that is not a UsernameToken, and this exception indicates an internal coding error in the server; contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Security
- BEA-090673: Digest data source {0} was not found. Disabling digest authentication.
-
Cause: The configured data source does not exist.
-
Action: Modify the DigestDataSourceName attribute on the WebLogic Identity Assertion provider to be the name of a valid WebLogic data source configured for this domain.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090674: Digest data source {0} was not initialized due to an exception. Disabling digest authentication. The exception text is {1}.
-
Cause: An exception was thrown when initializing the configured data source.
-
Action: Verify that the DigestDataSourceName attribute on the WebLogic Identity Assertion provider is valid and a WebLogic data source configured for this domain. Read the exception text for more information on diagnosing the problem.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090675: An SQL connection could not be obtained from a digest data source {0} due to an exception. Disabling digest authentication. The exception text is {1}.
-
Cause: An exception was thrown when obtaining a connection from the configured data source.
-
Action: Read the exception text for more information on diagnosing the problem.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090676: The SQL statement {0} could not be prepared due to an exception. Disabling digest authentication. The exception text is {1}.
-
Cause: An exception occurred when preparing the SQL statement.
-
Action: Read the exception text for more information on diagnosing the problem.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090677: The {0} table could not be created due to an exception. Disabling digest authentication. The exception text is {1}.
-
Cause: An exception occurred when validating or creating the table.
-
Action: Read the exception text for more information on diagnosing the problem.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090678: Authentication failed with digest {0} due to an exception that occurred while detecting the replay attack. The exception text is {1}.
-
Cause: An exception occurred when inserting the digest information row into the database.
-
Action: Read the exception text for more information on diagnosing the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090679: Authentication failed due to detection of a replay attack for nonce {0} and digest {1}.
-
Cause: An entry for this nonce and digest has already been used for authentication in this domain.
-
Action: Ensure that the client is not performing a replay attack. Investigate the client performing the digest authentication and check that it is using unique nonce, digest, and created values.
Level: 1
Type: ERROR
Impact: Security
- BEA-090680: Unable to verify the digest authentication for user {0} since the created time is not within the expiration time period.
-
Cause: The created timestamp of the digest authentication is not within the expiration time period.
-
Action: Increase the expiration time for the identity assertion provider or synchronize the system clocks on the client and server machines.
Level: 1
Type: ERROR
Impact: Security
- BEA-090681: Digest authentication for user {0} has been disabled due to a previous fatal error in initializing replay detection
-
Cause: A previous fatal error disabled digest authentication. Therefore, digest authentication for this user has failed.
-
Action: Look in the log, identity the previous error, and correct the problem.
Level: 1
Type: ERROR
Impact: Security
- BEA-090700: There is a problem with the class {0} pointed to by the weblogic.security.jacc.RoleMapperFactory.provider property.
-
Cause: JACC Was enabled by setting weblogic.security.jacc.RoleMapperFactory.provider property but there are problems instantiating the class.
-
Action: Ensure that the class is present or change weblogic.security.jacc.RoleMapperFactory.provider property to a class that can be instantiated.
Level: 1
Type: ERROR
Impact: Security
- BEA-090701: Unable to successfully obtain a RoleMapperFactory.
-
Cause: The weblogic.security.jacc.RoleMapperFactory.provider property may not be set to a valid implementation of RoleMapperFactory.
-
Action: Change weblogic.security.jacc.RoleMapperFactory.provider to point to an instance of a weblogic.security.jacc.RoleMapperFactory object.
Level: 1
Type: ERROR
Impact: Security
- BEA-090705: The PolicyConfigurationFactory, Policy, RoleMapperFactory class names are not specified or not compatible with each other.
-
Cause: Incompatible class names have been specified. Generally this is caused by specifying but not specifying all three or by specifying class names that are not designed to work with each other.
-
Action: Check the documentation and make sure that compatible class names are set for the three system properties.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090714: The certificate chain from the peer could not be validated. Chain : {0}. Reason : {1}.
-
Cause: Either the certificate chain from the peer should not be allowed to access the server or the server or one of the configured CertPathProviders is not properly configured to trust the peer.
-
Action: If the server is not supposed to trust the peer, inform the peer that it should use a different certificate chain. If the server should trust the peer, then either a configured CertPathProvider is improperly configured to not trust the peer, or the server is improperly configured to use the configured CertPathProviders for perform extra validation of SSL peer certificate chains. Check the server SSL configuration and the configured CertPathProvider configurations.
Level: 1
Type: WARNING
Impact: Security
- BEA-090720: The Managed Server could not start because the NodeManager's encryption service data was not found.
-
Cause: The Managed Server could not start because the NodeManager's NodeManagerProperties file was not found. The NodeManager's encryption service could not be instantiated.
-
Action: Verify the existence and location of the NodeManager's NodeManagerProperties file.
Level: 1
Type: ERROR
Impact: Security
- BEA-090721: The Managed Server could not start because it could not read the NodeManager's encryption service data.
-
Cause: The Managed Server could not start because it could not read the NodeManager's encryption service data.
-
Action: Verify the existence and location of the NodeManager's NodeManagerProperties file. Check that the read permissions are correct.
Level: 1
Type: ERROR
Impact: Security
- BEA-090724: Challenge identity assertion has not completed, subject is not available yet.
-
Cause: The method to get the subject was called before the identity assertion completed.
-
Action: Call the hasChallengeIdentityCompleted method before calling the method to get the subject.
Level: 1
Type: ERROR
Impact: Security
- BEA-090725: Challenge identity assertion has completed, challenge token is not available.
-
Cause: The method to get the challenge token was called after the identity assertion completed.
-
Action: Call the hasChallengeIdentityCompleted method before calling the method to get the challenge token.
Level: 1
Type: ERROR
Impact: Security
- BEA-090772: The security realm {0} does not support application versioning. Unable to deploy the application {1}.
-
Cause: The security realm {0} as configured does not support application versioning, and thus the deployment of the application version failed.
-
Action: Deploy the application using a security realm that supports application versioning.
Level: 1
Type: ERROR
Impact: Security
- BEA-090773: Failure in creating security application version information for the application {0}.
-
Cause: An attempt to create security version information for application {0} failed.
-
Action: Check the server log for additional security error messages, correct security errors, and try again.
Level: 1
Type: ERROR
Impact: Security
- BEA-090774: This method requires an encrypted argument but the argument passed to it was in clear text.
-
Cause: This method was called with a clear-text argument but requires an encrypted argument.
-
Action: To call this method programattically, call the non-encrypted set() method on the MBean. This will automatically encrypt the argument.
Level: 1
Type: ERROR
Impact: Security
- BEA-090779: Identity {0} failed validation, downgrading to anonymous.
-
Cause: Trust has not been properly established between two domains. If the domains are not configured properly, a hacker could make an attempt to guess the server identity for this domain.
-
Action: See the documentation on "Enabling Trust Between WebLogic Domains" at http://www.oracle.com/technology/products/weblogic/index.html.
Level: 1
Type: ERROR
Impact: Security
- BEA-090780: The values specified by -Dweblogic.security.URLResourceCaseMapping({0}) and WebAppFilesCaseInsensitive Attribute on SecurityConfiguraitonMBean({1}) do not match.
-
Cause: The value of the property -Dweblogic.security.URLResourceCaseMapping is different from the value for WebAppFilesCaseInsensitive attribute of the SecurityConfiguraitonMBean.
-
Action: Correct -Dweblogic.security.URLResourceCaseMapping to start the server.
Level: 1
Type: ERROR
Impact: Security
- BEA-090782: Server is running in production mode, and the Native Library (terminalio) to read the password securely from the command line was not found.
-
Cause: Server could not start because it didn't find the Native Library in the PATH to read the password securely from command line.
-
Action: Verify that the terminalio library exists in the path. You can set this by setting -Djava.library.path to the directory where this library exists, you can use boot.properties to store the password, or you can use -Dweblogic.management.allowPasswordEcho=true to enter the password in echo mode.
Level: 1
Type: ERROR
Impact: Security
- BEA-090783: Server is running in development mode and the Native Library (terminalio) to read the password securely from the command line wes not found.
-
Cause: Either the server could not start because it did not find the Native Library in the PATH to read the password securely from command line or -Dweblogic.management.allowPasswordEcho=false is set.
-
Action: Verify that the terminalio library exists in the path. You can set this by setting -Djava.library.path to the directory where this library exists, you can use boot.properties to store the password, or you can use -Dweblogic.management.allowPasswordEcho=true to enter the password in echo mode.
Level: 1
Type: ERROR
Impact: Security
- BEA-090788: Problem with data source or connection pool configuration, verify that data source name {0} is correct and pool configurations are correct.
-
Cause: A configuration setting that required a data source name was likely incorrect, or the pool settings associated with it are incorrect.
-
Action: Check configuration settings to ensure that the data source name is correct and the associated pool configuration settings are correct.
Level: 1
Type: ERROR
Impact: Security
- BEA-090812: Could not create a {0} keystore instance for provider {1}. Exception: {2}
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090817: These configuration changes cannot be activated because a default realm is not configured for the domain.
-
Cause: The quot;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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090818: These configuration changes cannot be activated because the domain does not have a properly configured default realm.
-
Cause: The "DefaultRealm" 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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090823: Could not register the WebLogic Server X509CertificateFactory as the default X509CertificateFactory for this JVM.
-
Cause: The WebLogic Server X509CertificateFactory could not be registered as the default X509CertificateFactory for this JVM.
-
Action: The WebLogic Server X509CertificateFactory orders the certificates in a CertPath that was created from PKCS7. Specify -Dweblogic.security.RegisterX509CertificateFactory=false on the command line for booting this server to indicate that WebLogic Server should not register the WebLogic Server X509CertificateFactory as the default X509CertificateFactory when the server boots (since your JDK does not support this). Also, since the WebLogic Server X509CertificateFactory cannot be registered with the JDK as the default X509CertificateFactory, the JDK will use its current default X509CertificateFactory. The default one (for example, the SUN implementation) may not properly convert PKCS7 to an ordered CertPath.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090827: LDIF template file {1} was empty. The WebLogic provider {0} has been bootstrapped but has not been initialized with any LDIF data.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090838: The required WebLogic JACC RoleMapperFactory was not specified. Please specify the factory class using the weblogic.security.jacc.RoleMapperFactory.provider system property.
-
Cause: A WebLogic JACC RoleMapperFactory class is required.
-
Action: Check the documentation and ensure that the WebLogic JACC RoleMapperFactory system property is set properly.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-090859: The realm {0} does not have a certification path validator configured. To correct the problem, configure a cert path provider that supports cert path validation.
-
Cause: The realm {0} does not have a certification path validator configured.
-
Action: To correct the problem, configure a certification path provider that supports certification path validation.
Level: 1
Type: WARNING
Impact: Security
- BEA-090861: Certificate policies extension processing failed. PolicyId: {0} does not exist in the allowed list.
-
Cause: Certificate policies extension processing failed. PolicyId: {0} does not exist in the allowed list.
-
Action: Add the Policyid to the Allowed Policyids list.
Level: 1
Type: ERROR
Impact: Security
- BEA-090862: Certificate policies extension processing failed. PolicyQualifierID: {0} is not CPS.
-
Cause: Certificate policies extension processing failed. PolicyQualifierID: {0} is not CPS.
-
Action: Check the Certificate Presented, as certificates containing a PolicyQualifierID other than CPS are not supported.
Level: 1
Type: ERROR
Impact: Security
- BEA-090865: The realm {0} is not configured to handle MBean authorization. To correct the problem, configure an authorization provider that supports MBean authorization.
-
Cause: The realm {0} is not configured to handle MBean authorization.
-
Action: To correct the problem, configure an authorization provider that supports MBean authorization.
Level: 1
Type: WARNING
Impact: Security
- BEA-090866: The deployment of an unchecked policy for the resource "{0}" has been ignored. Unchecked policy is the default policy for URL and EJB resources. An unchecked policy can result if a deployment descriptor specifies a transport guarantee without the use of an authorization constraint.
-
Cause: The application has been configured to ignore security data from deployment descriptors.
-
Action: When the deployment descriptor specifies a transport guarantee without the use of an authorization constraint, no action is needed. Otherwise, remove the security policy from the application deployment descriptor or change the security configuration to allow deployment of security policy.
Level: 1
Type: WARNING
Impact: Security
- BEA-090868: The realm {0} has an invalid SAML configuration. To correct the problem, ensure that there is only one of each SAML provider type and that the version of the SAML providers are the same.
-
Cause: The realm {0} has an invalid set of SAML providers.
-
Action: To correct the problem, ensure that there is only one of each SAML provider type and that the version of the SAML providers are the same.
Level: 1
Type: WARNING
Impact: Security
- BEA-090880: Could not load JAAS configuration file for JVM.
-
Cause: A class similar to com.sun/ibm.security.auth.login.ConfigFile was not located in the classpath.
-
Action: Ensure that com.sun.security.auth.login.ConfigFile/com.ibm.security.auth.login.ConfigFile is available as part of the classpath or that -Dweblogic.security.authentication.Configuration=class name is passed as a startup system property and is available as part of the classpath.
Level: 1
Type: WARNING
Impact: Security
- BEA-090882: SSL has established a session that uses a Null cipher.
-
Cause: The connecting SSL client presented a ciphersuite list to the server that contains only ciphersuites with null ciphers. This may or may not be a problem, depending on your domain configuration.
-
Action: Verify that the client's security providers are configured correctly, or disable the use of Null ciphers on the server.
Level: 1
Type: WARNING
Impact: Security
- BEA-090888: The SSL client running within the server does not have a certificate. It will use the server's certificate.
-
Cause: The SSL client running within the server does not have a certificate, but client certificates are required.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090889: The SSL client running within the server could not obtain the server's certificate.
-
Cause: An exception occurred when the SSL client running within the server tried to obtain the server's certificate.
-
Action: Check that the server's SSL configuration is correct, and that the server has a certificate and private key configured.
Level: 1
Type: WARNING
Impact: Security
- BEA-090890: The loading of the OPSS java security policy provider class {0} failed due to a problem in creating the OPSS java security policy provider instance {0}. Illegal access to the constructor of the class.
-
Cause: The loading of the OPSS java security policy provider class {0} failed due to an IllegalAccessException.
-
Action: Ensure that the correct version of the OPSS java security policy provider {0} is used.
Level: 1
Type: ERROR
Impact: Security
- BEA-090891: The loading of the OPSS java security policy provider failed due to a problem in instantiating the OPSS java security policy provider. An InstantiationException was received when creating an instance.
-
Cause: The loading of the OPSS java security policy provider class {0} failed due to InstantiationExceptions.
-
Action: Ensure that the correct version of the OPSS java security policy provider {0} is used.
Level: 1
Type: ERROR
Impact: Security
- BEA-090892: The loading of an OPSS java security policy provider failed due to an exception. See the exception stack trace or the server log file for the root cause. If there is no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: {1}
-
Cause: The loading of the OPSS java security policy provider class {0} failed due to an exception: {1}.
-
Action: Check the stack trace or server log file for the root cause of the exception, check for a possible configuration error, or enable the debug flag -Djava.security.debug=jpspolicy to get more information.
Level: 1
Type: ERROR
Impact: Security
- BEA-090893: The loading of the OPSS java security policy provider stopped due to a conflict with the JACC Policy provider. Only one security policy provider can be enabled.
-
Cause: The loading of the OPSS java security policy provider stopped due to a conflict with the JACC Policy provider. Only one security policy provider can be enabled.
-
Action: If enabling the OPSS java security policy provider {0}, please do not enable the JACC setting.
Level: 1
Type: ERROR
Impact: Security
- BEA-090895: OPSS Java Security Policy Provider {0} has already been loaded statically, programmatical loading has been skipped.
-
Cause: OPSS Java Security Policy Provider {0} has already been loaded statically, programmatical loading has been skipped.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: Security
- BEA-090896: The SSL ListenPort attribute {0} cannot be the same as the Administration Port for the server.
-
Cause: The same value was specified for the Administration Port and the SSL Listen port.
-
Action: Correct the configuration of the SSL Listen port or the Administration port. The SSL Listen port value must be different that than the Administration port.
Level: 1
Type: ERROR
Impact: Security
- BEA-090898: Ignoring the trusted CA certificate "{0}". Loading of the trusted certificate list raised a certificate parsing exception {1}.
-
Cause: It is possible that the CA to be added used a signature algorithm that is not supported by the SSL stack.
-
Action: The server has a long list of trusted CAs, and the one that caused the exception in the server is ignored.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090902: The certificate chain received from {0} contained a V1 certificate which cannot be a CA.
-
Cause: The certificate chain received by the peer contained a V1 certificate which cannot be a CA. This was 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, look at updating the peer certificate chain with valid CA certificates. If this is not possible, disable the basic constraints checking to allow the certificate chain to be accepted and to allow this vulnerability to be exploited.
Level: 1
Type: WARNING
Impact: Security
- BEA-090903: The JPS or JRF JAR is present in the classpath, but the jps-config.xml file was not supplied in the command line: the required system property "{0}" has not been defined.
-
Cause: System parameter "oracle.security.jps.config" is not supplied in the command line, but a JPS or JRF JAR is present in the classpath.
-
Action: If this is not a JRF domain, remove the JPS or JRF JAR from the classpath; otherwise, and add the system parameter "oracle.security.jps.config" in the command line to supply the path to the jps-config.xml file.
Level: 1
Type: WARNING
Impact: Security
- BEA-090904: The JPS or JRF JAR is present in the classpath, but no system property was supplied for "{0}" and "{1}". The server will start without setting the OPSS java policy provider.
-
Cause: System parameters "oracle.security.jps.config" and "oracle.domain.config.dir" are not supplied in the command line, but jps-internal.jar or jrf.jar is present in the classpath.
-
Action: If this is not a JRF domain, removed the jps-internal.jar and jrf.jar from the classpath. Otherwise, add the required system parameters for the JRF domain.
Level: 1
Type: WARNING
Impact: Security
- BEA-090905: Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -D{0}=true.
-
Cause: The CryptoJ JCE Provider self-integrity check incurs some performance penalty at server startup.
-
Action: No action is requirecx.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-090913: Unknown revocation status not causing failure for certificate with subject: {0}
-
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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090915: Nonce was ignored by the OCSP responder, forcing certificate revocation status to be ignored and considered unknown: {0}.
-
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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090916: Unknown revocation status causing failure for certificate with subject: {0}.
-
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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090917: Revoked certificate causing validation failure, certificate with subject: {0}.
-
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.
Level: 1
Type: WARNING
Impact: Security
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090921: JSSE has not been selected by system property {0}, however Certicom SSL is not available, so JSSE is being used for SSL.
-
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.
Level: 1
Type: WARNING
Impact: Security
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Security
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090924: JSSE has been selected by default, since the SSLMBean is not available.
-
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.
Level: 1
Type: WARNING
Impact: Security
- BEA-090926: Illegal key store source value [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090927: Illegal or unknown key store type value [keyStoreType="{0}", source="{1}"]
-
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".
Level: 1
Type: ERROR
Impact: Security
- BEA-090928: Unable to instantiate key store [keyStoreType="{0}", provider="{1}", exception="{2}", message="{3}"]
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-090929: Unable to load key store [keyStoreType="{0}", source="{1}", exception="{2}", message="{3}"]
-
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.
Level: 1
Type: ERROR
Impact: Security
- BEA-099000: Invalid property value: {0}={1}
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-099001: Caught exception while evaluating policy expression: {0} associated with: {1}
-
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.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-099002: An invalid predicate {0} was retrieved from the database. Ensure that the predicate class is in the server classpath.
-
Cause: The class file belonging to the condition was not in the server classpath.
-
Action: Update the classpath and restart the server.
Level: 1
Type: INTERNAL_ERROR
Impact: Security
- BEA-099003: Evaluation of policy associated with role {0} failed because the policy expression contains unregistered predicate: {1}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-099004: Evaluation of policy associated with resource {0} failed because the policy expression contains unregistered predicate: {1}.
-
Cause: The redicate 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.
Level: 1
Type: NOTIFICATION
Impact: Security
- BEA-100013: {0} not invalidated. The session that was serialized into the file system does not exist.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP Session
- BEA-100015: Deleted file-based session persistent store file: {0}.
-
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)
Level: 1
Type: NOTIFICATION
Impact: HTTP Session
- BEA-100016: Session expiration check failed for: {0}. Invalidating the session expiration check.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100019: The file-based persistent session ID: "{0}" was stored in file: "{1}". File exists: {2}.
-
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).
Level: 1
Type: NOTIFICATION
Impact: HTTP Session
- BEA-100028: The session data could not be deserialized.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100030: HTTP session expired. Session ID: {0}
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP Session
- BEA-100033: The license for replicated sessions is invalid: {0}. Downgrading sessions to memory, which are not replicated.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100035: The timer invalidated session ID: {0}, Web application: {1}, because it expired.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP Session
- BEA-100038: Unknown persistent type: {0} for Web application: {1}. Valid types are: memory, file, replicated, JDBC, cookie, and replicated_if_clustered.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100039: Replicated HTTP sessions were specified for the Web application: {0}, but clustering was not enabled.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100040: The getAttribute(): {0} was a handle. Reconstructing the EJB object.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP Session
- BEA-100042: An error occurred while reconstructing the EJB object: {0}, which was put into the 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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100043: An error occurred while finding the handle for the EJB object: {0}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100045: Malformed WLCookie. Value: {0} will be ignored.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100048: Looked up ROID: {0} from host {1}:{2} for ID: {3}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP Session
- BEA-100049: An error occurred while looking up the session with ID:{0}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100053: Failed to update the secondary server for HTTP session ID: {0}.
-
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.
Level: 1
Type: WARNING
Impact: HTTP Session
- BEA-100054: Failed to find the secondary server for HTTP session ID: {0}.
-
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.
Level: 1
Type: WARNING
Impact: HTTP Session
- BEA-100055: The generated session ID: {0} contains a reserved keyword and is regenerating.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP Session
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100059: An unexpected error occurred while cleaning up sessions during undeployment of Web application: {0}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100060: An unexpected error occurred while retrieving the session for Web application: {0}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- 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.
-
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.
Level: 1
Type: WARNING
Impact: HTTP Session
- 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.
-
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.
Level: 1
Type: WARNING
Impact: HTTP Session
- 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.
-
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.
Level: 1
Type: WARNING
Impact: HTTP Session
- 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.
-
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.
Level: 1
Type: WARNING
Impact: HTTP Session
- BEA-100066: Failed to look up the replicated session object for Web application: {0}, session ID: {1}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100067: Failed to look up the secondary information for Web application: {0} session ID: {1}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100068: Failed to look up the secondary information for Web application: {0} session ID: {1}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100070: Error reconstructing the EJBHome put into session for name: {0}
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100072: Error in finding the HomeHandle for the EJBHome: {0}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100082: Failed to deploy {0} because the JDBC data source was missing. Target a JDBC data source to the cluster.
-
Cause: The configuration was incomplete.
-
Action: Target a JDBC data source to the cluster. Refer to the cluster documentation for more information.
Level: 1
Type: ERROR
Impact: HTTP Session
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100087: The JDBC session data for session ID: {0} has been modified by another server in the cluster.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- 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}
-
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.
Level: 1
Type: WARNING
Impact: HTTP Session
- BEA-100094: The session ID: {0} has been accessed from {1}, a server that is not the primary ({2}). The request URL was: {3}.
-
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.
Level: 1
Type: WARNING
Impact: HTTP Session
- BEA-100095: persistent-data-source-jndi-name is required for an async-jdbc 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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-100097: The IDLength {0} is too short. It is not secure. WebLogic Server will increase the length to {1}.
-
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}.
Level: 1
Type: WARNING
Impact: HTTP Session
- BEA-100098: persistent-data-source-jndi-name or persistent-store-pool is required when persistent-store-type is jdbc.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Session
- BEA-101002: [{0}] Could not deserialize the context attribute.
-
Cause: The classloader changed. When this happens, the old attributes will be deserialized using the new classloader.
-
Action: Ensure that the attribute class is available to the Web application scope and is serializable.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101087: {0} is not a virtual host. Dispatching to default HTTP server.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101095: POST time exceeded the configured MaxPostTimeSecs of {0,number}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101096: POST size exceeded the MaxPostSize={0,number}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101100: [{0}] Got bad cookie header: {1} from User-Agent: {2}
-
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)
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101105: [{0}] error-page location: "{1}" for the error-code: "{2,number}" does not exist. Serving the default error page.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101138: {0} One of the getParameter family of methods was called after reading from the ServletInputStream. Not merging post parameters.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101159: [{0}] Received IllegalAccessException while instantiating servlet: "{1}". Ensure that the servlet implementation is a public class.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101160: Deployment descriptor is malformed; check against the DTD: {0}.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101168: The security-role-assignment references an invalid security-role: {0}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101169: The servlet {0} is referenced but not defined in web.xml.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101170: The servlet {0} is referenced in servlet-mapping {1} but not defined in web.xml.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101171: The web.xml descriptor has no resource-ref entries for the reference-descriptor defined in weblogic.xml.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101172: The web.xml descriptor has no ejb-ref entries.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101173: Did not find resource-ref in web.xml matching {0}.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101174: Did not find ejb-ref in web.xml matching {0}.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101198: Could not deploy role: {0} for Web application: {1} application: {2}.
-
Cause: The Web application could not deploy the role defined in web.xml.
-
Action: Ensure that the security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101199: Could not deploy policy for resource: {0}.
-
Cause: The Web application failed to deploy the policy for the security-constraint defined in web.xml.
-
Action: Ensure that the security is configured properly in the server. Also, check the stack trace for the exact cause.
Level: 1
Type: ERROR
Impact: HTTP
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101234: Attempting to initialize ExtendedLogFormat application specific header: {0}. However, initialization failed due to an exception.
-
Cause: An unexpected error occurred while initializing the log file format.
-
Action: Check the exception for the exact error message.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
Cause: An unexpected error occurred while initializing the ExtendedLogFormat.
-
Action: Check the exception for the exact error message.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101247: {0}: Public ID references the old version of the Servlet DTD. Change the public ID in web.xml file to "{1}".
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101248: [{0}]: Deployment descriptor "{1}" is malformed. Check against the DTD: {4} (line {2}, column {3}).
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101252: [{0}]: Servlet class {2} for servlet {1} could not be verified. {3}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101253: [{0}]: Servlet class {2} for servlet {1} could not be defined. The class file could be corrupt. {3}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101254: [{0}]: Servlet class {2} for servlet {1} could not be handled by the classloader with classpath {3}. {4}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
Cause: The run-as element in weblogic.xml refers to an invalid user.
-
Action: Check to see if the user exists.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101271: The url-pattern element is not specified for the web-resource-collection/web-resource-name: {0} in the web.xml descriptor.
-
Cause: The url-pattern element is a mandatory element.
-
Action: If you want the security constraint to apply for all requests, specify url-pattern=/*.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101276: Web application(s) {1} still have non-replicated sessions after {0} minutes of initiating SUSPEND. Waiting for non-replicated sessions to finish.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101277: Web application(s) {0} has {1} non-replicated session(s) respectively.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101282: {0}: jspServlet "{1}" defined in weblogic.xml could not be registered. It should be a subclass of javax.servlet.http.HttpServlet.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101287: {0}. The servlet: {1} received an exception during servlet destroy. Ensure that the super.init(config) is called in the init() method.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101291: The webAppModule: {1} in application: {0} is unable to reload classes because it shares a classloader with other modules.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- 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".
-
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".
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101299: The servlet-mapping for servlet-name "{0}" will override the default mapping for *.jsp. This can lead to a show code vulnerability.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- 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.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- 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.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- 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.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- 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.
-
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
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101306: Could not resolve entity "{0}" for the webapp at: "{1}". Check the DTD reference in the corresponding descriptor (web.xml/weblogic.xml).
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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).
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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}
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101317: The Web application: {0} has specified "DIGEST" as the auth-method in web.xml, which is not implemented. Will default to BASIC.
-
Cause: DIGEST authentication is not yet implemented. The Web application will fallback to BASIC authentication.
-
Action: Choose either BASIC, FORM, or CLIENT-CERT.
Level: 1
Type: WARNING
Impact: HTTP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101319: The Web application: {0} has "FORM" based authentication specified but the mandatory element: {1} is left blank.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101338: The context parameter "weblogic.httpd.defaultServlet" has been deprecated. Instead, use the servletMapping = "/" to define the default servlet.
-
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 = "/".
Level: 1
Type: WARNING
Impact: HTTP
- 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
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101343: {0}: Attempting to precompile {1}, since the class file associated with it was found to be out-of-date.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101344: {0}: Attempting to precompile {1}, since the class file associated with it was not found in the Web application classpath.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- 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}".
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101347: The server channel name (NetworkAccessPoint): {0} being used by the Virtual Host: {1} is already in use by: {2}
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
Cause: The NetworkAccessPoint is not yet defined.
-
Action: Choose a different NetworkAccessPoint name or define a new one using the Administration Console.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101349: Failed to save the WorkContexts into the session or cache for the request: {0}
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101350: Web application(s) {2} of module {1} of application {0} has {3} pending session(s) respectively.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101352: There are no active sessions. The Web application module {1} of application {0} is ready to go into administration mode.
-
Cause: All active sessions have completed. The Web service is ready to gracefully transition to administration mode.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101355: [{0}] Version {2} is specified for Web Services {1}, but versioning of Web Services is not supported.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101359: The servlet {0} initilization method failed while it was run in the background. The exception was: {1}.
-
Cause: The servlet initilization method caused an exception.
-
Action: The cause of the exception must be corrected and then the application should be redeployed.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101362: [{0}] could not deserialize the {1} scoped attribute with name: "{2}"
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
Cause: The context-root specified in application.xml takes higher precedence than the one in weblogic.xml.
-
Action: This is an informational message. PEnsure that this is what you intended to do.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101366: The server could not send the HTTP message during the configured timeout value. The socket has been closed.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101367: An error occurred while extracting archived file for "{0}", located at "{1}".
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- 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}
-
Cause: The library or the application descriptors are invalid.
-
Action: Fix the descriptors in the application or the library.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101371: There was a failure when processing annotations for application {0}. Ensure that the annotations are valid. The error is {1}
-
Cause: The descriptor has an invalid servlet-class, filter-class, or listener-class.
-
Action: Fix the descriptors in the application or the library.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101372: There was a failure in application {0} when attempting to inject dependencies into {1}. Dependencies will not be injected into this class.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- 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.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101374: The Web container failed to lookup the transaction associated with the current thread for Web application: ${0}.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101377: Filtering class loader configuration ignored for web module {1} of application {0}
-
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). Such 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}
Level: 1
Type: WARNING
Impact: HTTP
- 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
-
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
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101384: {0} annotation is deprecated, please use servlet 3.0 annotation instead. App:{1}, Class:{2}
-
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
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101385: WebListener annotation is used illegally, the class annotated by WebListener must implement listener interface
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101389: Cannot add this ServletContextListener
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101390: It is illegal to use both value and urlPatterns attributes together in the same WebServlet/WebFilter annotation: {0}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101394: The exception "{0}" occurred when processing getParameter or getParameterValues from a multipart value of a ServletRequest.
-
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.
Level: 1
Type: WARNING
Impact: HTTP
- BEA-101395: Application or module {0} is deployed as a web application.
-
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.
Level: 1
Type: NOTIFICATION
Impact: HTTP
- BEA-101396: Either the urlPatterns or the value attribute in the WebServlet annotation MUST be present: {0}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-101397: The urlPatterns attribute, servletNames attribute, or value attribute of the WebFilter annotation MUST be specified: {0}.
-
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.
Level: 1
Type: ERROR
Impact: HTTP
- BEA-110004: Unable to read transaction log record checksum.
-
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.
Level: 1
Type: WARNING
Impact: JTA
- BEA-110005: Transaction log record checksum failure [{0}].
-
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.
Level: 1
Type: WARNING
Impact: JTA
- BEA-110007: Log record class instantiation problem [{0}]: {1}
-
Cause: An internal error occurred. 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: Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110008: Log record class readExternal problem [{0}]: {1}
-
Cause: An internal error occurred. 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: Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110015: A version error occurred while reading the transaction log header file.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110020: Error reading transaction log file [{0}]: {1}
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110023: Transaction log record checksum failure [{0}]: {1}.
-
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.
Level: 1
Type: WARNING
Impact: JTA
- BEA-110026: Missing transaction log file [{0}]
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110028: The transaction manager did not call XA.forget() for transaction [{1}] on resource [{0}], which reported a heuristic decision during commit.
-
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.
Level: 1
Type: NOTIFICATION
Impact: JTA
- BEA-110029: The transaction manager did not call XA.forget() for transaction [{1}] on resource [{0}], which reported a heuristic decision during rollback.
-
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.
Level: 1
Type: NOTIFICATION
Impact: JTA
- BEA-110030: XA resource [{0}] has not responded in the last {1} second(s).
-
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().
Level: 1
Type: WARNING
Impact: JTA
- BEA-110200: User [{0}] is not authorized to invoke startCommit on a transaction branch.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110201: User [{0}] is not authorized to invoke startRollback on a transaction branch.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110202: User [{0}] is not authorized to invoke rollback on a transaction branch.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110204: XA resource [{0}] returns XAER_RMFAIL and is unavailable.
-
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().
Level: 1
Type: WARNING
Impact: JTA
- BEA-110207: A previously unavailable XA resource [{0}] is now available.
-
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.
Level: 1
Type: NOTIFICATION
Impact: JTA
- 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.
-
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.
Level: 1
Type: WARNING
Impact: JTA
- BEA-110213: The activation of Transaction Recovery Service for server [{0}] failed.
-
Cause: This is an internal error.
-
Action: Examine the error details, correct the error conditions, and perform the necessary manual migration again if possible. If unsuccessful, My Oracle Support.
Level: 1
Type: WARNING
Impact: JTA
- BEA-110405: Resource {0} was not assigned to any of these servers: {1}
-
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.
Level: 1
Type: WARNING
Impact: JTA
- BEA-110412: {0} completed heuristically: {1}.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110419: An attempt was made to add an incompatible object as a transaction property: keys must be strings and values must be serializable.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110420: An attempt was made to add an incompatible object as a local transaction property: keys must be String.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110423: Abandoning transaction after {0} seconds: {1}
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110433: Unable to obtain ownership of the transaction log.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110450: The administrative request to locally roll back the transaction {0} encountered an error {1}.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110451: The administrative request to globally roll back the transaction {0} encountered an error {1}.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110452: The administrative request to locally commit the transaction {0} encountered an error {1}.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110453: The administrative request to globally commit the transaction {0} encountered an error {1}.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110458: The administrative request to globally roll back the transaction {0} failed, because the coordinator {1} could not be contacted. {2}
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110459: The administrative request to globally commit the transaction {0} failed, because the coordinator at {1} could not be contacted. {2}
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110460: The administrative request to globally rollback the transaction {0} failed, because the coordinator does not support manual transaction resolution.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110462: The administrative request to locally commit the transaction {0} failed, because the transaction has been marked for rollback.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110464: The forced commit operation for transaction {0} on resource {1} was not performed, because the resource is busy.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110465: The forced rollback operation for transaction {0} on resource {1} was not performed, because the resource is busy
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110466: The forced commit operation for transaction {0} on resource {1} was not performed because the resource has already been committed.
-
Cause: The transaction may have completed before the administrative client invoked the commit operation.
-
Action: No action is required. The transaction has been resolved.
Level: 1
Type: NOTIFICATION
Impact: JTA
- BEA-110467: The forced rollback operation for transaction {0} on resource {1} was not performed because the resource has already been rolled back.
-
Cause: The transaction may have completed before the administrative client invoked the rollback operation.
-
Action: No action is required. The transaction has been resolved.
Level: 1
Type: NOTIFICATION
Impact: JTA
- BEA-110468: The forced commit operation for transaction {0} on resource {1} encountered an error. {2}
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110469: The forced rollback operation for transaction {0} on resource {1} encountered an error. {2}
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110470: User [{0}] is not authorized to invoke a forced global rollback.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110471: User [{0}] is not authorized to invoke a forced global commit.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110472: User [{0}] is not authorized to invoke a forced local rollback.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110473: User [{0}] is not authorized to invoke a forced local commit.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110475: User [{0}] is not authorized to invoke commit on a non-XA resource transaction branch.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: JTA
- BEA-110477: The unregisterResource operation for resource {0} timed out after {1} seconds.
-
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.
Level: 1
Type: NOTIFICATION
Impact: JTA
- 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}].
-
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.
Level: 1
Type: WARNING
Impact: JTA
- 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}].
-
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.
Level: 1
Type: WARNING
Impact: JTA
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: JTA
- BEA-110482: A logging last resource (LLR) failed during initialization. The server cannot boot unless all configured LLRs initialize. Failing reason: {0}
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: JTA
- BEA-110483: The JTA health state has changed from {0} to {1}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: JTA
- BEA-110484: The JTA health state has changed from {0} to {1} with reason codes: {2}.
-
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.
Level: 1
Type: WARNING
Impact: JTA
- BEA-110485: The JTA health state has changed from {0} to {1} with reason codes: {2}.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- 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.
-
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.
Level: 1
Type: WARNING
Impact: JTA
- 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.
-
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.
Level: 1
Type: WARNING
Impact: JTA
- 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.
-
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.
Level: 1
Type: WARNING
Impact: JTA
- BEA-110490: User [{0}] is not authorized to invoke Commit on a Coordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110491: User [{0}] is not authorized to invoke AckPrePrepare on a Coordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110492: User [{0}] is not authorized to invoke CheckStatus on a Coordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110493: User [{0}] is not authorized to invoke AckCommit on a Coordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110494: User [{0}] is not authorized to invoke NakCommit on a Coordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110495: User [{0}] is not authorized to invoke AckRollback on a Coordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110496: User [{0}] is not authorized to invoke NakRollback on a Coordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110500: User [{0}] is not authorized to invoke GetSubCoordinatorInfo on a SubCoordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110501: User [{0}] is not authorized to invoke GetProperties on a SubCoordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-110502: User [{0}] is not authorized to invoke Recover on a SubCoordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- 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].
-
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.
Level: 1
Type: WARNING
Impact: JTA
- 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.
-
Cause: See the message detail.
-
Action: Change the application to assign the proper TRANSACTION_COMPLETION_TIMEOUT_SECONDS_PROPERTY_KEY property value.
Level: 1
Type: ERROR
Impact: JTA
- BEA-111001: The Transaction Manager is being started in standalone mode and will not be able to participate in distributed transactions.
-
Cause: There are no suitable RMI or JNDI providers configured.
-
Action: Configure the appropriate RMI and JNDI context providers.
Level: 1
Type: NOTIFICATION
Impact: JTA
- 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.
-
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 accessible.
Level: 1
Type: NOTIFICATION
Impact: JTA
- BEA-111007: The commit operation for one-phase transaction {0} on resource {1} encountered an error. {2}
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-111011: A Transaction Log PrimaryStore failed during initialization. The server cannot boot unless configured Transaction Log Primary Store initialize. Failing reason: {0}
-
Cause: An internal error occurred.
-
Action: Examine the root exception thrown by the Transaction Log Primary Store to determine the root cause of the problem.
Level: 1
Type: INTERNAL_ERROR
Impact: JTA
- 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}].
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-114089: User [{0}] is not authorized to invoke ackPrepare on a Coordinator.
-
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.
Level: 1
Type: ERROR
Impact: JTA
- BEA-119000: One-phase transaction [{1}] for logging last resource [{0}] is in an unknown state.
-
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.
Level: 1
Type: WARNING
Impact: JTAExceptions
- BEA-119001: Two-phase transaction [{1}] for logging last resource [{0}] is in an unknown state.
-
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.
Level: 1
Type: WARNING
Impact: JTAExceptions
- BEA-119002: A LLR failed during initialization. The server cannot boot unless all configured LLRs initialize. Failing reason: {0}
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: JTAExceptions
- BEA-119003: LLR [{0}] failed during initialization, as one of its records is corrupted. Failure reason: {1}
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: JTAExceptions
- BEA-119004: The user-preferred server of JTAMigratableTargetMBean [{0}] cannot be set to [{1}].
-
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}].
Level: 1
Type: ERROR
Impact: JTAExceptions
- BEA-119005: JTA subsystem failed. A forced shutdown of the server was done because the server is in automatic JTA migration mode.
-
Cause: The JTA subsystem failed.
-
Action: JTA Transaction Recovery Service will be automatically migrated to back up the server.
Level: 1
Type: ERROR
Impact: JTAExceptions
- 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}
-
Cause: This is an internal error.
-
Action: Examine the root exception generated by the Transaction Log Primary Store to determine the root cause of the problem.
Level: 1
Type: INTERNAL_ERROR
Impact: JTAExceptions
- BEA-130000: Insertion of {0} into XML entity cache rejected. Entity size, {1}, exceeded cache size, {2}.
-
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.
Level: 1
Type: WARNING
Impact: XML
- BEA-130001: Entity cache appears to be broken. This impacts the performance of XML parsing.
-
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.
Level: 1
Type: WARNING
Impact: XML
- BEA-130002: The entity that was just put in the cache cannot be retrieved: "{0}". Timeout may be too short.
-
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.
Level: 1
Type: WARNING
Impact: XML
- 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}
-
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.
Level: 1
Type: WARNING
Impact: XML
- 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}
-
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.
Level: 1
Type: WARNING
Impact: XML
- BEA-130018: XML cache error: cache file {0} is corrupted. Creating new cache from scratch.
-
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.
Level: 1
Type: ERROR
Impact: XML
- BEA-130019: XML cache error for registry {0}: entry file {1} is corrupted. Removing from cache. entry: {2}
-
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.
Level: 1
Type: ERROR
Impact: XML
- BEA-130024: XML cache error for registry {0}: out of memory loading entry. Entry removed from cache. entry: {1}, file: {2}
-
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.
Level: 1
Type: ERROR
Impact: XML
- BEA-130027: XML cache warning: the requested memory size of the XML cache, {0}, exceeds the available memory, {1}.
-
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.
Level: 1
Type: WARNING
Impact: XML
- BEA-130028: XML cache warning: the requested memory size of the XML cache, {0}, is a large percentage of the available memory, {1}.
-
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.
Level: 1
Type: WARNING
Impact: XML
- BEA-130033: Parser or DocumentBuilder cannot be created to satisfy the configuration requested. {0}
-
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.
Level: 1
Type: ERROR
Impact: XML
- BEA-140008: Internal error. Failed to save configuration changes to the configuration repository - {0}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141009: Error occurred in the file distribution servlet while processing the request type "{0}", {1}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141011: The file distribution servlet failed to distribute the security properties file, because the file was not found at the configured location: {0}.
-
Cause: The identified file was not available to the Administration Server.
-
Action: Verify the configuration of this file.
Level: 1
Type: ERROR
Impact: Management
- BEA-141021: The cluster property {0} was ignored because the server is not part of a cluster.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141023: An error occurred while setting the attribute value in the MBean proxy {0}, method {1} with value {2} ({3}).
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141062: The user does not have permission to perform {1} operation on MBean {0}. Method = {3}, attribute = {2}
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141063: The user does not have permission to perform {1} operation on MBean {0}. Method: {2}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- 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}.
-
Cause: This is an internal error that should not occur during normal operation.
-
Action: Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Management
- BEA-141077: An error occurred during the parsing of descriptors for {0}. Exception {1} occurred.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141078: A descriptor initialization error occurred for module {0} in EAR file {1}. Creation of the temporary file {2} failed.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141081: The file distribution servlet failed to distribute the embedded LDAP initial replica data file due to the following error: {0}.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Management
- 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.
-
Cause: An unrecognized property has been specified on the start command.
-
Action: Eliminate the invalid properties from the start command.
Level: 1
Type: NOTIFICATION
Impact: Management
- BEA-141089: Starting the server based on the WebLogic Server 6.x configuration directory structure.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Management
- BEA-141102: Subject: {0} does not have access to perform {1} actions.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141124: An invalid system property was specified while booting the server {0}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141126: The configuration file {0} is read-only.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141145: An attempt was made to connect to the Administration Server without credentials.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141146: An attempt was made to connect to the Administration Server by the user {0} and a password which does not match.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141147: An attempt was made to upload a file to the Administration Server by the unauthorized user {0}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141148: An invalid attempt was made to download a {1} resource from the Administration Server by the unauthorized user {0}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- 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.
-
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 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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141151: The Administration Server could not be reached at {0}.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Management
- BEA-141191: The prepare phase of the configuration update failed with an exception.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141194: The registration of the configuration subsystem with the deployment subsystem failed with an exception.
-
Cause: An exception occurred during the registration of the configuration subsystem.
-
Action: Take action based upon the provided exception details. Restart the server.
Level: 1
Type: ERROR
Impact: Management
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Management
- 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.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Management
- 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.
-
Cause: The configuration was not modified because pending changes were present.
-
Action: Activate the changes before using the compatibility server.
Level: 1
Type: ERROR
Impact: Management
- 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.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Management
- BEA-141223: The server name {0} specified with -Dweblogic.Name does not exist. The configuration includes the following servers {1}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Management
- 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}.
-
Cause: An invalid encrypted value was found in the edit lock file.
-
Action: Start a new edit session.
Level: 1
Type: ERROR
Impact: Management
- BEA-141234: A rollback of a dynamic change failed. The message for the failure is "{0}". The cause of the exception is "{1}".
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141237: Extraneous text found in the config.xml file: {0}.
-
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.
Level: 1
Type: WARNING
Impact: Management
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141239: The non-dynamic attribute {1} on {0} has been changed. This may require redeploying or rebooting configured entities.
-
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.
Level: 1
Type: WARNING
Impact: Management
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Management
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141244: Schema validation errors while parsing {0} - {1}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141247: The configuration directory {0} does not exist, and the Administration Server is not available.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141249: The configuration directory {0} is missing the file {1}, and the Administration Server is not available to download it.
-
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.
Level: 1
Type: ERROR
Impact: Management
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141252: The domain version {0} is greater than the release version {1} of this server.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141254: Generating new domain directory in {0}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Management
- BEA-141265: Could not get the configuration lock used to serialize access to the configuration files.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141269: The temporary bean tree {0} was allocated for an undo, get, or activate operation, but has not been garbage collected.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141270: Could not get the configuration lock used to serialize access to configuration files. Retrying for another {0} seconds.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141271: An IOException occurred while recording setAttribute {1} on MBean {0}. Exception: {2}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141272: An IOException occurred while recording invoke {1} on MBean {0}. Exception: {2}.
-
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.
Level: 1
Type: ERROR
Impact: Management
- BEA-141273: An upgrade framework class was not found. Exception: {0}. The configuration and upgrade framework component may not have been installed.
-
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.
Level: 1
Type: ERROR
Impact: Management
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Management
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Management
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Management
- 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.
-
Cause: This message is informational and is printed every time WebLogic Server starts.
-
Action: Change your jave entropy configuration, if needed.
Level: 1
Type: NOTIFICATION
Impact: Management
- 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.
-
Cause: This message is informational and is printed every time WebLogic Server starts.
-
Action: Change your jave entropy configuration, if needed.
Level: 1
Type: NOTIFICATION
Impact: Management
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Management
- 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.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Management
- BEA-141285: The network access point property {0} was ignored because the specified network access point name was not found.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141286: The creation of the dynamic server failed with an exception.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141287: No matching machines were found based on the MachineNameMatchPrefix property. No machine has been calculated for servers from dynamic servers {0}.
-
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.
Level: 1
Type: WARNING
Impact: Management
- BEA-141288: Unable to obtain file lock but will retry.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Management
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Management
- 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.
-
Cause: The system component is not defined in config.xml
-
Action: Define the corresponding system component in config.xml.
Level: 1
Type: WARNING
Impact: Management
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Management
- 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.
-
Cause: Another server is running and still has the server lock.
-
Action: Check to see if another server is running.
Level: 1
Type: NOTIFICATION
Impact: Management
- BEA-141298: Could not register with the Administration Server: {0}
-
Cause: A network connection failed or an IO exception occurred.
-
Action: Check the underlying exception and determine why the managed server could not connect to the Administration Server.
Level: 1
Type: NOTIFICATION
Impact: Management
- BEA-149003: Unable to access application source information in "{0}" for application "{1}". The specific error is: {2}.
-
Cause: Source files for the application to be deployed are not accessible.
-
Action: Ensure that no other process is using the source file(s).
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149007: New source location, "{0}", cannot be deployed to the configured application, "{1}". The application source is at "{2}". Changing the source location is not allowed for a previously attempted deployment. Try deploying without specifying the source.
-
Cause: This error occurs when an attempt is made to change the source location for a previously configured application.
-
Action: Deploy the application with the same source location that was configured in the application.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149011: Some of the targets in the deployment request are not configured in this domain. The named targets are: "{0}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149013: Application "{0}" does not define the module, "{1}". {2} are the known valid module(s) for this application.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149021: Rejecting {2} request for application "{1}". The specified ID, {0}, is already being used.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149040: An attempt to change the staging mode for the application "{0}" has been rejected.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149043: The staging mode cannot be changed for an application that has already been configured. The staging mode change has been rejected for application "{0}" from {1} to {2}.
-
Cause: An attempt was made to change the staging mode on an application.
-
Action: Try deploying without changing the staging mode.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
Cause: The module is already targeted to a different cluster member.
-
Action: Target the entire cluster to the module.
Level: 1
Type: NOTIFICATION
Impact: Deployer
- BEA-149061: Module {1} of application {0} failed to transition from {2} to {3} on server {4}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Deployer
- BEA-149069: Deploying {0} using a deprecated protocol.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Deployer
- BEA-149073: The application "{0}" has no configured modules.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149081: Cannot {2} application, "{0}", with version "{1}". The application was previously deployed without a version.
-
Cause: An attempt was made to {2} a versioned application when it was previously deployed without a version.
-
Action: Try {2} without a version.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149082: Cannot {2} application "{0}" without a version. The application was previously deployed with version "{1}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149083: An attempt was made to activate the application "{0}" when stop was in progress.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149085: No application version was specified for application "{0}". The {2} operation will be performed against the currently active version "{1}".
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149089: An attempt was made to activate the application "{0}" when retirement was in progress.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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}".
-
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}".
Level: 1
Type: ERROR
Impact: Deployer
- 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}".
-
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}".
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149093: No version specified for the versioned application named "{0}" for operation {1}, and no active version is available.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149094: New version "{1}" of application "{0}" cannot be deployed to the source location, "{2}". The source location is the same as the nostage source location of a previously deployed application version "{3}".
-
Cause: This error occurs when an attempt is made to deploy a new application version with the same source location as the nostage source location of a previous application version.
-
Action: Deploy the new application version with a different source location. Also ensure that the old application source is still available at the old nostage source location.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149096: Operation {1} is deprecated and cannot be applied to versioned application "{0}". Use operation {2} instead.
-
Cause: An attempt was made to perform the deprecated operation {1} on a versioned application. Use operation {2} instead.
-
Action: Use operation {2} instead.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149098: An attempt was made to gracefully undeploy the application "{0}" when retirement was in progress.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149099: Unexpected errors occurred while sending deployment event {1} on behalf of application "{0}".
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149100: Unexpected errors occurred while sending a vetoable deployment event on behalf of application "{0}".
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- 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.
-
Cause: Incorrect target information was provided in the {2} operation request.
-
Action: Ensure that the target information in the request is accurate.
Level: 1
Type: WARNING
Impact: Deployer
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149103: An exception occurred while executing task {0} for application "{1}": {2}.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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}".
-
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).
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149114: Cannot deploy or redeploy application "{0}" with version identifier "{1}" because the maximum length of the version identifier ({2}) has been exceeded.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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 "..".
Level: 1
Type: ERROR
Impact: Deployer
- 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}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149120: The plan version "{1}" cannot be specified when deploying a non-versioned application "{0}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149121: Rejecting {1} request for application {0} because the deployment service is not started.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- 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.
-
Cause: No application version was specified for the {0} operation of application "{1}".
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: Deployer
- 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.
-
Cause: This is an informational message only.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Deployer
- BEA-149132: Split directory application {0} can only be deployed on the Administration Server.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149133: Auto-deployed application {0} can only be deployed on the Administration Server.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
Cause: An attempt was made to partially redeploy an archived application.
-
Action: Specify -source for production redeployment, or redeploy the entire application.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
Cause: The file could not be located in the application.
-
Action: Use a valid specification for the file.
Level: 1
Type: ERROR
Impact: Deployer
- 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}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Deployer
- BEA-149146: Attempt to reach the Administration Server with alternate URL: "{0}" failed.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Deployer
- BEA-149147: Could not reach the Administration Server through any of its URLs: "{0}".
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149148: Exception occurred while receiving a message on loopback.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149149: Malformed URL: "{0}".
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149150: An IOException occurred while reading the input.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149151: Could not find a registered DeploymentReceiver to handle requests for "{0}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149152: No deployment request for which to set up the context.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149153: A "prepare" message was received for ID "{0}" that has already been completed or canceled.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149155: Received "get deployments response" message "{0}" while already handling one. Ignoring the second request.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149156: Illegal state for operation start: "{0}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149159: There was an attempt to create a staging directory that is null.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149160: There was an attempt to create a staging directory for a null application name.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149164: The domain edit lock is owned by another session in exclusive mode. Therefore, this deployment operation cannot proceed.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149165: Invalid target specified.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149166: Deployments cannot be triggered through configuration updates and through the Deployment APIs simultaneously.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149168: Request "{0}" has already been completed or was canceled.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149170: Invalid targeting was specified for this operation. Module and submodule targets cannot both be specified for this type of request.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
Cause: This is an informational message indicating that deployment involves a non-dynamic property.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Deployer
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149182: An invalid alternate descriptor was specified for the redeploy operation. Alternate descriptors cannot be changed during a redeploy operation.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
Cause: Autodeployed applications cannot be redeployed through tools.
-
Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149185: The application "{0}" was autodeployed and may only be deleted by removing the files from the domain autodeploy directory.
-
Cause: Autodeployed application cannot be undeployed through tools.
-
Action: See the WebLogic Server documentation on autodeployed applications for more information.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149187: An unexpected error occurred when specifying configuration information for the application "{0}" due to {1}.
-
Cause: Application configuration upgrade requires targeting information.
-
Action: Inspect the problematic application parts and deploy the application.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149188: No application named "{0}" exists for operation {1}. Operation cannot be performed until the server is restarted.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- 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.
-
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).
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149196: Rejecting {1} request for application {0} because {2} request is running for the application.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149199: Security permissions declared in the "{0}" deployment descriptor are not allowed due to the server's configuration.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149202: Encountered an exception while attempting to commit the {0} task for the application "{1}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149205: Failed to initialize the application "{0}" due to error {1}
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149229: Server "{0}" in cluster "{1}" is unable to initialize due to failed deployments.
-
Cause: This problem occurred due to failed deployments, which are already logged.
-
Action: Correct the deployment problem, and restart the server in the cluster.
Level: 1
Type: INTERNAL_ERROR
Impact: Deployer
- BEA-149233: An unexpected error occurred during the deployment process.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149239: Application deployment failures were detected during startup of the Administration Server, "{0}", member of cluster "{1}".
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149246: The security realm "{0}" does not support application versioning. Deployment of application "{1}" failed.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149247: Failed to transition the application "{0}" to running mode due to error {1}
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149248: Failed to transition the application "{0}" to administration mode due to error {1}.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149256: Failed to find deployment for application "{0}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
Cause: Another application might be using the files under a staging directory.
-
Action: Delete the appropriate staged files manually.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149259: Server "{0}" in cluster "{1}" is being brought up in administration state due to failed deployments.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Deployer
- BEA-149260: A failure occurred during application startup.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149268: Static deployment of non-versioned application "{0}" failed due to a version being defined in its manifest file.
-
Cause: The manifest file was modified with a version for a non-versioned application.
-
Action: Remove the application and redeploy it with a version.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Application Poller
- BEA-149408: An exception occurred while deploying an application {0}: {1}.
-
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.
Level: 1
Type: ERROR
Impact: Application Poller
- BEA-149412: Application "{0}" is being redeployed, because it changed since the previous server run.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Application Poller
- BEA-149414: Could not create directory for autodeployed applications: {0}
-
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.
Level: 1
Type: WARNING
Impact: Application Poller
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Application Poller
- BEA-149501: An exception occurred while registering the MBean {0} at property {1}.
-
Cause: Refer to the embedded exception information for more details as to the probable cause of this error.
-
Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1
Type: ERROR
Impact: JMX
- BEA-149503: An exception occurred while unregistering the MBean {0} at property {1}.
-
Cause: Refer to the embedded exception information for more details as to the probable cause of this error.
-
Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1
Type: ERROR
Impact: JMX
- BEA-149504: The Administration Server was unable to establish JMX Connectivity with the {0} at the JMX Service URL of {1}.
-
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.
Level: 1
Type: WARNING
Impact: JMX
- BEA-149505: The Administration Server was unable to establish JMX Connectivity with the {0} at the JMX Service URL of {1}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: JMX
- BEA-149508: Unable to establish JMX Connectivity with the Administration Server.
-
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.
Level: 1
Type: WARNING
Impact: JMX
- BEA-149509: Unable to establish JMX connectivity with the Administration Server {0} at {1}.
-
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.
Level: 1
Type: WARNING
Impact: JMX
- BEA-149510: Unable to establish JMX Connectivity with the Administration Server {0} at {1}.
-
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.
Level: 1
Type: WARNING
Impact: JMX
- BEA-149521: An exception occurred during the processing of JMX Connectivity with the Administration Server: {0}
-
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.
Level: 1
Type: WARNING
Impact: JMX
- BEA-149608: Unknown type of deployable: "{0}"
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149609: AppRuntimeStateRuntime only available on the Administration Server.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149610: Problems were encountered while creating the persistent store.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149611: Problems were encountered while creating the persistent store.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149612: Problems were encountered while saving to the persistent store for "{0}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149613: Problems were encountered while deleting from the persistent store for "{0}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149614: There were problems during the server disconnect for listener "{0}". {1}
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149615: Unrecognized type: "{0}".
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149616: A critical internal application {0} was not deployed. Error: {1}
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- BEA-149617: Non-critical internal application {0} was not deployed. Error: {1}
-
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.
Level: 1
Type: WARNING
Impact: Deployer
- BEA-149618: Unable to deploy an internal management Web application - {0}. Managed Servers may be unable to start.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Deployer
- BEA-149622: Could not get file lock used to serialize access to configuration files.
-
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.
Level: 1
Type: ERROR
Impact: Deployer
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- BEA-150001: An error occurred while connecting to the Administration Server to bootstrap through the URL: {0}, user: {1}.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- BEA-150014: The Managed Server Independence feature is disabled for this server ({0}).
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Configuration Management
- BEA-150018: This server is being started in Managed Server independence mode in the absence of the Administration Server.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Configuration Management
- BEA-150020: The Managed Server could not reach the Administration Server at {0}.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- BEA-150028: A security failure or an exception occurred when retrieving the bootstrap information for the Managed Server.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- BEA-150032: The Managed Server did not provide any version details at initial contact.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- BEA-150034: An attempt was made to download the configuration for the server {0} without the required credentials.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- BEA-150035: An attempt was made to download the configuration for the server {0} by the user {1} with an invalid password.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- BEA-150036: An attempt was made to download the configuration for the server {0} by the unauthorized user {1}.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- BEA-150038: A configuration file was found in the parent directory {0}, but the root directory is empty.
-
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.
Level: 1
Type: WARNING
Impact: Configuration Management
- BEA-150041: The server name {0} is unknown to the Administration Server. Check if restart is required.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- 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.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Configuration Management
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Configuration Management
- BEA-160001: Error deploying {0}: {1}
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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}".
-
Cause: The specified EJB does not exist in the module.
-
Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1
Type: ERROR
Impact: J2EE
- 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}".
-
Cause: The specified EJB does not exist in the module.
-
Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: The link did not resolve to a valid EJB.
-
Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: The link did not resolve to a valid EJB.
-
Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: The specified EJB does not exist in the module.
-
Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: The specified EJB does not exist in the module.
-
Action: The ejb-link must be fixed to point to a valid EJB.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- 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.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160109: ERROR: Error copying files to the directory "{0}": {1}
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160110: ERROR: appc could not create the working directory, "{0}". Ensure that this directory can be created and try again.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160118: appc is unable to continue processing the file "{0}". The following error occurred while accessing it: {1}
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160125: ERROR: Could not delete old backup file: {0}.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160126: ERROR: Could not create backup file "{0}". The error was: {1}
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: Too many arguments were specified in the appc command.
-
Action: Correct the command and try again.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: The specified alt-dd could not be found.
-
Action: Correct or remove the invalid alt-dd setting in the appc command.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- 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.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- 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.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- 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.
-
Cause: The target of the message-destination-link could not be found in the application.
-
Action: Fix the message-destination-link to point to a valid message-destination.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160139: The following library reference has "context-path" set, which has no effect when referencing a {1} library: {0}.
-
Cause: The library reference has "context-path" set, but is not referencing a WAR library.
-
Action: Remove "context-path" from the library reference.
Level: 1
Type: NOTIFICATION
Impact: J2EE
- BEA-160140: Unresolved optional package references (in META-INF/MANIFEST.MF): {0}. Ensure that the referenced optional package has been deployed as a library.
-
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).
Level: 1
Type: WARNING
Impact: J2EE
- 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
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160148: These libraries were not referenced by the compiled application: {0}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: J2EE
- 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
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- 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.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- BEA-160165: The EAR library at {0} is organized using the splitdir directory structure. splitdir is not supported for libraries.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160167: The module {1} in application {0} uses ejb-links but no EJB modules were found for this application.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160175: ERROR: Could not find JMS module of name "{2}" specified in the resource-link named "{3}" in the "{1}" component named "{0}".
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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}".
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: The application was not a valid J2EE application.
-
Action: Correct the application and try again.
Level: 1
Type: ERROR
Impact: J2EE
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160184: ERROR: Could not find JDBC module of name "{2}" specified in the resource-link named "{3}" in the "{1}" component named "{0}".
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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}".
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160187: weblogic.appc failed to compile the application. Recompile with the -verbose option for more details about the issue.
-
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. If you believe the error is due to a bug in WebLogic Server, please contact My Oracle Support.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160191: While upgrading weblogic.xml, the server encountered "{1}" parameter "{0}". This parameter has been deprecated and will be removed
-
Cause: This is a deprecated parameter.
-
Action: Remove the deprecated parameter from the weblogic.xml deployment descriptor.
Level: 1
Type: NOTIFICATION
Impact: J2EE
- BEA-160192: While upgrading weblogic.xml, the server encountered "{1}" parameter "{0}". This parameter is unknown and will be removed
-
Cause: The parameter is not defined in the schema.
-
Action: Check the weblogic.xml deployment descriptor and remove the parameter.
Level: 1
Type: NOTIFICATION
Impact: J2EE
- BEA-160195: The application version lifecycle event listener {1} is ignored because the application {0} is not versioned.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- BEA-160196: Unable to find the jar-uri: {1} specified for the Singleton class in the weblogic-application.xml of application: {0}
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: See the error message for details.
-
Action: Ensure that the ejb-link and interface name(s) declared in the ejb-ref are correct.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: Persistence unit configuration specifies logging information, but WebLogic Server will ignore this information.
-
Action: Remove the {1} setting from persistence unit {0}.
Level: 1
Type: WARNING
Impact: J2EE
- BEA-160203: You have specified a {1} setting in your configuration for persistence unit {0}. This value will be replaced with {1}.
-
Cause: The persistence unit configuration specifies ID information, but WebLogic Server will ignore this information.
-
Action: Remove the {1} setting from persistence unit {0}.
Level: 1
Type: WARNING
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: Higher run-as privileges are needed to deploy an ApplicationLifecycleListener in this situation.
-
Action: Try the deployment action with an administrative privileged user.
Level: 1
Type: ERROR
Impact: J2EE
- 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}".
-
Cause: There was a problem resolving the target of the specified ejb-ref.
-
Action: Specify a beanInterface to indicate which EJB is the target.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: TBD
-
Action: TBD
Level: 1
Type: NOTIFICATION
Impact: J2EE
- BEA-160216: Unexpected errors occurred while sending deployment event {1} on behalf of application ''{0}''.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- BEA-160217: Unexpected errors occurred while sending a vetoable deployment event on behalf of application ''{0}''.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- BEA-160218: Filtering classloader configuration ignored for module {1} of application {0}
-
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}.
Level: 1
Type: WARNING
Impact: J2EE
- BEA-160219: The JPA persistence unit {0} will use the following configured default persistence provider: {1}
-
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.
Level: 1
Type: NOTIFICATION
Impact: J2EE
- 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.
-
Cause: See the error message body.
-
Action: See the error message body.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160225: JPA 2.0 API methods cannot be invoked on JPA 1.0 persistence provider. Update the application to use a JPA 2.0 compliant provider, such as EclipseLink, or ensure that the application does not attempt to invoke JPA 2.0 methods.
-
Cause: The application is invoking a method defined in JPA 2.0 but the persistence provider configured in the application is only JPA 1.0 compliant. Note the deprecated Kodo-OpenJPA persistence provider that ships with WebLogic Server does not support JPA 2.0.
-
Action: Update your application to use a JPA 2.0 compliant persistence provider, such as EclipseLink, or modify the application to ensure that only JPA 1.0 API methods are invoked.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160226: Ignoring the configuration file [{0}: {1}]. Only applications that use Kodo as the JPA provider can be configured with this file.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- 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.
-
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.
Level: 1
Type: WARNING
Impact: J2EE
- 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.
-
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. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160229: Ignoring plan file {0} as does not exist.
-
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. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: J2EE
- BEA-160231: Unable to identify application type for {0}
-
Cause: The source file type may not be supported.
-
Action: Use the provided error message to track down and fix the problem. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160232: Unable to identify module type for {0}
-
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. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160233: Unable to identify module type
-
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. If you believe the error is due to a bug in WebLogic Server, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
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.
Level: 1
Type: ERROR
Impact: J2EE
- 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.
-
Cause: See the error message body.
-
Action: See the error message body.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160241: Error: There are environment entries conflict in module {0}. Multiple environment entries are defined with the same name but different values. {1}
-
Cause: With an EJB in WAR files, it is possible that environment entries names 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.
-
Action: Make sure they have different environment entries names. Or have same names with identical values.
Level: 1
Type: ERROR
Impact: J2EE
- BEA-160242: Warning: Data source definition {0} in interceptor {1} may have been overwritten by EJB component in module {2}, ignored.
-
Cause: EJB component may overwrite data source definitions in its interceptors. In this case, data source definitions in interceptors will be ignored.
-
Action:
Level: 1
Type: WARNING
Impact: J2EE
- BEA-169800: A PooledConnectionFactory object with an invalid external version of {0} was found.
-
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.
Level: 1
Type: ERROR
Impact: JMSPool
- BEA-169802: Cannot create a wrapped JMS connection using a username and password when the res-auth element is set to Container.
-
Cause: The application code is not using the J2EE APIs properly.
-
Action: Either remove the username and password, or set the res-auth element to Application.
Level: 1
Type: ERROR
Impact: JMSPool
- BEA-169803: JNDI lookup of the JMS connection factory {0} failed
-
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.
Level: 1
Type: ERROR
Impact: JMSPool
- BEA-169804: Cannot use a JMS connection factory because the object is of the wrong type.
-
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.
Level: 1
Type: ERROR
Impact: JMSPool
- BEA-169805: A pooled JMS connection is being closed because an error was detected on the connection: {0}
-
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.
Level: 1
Type: ERROR
Impact: JMSPool
- 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}
-
Cause: See the error message from the JMS provider.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: JMSPool
- 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}
-
Cause: See the error message from the JMS provider.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: JMSPool
- BEA-169809: An error occurred while registering the JMS connection with JTA.
-
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.
Level: 1
Type: ERROR
Impact: JMSPool
- BEA-169812: The pooled JMS session is enlisted in another transaction and may not be used elsewhere.
-
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.
Level: 1
Type: ERROR
Impact: JMSPool
- 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.
-
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.
Level: 1
Type: WARNING
Impact: JMSPool
- 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}".
-
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.
Level: 1
Type: WARNING
Impact: JMSPool
- BEA-169822: Unable to use a wrapped JMS session in the transaction because two-phase commit is not available.
-
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.
Level: 1
Type: ERROR
Impact: JMSPool
- BEA-169823: Failure occured on createQueueConnection. Unexpected return type.
-
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.
Level: 1
Type: ERROR
Impact: JMSPool
- BEA-169824: Failure occured on createTopicConnection. Unexpected return type.
-
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.
Level: 1
Type: ERROR
Impact: JMSPool
- BEA-170003: The DomainLogfile Handler is unable to open the domain logfile {0}. The domain logfile is disabled.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: Log Management
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Log Management
- BEA-170028: The remote handler is not available, so the trap notification information can not be sent.
-
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.
Level: 1
Type: ERROR
Impact: Log Management
- 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).
-
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.
Level: 1
Type: ERROR
Impact: EmbeddedLDAP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: EmbeddedLDAP
- BEA-171507: The embedded LDAP replica file: {0} could not be written. The underlying exception was {1}.
-
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.
Level: 1
Type: ERROR
Impact: EmbeddedLDAP
- 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.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: EmbeddedLDAP
- BEA-171513: Could not schedule the trigger used for embedded LDAP timer activities. The underlying exception was {0}.
-
Cause: A TimeTrigger exception occurred when scheduling the trigger.
-
Action: See the exception text in {0} for more information on diagnosing the problem.
Level: 1
Type: INTERNAL_ERROR
Impact: EmbeddedLDAP
- 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}.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: EmbeddedLDAP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: EmbeddedLDAP
- 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.
-
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.
Level: 1
Type: WARNING
Impact: EmbeddedLDAP
- 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.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: EmbeddedLDAP
- 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}.
-
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.
Level: 1
Type: INTERNAL_ERROR
Impact: EmbeddedLDAP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: EmbeddedLDAP
- BEA-180008: A transaction identifier exists for a non-existent domain {0}.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180009: Could not complete the execution for the MBean named: {0}.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180016: The RemoteTDomain {0} is unknown.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180022: Could not set up the field table information for TDMResources: {0}.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180024: Unable to reply to unknown transaction with exception: {0}.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180055: Received an unexpected token type, error information({0}, {1}, {2}).
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180056: atntd(1) crypto error: {0}
-
Cause: There was not enough free memory space to continue, or an internal error occurred.
-
Action: Try to force garbage collection, and remove some services to reduce memory usage. If the problem persists, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180059: atntd(2) crypto error: {0}
-
Cause: There is not enough free memory space to continue, or an internal error occurred.
-
Action: Try to force garbage collection, and remove some services to reduce memory usage. If the problem persists, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180079: rsession.run read_tfmh failed.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180081: Unexpected close on rsession socket. The following exception occurred: {0}
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180099: The MinEncryptionBits is greater then the MaxEncryptionBits in {0} domain {1}.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180103: There are two remote domains {0} with the same local domain {1}.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180109: Internal FML to XML conversion failed.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180110: Internal FML32-to-XML conversion failed.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180111: Internal FML to XML conversion failed.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180112: Internal FML32 to XML conversion failed.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180133: AppKey plug-in initialization failed. Reason: {0}
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180134: Create new AppKey class {0} instance failed.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180138: The {0} MBean appears to contain previously defined import service information.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180141: Message header contains an invalid magic number, connection closed.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180155: No valid network address for TDomain session ({0}, {1}) to try to connect to.
-
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.
Level: 1
Type: WARNING
Impact: WTC
- BEA-180157: Failed to connect to remote access point(//{0}:{1}), no more address to try.
-
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.
Level: 1
Type: WARNING
Impact: WTC
- BEA-180163: The received Tuxedo reply uses the unsupported buffer type {0}, so the tBridge has redirected the message to the wlsErrorDestination.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180166: The remote gateway does not support application level keep alive. This feature is disabled for the TDomain session ({0}, {1}).
-
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.
Level: 1
Type: WARNING
Impact: WTC
- 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.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180171: SSL null ciphers are not enabled and will be upgraded to the minimum 56 bits.
-
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.
Level: 1
Type: WARNING
Impact: WTC
- BEA-180173: Invalid private key for identity alias {0} from key store {1}, detected by {2}.
-
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.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180176: An error occurred while retrieving the trusted certificate from trust store {0}, detected by {1}.
-
Cause: The configured trust certificate was corrupted or an incorrect passphrase was configured.
-
Action: Correct the trust certificate store configuration information.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180177: An error occurred while retrieving trusted certificates from WebLogic Server, detected by {0}.
-
Cause: The configured trust certificate was corrupted or an incorrect passphrase was configured.
-
Action: Correct the trust certificate store configuration information.
Level: 1
Type: ERROR
Impact: WTC
- BEA-180178: The requested encryption strength of 256 bits of local access point {0} is not supported by LLE. Downgrade to 128 bits.
-
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.
Level: 1
Type: NOTIFICATION
Impact: WTC
- BEA-180179: When enabling access point {0} to support SDP, the SSL support setting for this access point was ignored.
-
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.
Level: 1
Type: WARNING
Impact: WTC
- BEA-190004: ConnectionFactory not found for jndiName {0}.
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-190005: An error occurred while creating a connection factory for ManagedConnectionFactory with jndiName {0}.
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190008: An error occurred while {2} the connection instance {1} for {0} resource adapter. Exception is: {3}
-
Cause: This error occurs 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 internal 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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190019: < {0} > An error occurred when opening the log file {1} for the resource adapter.
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190020: < {0} > An error occurred while setting the log file to the resource adapter.
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190023: < {0} > Error invoking the ManagedConnectionFactory "set" method for the configuration property "{1}". Reason: {2}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190024: < {0} > Error making initial connections for pool. Reason: {1}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-190032: < {0} > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "{1} "
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-190033: < {0} > createManagedConnection returned a null ManagedConnection.
-
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
Level: 1
Type: ERROR
Impact: Connector
- BEA-190049: The connector service failed to initialize. ServiceMBean initialization error: {0}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190051: An error occurred while shutting down the connection pool with pool name: {0}. Reason: {1}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190052: An error occurred while creating a connection pool Runtime MBean with pool name: {0}. Reason: {1}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190053: An error occurred while creating a resource for a connection pool {0}. Reason: {1}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190054: An error occurred while destroying a resource for a connection pool {0}. Reason: {1}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190056: An error occurred while reserving a resource from a connection pool {0}. Reason: {1}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190064: Access has been denied to {0}, Application: {1}, Module: {2}, EIS Type: {3}, while reserving a connection.
-
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.
Level: 1
Type: WARNING
Impact: Connector
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190090: Call to implementation of ManagedConnection.getLocalTransaction in resource adapter with jndiName = {1} failed: {0}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190091: Call to implementation of ManagedConnection.getXAResource in resource adapter with jndiName = {1} failed: {0}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190092: An error occurred while reserving a resource from a connection pool {0}. Reason: {1}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- 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}
-
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.
Level: 1
Type: NOTIFICATION
Impact: Connector
- BEA-190098: Trying to release a resource that has already been released for {0}.
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-190100: A close() method was not found on the connection handle while testing for the viability for connection proxies : {0}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190104: While configuring an object of type: {0} of Resource Adapter {1}, the following errors/omissions were found: {2}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-190115: The ManagedConnectionFactory class does not implement the ResourceAdapterAssociation interface: {0}
-
Cause: See the error in the message body for information.
-
Action: Please contact the resource adapter vendor and notify them of this error condition.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190122: The resource adapter passed a null ManagedConnection into WebLogic Server's implementation of ConnectionManager.lazyEnlist().
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190146: An error occurred while setting the log file to the resource adapter's ManagedConnectionFactory: {0}. The exception was "{1}" with cause "{2}".
-
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.
Level: 1
Type: ERROR
Impact: Connector
- 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}".
-
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.
Level: 1
Type: WARNING
Impact: Connector
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-190150: The process of creating the Connector Diagnostic Image has been timed out by the Diagnostic Framework. The resulting image may be incomplete.
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-190151: Parsing error, buildOutboundResourceAdapter() error in parsing ra.xml. While looking for connectionfactory-interface, failed to find: "{0}"
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-190155: Compliance checking and validation of the resource adapter {0} resulted in the following warnings: {1}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-190158: This is a link ref resource adapter for {0}. No validation can be done at this time.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Connector
- BEA-190161: Failed to extract adapter {0} to server temporary directory due to exception {1}.
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199010: No ra.xml or weblogic-ra.xml has been specified. The RAR is null and there is no alternate descriptor.
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199019: Failed to initialize the connector-specific JNDI sub-contexts for the application, {0}, {1}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199032: Unable to getInitialContext() during unbindConnectionFactory, {0}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199038: NamingException while trying to unbind references during unbindAdminObject of resource adapter, {0}
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199107: Resource Adapter returned null from ManagedConnectionFactory.createManagedConnection() while trying to create ManagedConnection for recovery.
-
Cause: Check the logs for the cause of this exception.
-
Action: Inspect the cause and take appropriate action.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199113: Failed to setup the ManagedConnection with WLS after successfully getting it from a call to the Resource Adapter's ManagedConnectionFactory.createManagedConnection method.
-
Cause: Check the logs for the cause of this exception.
-
Action: Inspect the cause and take appropriate action.
Level: 1
Type: ERROR
Impact: Connector
- 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.
-
Cause: Check the logs for the cause of this exception.
-
Action: Inspect the cause and take appropriate action.
Level: 1
Type: ERROR
Impact: Connector
- 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.
-
Cause: Check the logs for the cause of this exception.
-
Action: Inspect the cause and take appropriate action.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199137: The ManagedConnectionFactory class implementation "{0}" does not implement the ResourceAdapterAssociation interface and does not implement setResourceAdapter() and/or getResourceAdapter().
-
Cause: Check the logs for the cause of this exception.
-
Action: Inspect the cause and take appropriate action.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199153: Connection testing cannot be enabled for a pool when the ManagedConnectionFactory does not implement ValidatingManagedConnectionFactory. The following invalid settings have been detected:
-
Cause: Check the logs for the cause of this exception.
-
Action: Inspect the cause and take appropriate action.
Level: 1
Type: ERROR
Impact: Connector
- 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.
-
Cause: Check the logs for the cause of this exception.
-
Action: Inspect the cause and take appropriate action.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199168: Unable to force log rotation: The connection pool for "{0}" is configured to use the server log.
-
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.
Level: 1
Type: ERROR
Impact: Connector
- BEA-199170: For the setting {0}: "{1}" has higher privileges than the deployment user: "{2}".
-
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.
Level: 1
Type: ERROR
Impact: Connector
- 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}.
-
Cause: Check the logs for the cause of this exception.
-
Action: Inspect the cause and take appropriate action.
Level: 1
Type: ERROR
Impact: Connector
- 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.
-
Cause: Check the logs for the cause of this exception.
-
Action: Inspect the cause and take appropriate action.
Level: 1
Type: ERROR
Impact: Connector
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Connector
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Connector
- BEA-199185: There is no META-INF/validation.xml file in the adapter archive {0}. The default Bean Validation configuration will be used.
-
Cause: No META-INF/validation.xml file was found in the RAR archive.
-
Action: No action is required if this behavior is expected.
Level: 1
Type: NOTIFICATION
Impact: Connector
- 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}.
-
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.
Level: 1
Type: WARNING
Impact: Connector
- 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 since its ManagedConnectionFactory class has @Unshareable annotation. Will treat as unshareable.
-
Cause: An invalid resource reference definition was made to an unshareable ConnectionFactory.
-
Action: Change the SharingScope of the resource reference definition to Unshareable.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199192: Warning: Caller application {2} defines a resource reference {1} to outbound connection pool {0} without define SharingScope explicitly. The pool does not support share by its design since its ManagedConnectionFactory class has @Unshareable annotation. Will treat as unshareable.
-
Cause: An invalid resource reference definition was made to an unshareable ConnectionFactory.
-
Action: Change the SharingScope of the resource reference definition to Unshareable.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199194: Resource adapter generated unexpected exception during work event notification for event {0}. Ignored. Exception: {1}
-
Cause: The resource adapter generated an unexpected exception during work event notification.
-
Action: Check the work event processing codes of the resource adapter.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199195: Connector annotation scan: Ignored unexpected error [{2}] when processing annotations on {0} while {1}.
-
Cause: Check the error message and stacktrace to determine the cause.
-
Action: Check error message and stacktrace to determine the appropriate action to take.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199196: Ignore @javax.resource.Connector annotation on class {0} since ResourceAdapter Bean {1} is already specifed in ra.xml.
-
Cause: ra.xml already specifies the ResourceAdapter bean to use.
-
Action: No action is required if this behavior is expected.
Level: 1
Type: NOTIFICATION
Impact: Connector
- BEA-199197: An exception occurred when removing admin object {0}. Exception is: {1}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199198: An exception occurred when invoking preDestroy on {0}: {1}. Exception is: {1}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199199: The work was rejected because it has expired before WorkManager executed it.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Connector
- BEA-199200: Annotation scan/process of the resource adapter {0} resulted in the following {1} warnings: {2}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199202: Ignored unexpected exception [{1}] when unregistering runtime mbean {0}.
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199211: Compliance checking and validation of the resource adapter {0} resulted in the following non-critical errors: {1}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- 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}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199214: The connection pool [{0}] was in a HEALTH_CRITICL state already, therefore this method call is not allowed.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Connector
- 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}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-199216: An error occurred when performing action {2} on connection pool [{0}]. The following error will be ignored: {1}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Connector
- 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}
-
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.
Level: 1
Type: WARNING
Impact: Connector
- BEA-200002: Failed to deploy the messaging bridge "{0}" because the messaging bridge service is shut down.
-
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.
Level: 1
Type: ERROR
Impact: MessagingBridge
- 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.
-
Cause: One of the adapters was not deployed.
-
Action: Deploy the required adapters.
Level: 1
Type: WARNING
Impact: MessagingBridge
- BEA-200021: Bridge "{0}" failed to get one of the adapters from JNDI ({1}).
-
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.
Level: 1
Type: NOTIFICATION
Impact: MessagingBridge
- BEA-200024: Bridge "{0}" refused to obtain connections and transfer any messages, because it has been stopped, suspended, or is shutting down.
-
Cause: The administrator has shut down or stopped the bridge, or the bridge is suspended for migration.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: MessagingBridge
- 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.
-
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.
Level: 1
Type: ERROR
Impact: MessagingBridge
- 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})
-
Cause: There was a problem in receiving or sending messages to one of the sides of the bridge.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: MessagingBridge
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: MessagingBridge
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: MessagingBridge
- BEA-200032: Bridge "{0}" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.
-
Cause: This message indicates that the quality of service of the bridge is not allowed to be downgraded.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: MessagingBridge
- 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})
-
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.
Level: 1
Type: NOTIFICATION
Impact: MessagingBridge
- 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})
-
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.
Level: 1
Type: NOTIFICATION
Impact: MessagingBridge
- BEA-220010: A MIME-encoded SOAP response must include a content-type mime header specifying the MIME start and boundary.
-
Cause: The content-length was zero or the content-type was null. An attachment, however, was provided.
-
Action: Verify the server configuration and retry the request.
Level: 1
Type: INTERNAL_ERROR
Impact: WebService
- BEA-220018: The handler class:{0} issued an exception from its destroy method. This exception is ignored. The exception was: {1}.
-
Cause: A handler class issued an exception from its destroy method.
-
Action: Correct the handler Handler.destroy implementation.
Level: 1
Type: NOTIFICATION
Impact: WebService
- BEA-220100: An error occurred while registering this Web service for monitoring. Although this does not affect the Web service itself, monitoring information about it may be unavailable. The specific error was {0}.
-
Cause: An error condition was reported.
-
Action: No action is required.
Level: 1
Type: WARNING
Impact: WebService
- BEA-220103: Async Web service support is not fully configured. The async response Web service {0} for this server was not fully deployed because the JMS reliability queue was not defined/deployed: {1}. The server will periodically retry completing the deploy for the service. This message can usually be ignored unless there are async Web service applications. To completely disable async Web service support, thus avoiding this message, set -Dweblogic.wsee.skip.async.response=true.
-
Cause: The JMS queue JNDI name specified in the WebservicesMBean (or allowed to default) was not found on this server. The async response service requires this JMS queue in order to operate. To avoid obscure errors while processing Web service async responses, this service was not fully deployed. Not having this JMS queue available can indicate that Web services have not been configured/enabled for this domain. The server will periodically retry deploying the service, so there is no need to restart the server once the JMS queue is made available.
-
Action: If you do not intend to use async Web services in this domain, no action is required. To avoid seeing this message and completely disable async Web service support, set -Dweblogic.wsee.skip.async.response=true. If you intend to use async Web services in this domain, define a non-distributed JMS queue with the local JNDI name given in WebservicesMBean (which has a default value), and after a short delay, the async response service will be fully deployed to use the newly defined queue. Oracle recommends that the JMS queue be located on a JMS server that is targeted to the same server as the Web service. Note that you can easily add async response Web services support to an existing domain by extending your domain with the Configuration Wizard and applying the wls_webservice.jar extension template. For more information, see the WebLogic Server online documentation in the 'Web Services->Get Started Using JAX-RPC' section.
Level: 1
Type: NOTIFICATION
Impact: WebService
- BEA-220104: Web services async response service {0} for this server was just deployed because the reliability queue was found: {1}
-
Cause: The queue specified in the WebservicesMBean (or allowed to default) was recently deployed to this server. The async response service requiring this queue is now deployed.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: WebService
- BEA-220105: Web services async/reliable invocations for service {0} are NOT available because the async/reliability queue was not found: {1}
-
Cause: You have deployed a Web service that indicates it can use async/reliable features, but the queue for async/reliable invocations (specified in WebservicesMBean, @Buffer or @ReliabilityBuffer annotations, or allowed to default) is not deployed to the local server. Therefore, async and reliable invocations will fail if attempted. Standard synchronous invocations will still work correctly despite this problem.
-
Action: Remove any async or reliable features from the Web service (e.g. @AsyncResponse, @Buffer, @ReliabilityBuffer annotations or @Policy annotations specifying reliable policy) or properly configure this server for async/reliable invocations. See the WebLogic Server online documentation in the 'Web Services->Get Started Using JAX-RPC' section for help on fixing this configuration problem. Once you have defined the proper async/reliable resources, you must redeploy your application.
Level: 1
Type: WARNING
Impact: WebService
- BEA-220106: OWSM Security requires that a WSDL be associated with the Web service.
-
Cause: You have deployed a Web service that does not have a WSDL associated with it.
-
Action: Associate a WSDL with the Web service. For example you can add a wsdlLocation attribute to a WebService or WebServiceProvider annotation.
Level: 1
Type: ERROR
Impact: WebService
- BEA-220501: The service port {1} bound to https transport in service {0} is NOT available, the https address cannot be resolved because SSL is not enabled for the server. The service port definition will be removed from WSDL that is being accessed through {2}.
-
Cause: While a WSDL is being retrieved through http protocol, the server requires replacing the service port address in WSDL with the actual address for the server. For any web service which defines one or more service ports bound to https transport, if the domain does not enable SSL functionality then the service port address could not be replaced correctly because https address for the server cannot be resolved.
-
Action: Enable SSL functionality for the server.
Level: 1
Type: WARNING
Impact: WebService
- BEA-220505: Implicit/generated Client Identity {0} has been used in multiple calls to Service.getPort()/createDispatch() where these calls have used different services and/or sets of features. Monitoring statistics for this client will include all these different usages. Validation failures were: {1}
-
Cause: WebLogic JAX-WS web service clients are assigned a unique identity that is intended to represent the business purpose of that client. This identity can be specified directly using weblogic.jws.jaxws.client.ClientIdentityFeature or it can be allowed to be implicit. Implicit identity is generated automatically based on environmental information at the point where a Port/Dispatch instance is created. Your code has received an implicit client identity that is getting used (again implicitly) across multiple services or sets of features. All statistics gathered for a given client instance are rolled up under the client instance's client identity. If client instances using different services and/or feature sets contribute statistics to the same client identity, this can be confusing. It is even possible for clients to behave incorrectly when more advanced web service features are used.
-
Action: Best practice is to create a specific client identity (with a name representing a logical business purpose) for the client and denote this identity by passing weblogic.jws.jaxws.client.ClientIdentityFeature to the call to Service.getPort/createDispatch. Further, it is recommended that you pass a single/global set of web service feature objects to that call (e.g. Create WebServiceFeature instances as static class members or in a method annotated with @PostConstruct for containers compatible with this annotation). The actual call to Service.getPort()/createDispatch() should still be made in any way that makes sense for your uses (e.g. calling getPort on demand in a web service method, with Service created as a static class member).
Level: 1
Type: WARNING
Impact: WebService
- 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.
-
Cause: An invalid URI was provided when allocating a Deployment Manager.
-
Action: No action is required.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- 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.
-
Cause: Incorrect host/port used when attempting to allocate a Deployment Manager.
-
Action: No action is required.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- 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}.
-
Cause: There was a deployment failure.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: J2EE Deployment SPI
- BEA-260027: Non-root module, "{1}", is not supported for {0} operations. All modules must represent root modules.
-
Cause: All modules must represent root modules. This operation does not support embedded modules.
-
Action: Use DeploymentManager.enableModuleTargeting.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- BEA-260083: No plan document at "{0}"
-
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.
Level: 1
Type: WARNING
Impact: J2EE Deployment SPI
- BEA-260087: The descriptor at "{0}" is missing the required {1} element for custom module with URI, "{2}", and provider, "{3}".
-
Cause: The named element is missing from the weblogic-extensions.xml descriptor.
-
Action: Correct the errors in the weblogic-extensions.xml descriptor.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- BEA-260099: No root element in {0} descriptor, {1} at {2}.
-
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.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- BEA-260107: Failed to write descriptor for module "{0}" configuration: {1}.
-
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.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- BEA-260110: Failed to create configuration for module: {0}
-
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.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- BEA-260111: Errors were detected while attempting to communicate with the Administration Server.
-
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.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- BEA-260125: Errors were detected when attempting to communicate with Administration Server: {0}
-
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.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- 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.
-
Cause: A property in a DTD based descriptor was modified.
-
Action: Upgrade the application with schema based descriptors.
Level: 1
Type: WARNING
Impact: J2EE Deployment SPI
- BEA-260129: Export not allowed on DTD based descriptors. No properties for the {0} descriptor in module, "{1}", will be exported.
-
Cause: An attempt was made to export a DTD based descriptor.
-
Action: Upgrade the application with schema based descriptors.
Level: 1
Type: WARNING
Impact: J2EE Deployment SPI
- BEA-260132: "{0}" is not a child of "{1}".
-
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.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- 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}".
-
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}".
Level: 1
Type: WARNING
Impact: J2EE Deployment SPI
- BEA-260138: Failures were detected while trying to create a backup plan.xml file at "{1}" {0}.
-
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}.
Level: 1
Type: WARNING
Impact: J2EE Deployment SPI
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: J2EE Deployment SPI
- 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().
-
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.
Level: 1
Type: ERROR
Impact: J2EE Deployment SPI
- BEA-280021: There was an error while opening the file store file "{0}".
-
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.
Level: 1
Type: ERROR
Impact: Store
- BEA-280024: There was an error while creating a new file named "{0}" for the file 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.
Level: 1
Type: ERROR
Impact: Store
- BEA-280036: Missing the file store file "{0}" in the directory "{1}".
-
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.
Level: 1
Type: ERROR
Impact: Store
- BEA-280042: The file store primary or cache file "{0}" cannot be opened because it is actually a directory.
-
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.
Level: 1
Type: ERROR
Impact: Store
- BEA-280045: The file store primary or cache directory "{0}" is not a directory.
-
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.
Level: 1
Type: ERROR
Impact: Store
- 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.
-
Cause: This is a configuration error.
-
Action: When configuring a table name, choose a shorter name for the indicated field. Note that JDBC stores automatically append "WLStore" to the table name.
Level: 1
Type: ERROR
Impact: Store
- BEA-280066: Empty field value in table reference "{0}" (format [[[catalog.]schema.]table).
-
Cause: This is a configuration error.
-
Action: Ensure that the entire table reference is blank, or that the table field is not blank. If there is no schema, 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.
Level: 1
Type: ERROR
Impact: Store
- 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}".
-
Cause: See the linked exception text and linked exception stack trace.
-
Action: See the linked exception text and linked exception stack trace.
Level: 1
Type: ERROR
Impact: Store
- 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}".
-
Cause: See the exception text and exception stack trace.
-
Action: See the text exception text and exception stack trace.
Level: 1
Type: ERROR
Impact: Store
- 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}".
-
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.
Level: 1
Type: ERROR
Impact: Store
- 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.
-
Cause: A JDBC store booted.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: Store
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Store
- BEA-280074: The persistent store "{0}" encountered an unresolvable failure while processing transaction "{1}". Shut down and restart to resolve this transaction. {2}
-
Cause: There was a serious I/O error, either with file I/O or the JDBC connection to the database, or an unexpected exception occurred while processing a transaction.
-
Action: Restart the server.
Level: 1
Type: ERROR
Impact: Store
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Store
- BEA-280076: Database table "{1}" for store "{0}" is currently owned by "{2}". Trying to wait for ownership.
-
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.
Level: 1
Type: WARNING
Impact: Store
- 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}".
-
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.
Level: 1
Type: ERROR
Impact: Store
- BEA-280092: Specified value "{1}" of the property "{0}" is not a valid Integer system property. Using default value "{2}" instead.
-
Cause:
-
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).
Level: 1
Type: WARNING
Impact: Store
- BEA-280093: Block size "{1}" specified by the property {0} is outside the valid range from {2} to {3}. Using default value "{2}" instead.
-
Cause:
-
Action: Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
Level: 1
Type: WARNING
Impact: Store
- 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.
-
Cause:
-
Action: Refer to the JMS chapter of the Performance and Tuning for Oracle WebLogic Server guide for details of this setting.
Level: 1
Type: WARNING
Impact: Store
- BEA-280096: Opening existing file store "{2}". The direct IO mode "{1}" specified by the property "{0}" is invalid and will be ignored. Using the default value "{3}"
-
Cause:
-
Action: Use a valid direct I/O mode. The valid values are: "read-buffered", "single-handle-unbuffered", and "single-handle-buffered".
Level: 1
Type: WARNING
Impact: Store
- 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.
-
Cause:
-
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.
Level: 1
Type: WARNING
Impact: Store
- 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.
-
Cause: See the message body.
-
Action: See the documentation for store synchronous write policy configuration.
Level: 1
Type: NOTIFICATION
Impact: Store
- BEA-280102: The perisistent file store "{0}" must reinitialize its cache: recovery may take longer than usual. The signature in the cache file "{1}" for the persistent store file "{0}" 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.
-
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.
Level: 1
Type: WARNING
Impact: Store
- 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.
-
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 store files are removed before starting WebLogic Server again.
Level: 1
Type: WARNING
Impact: Store
- 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.
-
Cause: See the message body.
-
Action: Consult your storage vendor and operating system documentation.
Level: 1
Type: ERROR
Impact: Store
- BEA-280109: Unable to load the native wlfileio library for the persistent file store "{0}". The store will use buffered I/O. The store is still operating in a transactionally safe synchronous mode. See store open log messages for the requested and final write policies.
-
Cause: See message body.
-
Action: See the documentation for store synchronous write policy configuration.
Level: 1
Type: WARNING
Impact: Store
- 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.
-
Cause: The JDBC store was not able to acquire enough JDBC connections for the configured worker count.
-
Action: Modify the data source configuration.
Level: 1
Type: NOTIFICATION
Impact: Store
- BEA-281006: FailedMessage for store-and-forward: MessageId={0} > </FailedMessage.
-
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.
Level: 1
Type: NOTIFICATION
Impact: SAFService
- BEA-281021: SAF service failed to connect to the remote endpoint "{0}", because of {1}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: SAFService
- BEA-282000: Unsupported class version {0}. Expected a value between {1} and {2} inclusive.
-
Cause: While attempting to interoperate between different releases or service packs, an error occurred while attempting to serialize or deserialize an object. The version number of the object was not in the expected range. If {0} is larger than {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.
Level: 1
Type: ERROR
Impact: Messaging
- 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.
-
Cause: See the previous error messages, which should explain the cause.
-
Action: Restart the WebLogic Server.
Level: 1
Type: ERROR
Impact: Messaging
- BEA-282010: A sequence number update transaction for the messaging kernel {0} could not be committed because the kernel has been shut down.
-
Cause: A server was shut down or a destination was removed while a transaction was in progress.
-
Action: No action is required.
Level: 1
Type: ERROR
Impact: Messaging
- BEA-282013: Skipping unexpected null message encountered on store boot, {0}.
-
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.
Level: 1
Type: WARNING
Impact: Messaging
- BEA-282014: [StoreBootOnError] "{0}" Ignoring 2PC record for sequence={1}, queue={2}, type={3}, id={4}, xid={5}; message reference element cannot be found.
-
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.
Level: 1
Type: WARNING
Impact: Messaging
- BEA-290001: Error occurred in the deployment service servlet. It received an unacceptable request of type "{0}" with content type "{1}".
-
Cause: An invalid request was made to the deployment service servlet.
-
Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: DeploymentService
- BEA-290003: Deployment service servlet encountered an exception while handling request of type "{0}". Exception is: "{1}".
-
Cause: Error occurred while handling the deployment servlet request.
-
Action: This is an internal error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290006: Deployment service servlet received a request of type "{0}" with no application name.
-
Cause: An invalid deployment service servlet request was made.
-
Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290007: Deployment service servlet unable to find upload directory while handling request of type "{0}" for application "{1}".
-
Cause: The servlet was unable to find the upload directory.
-
Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290008: Deployment service servlet encountered an error while extracting uploaded file to directory "{0}". Exception is: "{1}".
-
Cause: An exception occurred while extracting the uploaded file.
-
Action: This is an internal error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290009: Deployment service servlet failed to get initialized due to unavailable security service.
-
Cause: The WebLogic Server security service is not present in the installation files.
-
Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290010: Deployment service servlet failed to get initialized due to privileged action violation. Exception is: "{0}".
-
Cause: An exception occurred while initializing the deployment service servlet.
-
Action: This is an internal error. Refer to the exception message and determine if the exception can be corrected. If the problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290012: Deployment service servlet received jspRefresh request with no upload file name.
-
Cause: The request parameter upload file name was null.
-
Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290015: Domain wide secret mismatch
-
Cause: Thee was an invalid signature between the Administration Server and Managed Servers.
-
Action: This is an internal error. Verify that the Administration Server and Managed Servers have the same SerializedSystemIni.dat file.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290020: Exceptions encountered while invoking application lifecycle listeners
-
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.
Level: 1
Type: ERROR
Impact: DeploymentService
- BEA-290024: Deployment type {0} has already been registered with the DeploymentService.
-
Cause: More than one deployment handler was registered for this deployment type.
-
Action: This is an internal error. No action is required. If the problem persists, contact My Oracle Support.
Level: 1
Type: ERROR
Impact: DeploymentService
- BEA-290040: The cancel call cannot be completed at this point because the deployment request "{0}" has already been partially committed.
-
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.
Level: 1
Type: ERROR
Impact: DeploymentService
- BEA-290041: Commit failed message received for id: "{0}" that has no request. It may be completed or cancelled. Sending commit succeeded message anyway.
-
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.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290042: Received a commit message call without a corresponding request. It may have been completed or cancelled. Sending commit failed message.
-
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.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290043: Cancel failure encountered when attempting to cancel "{0}" due to optimistic concurrency violation.
-
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.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290050: Failed to deliver commit message to the following targets "{0}".
-
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.
Level: 1
Type: ERROR
Impact: DeploymentService
- BEA-290051: The commit message for the deployment "{0}" could not be completed because the deployment timed out.
-
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.
Level: 1
Type: ERROR
Impact: DeploymentService
- BEA-290053: Request with id "{0}" timed out on the Administration Server.
-
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.
Level: 1
Type: ERROR
Impact: DeploymentService
- BEA-290055: Deployment request "{0}" timed out on the Administration Server during "{1}".
-
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.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290057: Invalid DeploymentRequest: the object returned by the DeploymentService has been modified in an incompatible way.
-
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.
Level: 1
Type: NOTIFICATION
Impact: DeploymentService
- 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.
-
Cause: The specified request ID is not active.
-
Action: Check that your task ID is the task that you would like to cancel.
Level: 1
Type: ERROR
Impact: DeploymentService
- BEA-290062: The server configuration is out of date with the domain configuration and an attempt to synchronize with the Administration Server failed. This server needs to be restarted to enable it to synchronize with the domain configuration.
-
Cause: An attempt to synchronize with the Administration Server failed.
-
Action: Restart the server and if that does not resolve the problem, contact My Oracle Support and provide the stack trace for further analysis.
Level: 1
Type: ERROR
Impact: DeploymentService
- BEA-290063: Commit for request "{0}" will not proceed further since its requires restart flag is set.
-
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.
Level: 1
Type: NOTIFICATION
Impact: DeploymentService
- BEA-290064: Deployment service servlet encountered an exception while handling the deployment service message for request id "{0}" from server "{1}". Exception is: "{2}".
-
Cause: Error occurred while handling the deployment service message request.
-
Action: This is an internal 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.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290065: Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "{0}" from server "{1}". Exception is: "{2}".
-
Cause: Error occurred while handling the deployment datatransfer request.
-
Action: This is an internal 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.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290066: Error occurred while downloading files from Administration Server for deployment request "{0}". Underlying error is: "{1}"
-
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.
Level: 1
Type: WARNING
Impact: DeploymentService
- 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.
-
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.
Level: 1
Type: WARNING
Impact: DeploymentService
- 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}".
-
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.
Level: 1
Type: WARNING
Impact: DeploymentService
- 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.
-
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.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290070: Deployment service servlet encountered an exception while parsing the multipart/form-data request:"{0}". Exception is: "{1}".
-
Cause: The request is not an RFC 1867-compliant multipart/form-data request.
-
Action: This is an internal error. No action is required.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-290071: Deployment service servlet failed when parsing the request or uploading the file.
-
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.
Level: 1
Type: WARNING
Impact: DeploymentService
- BEA-300001: Could not execute command {0} for the Managed Server through the NodeManager, because the server name is not set.
-
Cause: No name has been specified for the Managed Server.
-
Action: Specify a name for the Managed Server in its configuration settings.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300002: Could not execute command {0} for the Managed Server {1} through the NodeManager because the domain name is not set.
-
Cause: No domain has been specified for the Managed Server.
-
Action: Verify that a domain has been specified for the Managed Server.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300004: Could not execute command {0} for the Managed Server {1} through the NodeManager because this command can only be performed from an admin server.
-
Cause: The WebLogic Server instance where the Administration Console is running is not an Administration Server.
-
Action: Run the WebLogic Administration Console on the Administration Server.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300005: Could not execute command {0} for server {1} through the NodeManager. This command {0} cannot be executed on the Administration Server using the NodeManager.
-
Cause: The NodeManager does not perform any operations on the Administration Server.
-
Action: No action is required as this operation is not supported on the Administration Server.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300006: Could not execute command {0} for server {1} using the NodeManager. Logs cannot be obtained for the Administration Server using the NodeManager.
-
Cause: The NodeManager does not perform any operations on the Administration Server.
-
Action: No action is required as this operation is not supported on the Administration Server.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300007: Could not execute command {0} for server {1} using the NodeManager, because the NodeManager does not monitor the Administration Server.
-
Cause: The NodeManager does not perform any operations on the Administration Server.
-
Action: No action is required as this operation is not supported on the Administration Server.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300009: Server {0} cannot be started in the standby state because the administration port is not configured.
-
Cause: An attempt was made to start a server in the standby state without configuring an administration port.
-
Action: Configure an administration port for the domain and retry the operation.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300011: Could not execute command {0} for server {1} using the NodeManager because the target machine configuration was not found. This feature is applicable only for servers that are started up through the NodeManager.
-
Cause: An attempt was made to use the NodeManager to perform an operation on a server that is only valid if the server was started using the NodeManager.
-
Action: Start the server using the NodeManager.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300012: Could not execute command {0} for server {1} using the NodeManager because the NodeManager configuration for target machine {2} was not found.
-
Cause: This is an internal error.
-
Action: Associate a machine on which server {1} is to be started by the NodeManager, then execute command {0}.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300013: Could not execute command {0} for server {1} using the NodeManager because the NodeManager configuration for target machine {2} was not found. This feature is applicable only for servers that were started up using the NodeManager.
-
Cause: An attempt was made to use the NodeManager to perform an operation on a server that is only valid if the server was started using the NodeManager.
-
Action: Configure the NodeManager for machine {3}, then execute command {0} for server {1}.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300016: Could not execute command {0} for server {1} using the NodeManager because the remote start configuration was not found.
-
Cause: The remote start configuration is missing.
-
Action: Set the remote start configuration for server {1} in the Remote Start tab on the configuration page for this server in the Administration Console.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300017: Could not execute command {0} for server {1} using the NodeManager because the username and password are not set.
-
Cause: The username and password to be used to boot the server are not set.
-
Action: Set the username and password in the Remote Start tab for the server in the Administration Console.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300020: Could not get logs for server {0} using the NodeManager because the specified log type {1} is invalid. This type can only be either WL_output or WL_error.
-
Cause: An attempt was made to get a log of an invalid type.
-
Action: Specify a valid type and retry the operation.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300028: Error: Authentication Failure - {0}.
-
Cause: This is a security configuration error. The identity (username/password) specified in the Remote Start configuration of this server, which is used to boot the server, is being denied access to the server at runtime.
-
Action: Ensure that the identity specified in the Remote Start parameters for this server also has the privileges to access this server at runtime.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300032: Could not execute command {0} on the NodeManager. Unable to create file {1} under directory {2}.
-
Cause: The specified log file could not be created.
-
Action: Verify that the disk is not full and that the directory is writeable, then retry the operation.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300038: The NodeManager is unable to monitor this server. Could not create an SSL connection to the NodeManager. Reason : {0}
-
Cause: Check the message for details. This error might be due to a faulty SSL configuration.
-
Action: Check the message for details.
Level: 1
Type: WARNING
Impact: NodeManager
- BEA-300039: The state change notification registration failed. The server will only be able to respond to the GETSTATE messages by the NodeManager. Reason : {0}
-
Cause: See the message for details.
-
Action: Check the message for details and take corrective action accordingly.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300040: An I/O error occurred while writing a NodeManager status change message.
-
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.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300043: NodeManager native library not found - server process ID not saved.
-
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.
Level: 1
Type: WARNING
Impact: NodeManager
- BEA-300044: An I/O error occurred while writing the server PID file: "{0}".
-
Cause: The server PID file might be write protected.
-
Action: Ensure that the server PID file is not write protected. Also, check to see if the parent directory exists (should have been created by the NodeManager server before starting the server).
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300045: An I/O error occurred while executing command "{0}" on the NodeManager.
-
Cause: The NodeManager command execution failed due to a file I/O or socket exception.
-
Action: Ensure that the NodeManager is running and listening on the configured address
Level: 1
Type: WARNING
Impact: NodeManager
- BEA-300046: An I/O error occurred while executing command "{0}" for server "{1}" using the NodeManager.
-
Cause: The NodeManager command execution failed due to a file I/O or socket exception.
-
Action: Ensure that the NodeManager is running and listening on the configured address.
Level: 1
Type: WARNING
Impact: NodeManager
- BEA-300048: Unable to start the server {0} : {1}
-
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. Also, ensure that the default PATH settings for the remote NodeManager are correct. See the NodeManager documentation for more information.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300049: An I/O error occurred while writing the server URL file: "{0}".
-
Cause: The server URL file might be write protected.
-
Action: Ensure that the server URL file is not write protected. Also, check to see if the parent directory exists (should have been created by the NodeManager server before starting the server).
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300051: An I/O error occurred while updating the startup properties for "{0}". This probably occured 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.
-
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.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-300052: The specified script path, "{0}", contains improper characters. The script path must be a valid path that exists within the NodeManager script execution directory.
-
Cause: The specified script path, "{0}", contains improper characters.
-
Action: Ensure that the script path is a be a valid path that exists within the NodeManager script execution directory.
Level: 1
Type: ERROR
Impact: NodeManager
- 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.
-
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.
Level: 1
Type: ERROR
Impact: NodeManager
- 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 address specified and the server may not start without the available address. Configure an appropriate floating listen address for the server.
-
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.
Level: 1
Type: ERROR
Impact: NodeManager
- BEA-310003: Free memory in the server is {0} bytes. There is danger of receiving an OutOfMemoryError.
-
Cause: Free memory in the server is very low.
-
Action: Analyze heap memory usage for possible memory leak. Contact Oracle Support if the leak is in WebLogic server. If no memory leak is found, consider restarting server with a larger maximum heap size.
Level: 1
Type: WARNING
Impact: Health
- BEA-310007: Subsystem {0} has failed because of: {1} However, notification did not occur because {0} was not registered with the HealthMonitorService.
-
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.
Level: 1
Type: WARNING
Impact: Health
- BEA-320009: The elapsed time of the last snapshot of diagnostic metrics exceeded the configured sample period by the following number of milliseconds: {0}.
-
Cause: Harvested MBeans and/or DataSources are taking too long to return sampled attribute values.
-
Action: Increase the sample period window.
Level: 1
Type: WARNING
Impact: Diagnostics
- BEA-320010: An error occurred while generating a diagnostic image: {0}
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320011: The following diagnostic image destination directory could not be created: {0}
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320012: The following destination directory for diagnostic images could not be read/written: {0}.
-
Cause: The directory was not created the directory read/write permissions were not given to the directory.
-
Action: Create the destination directory with the appropriate read/write permissions.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320016: Creating diagnostic image in {0} with a lockout minute period of {1}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Diagnostics
- BEA-320031: An attempt to add a monitor of type {1} to instrumentation scope {0} failed because the monitor already exists in the scope.
-
Cause: Instrumentation configuration was incorrect.
-
Action: Remove multiple monitor entries with same types from the instrumentation scope configuration.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320032: Attempt to add duplicate action {2} to monitor {1} in scope {0} failed.
-
Cause: Instrumentation scope configuration is incorrect. It has duplicate actions attached to the same monitor.
-
Action: Remove duplicate actions attached to the same monitor.
Level: 1
Type: WARNING
Impact: Diagnostics
- BEA-320036: Instrumented method {1}{2} in class {0} exceeds size limit. Original method is preserved.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320042: Invalid diagnostic image location {0} specified in notification, exception message is {1}. Image capture was not performed.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320043: Image notification was not performed because the image capture was attempted before the lockout time expired. The exception message is {0}
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320047: Mail notification has not been sent due to an error that occurred while creating or sending a mail message:
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320048: JMS notification message has not been sent due to an error that occurred while creating a JMS map message:
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320049: Exception occurred sending JMS notification message. Reinitializing JMS objects and retrying.
-
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.
Level: 1
Type: WARNING
Impact: Diagnostics
- BEA-320052: Error occurred while initializing a SMTP notification:
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320054: Error occurred while sending a SNMP notification:
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320070: Error occurred while performing notification {1} for watch {0}. Notification may not have completed.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320071: Error occurred while creating watch notification {0}. Notifications may not have completed for this watch.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320078: Could not initialize the Diagnostic Accessor Service Runtime during server startup.
-
Cause: The exception message includes the details about the cause of this problem.
-
Action: Take corrective action based on the exception stack trace. Contact My Oracle Support if this problem persists.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320079: Watch "{0}" rule expression evaluation failed with an exception. No notifications will be performed for this watch. The exception is:
-
Cause: An exception occurred during rule evaluation.
-
Action: Verify that the rule expression is valid. Take appropriate action based on the exception message.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320080: The log type {0} is unknown. Unable to lookup the DiagnosticDataAccessRuntimeMBean instance.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320082: Configuration for diagnostic monitor {0} in instrumentation scope {1} has errors. The exception is:
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320083: Custom diagnostic monitor {0} in instrumentation scope {1} has missing or invalid location attribute.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320085: The diagnostic data is accessible only through https in Production mode.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320086: The monitor type {1} in scope {0} contains unacceptable characters.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320087: The cursor {0} has timed out and is being removed from the registry of open cursors.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Diagnostics
- BEA-320097: Monitor {0} can be created only in an application instrumentation scope. It cannot be created in server instrumentation scope.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320098: Monitor {0} can be created only in server instrumentation scope. It can not be created in application instrumentation scope {1}.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320100: Configuration for JDBC-based diagnostic archives is invalid or incomplete. Using file based diagnostic archive.
-
Cause: The configuration for JDBC-based diagnostic archives is invalid or incomplete.
-
Action: Fix the configuration for JDBC-based diagnostic archives.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320103: An error occurred while creating the DiagnosticDataRuntimeMBean instance with the given logical name {0}.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320104: An error occurrred when invoking the log4j operation while activating/deactivating log watch rules.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Diagnostics
- BEA-320113: The type {0} is no longer being harvested.
-
Cause: This is caused by an earlier problem. Sufficient log messages should have been issued at the point of failure to allow the problem to be debugged. Note that the type will remain deleted until the Harvester configuration is reloaded. At that time, if the problem is not yet resolved, this message may be issued again.
-
Action: No action is required. Typically, this type of error will cause some of the requested data to not be harvested. It is advisable to fix the issue.
Level: 1
Type: WARNING
Impact: Diagnostics
- BEA-320117: The Harvester is being disabled because there are no valid Harvestable types configured.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Diagnostics
- BEA-320122: Unable to harvest attribute {0} on item {1} due to errors. This attribute will no longer be harvested.
-
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.
Level: 1
Type: WARNING
Impact: Diagnostics
- BEA-320123: Could not add MBean instance {0} to the harvested instance list for type {1}: {2}.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320125: Attention: {0}
-
Cause: This indicates a system error, not a user error. Further investigation is required to determine the cause.
-
Action: The user should contact Oracle support to debug this problem. It is often possible to turn on Harvester debug to obtain additional information.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320127: An error occurred while generating Image Source {0} as part of the diagnostic image zip file:
-
Cause: An unexpected error occurred while the subsystem was collecting or persisting the diagnostic image source information.
-
Action: Take appropriate action based on the unexpected exception message.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320128: The WLDFResourceBean is not found for the WLDFSystemResource {0}.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Diagnostics
- BEA-320133: Could not instantiate one of the known accessors during server startup.
-
Cause: The exception message includes the details about the cause of this problem.
-
Action: Take corrective action based on the exception stack trace. Contact My Oracle Support if this problem persists.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320135: JDBC-based {0} archive could not be created. Falling back on persistent store based archive.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320136: Class {0} could not be instrumented, due to reason: "{1}".
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320137: Invalid class inclusion pattern(s) for instrumentation monitor {1} in scope {0}. Disabling instrumentation in scope {0}.
-
Cause: There are malformed inclusion patterns in the instrumentation monitor.
-
Action: Specify inclusion patterns in the instrumentation monitor using the correct format.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320138: Invalid class exclusion pattern(s) for instrumentation monitor {1} in scope {0}. Disabling instrumentation in scope {0}.
-
Cause: There are malformed exclusion patterns in the instrumentation monitor.
-
Action: Specify exclusion patterns in the instrumentation monitor using the correct format.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320139: Archive {0} is not found during a data retirement operation.
-
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.
Level: 1
Type: WARNING
Impact: Diagnostics
- BEA-320151: The instance name {0} in the Watch configuration {1} is invalid.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320152: An unexpected exception occurred while removing the set of watched metrics "{0}" from the harvester: {1}
-
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: Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Diagnostics
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Diagnostics
- BEA-320154: Class redefinition failed after instrumentation configuration was changed for application "{0}" : {1}
-
Cause: An unexpected exception occurred while redefining classes after the instrumentation configuration was updated.
-
Action: Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320155: Inconsistent instrumentation handling information was specified in the same pointcut definition for {0} : {1} : {2}.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320156: The renderer class {0} could not be loaded due to {1}, the following renderer will be used instead: {2}.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- 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.
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320163: Wildcarded types are not allowed to be marked as being insensitive with %
-
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.
Level: 1
Type: ERROR
Impact: Diagnostics
- BEA-320300: The WLS ServerRuntime MBeanServer was not available for harvesting; custom MBean harvesting will not be available.
-
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.
Level: 1
Type: ERROR
Impact: DiagnosticsHarvester
- BEA-320301: The WLDF Harvester could not activate the Watch and Notifications framework due to an exception: {0}
-
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.
Level: 1
Type: ERROR
Impact: DiagnosticsHarvester
- 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.
-
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.
Level: 1
Type: WARNING
Impact: DiagnosticsHarvester
- BEA-320304: The following errors were reported during the validation of the metrics for watched values {0}: {1}
-
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.
Level: 1
Type: WARNING
Impact: DiagnosticsHarvester
- BEA-320305: The instance name {0} is not a valid ObjectName or instance name pattern.
-
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.
Level: 1
Type: ERROR
Impact: DiagnosticsHarvester
- 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.
-
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.
Level: 1
Type: NOTIFICATION
Impact: LoggingService
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: DiagnosticsRuntimeControl
- BEA-320913: Failed to register Attribute Change listener {0} for MBean type {1} on server {2}.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320923: Error creating JMX Monitor {0} of type {1} for MBean {2}.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320928: SNMP Agent initialization failed while accessing server information for the configured Domain.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320939: An error occurred while adding a row to the SNMP table for MBean {1} of type {0}.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320940: An error occurred while deleting the row from the SNMP table for MBean {0}.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320941: An SNMP message was received over the default channel instead of the dedicated SNMP channel.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320943: The specified attribute name {1} is not valid for the given type {0}.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320944: The SecurityName attribute is not specified for the SNMPTrapDestination {0}.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320946: The SNMP Agent {0} is already deployed to server {1}.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320947: The AuthenticationProtocol for SNMP Agent {0} cannot be noAuth when PrivacyProtocol {1} is specified.
-
Cause: An invalid combination of authentication and privacy protocols was configured.
-
Action: Specify either MD5 or DES as the AuthenticationProtocol in combination with Privacy.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320948: The SNMPTrapDestinationMBean {0} has a higher SecurityLevel {1} than the SNMPAgent's SecurityLevel {2}.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- 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.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- 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}.
-
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.
Level: 1
Type: ERROR
Impact: SNMP
- BEA-320953: The SNMP Agent has been started on port {0}.
-
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.
Level: 1
Type: NOTIFICATION
Impact: SNMP
- 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.
-
Cause: The configuration-support stanza was missing or has XML errors.
-
Action: Correct the weblogic-extension.xml file and redeploy the application.
Level: 1
Type: WARNING
Impact: CustomModule
- 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.
-
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.
Level: 1
Type: ERROR
Impact: CustomModule
- BEA-420002: The addAssociation method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420003: The addAssociation method encounters some usage error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420004: The removeAssociation method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420005: The registerInterceptionPointNameDescription method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420006: The registerInterceptionPoint method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420007: The registerInterceptionPoint method encountered a usage error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420008: The unRegisterInterceptionPoint method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420009: The registerProcessorType method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420011: The addProcessor method encountered a usage error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420012: The removeProcessor method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420013: The getAssociationHandle method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420014: The getProcessorHandles method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420015: The getProcessorHandle method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420016: The registerInterceptionPointNameDescriptionListener method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420017: The removeAssociation method encountered an input error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420019: The process method encountered a usage error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420026: The unregisterInterceptionPoint method encountered a usage error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420027: The interception point name argument is invalid due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420029: The registerProcessorType method encountered a usage error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420030: The registerProcessorType method encountered a usage error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-420031: The process method encountered a usage error due to "{0}".
-
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.
Level: 1
Type: ERROR
Impact: MIExceptions
- BEA-1000003: The filter passed into the registerDependencyWithFilter method is null.
-
Cause: The user passed null in as the filter to the method registerDependencyWithFilter.
-
Action: Modify the code such that it does not pass null in as the filter to the method registerDependencyWithFilter.
Level: 1
Type: WARNING
Impact: ServiceHelper
- BEA-1000004: The filter passed into the registerDependencyWithFilter method is null.
-
Cause: The user passed null in as the filter to the method registerDependency.
-
Action: Modify the code such that it does not pass null in as the filter to the method registerDependency.
Level: 1
Type: WARNING
Impact: ServiceHelper
- BEA-1000006: The timer expired while waiting for a service object with filter "{0}".
-
Cause: The service object corresponding to the given filter was not available within the specified timeout.
-
Action: Ensure the service is available in the timeout period.
Level: 1
Type: WARNING
Impact: ServiceHelper
- BEA-1000008: Could not find a setter named "{0}" for type "{1}" on an object of type "{2}".
-
Cause: There was no method of the given name of the given type on the given class.
-
Action: Ensure the setter name is correct. Ensure the object upon which it is looking for such a method has the method.
Level: 1
Type: WARNING
Impact: ServiceHelper
- BEA-2011101: An unexpected Exception occurred in harvester {0}. Logging it here and continuing processing... Context: {1}, Exception: {2}
-
Cause: An unexpected exception occurred during the harvesting process.
-
Action: You should attempt to uncover the reason for the underlying Exception.
Level: 1
Type: WARNING
Impact: HarvesterJMX
- BEA-2011102: An unexpected condition was encountered in harvester {0}. Logging it here and continuing processing... Context: {1}
-
Cause: An unexpected condition occurred during the harvesting process.
-
Action: The user should attempt to uncover the reason for the problem.
Level: 1
Type: WARNING
Impact: HarvesterJMX
- 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.
-
Cause: This is an internal error.
-
Action: Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: MBeanTypingUtil
- BEA-2012306: {1} Unable to process the {2} of MBean: {0} due to internal errors. The managed process might be shutting down. Stack trace: {3}
-
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.
Level: 1
Type: ERROR
Impact: MBeanTypingUtil
- BEA-2012307: {1} Unable to process the {2} of MBean: {0} due to internal errors. The managed process appears to be shutting down. Stack trace: {3}
-
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.
Level: 1
Type: WARNING
Impact: MBeanTypingUtil
- BEA-2012308: An uexpected error occurred while scheduling work for MBeanTypeUtil instance {0} with work manager {1}: {2}
-
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.
Level: 1
Type: ERROR
Impact: MBeanTypingUtil
- BEA-2012309: An uexpected error occurred while communicating with the MBeanServer: {0}
-
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.
Level: 1
Type: ERROR
Impact: MBeanTypingUtil
- BEA-2150007: Cannot find configuration for referenced message filter {0}; check message-filter in the PubSub server configuration.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Pubsub Server
- 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.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Pubsub Server
- BEA-2150009: Invalid message-filter configured: message-filter {0} is configured in PubSub server configuration, but its associated class {1} cannot be initialized correctly.
-
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.
Level: 1
Type: ERROR
Impact: HTTP Pubsub Server
- BEA-2150015: Client {0} has no permission to subscribe channel {1}
-
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.
Level: 1
Type: ERROR
Impact: HTTP Pubsub Server
- BEA-2150016: Client {0} has no permission to publish on channel {1}
-
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.
Level: 1
Type: ERROR
Impact: HTTP Pubsub Server
- BEA-2150024: Unknown meta channel found from Bayeux message: {0}
-
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.
Level: 1
Type: ERROR
Impact: HTTP Pubsub Server
- BEA-2150025: System property {0} is not set to specify an MBeanManagerFactory implementation.
-
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.
Level: 1
Type: WARNING
Impact: HTTP Pubsub Server
- BEA-2150030: Cannot fetch JSON message from incoming request
-
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.
Level: 1
Type: ERROR
Impact: HTTP Pubsub Server
- BEA-2150043: Security authorization has been disabled for the 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.
Level: 1
Type: WARNING
Impact: HTTP Pubsub Server
- BEA-2152001: Cannot create a default JmsProviderFactory instance.
-
Cause: The class loader could not find the default JmsProviderFactory class in the classpath or the default JmsProviderFactory class has no public non-argument constructor.
-
Action: No action is required.
Level: 1
Type: ERROR
Impact: HTTP Pubsub Server JMS support
- BEA-2152002: Cannot create JmsProviderFactory instance for given class name [{0}].
-
Cause: The class loader could not find {0} in the classpath or {0} has no public no-argument constructor.
-
Action: Ensure that the correct JmsProviderFactory class name is used.
Level: 1
Type: ERROR
Impact: HTTP Pubsub Server JMS support
- BEA-2152021: Try to initialize JmsProvider using the following configurations: JmsProviderUrl -> [{0}]; ConnectionFactoryJndiName -> [{1}]; TopicJndiName -> [{2}].
-
Cause: This is an informational message.
-
Action: No action is required.
Level: 1
Type: NOTIFICATION
Impact: HTTP Pubsub Server JMS support
- BEA-2156002: Attribute "{0}": duration value "{1}" is not valid: {2}
-
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.
Level: 1
Type: ERROR
Impact: WebLogicDescriptorWL
- BEA-2156003: Attribute "{0}": logical store name value "{1}" is not valid.
-
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.
Level: 1
Type: ERROR
Impact: WebLogicDescriptorWL
- BEA-2156004: Attribute "{0}": JNDI name value "{1}" is not valid.
-
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.
Level: 1
Type: ERROR
Impact: WebLogicDescriptorWL
- 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.
-
Cause: The required version attribute was missing.
-
Action: Add the version attribute with the appropriate JEE version value.
Level: 1
Type: WARNING
Impact: Munger
- 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.
-
Cause: The plan contained no matching variable overrides.
-
Action: No action is required. This is an informational message. It may be an expected action.
Level: 1
Type: NOTIFICATION
Impact: Munger
- BEA-2156207: The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.
-
Cause: The plan contained matching variable overrides.
-
Action: No action is required. This is an informational message used to troubleshoot deployment plan overrides.
Level: 1
Type: NOTIFICATION
Impact: Munger
- BEA-2156208: The variable assignment from the deployment plan with variable name "{0}" and XPath "{1}" will be included when overriding the deployment configuration.
-
Cause: The plan contained matching variable overrides.
-
Action: No action is required. This is an informational message used to troubleshoot deployment plan overrides.
Level: 1
Type: NOTIFICATION
Impact: Munger
- BEA-2156214: The XPath "{0}" specifies a key selection but the bean "{1}" does not have any keys defined.
-
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.
Level: 1
Type: ERROR
Impact: Munger
- BEA-2156215: Removed the value matched by the deployment plan variable "{0}" with element name "{1}".
-
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.
Level: 1
Type: NOTIFICATION
Impact: Munger
- BEA-2156216: The deployment plan operation failed because there was no method named "{0}" on the bean "{1}" corresponding to the element "{2}".
-
Cause: A deployment plan operation requires a corresponding destroy, remove, or set method. This method was not present.
-
Action: Contact My Oracle Support.
Level: 1
Type: ERROR
Impact: Munger
- BEA-2156217: An error occurred while performing the plan operation for variable "{0}" with element name "{1}" : {2}.
-
Cause: An unexpected exception occurred during the deployment plan operation.
-
Action: Check the associated exception to determine the cause, and correct the issue.
Level: 1
Type: ERROR
Impact: Munger
- BEA-2156218: Updated the element matched by the deployment plan variable "{0}" with element name "{1}" to have value "{2}".
-
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.
Level: 1
Type: NOTIFICATION
Impact: Munger
- BEA-2156219: Created the element matched by the deployment plan variable "{0}" with element name "{1}".
-
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.
Level: 1
Type: NOTIFICATION
Impact: Munger
- BEA-2156220: Created the element matched by the deployment plan variable "{0}" with element name "{1}" to have name "{2}".
-
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.
Level: 1
Type: NOTIFICATION
Impact: Munger
- 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.
-
Cause: The specified array index was larger than the size of the array.
-
Action: No action is required. This is an informational message.
Level: 1
Type: NOTIFICATION
Impact: Munger
- BEA-2156222: The variable "{0}" specifies a property "{1}" that is a primitive array but no index is specified in the XPath.
-
Cause: The specified XPath value was invalid since no array index was defined for this element.
-
Action: Check the XPath, and specify an index.
Level: 1
Type: ERROR
Impact: Munger
- BEA-2156223: The variable "{0}" for the add operation does not specify a property in the XPath "{1}". This variable assignment has been ignored.
-
Cause: The specified XPath value was invalid since no property was specified for the add operation.
-
Action: Check the XPath, and specify a property.
Level: 1
Type: WARNING
Impact: Munger
- BEA-2156224: Added the element matched by the deployment plan variable "{0}" with element name "{1}" with value "{2}".
-
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.
Level: 1
Type: NOTIFICATION
Impact: Munger
- BEA-2156226: Skipping the override for the deployment plan variable "{0}" and XPath "{1}" since the value is not set in the deployment plan.
-
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.
Level: 1
Type: NOTIFICATION
Impact: Munger
- 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.
-
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.
Level: 1
Type: WARNING
Impact: WebLogicJavaEEDescriptorValidator
- BEA-2156300: Coherence JAR is in the system classpath and there are more than one CoherenceClusterSystemResourceMBean defined using {0}
-
Cause: Multiple CoherenceClusterSystemResourceMBean were targeted.
-
Action: When the Coherence JAR is in the system classpath, only one CoherenceClusterSystemResourceMBean should be targeted to the server.
Level: 1
Type: NOTIFICATION
Impact: CacheProvider
- BEA-2156400: The validation.xml file, located at {0}, does not conform to the JSR 303 specifications.
-
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.
Level: 1
Type: WARNING
Impact: Weblogic-Validation
- BEA-2159000: An exception occurred while the listener {1} processed event {0}. The error is {1}.
-
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.
Level: 1
Type: WARNING
Impact: InternalEventBus
- BEA-2159001: An exception occurred while initializing WLS internal event bus {0}. The error is {1}.
-
Cause: Refer to the embedded exception information for more details as to the probable cause of this error.
-
Action: This is an internal error and should be reported as a bug to My Oracle Support.
Level: 1
Type: ERROR
Impact: InternalEventBus
- BEA-2159002: An exception occurred while loading the listener class {0}. The error is {1}. This listener will not be registered.
-
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.
Level: 1
Type: WARNING
Impact: InternalEventBus
- BEA-2159003: An exception occurred while instantiating an instance of listener class {0}. The error is {1}. This listener will not be registered.
-
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.
Level: 1
Type: WARNING
Impact: InternalEventBus
- BEA-2159004: An exception occurred while registering listeners defined as resources. The error is {1}.
-
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.
Level: 1
Type: WARNING
Impact: InternalEventBus
- BEA-2160000: Context "{0}" is not a web context. Spring runtime MBeans cannot be created.
-
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.
Level: 1
Type: WARNING
Impact: WeblogicSpring
- 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.
-
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.
Level: 1
Type: WARNING
Impact: Application Client
- BEA-2162500: Class, {0}, was compiled with an incompatible version of Java. Make sure that all the classes needed by the application have been compiled with a compatible java version. {1}
-
Cause: Class compiled with an incompatible Java compiler version.
-
Action: Insure that this and other classes are compiled with a compiler that is compatible with the JVM used by the application server.
Level: 1
Type: ERROR
Impact: Class Loaders
- BEA-2163002: OSGi system {0} could not install bundles from $WL_HOME/server/osgi-lib.
-
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.
Level: 1
Type: ERROR
Impact: OSGi
- 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.
-
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.
Level: 1
Type: ERROR
Impact: OSGi
- 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.
-
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.
Level: 1
Type: ERROR
Impact: OSGi