com.ibm.ws.mongo.resources.CWKKDMessages

CWKKD0010E: Unable to configure the property {0} on the service {1} with id {2} and value {3}.

Explanation

A configured property is either not recognized or could not be configured due to an error.

Action

Correct or remove the configured property.

CWKKD0011E: The {0} service with id {1} is defined with an unequal number of hostNames ({2}) and ports ({3}).

Explanation

The hostName and port number lists must have the same number of elements.

Action

Update the server configuration so that the hostNames and ports attributes contain the same number of elements.

CWKKD0012E: The {0} service with id {1} is unable to authenticate to the database {2}.

Explanation

The database rejected the authentication attempt.

Action

Update the server configuration with the correct user name and password.

CWKKD0013E: The {0} service encountered an unsupported version of the MongoDB driver at shared library {1}. Expected a minimum level of {2}, but found {3}.

Explanation

The MongoDB service was provided with an invalid driver library.

Action

Update the shared library with a supported level.

CWKKD0014E: The {0} service was unable to locate the required MongoDB driver classes at shared library {1}.

Explanation

The MongoDB service is unable to locate the required classes in the configured shared library.

Action

Update the shared library with a supported level.

CWKKD0015E: The {0} service with id {1} is attempting to use SSL without the ssl-1.0 feature enabled in the server.xml file.

Explanation

The SSL configuration cannot be used without the ssl-1.0 feature enabled.

Action

Add the ssl-1.0 feature to the server.xml file.

CWKKD0017E: The {0} service with id {1} encountered an incompatible version of the MongoDB driver at shared library {2}. For SSL a minimum level of {3} is required, but the service found {4}.

Explanation

The MongoDB service was provided with an invalid driver library for use with SSL.

Action

Update the shared library with a supported level.

CWKKD0018E: The {0} service with id {1} encountered an incompatible combination of authentication options. useCertificateAuthentication is incompatible with user and password.

Explanation

The MongoDB service was provided with an incompatible authentication options for use with SSL.

Action

Update the server.xml mongo element to specify either user and password or useCertificateAuthentication but not both.

CWKKD0019E: The {0} service with id {1} was configured to use certificate authentication without SSL enabled.

Explanation

The MongoDB service was configured for certificate based authentication without SSL.

Action

Update the mongo element in the server.xml to include sslEnabled=true, or remove useCertificateAuthentication.

CWKKD0020E: The {0} service with id {1} received an exception while reading the client key and certificate from the provided keystore. Nested exception is {2}

Explanation

The MongoDB service tried to read the client key and certificate from the keystore, and encountered a problem with the keystore or with a certificate in it.

Action

The nested exception should provide more information.

CWKKD0023E: The {0} service with id {1} encountered an incompatible version of the MongoDB driver at shared library {2}. For certificate authentication, a minimum level of {3} is required, but the service found level {4}.

Explanation

The MongoDB service was provided with an invalid driver library for use with certificate authentication.

Action

Update the shared library with a level that is supported...

CWKKD0024E: The {0} service with id {1} has the sslRef property set in the server.xml file but sslEnabled is not set to true.

Explanation

Having the sslRef set without ssl is invalid.

Action

Set sslEnabled=true, or remove sslRef.

CWKKD0026E: The {0} service with id {1} was unable to extract the client key and certificate from the keystore. Either there are no keys in the keystore, or there are multiple keys and clientKeyAlias was not specified on the ssl element.

Explanation

The referenced keystore must contain at least one client key and certificate pair and if it contains more that one the clientKeyAlias parameter must be used to identify which to use.

Action

Examine the keystore in use with Java keytool. For example, "keytool -list -keystore keystorename.jks" shows the entries in the keystore and their aliases. Specify one of these aliases using clientKeyAlias on the ssl element.