|
BEA-000100(retired)
|
Info: Using default multicast address: address
|
Description
| Server is going to use default multicast address: address to send heartbeat messages and JNDI announcements.
|
|
Cause
| If you create a cluster without specifying a cluster address, by default, servers use multicast address 237.0.0.1
|
|
Action
| Please 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).
|
|
|
BEA-000101
|
Info: Cannot resolve ClusterAddress: address
|
Description
| Failed to resolve ClusterAddress: address.
|
|
Cause
| Could not resolve the cluster address address. ClusterAddress should be a DNS name that maps to multiple IP addresses.
|
|
Action
| Set the correct ClusterAddress property for the cluster.
|
|
|
BEA-000102
|
Notice: Joining cluster name on address:port
|
Description
| This is an informational message to indicate that the server has joined the cluster.
|
|
Cause
| Server has joined cluster name.
|
|
Action
| No action required.
|
|
|
BEA-000103
|
Info: Disconnecting from cluster clusterName
|
Description
| Disconnecting from cluster clusterName
|
|
Cause
| When a server gets suspended, it is no longer a member of cluster clusterName.
|
|
Action
| No action required.
|
|
|
BEA-000104
|
Error: Cluster members are running incompatible versions. \n\tLocal version: localVersion. \n\tRemote version (remoteServer): remoteVersion
|
Description
| Cluster members are running incompatible versions. \n\tLocal version: localVersion. \n\tRemote version (remoteServer): remoteVersion
|
|
Cause
| This server is a different version than other servers in this cluster.
|
|
Action
| Ensure that all members of this cluster are running the same version.
|
|
|
BEA-000105
|
Info: The server is leaving the cluster, because it is an incompatible version.
|
Description
| 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.)
|
|
|
BEA-000106(retired)
|
Error: Failed to move offer to pending list due to e.
|
Description
| Failed to move offer to pending list due to e.
|
|
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 BEA support and provide the stack trace for further analysis.
|
|
|
BEA-000107
|
Error: Failed to install offer in place of those currently installed due to e.
|
Description
| Failed to install offer in place of those currently installed due to e.
|
|
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 BEA support and provide the stack trace for further analysis.
|
|
|
BEA-000108
|
Error: Attempt to retract offer offer, which is neither installed nor pending.
|
Description
| An attempt was made to retract an offer, which was neither previously installed nor is in the conflict resolution stage.
|
|
Cause
| An attempt was made to retract an offer, which was neither previously installed nor is in the conflict resolution stage.
|
|
Action
| No action required.
|
|
|
BEA-000109
|
Error: An error occurred while sending multicast message: e
|
Description
| An IO error occurred while trying to send a message over multicast.
|
|
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 BEA support and provide the stack trace for further analysis.
|
|
|
BEA-000110
|
Error: Multicast socket receive error: e
|
Description
| An error occurred while trying to receive a message over the multicast.
|
|
Cause
| An error occurred while trying to receive a message over the multicast.
|
|
Action
| Make sure that the NIC is functioning properly. If you believe there no environment problems exist, contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-000111
|
Info: Adding server with ID id to cluster: clusterName view.
|
Description
| Adding server with ID id to cluster: clusterName view.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-000112
|
Info: Removing server from cluster view due to timeout.
|
Description
| Every server in the cluster sends heartbeat messages every 10 seconds over the multicast. Failure to receive such messages for three timeout periods results in removal of the server from the cluster view.
|
|
Cause
| Removing server from cluster as it failed to send heartbeats over the multicast in the past 30 seconds.
|
|
Action
| If a server has been shutdown or suspended, no action is required. If the remote server server appears to be hung, take threaddumps and send them to BEA support.
|
|
|
BEA-000113
|
Info: Removing server from cluster view due to PeerGone.
|
Description
| Servers in a cluster might have a direct connection over tcp/ip. Failure of this connection results in removing the server from the cluster view.
|
|
Cause
| Lost tcp/ip connection to server server.
|
|
Action
| If a server has been shutdown or suspended, no action is required. If the remote server server appears to be hung, take threaddumps and send them to support.
|
|
|
BEA-000114
|
Error: Failed to find cluster license: message
|
Description
| Failed to find cluster license: message in the license file.
|
|
Cause
| You need a valid license file to run clusters.
|
|
Action
| Contact your sales representative for a valid license.
|
|
|
BEA-000115
|
Info: Lost numMessages multicast message(s).
|
Description
| Server failed to receive numMessages messages.
|
|
Cause
| This is an informational message. When a server joins a stable cluster, you will see this message since it did not receive multicast messages sent out by servers in the cluster.
|
|
Action
| No action required.
|
|
|
BEA-000116
|
Error: Failed to join cluster name at address address due to: e.
|
Description
| Failed to join cluster name at address address due to: e. Servers in a cluster use multicast to determine cluster membership. Set a valid multicast address and try again.
|
|
Cause
| This happens if you specify an incorrect multicast address for the cluster. Use an address in the range of 224.0.0.0 - 239.255.255.255. (Avoid the reserved range 224.0.0.0 - 224.0.1.255.)
|
|
Action
| Set a valid multicast address and try again.
|
|
|
BEA-000117
|
Error: Received a stale replication request for object id.
|
Description
| A server with an older version of session data tried to corrupt the session data.
|
|
Cause
| This happens when a network problem exists, or one of the servers is taking a long time to collect garbage, causing the vm to freeze.
|
|
Action
| Tune garbage collection so that it does not pause. If the problem still persists, contact BEA support at support@beasys.com.
|
|
|
BEA-000118
|
Info: Lost numLost replication updates of object id.
|
Description
| Lost numLost replication updates of object id on secondary server. Primary server will recreate session and bring session state in sync with primary.
|
|
Cause
| If the secondary failed to receive some of the updates, it indicates this to the primary server by throwing a NotFoundException to the primary so that the primary server can recreate the session state.
|
|
Action
| No action required.
|
|
|
BEA-000119
|
Emergency: Missing multicast address for cluster: clusterName. Please 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.)
|
Description
| Missing multicast address for cluster: clusterName. Please 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
| Cluster does not have a defined multicast address.
|
|
Action
| Specify a valid multicast address.
|
|
|
BEA-000120
|
Error: Received error while creating Cluster RuntimeMBean.
|
Description
| Failed to create ClusterRuntimeMBean. Check configuration for accuracy.
|
|
Cause
| The JMX framework failed to initialize the Cluster RuntimeMBean.
|
|
Action
| Check your cluster configuration. If you believe there are no configuration problems, contact BEA support.
|
|
|
BEA-000121
|
Error: Two domains in the same LAN should not use the same multicast address. Domains in conflict are domainOne and domainTwo.
|
Description
| Two domains in the same LAN should not use the same multicast address. Domains in conflict are domainOne and domainTwo.
|
|
Cause
| Two clusters on the local area network are using the same multicast address.
|
|
Action
| Change the multicast address of either domain domainOne or domainTwo.
|
|
|
BEA-000122
|
Error: Clusters clusterOne and clusterTwo cannot use the same multicast address.
|
Description
| Clusters clusterOne and clusterTwo cannot use the same multicast address. Specify different multicast address for each cluster.
|
|
Cause
| Multiple clusters in the same domain are using the same multicast address.
|
|
Action
| For efficiency purposes, it would be better to use two different multicast addresses.
|
|
|
BEA-000123
|
Error: Conflict start: You tried to bind an object under the name bindName in the JNDI tree. The object bindObject 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.
|
Description
| Conflict start: You tried to bind an object under the name bindName in the JNDI tree. The object bindObject 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
| Your cluster is not homogeneous. Two servers in the cluster are providing different services under the same name bindName. 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, when you bind it into the JNDI tree, set the replicate bindings property to false.
|
|
|
BEA-000124
|
Error: Conflict start: The object bindObject you tried to bind under the name bindName in the JNDI tree is clusterable but is incompatible. Make sure all the servers in the cluster use the identical copy of object.
|
Description
| Conflict start: The object bindObject you tried to bind under the name bindName in the JNDI tree is clusterable but is incompatible. Make sure all the servers in the cluster use the identical copy of object.
|
|
Cause
| The object bindObject is clusterable. However, it implements different or incompatible interfaces on different servers.
|
|
Action
| Make sure all the servers in the cluster use the identical copy of the object.
|
|
|
BEA-000125
|
Info: Conflict resolved: bindName for the object bindObject under the bind name bindName in the JNDI tree.
|
Description
| Conflict resolved: bindName for the object bindObject under the bind name bindName in the JNDI tree.
|
|
Cause
| Conflict was resolved as a result of corrective action taken.
|
|
Action
| No action required.
|
|
|
BEA-000126
|
Error: All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.
|
Description
| All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.
|
|
Cause
| Objects in the session are not serializable or externalizable.
|
|
Action
| Make sure all user-defined objects in the HTTP session are serializable.
|
|
|
BEA-000127
|
Info: Adding name to the cluster.
|
Description
| Adding name to the cluster.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-000128
|
Info: Updating name in the cluster.
|
Description
| Updating name in the cluster with new attributes.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-000129
|
Info: Removing name from the cluster.
|
Description
| Removing name from the cluster due to peergone or timeout.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required unless you did not shutdown a server.
|
|
|
BEA-000131(retired)
|
Error: An error occurred in the JNDI Naming Event Listener while de-serializing messages:Message. Exception was:t.
|
Description
| An error occurred in JNDI Naming Event Listener while de-serializing messages:Message. Exception was:t.
|
|
Cause
| Possible causes are not listed.
|
|
Action
| This is an internal error. Contact support and provide the stack trace for further analysis.
|
|
|
BEA-000132(retired)
|
Emergency: Invalid multicast port for cluster: listenPort. Set the MulticastPort for the cluster or the ListenPort for the server with a valid number (e.g. 1 - 65534).
|
Description
| Invalid multicast port for cluster: listenPort. Set the MulticastPort for the cluster or the ListenPort for the server with a valid number (e.g. 1 - 65534).
|
|
Cause
| Port listenPort is not in the valid range 1 - 65534.
|
|
Action
| Set the multicast port to a valid number between 1 - 65534.
|
|
|
BEA-000133
|
Notice: Waiting to synchronize with other running members of clusterName.
|
Description
| Waiting to synchronize with other running members of the cluster.
|
|
Cause
| The cluster member is waiting to synchronize cluster information with other cluster members before completing startup and entering running mode.
|
|
Action
| No action required.
|
|
|
BEA-000134(retired)
|
Notice: Discovered and synchronized with reporting other running members of clusterName.
|
Description
| Message is retired.
|
|
Cause
| A cluster member has finished exchanging cluster information with other cluster members.
|
|
Action
| No action required.
|
|
|
BEA-000135(retired)
|
Warning: Cluster.MemberWarmupTimeoutSeconds was reached before this server was able to synchronize with all discovered servers in clusterName. missing/total servers failed to synchronize. This may indicate multicast packet loss or that servers have failed.
|
Description
| Retired message.
|
|
Cause
| Cluster member failed to synchronize with some or all of the other members during the MemberWarmupTimeoutSeconds.
|
|
Action
| Check for multicast packet loss. If the multicast setup is fine, check the server logs for cluster-related errors and take action as indicated. Enable cluster debugging for detailed information.
|
|
|
BEA-000136(retired)
|
Warning: Discovered but failed to synchronize with server.
|
Description
| Retired message.
|
|
Cause
| Cluster member failed to synchronize with server.
|
|
Action
| Check for multicast packet loss. If the multicast setup is fine, check the server logs for cluster-related errors and take action as indicated.
|
|
|
BEA-000137
|
Error: Error sending multicast message: msg.
|
Description
| Error sending multicast message: msg.
|
|
Cause
| Failed to send multicast message due to IOException.
|
|
Action
| Enable cluster debugging to see a detailed message.
|
|
|
BEA-000138
|
Notice: Listening for announcements from cluster name on address:port.
|
Description
| Listening for announcements from cluster name on address:port.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-000139
|
Error: There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name name and they are using the same address address and port port.
|
Description
| There are two clusters in the network that are possibly running different versions of WebLogic Server. These two clusters probably have the same name name and they are using the same address address and port port.
|
|
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 name and they are using the same address address and port port.
|
|
Action
| Change multicast address and/or multicast port.
|
|
|
BEA-000140
|
Error: Failed to deserialize statedump from server serverName with e.
|
Description
| Could not locate all the classes required to deserialize JNDI statedump.
|
|
Cause
| Server failed to deserialize object since it does not have the class definition. This usually happens if your 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
| Make sure all the classes are available on all the nodes of the cluster.
|
|
|
BEA-000141
|
Error: TCP/IP socket failure occurred while fetching statedump over HTTP from serverName.
|
Description
| TCP/IP socket failure occurred while fetching statedump over HTTP from serverName with e.
|
|
Cause
| An IOException occurred in the OS.
|
|
Action
| Make sure that no problems exist in the network. If the problem persists, contact BEA support with the stack trace for further analysis.
|
|
|
BEA-000142
|
Notice: Trying to download cluster JNDI tree from server serverName.
|
Description
| When a server boots in a cluster, it detects running members of the cluster and fetches the JNDI tree bindings of the entire cluster.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-000143
|
Notice: Trying to download JNDI tree from a server listening on serverAddress.
|
Description
| A server listening on serverAddress is participating in the cluster. This server does not have information about the services offered by the other server. To synchronize this information and make the missed JNDI announcements visible in this JNDI tree, the server makes an HTTP request to populate the JNDI tree.
|
|
Cause
| This is an informational message.
|
|
Action
| If you continue to receive this message, make sure that the network is stable. Contact BEA support for further assistance.
|
|
|
BEA-000144
|
Info: Managed server serverName has been suspended or shutdown.
|
Description
| Managed server serverName has been suspended. It is no longer part of the running cluster.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-000145
|
Error: Managed server serverName is tagged as a migratable server. A cluster that has migratable servers should configure a JDBC DataSource to ensure that the migratable server is highly available.
|
Description
| Managed server serverName is tagged as a migratable server. A cluster that has migratable servers should configure a JDBC DataSource to ensure that the migratable server is highly available.
|
|
Cause
| Mis-configuration.
|
|
Action
| Please configure DataSourceForAutomaticMigration property.
|
|
|
BEA-000146(retired)
|
Error: In the cluster dsName, JDBCDataSource clusterName cannot be reached by all the nodes in the cluster.
|
Description
| In the cluster dsName, JDBCDataSource clusterName cannot be reached by all the nodes in the cluster.
|
|
Cause
| Mis-configuration.
|
|
Action
| Please target JDBCDataSource dsName to the entire cluster and ensure that the database is highly available.
|
|
|
BEA-000147
|
Warning: Server "name" failed to renew lease in the leaseTableOwner.
|
Description
| Server "name" failed to renew lease in the leaseTableOwner.
|
|
Cause
| Server failed to renew the lease on time.
|
|
Action
| No action required.
|
|
|
BEA-000148
|
Warning: Migratable server "name" 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 couple of machines assigned to it for automatic migration.
|
Description
| Migratable server "name" 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 couple of machines assigned to it for automatic migration.
|
|
Cause
| Mis-configuration.
|
|
Action
| Please ensure that the server is targeted to machine and restart the migratable server.
|
|
|
BEA-000149
|
Error: Server failed to get a connection to the leaseTableOwner during operation.
|
Description
| Server failed to get a connection to the leaseTableOwner during operation.
|
|
Cause
| Database or the consensus leasing basis appears to be down.
|
|
Action
| Please 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 in some other partition is not reachable.
|
|
|
BEA-000150
|
Error: Server failed to get a connection to the leaseTableOwner in the past time seconds for lease renewal. Server will shut itself down.
|
Description
| Server failed to get a connection to the leaseTableOwner in the past time seconds for lease renewal. Server will shut itself down.
|
|
Cause
| Database or consensus leasing basis appears to be down.
|
|
Action
| Please 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 in some other partition is not reachable.
|
|
|
BEA-000151
|
Info: Server "serverName" has taken over the role of Cluster Master.
|
Description
| Server "serverName" has taken over the role of Cluster Master.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-000152
|
Info: Server "serverName" lost the privileges to be the Cluster Master.
|
Description
| Server "serverName" lost the privileges to be the Cluster Master.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-000153
|
Error: 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 couple of machines assigned to it for automatic migration.
|
Description
| 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 couple of machines assigned to it for automatic migration.
|
|
Cause
| Mis-configuration.
|
|
Action
| Please assign a pool of machines for automatic migration and refer to WebLogic server documentation for more details.
|
|
|
BEA-000154
|
Error: Cluster is misconfigured. The remote cluster address address is not a valid URL.
|
Description
| Cluster is misconfigured. The remote cluster address address is not a valid URL. The remote cluster address has to be a valid url that can be reached via t3, t3s, iiop or iiops protocol.
|
|
Cause
| Mis-configuration.
|
|
Action
| Please set right the remote cluster address and restart your servers. If it is not clear on how to set remote ClusterAddress, please refer to WebLogic server configuration
|
|
|
BEA-000155
|
Notice: Configured cluster address is invalid : address. Constructing cluster address dynamically.
|
Description
| Protocol is not required in cluster address configuration. Cluster address can contain either dns name or comma separated host list(or IP list) or comma separated host:port list (or IP:port list).
|
|
Cause
| Invalid Configuration.
|
|
Action
| Protocol is not required in cluster address configuration. Cluster address can contain either dns name or comma separated host list(or IP list) or comma separated host:port list (or IP:port list).
|
|
|
BEA-000156
|
Error: Could not send out new attributes for cluster member name: ioe.
|
Description
| Could not send out new attributes for cluster member name: ioe.
|
|
Cause
| There was a problem sending out changed member attributes.
|
|
Action
| Examine the server logs.
|
|
|
BEA-000157(retired)
|
Error: Failed to restart/migrate server "serverName" to one of machines machines
|
Description
| Failed to restart/migrate server "serverName" to one of machines machines
|
|
Cause
| There was a while restarting migratable server. Please send all the servers logs to support@bea.com for further investigation.
|
|
Action
| Examine the server logs.
|
|
|
BEA-000158
|
Info: Server has stopped sending cluster heartbeats and announcements. It is still receiving heartbeats and announcements from other cluster members.
|
Description
| Server has stopped sending cluster heartbeats and announcements
|
|
Cause
| Server is going out of the cluster as a result of the suspend or shutdown operation
|
|
Action
| No action required
|
|
|
BEA-000159
|
Warning: Clocks of machines hosting local server and remote server "serverName" are off by diff seconds
|
Description
| Clocks of machines hosting local server and remote server "serverName" are off by diff seconds
|
|
Cause
| Clocks of machines hosting servers in the cluster are not synchronized.
|
|
Action
| Please make sure all the machines are synchronized to the same time.
|
|
|
BEA-000160
|
Error: Request to synchronize JNDI tree is made over a insecure channel. Please configure a secure HTTP channel for all the servers in the cluster.
|
Description
| Request to synchronize JNDI tree is made over a insecure channel. Please configure a secure HTTP channel for all the servers in the cluster.
|
|
Cause
| Cluster is configured to encrypt multicast data but the request to synchronize JNDI tree is being done on a non secure channel (HTTP). To secure the cluster completely you should configure a secure HTTP channel for all the servers in the cluster.
|
|
Action
| Please configure secure HTTP channel on all the servers in the cluster.
|
|
|
BEA-000161
|
Error: Multicast message from server serverName appears to be tampered.
|
Description
| Multicast message from server "serverName" appears to be tampered.
|
|
Cause
| We couldn"t verify the authenticity of the message.
|
|
Action
| Please ensure that your network is not being hijacked.
|
|
|
BEA-000162
|
Notice: Starting "type" replication service with remote cluster address "url"
|
Description
| Starting "type" replication service with remote cluster address "url"
|
|
Cause
| This is an informational message
|
|
Action
| No action required
|
|
|
BEA-000163
|
Notice: Stopping "type" replication service
|
Description
| Stopping "type" replication service
|
|
Cause
| This is an informational message
|
|
Action
| No action required
|
|
|
BEA-000164
|
Notice: Synchronized cluster JNDI tree from server serverName.
|
Description
| Synchronized cluster JNDI tree from server serverName.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-000165
|
Error: Some other domain has a cluster that is configured to use the same multicast address and port as a cluster in domain. Two domains in the same LAN should not use the same multicast address.
|
Description
| Some other domain has a cluster that is configured to use the same multicast address and port as a cluster in domain. 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.
|
|
|
BEA-000166
|
Error: Some other cluster in this domain is configured to use the same multicast address as cluster. Clusters cannot use the same multicast address.
|
Description
| Some other cluster in this domain is configured to use the same multicast address as cluster. Clusters cannot use the same multicast address.
|
|
Cause
| Multiple clusters in the same domain are using the same multicast address.
|
|
Action
| For efficiency purposes, it would be better to use two different multicast addresses.
|
|
|
BEA-000167
|
Error: Some services failed to rollback successfully when we tried to abort the migration: e.
|
Description
| Some services failed to rollback successfully when we tried to abort the migration: e.
|
|
Cause
| Exception that caused the rollback to fail: e
|
|
Action
| It would be safest to shutdown 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, you should be able to migrate to this server successfully.
|
|
|
BEA-000168
|
Error: Failed to restart/migrate server "serverName" because of e
|
Description
| Failed to restart/migrate server "serverName" because of e
|
|
Cause
| There was an error while restarting migratable server: e
|
|
Action
| Examine the server logs.
|
|
|
BEA-000169(retired)
|
Error: There is an entry for "serverName" in the migration tables, but there is no corresponding server configured in this domain.
|
Description
| There is an entry for "serverName" in the migration tables, but there is no corresponding server configured in this domain. We will ignore this server and not try to start it. The server should either be configured in the domain or removed from the table.
|
|
Cause
| There is an entry for "serverName" in the migration tables, but there is no corresponding server configured in this domain.
|
|
Action
| Configure the server for your domain, or delete the servers rows from the database tables.
|
|
|
BEA-000170
|
Error: Server serverName did not receive the multicast packets that were sent by itself
|
Description
| Server serverName did not receive the multicast packets that were sent by itself
|
|
Cause
| Each WLS server is expected to receive the messages it multicast to the multicast group it is part of. Since the server does not receive its own messages, it is indicative of the fact that multicast address configuration in the cluster configuration or the interface address specification may be wrong.
|
|
Action
| Please ensure that the cluster configuration and server interface configuration are valid
|
|
|
BEA-000171
|
Error: Failed to load the custom Singleton Services SQL Query Helper: queryHelperClassName, because of t.
|
Description
| Failed to load the custom Singleton Services SQL Query Helper: queryHelperClassName, because of t.
|
|
Cause
| The most likely cause for failing to load the named class is either a typo in the classs name or that the class is missing from the servers classpath.
|
|
Action
| Please ensure that the classname provided is valid, and that the class exists in the classpath of the server.
|
|
|
BEA-000172
|
Error: TCP/IP socket failure occurred while fetching statedump over HTTP from serverName. \nError message received: remoteError. \nThe request was generated by localServerDetails. \ne
|
Description
| TCP/IP socket failure occurred while fetching statedump over HTTP from serverName with e.
|
|
Cause
| An IOException occurred in the OS.
|
|
Action
| Make sure that no problems exist in the network. If the problem persists, contact BEA support with the stack trace for further analysis.
|
|
|
BEA-000173(retired)
|
Debug: message
|
Description
| message
|
|
Cause
| Informational debug.
|
|
Action
| None.
|
|
|
BEA-000174(retired)
|
Warning: message e
|
Description
| message e
|
|
Cause
| Informational warning.
|
|
Action
| None.
|
|
|
BEA-000175(retired)
|
Error: The provided script does not exist: filename. The script is used by target.
|
Description
| The provided script does not exist: filename. The script is required by target in the configuration.
|
|
Cause
| The specified file does not exist.
|
|
Action
| Check targets script values and make sure that the specified files exist as named.
|
|
|
BEA-000176
|
Error: serverName does not specify a machine.
|
Description
| serverName does not specify a machine.
|
|
Cause
| serverNames configuration does not specify what machine it is running on. Machines must be specified if scripts are to be executed when migrations happen.
|
|
Action
| Specify which machine serverName is running on in the servers console page.
|
|
|
BEA-000178
|
Error: Failed to execute scriptname because of e.
|
Description
| Failed to execute scriptname because of e.
|
|
Cause
| While trying to run scriptname, an exception occurred: e.
|
|
Action
| Check that the script, scriptname, is fully debugged. It may help to run the script by hand to see if any errors are raised.
|
|
|
BEA-000179
|
Error: target failed while altering its lease.
|
Description
| target failed while altering its lease because of e.
|
|
Cause
| An exception occurred: e.
|
|
Action
| Make sure that if a DB is being used for leasing, that it is available.
|
|
|
BEA-000180
|
Error: Unable to retrieve Job id from the database. The retrieval failed with e
|
Description
| Unable to retrieve Job id from the database. The retrieval failed with e
|
|
Cause
| An error occurred while reading a job from the database
|
|
Action
| Make sure that the classes corresponding to the job are present in the server classpath and is of the right version
|
|
|
BEA-000181
|
Debug: name
|
Description
| debug
|
|
Cause
| debug
|
|
Action
| no action
|
|
|
BEA-000182
|
Info: Job Scheduler created a job with ID id for TimerListener with description description
|
Description
| Job Scheduler created a job with ID id for TimerListener with description description
|
|
Cause
| Job Scheduler created an entry in the database for a submitted job
|
|
Action
| no action is needed.
|
|
|
BEA-000183
|
Info: Successfully cancelled job with ID id
|
Description
| Job Scheduler cancelled a job with ID id
|
|
Cause
| Job Scheduler removed a job entry from database based on application request
|
|
Action
| no action is needed.
|
|
|
BEA-000184
|
Warning: This server did not attempt to renew its lease for seconds seconds. The server may restarted or migrated.
|
Description
| This server did not attempt to renew its lease for seconds seconds. The server may 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.
|
|
|
BEA-000185
|
Info: 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.
|
Description
| 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 needed.
|
|
|
BEA-000186
|
Error: An error was encountered while migrating serviceName: e
|
Description
| An error was encountered while migrating serviceName: e
|
|
Cause
| e
|
|
Action
| Make sure that there are enough candidate servers in the cluster alive.
|
|
|
BEA-000187
|
Info: The Singleton Service serviceName is now registered on this server. This server may be chosen to host this service.
|
Description
| The Singleton Service serviceName is now registered on this server. This means that this server is now a candidate to host this service. The service is NOT active at the moment. A different message will be printed if it becomes active on this server.
|
|
Action
| No action required.
|
|
|
BEA-000188
|
Info: The Singleton Service serviceName is no longer registered on this server.
|
Description
| The Singleton Service serviceName is no longer registered on this server. This means that this server is no longer a candidate to host this service. If the service was active, it has been deactivated by the time this message has been printed.
|
|
Action
| No action required.
|
|
|
BEA-000189
|
Info: The Singleton Service serviceName is now active on this server.
|
Description
| The Singleton Service serviceName is now active on this server.
|
|
Action
| No action required.
|
|
|
BEA-000190
|
Info: The Singleton Service serviceName has been deactivated on this server.
|
Description
| The Singleton Service serviceName has been deactivated on this server.
|
|
Action
| No action required.
|
|
|
BEA-000191
|
Info: Now monitoring the Migratable Server serverName
|
Description
| This server is now monitoring the Migratable Server serverName. If serverName becomes unavailable or crashes, it will be migrated to a new machine.
|
|
Action
| No action required.
|
|
|
BEA-000192
|
Warning: No currently living server was found that could host serviceName. The server will retry in a few seconds.
|
Description
| All living servers were asked to host serviceName, but none successfully activated the service. Make sure that there is at least one candidate server for this service active, and that there is no bug in the activate() method.
|
|
Cause
| All currently living servers failed when asked to activate serviceName.
|
|
Action
| Make sure that there is at least one candidate server for this service active, and that there is no bug in the activate() method. The service will be tried on all living servers in another few seconds.
|
|
|
BEA-000193
|
Error: The JTA service for serverName has failed, but serverName is still running. JTA cannot be migrated from a running server.
|
Description
| The JTA service for serverName has failed, but serverName is still running. JTA cannot be migrated from a running server.
|
|
Cause
| The JTA service failed. Please check the logs of serverName.
|
|
Action
| serverName should be restarted once the cause of the error has been determined and fixed. Upon restart, the JTA service will be migrated and running transactions recovered.
|
|
|
BEA-000194
|
Warning: An error was encountered while trying to report a migration event: e.
|
Description
| An error was encountered while trying to report a migration event: e.
|
|
Cause
| The most likely cause is the administration server being unavailable. If this is intended, this message can be ignored.
|
|
Action
| If monitoring information is desired, the administration server should be running and reachable.
|
|
|
BEA-000195
|
Warning: An error was encountered while trying to save a migration event. The error was: e
|
Description
| An error was encountered while trying to save a migration event. The error was: e
|
|
Cause
| An internal error occurred while trying to create a runtime MBean to encapsulate this data.
|
|
Action
| Contact BEA support and provide the stack trace for further analysis.
|
|
|
BEA-000196
|
Warning: Received data about a migration of type type, but no such type is recognized by the admin server.
|
Description
| Received data about a migration of type type, but no such type is recognized by the admin server.
|
|
Cause
| If the managed servers have been upgraded to a newer version of WebLogic, they may be reporting data that the admin server does not know how to handle.
|
|
Action
| Upgrade the admin server to the same version as the cluster members.
|
|
|
BEA-000197
|
Notice: Listening for announcements from cluster using unicast cluster messaging
|
Description
| Listening for announcements from cluster using unicast cluster messaging
|
|
Cause
| Unicast cluster messaging mode is enabled
|
|
Action
| none required
|
|
|
BEA-000198
|
Error: All Replication calls for cluster clusterName must be made over channel channel
|
Description
| All Replication calls for cluster clusterName must be made over channel channel
|
|
Cause
| All Replication calls for cluster clusterName must be made over channel channel
|
|
Action
| Check the configured channel for Replication calls.
|
|
|
BEA-000199
|
Error: Replication calls can only be made by rights over channelType channel
|
Description
| Replication calls can only be made by rights over channelType channel
|
|
Cause
| Replication calls can only be made by rights over channelType channel
|
|
Action
| Check the roles of the users for whom the replication calls are being made.
|
|
