The Cluster1.0 catalog contains messages in the range
BEA-003101 - BEA-003199. Messages in this catalog are part of the
weblogic.cluster
Internationalization package and the weblogic.cluster Localization package.
|
BEA-003101
|
Warning: Modified non-dynamic propertyName property on Admin server.
|
Description
| Updated non-dynamic propertyName property on Admin server. Change will be made to config.xml but new value will not take effect till the server is rebooted. |
|
Cause
| Updated non-dynamic propertyName property while server was in running state. |
|
Action
| Reboot Admin server for propertyName property to take effect. |
|
|
BEA-003102
|
Error: There was a failure in the execution of the post script script while deactivating MigratableTarget mt. Since post script failure is marked as fatal, so the MigratableTarget will not be automatically migrated. To enable automigration, please fix the post script failure and manually migrate the failed migratable target or disable post script failure fatal flag.
|
Description
| There was a failure in the execution of the post script script while deactivating MigratableTarget mt. Since post script failure is marked as fatal, so the MigratableTarget will not be automatically migrated. To enable automigration, please fix the post script failure and manually migrate the failed migratable target or disable post script failure fatal flag. |
|
Cause
| Execution of post deactivation script failed. |
|
Action
| Fix the post deactivation script and migrate the MigratableTarget manually. |
|
|
BEA-003103
|
Error: target failed to release its lease because of e. This may affect its automatic migration behaviour.
|
Description
| target failed to release its lease because of e. This may affect its automatic migration behaviour. |
|
Cause
| An exception occurred: e. |
|
Action
| Make sure that if a DB is being used for leasing, that it is available. |
|
|
BEA-003104
|
Error: Failed to notify the execution failure of the post script postScript for target to the SingletonServiceStateManager because of e.This may affect its automatic migration behaviour.
|
Description
| Failed to notify the execution failure of the post script postScript for target to the SingletonServiceStateManager because of e.This may affect its automatic migration behaviour. |
|
Cause
| An exception occurred: e. |
|
Action
| Make sure that the network is working fine. |
|
|
BEA-003105
|
Warning: The async replication request timed out attempting to add object id to the replication queue. This session has not been replicated to any backup at this point.
|
Description
| The async replication request timed out attempting to add object id 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 onto the queue and will not be replicated at this time. |
|
Cause
| The async replication request timed out attempting to add object id 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 onto the queue and will not be replicated at this time. |
|
Action
| This could be due to your secondary server or persistent store slowing down the replication process. In order to better handle this the SessionFlushInterval and the SessionFlushThreshold can be reduced to replicate less at a time, and replicate more often. Also, checking the performance of your secondary server or persitent store is advised. |
|
|
BEA-003106
|
Warning: An unexpected exception occured during replication: t. Future session updates should replicate as expected.
|
Description
| An unexpected exception occured during replication: t. Future session updates should replicate as expected. |
|
Cause
| An unexpected runtime exception occured during replication probably from the rmi stub. Future session updates should replicate as expected. |
|
Action
| Make sure that no problems exist in the network. If the problem persists, contact Oracle Customer Support with the stack trace for further analysis. |
|
|
BEA-003107
|
Info: Lost numMessages unicast 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 unicast messages sent out by servers in the cluster. |
|
Action
| No action required. |
|
|
BEA-003108
|
Error: Unicast receive error : e
|
Description
| An error occurred while trying to receive a message over the cluster broadcast. |
|
Cause
| An error occurred while trying to receive a message over the cluster broadcast. |
|
Action
| Make sure that the NIC is functioning properly. If you believe there no environment problems exist, contact Oracle Customer Support and provide the stack trace for further analysis. |
|
|
BEA-003109
|
Error: Cluster cluster uses database as the migration basis but no data source for migration has been configured.
|
Description
| Cluster cluster uses database as the migration basis but no data source for migration has been configured. |
|
Cause
| Cluster cluster uses database as the migration basis but no data source for migration has been configured. |
|
Action
| Make sure that the data source is created and set for database migration basis. |
|
|
BEA-003111
|
Error: No channel exists for replication calls for cluster clusterName
|
Description
| No channel exists for replication calls for cluster clusterName |
|
Cause
| No channel exists for replication calls for cluster clusterName |
|
Action
| Configure the channels for Replication calls. |
|
|
BEA-003112
|
Info: Channels "channelNames" configured for replication traffic.
|
Description
| Multiple replication channels are configured which will be used to send secondary update / remove calls. |
|
Cause
| None. |
|
Action
| None. |
|
|
BEA-003113
|
Info: Using one way RMI for replication.
|
Description
| The server is configured to use one way RMI calls for update / remove calls made to secondary server. These calls will return immediately without waiting for any response. |
|
Cause
| None. |
|
Action
| None. |
|
|
BEA-003114
|
Notice: Ignoring one way RMI for replication because multiple replication channels are not found.
|
Description
| One way RMI for replication only works with multiple replication channels. |
|
Cause
| None. |
|
Action
| None. |
|
|
BEA-003115
|
Error: Failed to sync secondary session due to missing updates.
|
Description
| The server is configured to use one way RMI calls for update calls. Due to an error condition some updates could not be applied and hence we have stale sessions on secondary. |
|
Cause
| Work manager queue could be full and hence update messages were dropped. |
|
Action
| Either increase the no of servers in the cluster (preferred) or add more replication channels (requires server re-start). |
|
