The WLSS.ReplicatedStore1.0 catalog contains messages in the range
BEA332000 - BEA332199. Messages in this catalog are part of the
com.bea.wcp.sip.i18n
Internationalization package and the com.bea.wcp.sip.i18n Localization package.
|
BEA-332000
|
Notice: Initializing as first replica in partition
|
Description
| Initializing as first replica in partition, as no existing, active members of the partition could be located. |
|
Cause
| There were no other replicas running in the data tier partition. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332001
|
Notice: New view for partition partitionName: view
|
Description
| New view for partition partitionName: view |
|
Cause
| A new data tier partition view was established due to a replica joining or leaving the partition. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332002
|
Notice: Attempting to join an existing replica in partition
|
Description
| Attempting to join an existing replica in partition |
|
Cause
| The replica is starting and is looking for existing replicas to join. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332003
|
Notice: Failed to find active replicas in partition; will initialize as first replica
|
Description
| Failed to find active replicas in partition; will initialize as first replica |
|
Cause
| There are no other running replicas in the data tier partition. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332004
|
Notice: Replica initialized in ONLINE state
|
Description
| Replica initialized in ONLINE state |
|
Cause
| There was no data in the partition, so this replica initialized as fully ONLINE. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332005
|
Notice: Replica initialized as lock authority only, and will catch-up to online replicas
|
Description
| Replica initialized as lock authority only, and will catch-up to online replicas. |
|
Cause
| The replica that this replica joined to has existing data that this replica needs to catch-up with. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332006
|
Notice: Replica starting data catchup process for itemCount data items.
|
Description
| Replica starting data catchup process for itemCount data items. |
|
Cause
| The replica is beginning to catch up to the other replicas in the data tier partition. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332007
|
Notice: Replica service on server replicaName started, serving in partition partitionName
|
Description
| Replica service on server replicaName started, serving in partition partitionName |
|
Cause
| The service started. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332008
|
Notice: Received join request from replica noviceReplicaName
|
Description
| Received join request from replica noviceReplicaName |
|
Cause
| Another replica is attempting to join to this replica. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332009
|
Warning: Joining novice (noviceReplicaName) already in view
|
Description
| Joining novice (noviceReplicaName) already in view |
|
Cause
| The replica joined a sponsor replica and the sponsor replica thought the replica was already in the view. |
|
Action
| No action is necessary. |
|
|
BEA-332010
|
Notice: Client server has been registered; registration id: clientHostId
|
Description
| Client server has been registered; registration id: clientHostId |
|
Cause
| An engine node has started and connected to this replica. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332011
|
Notice: Throttling timers based on data size: byteCount
|
Description
| Throttling timers based on data size: byteCount |
|
Cause
| A large number of timers expired at once. |
|
Action
| Increase the size of the timer thread pool (sip.timer.Default) on the engine. |
|
|
BEA-332012
|
Warning: Error fetching data from replica fetchReplicaName
|
Description
| Error fetching data from replica fetchReplicaName |
|
Cause
| reason |
|
Action
| No action is required, as the replica will retry the fetch operation (from another replica, if necessary) |
|
|
BEA-332013
|
Notice: Client reported death of replica replicaName
|
Description
| Client reported death of replica replicaName |
|
Cause
| An engine node detected that some replica has failed. |
|
Action
| The failed replica should be examined and restored when possible. |
|
|
BEA-332014
|
Notice: Replica has completed data catch-up
|
Description
| Replica has completed data catch-up |
|
Cause
| The data catch-up process completed. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332015
|
Error: Fatal error merging data from sponsor. Catchup process aborted.
|
Description
| Fatal error merging data from sponsor. Catchup process aborted. |
|
Cause
| t |
|
Action
| The replica must be restarted. |
|
|
BEA-332016
|
Notice: Replica entering state state
|
Description
| Replica entering state state |
|
Cause
| The replica changed states. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332017
|
Error: Recovering replica promoted to ONLINE state and dataItemsLostCount data items were permanently lost
|
Description
| Recovering replica promoted to ONLINE state and dataItemsLostCount data items were permanently lost |
|
Cause
| This replica was recovering data and all other ONLINE replicas failed. This replica was promoted to being ONLINE. |
|
Action
| No action is required, as the data tier partition has recovered from the failure. |
|
|
BEA-332018
|
Error: Client reported replica death of replica deadReplicaName, but replica deadReplicaName is alive from local perspective
|
Description
| Client reported replica death of replica deadReplicaName, but replica deadReplicaName is alive from local perspective |
|
Cause
| An engine node believed that a replica had failed and reported it to this replica, but this replica was able to communicate with the supposed failed replica. A possible network partition condition exists. |
|
Action
| Check network connectivity between engine nodes and replica nodes. Restore network connectivity if necessary. |
|
|
BEA-332019
|
Warning: Join attempt to replica replicaName resulted in communications exception; replica replicaName likely not running
|
Description
| Join attempt to replica replicaName resulted in communications exception; replica replicaName likely not running |
|
Cause
| The chosen candidate sponsor could not be contacted. |
|
Action
| No action is necessary unless this is a chronic condition. If the condition is chronic, ensure that at least one replica in the data tier partition is ONLINE. |
|
|
BEA-332020
|
Error: Fatal error; shutting down
|
Description
| Fatal error; shutting down |
|
Cause
| An unexecpted fatal error occurred t |
|
Action
| Restart the replica. |
|
|
BEA-332021
|
Error: Replica was forced OFFLINE by replica requestingReplicaName
|
Description
| Replica was forced OFFLINE by replica requestingReplicaName |
|
Cause
| Some engine node believed this replica was dead when it was not. Another replica pushed this replica OFFLINE so that the data tier partition could continue functioning. This indicates a possible network partition. |
|
Action
| Check network connectivity between engine nodes and replica nodes. Restore network connectivity if necessary. |
|
|
BEA-332022
|
Notice: Replica service on server replicaName stopped (was serving in partition partitionName)
|
Description
| Replica service on server replicaName stopped (was serving in partition partitionName) |
|
Cause
| There can be various causes. Check nearby log messages for more detail. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332023
|
Notice: Forcing replica replicaName offline.
|
Description
| Forcing replica replicaName offline. |
|
Cause
| An engine node believes that some replica has failed, so we are trying to force it offline in case there is a network partition that would prevent the data tier partition from functioning. |
|
Action
| Check network connectivity between engine nodes and replica nodes. Restore network connectivity if necessary. |
|
|
BEA-332024
|
Warning: Lookup for replica service on server replicaName at location url failed
|
Description
| Lookup for replica service on server replicaName at location url failed |
|
Cause
| The replica is not running, or network connectivity has failed. |
|
Action
| If there are no replicas running in the data tier partition, start at least one of the replicas. |
|
|
BEA-332025
|
Error: Replica replicaName timed out after timeoutms
|
Description
| Replica replicaName timed out after timeoutms |
|
Cause
| A request to a replica timed out. |
|
Action
| Ensure that there are sufficient resources on the engine node, replica node, and network. |
|
|
BEA-332026
|
Error: Error communicating with replica replicaName
|
Description
| Error communicating with replica replicaName |
|
Cause
| A request to a replica resulted in an exception. |
|
Action
| Ensure that the replica is running properly. |
|
|
BEA-332027
|
Notice: Attempting to join using replica replicaName as sponsor
|
Description
| Attempting to join using replica replicaName as sponsor |
|
Cause
| A replica is initializing and trying to join to some replica in the data tier partition. |
|
Action
| No action is required, as the data tier partition has recovered from the failure. |
|
|
BEA-332028
|
Notice: Successfully joined partition; using replica replicaName as sponsor
|
Description
| Successfully joined partition; using replica replicaName as sponsor |
|
Cause
| This replica joined the partition. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332029
|
Warning: Join to replica replicaName failed
|
Description
| Join to replica replicaName failed |
|
Cause
| The chosen candidate sponsor was unable to sponsor this replica at this time. |
|
Action
| No action is necessary unless this is a chronic condition. If the condition is chronic, ensure that at least one replica in the data tier partition is ONLINE. |
|
|
BEA-332030
|
Alert: Join to replica replicaName timed out
|
Description
| Join to replica replicaName timed out |
|
Cause
| The chosen candidate sponsor did not respond in a timely fashion. |
|
Action
| No action is necessary unless this is a chronic condition. If the condition is chronic, ensure that at least one replica in the data tier partition is ONLINE. |
|
|
BEA-332031
|
Warning: Timers belonging to client have been rescheduled
|
Description
| Timers belonging to client have been rescheduled |
|
Cause
| Oustanding timers for an engine are rescheduled under various lateness and failure scenarios. See adjacent log message for the underlying cause. |
|
Action
| Ensure that the engine is running properly, has connectivity, and has reasonable load |
|
|
BEA-332032
|
Warning: Removing the registration for client client; registration id clientHostid
|
Description
| Removing the registration for client client; registration id clientHostid |
|
Cause
| The clients registration was removed, likely due to engine failure, connectivity loss, etc. |
|
Action
| The engine needs to be restarted to reconnect to the replica. |
|
|
BEA-332100
|
Notice: Partition partitionName online
|
Description
| Partition partitionName online |
|
Cause
| The partition client successfully connected to the data tier partition. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
|
BEA-332101
|
Warning: Connection to replica replicaName in partition partitionName failed
|
Description
| Connection to replica replicaName in partition partitionName failed |
|
Cause
| The connection to the replica failed for some reason; either the replica died or the network route between the engine and the replica failed. |
|
Action
| The failed component should be isolated and restored. |
|
|
BEA-332102
|
Error: Partition partitionName offline; starting partition re-initialization procedure
|
Description
| Partition partitionName offline; starting partition re-initialization procedure |
|
Cause
| All replicas in the data tier partition went offline and the partition client needs to re-establish a connection to the partition. |
|
Action
| No action is necessary unless this is a chronic condition. If the condition is chronic, ensure that at least one replica in the data tier partition is ONLINE. |
|
|
BEA-332103
|
Notice: Starting partition client initializer thread for partition partitionName
|
Description
| Starting partition client initializer thread for partition partitionName |
|
Cause
| The engine node could not intialize the data tier partition client and is scheduling retries. |
|
Action
| Ensure that at lease one replica in the specified data tier partition is running and ONLINE. |
|
|
BEA-332104
|
Error: Unexpected exception from replica replicaName
|
Description
| Unexpected exception from replica replicaName |
|
Cause
| t |
|
Action
| There is no corrective action. |
|
|
BEA-332105
|
Alert: Replica replicaName claims client is not registered
|
Description
| Replica replicaName claims client is not registered |
|
Cause
| Unknown |
|
Action
| Restart the engine node to force it to re-register to the replica. |
|
|
BEA-332106
|
Error: Unexpected error processing timers on partition partitionName: t
|
Description
| Unexpected error processing timers on partition partitionName: t |
|
Cause
| Unknown |
|
Action
| No action is necessary. |
|
|
BEA-332107
|
Alert: Too many errors processing timers on partition partitionName; shutting down
|
Description
| Too many errors processing timers on partition partitionName; shutting down |
|
Cause
| Unknown |
|
Action
| Unknown |
|
|
BEA-332108
|
Alert: Fatal error processing timers: t; shutting down
|
Description
| Fatal error processing timers: t; shutting down |
|
Cause
| Unknown |
|
Action
| Unknown |
|
|
BEA-332109
|
Notice: Registered with replica replicaServer; registration id clientHostId
|
Description
| Registered with replica replicaServer; registration id clientHostId |
|
Cause
| The engine registered with a replica. |
|
Action
| This is an informational message for debug purposes only, and no action is required. |
|
