Explanation | During startup the collective controller restored its state from the disk. Some files were corrupt but the collective controller recovered and corrected the problem. |
Action | No immediate action is required. Corrupted files may indicate a bad storage device. Check the storage device is healthy. |
Explanation | The collective controller is unable to connect or communicate with the specified replica. The specified replica may be down or there may be network connection issues. |
Action | Ensure that replica host and port for the specified replica in the <collectiveController> replicaSet configuration is correct, that the corresponding replica is running and that there are no network communication problems. |
Explanation | The collective controller is unable to delete a file from the file system. |
Action | Verify the permissions of the mentioned file, ensure the collective controller has delete permissions, and that the file is not locked. Ensure the storage device is functioning properly. |
Explanation | During normal work the collective controller writes its state to the disk in a dedicated directory. It is unable to create this directory. |
Action | Verify the permissions of the mentioned directory, and ensure the collective controller has write/modify permissions. Check that the storage device has enough free disk space. Ensure the storage device is functioning properly. |
Explanation | During startup the collective controller tries to restore its state from the disk. It encountered files that indicate a version which is not supported. |
Action | See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | During normal work, the collective controller writes its state to the disk in a dedicated directory. The value provided is not a directory. |
Action | Fix the value of the configuration parameter to identify a directory. |
Explanation | Communication among collective controller replicas is inconsistent. This might be a transient state due to a heavy load on the network or hosts. |
Action | Verify that hosts running collective controller are stable and have enough CPU power. Also, use the ping utility to measure round trip time (RTT) between hosts. High variations in RTT indicate that the system has a heavy load and it lacks network or CPU power resources. |
Explanation | The collective controller received a message that it cannot understand. The likely cause is a version mismatch between collective controller replicas. |
Action | Ensure the collective controller replicas have compatible versions. |
Explanation | The collective controller was unable to replicate the state to a majority of the replicas. A likely cause is network problems or unavailable replicas. |
Action | Ensure a majority of the replicas are running. Ensure the network connection connecting the replicas is functioning properly. |
Explanation | The collective controller opened a connection to the specified replica. This information denotes a healthy state. |
Action | No user action is required. |
Explanation | The collective controller closed the connection to a replica successfully. This is usually due to a planned replica set change or an orderly stopping of a replica. |
Action | No user action is required. |
Explanation | The collective controller is ready to accept requests. Consistency, high availability and load balancing are available. This message occurs after initialization ends, or when the replica set changes, either due to administrator actions or due to replica failure. |
Action | No user action is required. |
Explanation | The collective controller is temporarily unable to accept requests, but will probably be ready within a few seconds. This message occurs after initialization ends, or when the replica set changes, either due to administrator actions or due to replica failure. The system will automatically adjust to the new replica set. If there are not enough replicas to regain consistency and high availability, a separate message is written to the log with a higher severity. |
Action | No user action is required. |
Explanation | This is a periodic state report. Use this report to resolve future problems, if they occur. |
Action | No user action is required. |
Explanation | This collective controller replica synchronized with the other replicas. This replica was out of sync with the other replicas. This usually happens when the replica is started and joins an active repository, but can also happen when a replica is restarted or is disconnected from the other replicas for a period of time. |
Action | No user action is required. |
Explanation | The administrator requested to change the set of replicas in the collective controller. The change request is processing. |
Action | No user action is required. |
Explanation | Changing the active collective controller replica set was successful. The new set now can serve high availability and consistency. Replicas not in the current set can be shut down. |
Action | No user action is required. |
Explanation | During startup, the collective controller tries to restore its state from the disk. It checks for relevant files in the specified directory. |
Action | Verify the permissions. |
Explanation | The collective controller is unable to read data from the specified file. The problem might be a permissions issue or a storage device error. |
Action | Verify the permissions of the mentioned file, and ensure the collective controller has write permissions. Ensure the storage device is functioning properly. |
Explanation | The collective controller is unable to write data into the specified file. The problem might be a permissions issue, out of disk space error, or a storage device malfunction. |
Action | Check that the storage device has enough free disk space. Verify the permissions of the mentioned file, and ensure the collective controller has write permissions. Ensure the storage device is functioning properly. |
Explanation | An unexpected internal problem encountered, and the replica had to shutdown. |
Action | Restart the replica. If the problem persists, use the error details and see the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The collective controller allows changes in the set of replicas if at least one replica is included in both the new set and the old set. |
Action | To completely change the set of replicas, use a staged approach, where every stage includes at least one replica in both the set before and after reconfiguration. For example, when moving from {A,B,C} to {D,E,F}, where each of A, B, C, D, E, F represents a collective controller replica, try {A,B,C} to {A,D,E,F} and then {A,D,E,F} to {D,E,F}. Or try {A,B,C} to {C,D,E} and then {C,D,E} to {D,E,F}. |
Explanation | The collective controller given configuration parameter must be a list of host:port, separated by spaces; for example, "10.0.0.11:10010 10.0.0.21:10010 10.0.0.31:10010". The provided value does not match this pattern. |
Action | Fix the value of the configuration parameter. Ensure that it fits the required pattern and has the correct host names and ports. |
Explanation | The collective controller configuration parameter stated in the message must be the host name or IP address. The value that was provided is not in the correct format for a host name or IP address. |
Action | Fix the value of the configuration parameter. Ensure that it fits the required pattern and has the correct host name or IP address. |
Explanation | The collective controller configuration parameter mentioned in the message must be a boolean value (true or false). The value that was provided is not boolean. |
Action | Set the value of the configuration parameter to either true or false. |
Explanation | The collective controller configuration parameter specified is missing. |
Action | Check whether the default value fits your needs. If not, add the missing configuration parameter. |
Explanation | The collective controller configuration parameter specified is missing. The collective repository is unable to start. |
Action | Add the missing collective controller configuration parameter. |
Explanation | The socket bind operation did not succeed. A common cause is that the port number is already in use. |
Action | Check that the collective controller is configured to use an available port number. |
Explanation | The collective controller configuration parameter stated in the message must be a valid port. The value that was provided is not an integer. |
Action | Fix the value of the configuration parameter and ensure the port value is an integer. |
Explanation | The collective controller configuration parameter stated in the message must be an integer in the given range. The value that was provided is not an integer in the correct range. |
Action | Fix the value of the configuration parameter and ensure it fits the above pattern. |
Explanation | The collective controller configuration parameter stated in the message must be a string, delimited using double quotes. The value was not identified as a string. |
Action | Fix the value of the configuration parameter to be a double quoted string. |
Explanation | The collective controller configuration parameter stated in the message must be one of a list of predefined values. The value provided is not one of these values. |
Action | Fix the value of the configuration parameter and ensure it is a predefined value. |
Explanation | A replica can either be part of an initial replica set, or join an already running replica set, and replicate the existing data from the replicas that were already running. The collective controller identified that none of the running replicas were previously part of a running collective controller replica set, and an initial set was not defined. |
Action | Fix configuration to define an initial set of replicas. |
Explanation | The collective controller requires that most replicas be active and reachable. Changing the replica set stops the collective controller and it will not be able to replicate properly. |
Action | Ensure that the replicas are active and available. You may need to verify that the network is functioning properly. |
Explanation | The mentioned replica's configuration states that it is part of a different replica set, and should not connect to this replica set. |
Action | Fix the configuration of the mentioned replica so that the replica set value will not contain replicas from a different replica set, or change the mentioned configuration parameter to be the same as in this replica set. |