JSSL

Express (Distributed operating systems), v8.0 > Reference > Messages

JSSL

JSSL0010E: IIOPSSLConnection.createSSLServerSocket(...) threw an INTERNAL exception. Additional information: {0}.

Explanation A failure occurred creating an SSL server socket.
Action This problem usually indicates that there is a problem with the SSL configuration. Make sure that the listener port configured for IIOP connections is not already being used by another process, and that another instance of the Application Server is not already started. Also make sure that the SSL keystore and truststore files are valid and contain the correct certificates. We can use the Application Server's IKeyMan tool to validate the keystore and truststore files.

JSSL0020E: The SSLServerConnectionData object that is passed to createSSLServerSocket returned a value from getTargetRequiresQOP() that is less than 1.

Explanation There might be a problem with the server's SSL configuration.
Action Use the administrative console to review the settings for the server's SSL configuration.

JSSL0030E: The SSLServerConnectionData object that is passed to createSSLServerSocket contains a TargetSupportsQOP() value that is less than its TargetRequiresQOP value.

Explanation There might be a problem with the server's SSL configuration.
Action Use the administrative console to review the settings for the server's SSL configuration.

JSSL0050E: IIOPSSLConnection.initContext(...) threw an INTERNAL exception. Additional: information {0}.

Explanation A problem occurred while the SSL context was being created in preparation for the server socket.
Action This problem usually indicates that there is a problem with the SSL configuration. Make sure that the SSL keystore and truststore files are valid and contain the correct certificates, and that these files have valid passwords. Also make sure that the file types specified are the correct types for the files they represent, for example JKS, JCEK, and so forth. We can use the Application Server's IKeyMan tool to validate the keystore and truststore files.

JSSL0070E: IIOPSSLConnectionClient.createSSLSocket(...) threw an INTERNAL exception. Additional information: {0}

Explanation A problem occurred while an SSL client socket was being created.
Action This problem usually indicates that there is a problem with the client's SSL configuration. Make sure that the SSL keystore and truststore files are valid and contain the correct certificates, and that these files have valid passwords. Also make sure that the file types specified are the correct types for the files they represent, for example JKS, JCEK, and so forth. We can use the Application Server's IKeyMan tool to validate the keystore and truststore files.

JSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: {0}

Explanation The client and server could not negotiate the desired level of security. The connection is no longer usable.
Action Make sure that the server's trust store has the signer certificate from the client.

JSSL0090E: javax.net.ssl.SSLProtocolException - Reports an error in the operation of the SSL protocol. Reason: {0}

Explanation An error occured during the operation of the SSL protocol.
Action This problem usually indicates that there is a flaw in one of the protocol implementations.

JSSL0100E: javax.net.ssl.SSLPeerUnverifiedException - Indicates that the peer''s identity has not been verified. You may request the identity of the peer. Reason: {0}

Explanation The peer was not able to identity itself. This situation might have occurred because there is no certificate for the peer, the particular cipher suite being used does not support authentication, or no peer authentication was established during SSL handshaking.
Action See the description of the exception for more information. We can also request the identity of the peer.

JSSL0110E: javax.net.ssl.SSLKeyException - Reports a bad SSL key. Reason: {0}

Explanation A bad SSL key was encountered.
Action This problem usually indicates that there is a server configuration problem, or there is a problem with a client's SSL certificate and private key. See the description of the exception for more information.

JSSL0120E: javax.net.ssl.SSLException: Indicates some kind of error detected by an SSL subsystem. Reason: {0}

Explanation This problem usually indicates that an SSL subsystem detected an error.
Action Verify that the SSL configuration is setup correctly.

JSSL0130E: java.io.IOException: Signals that an I/O exception of some sort has occurred. Reason: {0}

Explanation An I/O exception has occurred. The specified class is the general class of exceptions produced by failed or interrupted I/O operations.
Action See the description of the exception for more information.

JSSL0140I: Client aliases to choose from: {0}

Explanation This list indicates the client keystore aliases that can be selected.
Action No action required.

JSSL0150I: Server aliases to choose from: {0}

Explanation This list indicates the server keystore aliases that can be selected.
Action No action required.

JSSL0160E: Client alias specified ({0}) does not match a valid client alias.

Explanation The client alias specified in the SSL configuration is not in the client keystore.
Action Make sure that the specified client alias is correct, and that this client alias exists in the client keystore.

JSSL0170E: Server alias specified ({0}) does not match a valid server alias.

Explanation The server alias specified in the SSL configuration is not in the server keystore.
Action Make sure that the specified server alias is correct and that this server alias exists in the server keystore.

JSSL0180I: SSL client alias chosen: {0}

Explanation The specified client alias is the client alias that will be used to make the SSL connection.
Action No action required.

JSSL0190I: SSL server alias chosen: {0}

Explanation The specified server alias is the server alias that will be used to make the SSL connection.
Action No action required.

JSSL0191W: The keystore or truststore type specified is invalid. Adjusting to use the correct type, however, please correct the SSL configuration for performance reasons.

Explanation The file type specified for either the keystore or the truststore file is not valid.
Action Modify the SSL configuration such that a valid file type is specified for the keystore or truststore file. The current file type is not valid. We can use the Application Server's IKeyMan tool to check the file type currently specified for the keystore and the truststore files.

JSSL0200I: A PKCS keystore has been initialized. Library name: {0}

Explanation A pkcs keystore file has been initialized in the indicated library.
Action No action required.

JSSL0201E: Unable to get a PKCS keystore. Library name: {0}

Explanation A PKCS keystore instance cannot be obtained.
Action Make sure the Cryptographic token configuration is valid.

JSSL0202E: Unable to open keystore: {0}

Explanation The specified keystore file or URL exists, but the program is unable to open the file.
Action Make sure that the specified file name is the name of a valid keystore file and that the file is accessible. If the file name is valid and the file is accessible, make sure that the URL being used to access this file is also valid and accessible.

JSSL0203E: The keystore file {0} exists, but it is empty.

Explanation The specified keystore file has a file size of zero bytes.
Action Make sure that the specified file name is the name of a valid keystore file and that the file is accessible.

JSSL0204E: The keystore file {0} was not found, or the URL syntax is not correct.

Explanation Either the specified keystore file does not exist, or URL specification used to access this file is incorrect.
Action Make sure that the specified file name is the name of a valid keystore file and that the file is accessible. If the file name is valid and the file is accessible, make sure that the URL being used to access this file is also valid and accessible.

JSSL0205E: Unable to gain access to the keystore: {0}

Explanation The Application Server runtime does not have the proper permissions to access the specified keystore file.
Action Make sure that the Application Server runtime has the proper security policy to access the specified file.

+
Search Tips | Advanced Search

Explanation	There might be a problem with the server's SSL configuration.
Action	Use the administrative console to review the settings for the server's SSL configuration.

Explanation	The client and server could not negotiate the desired level of security. The connection is no longer usable.
Action	Make sure that the server's trust store has the signer certificate from the client.

Explanation	An error occured during the operation of the SSL protocol.
Action	This problem usually indicates that there is a flaw in one of the protocol implementations.

Explanation	The peer was not able to identity itself. This situation might have occurred because there is no certificate for the peer, the particular cipher suite being used does not support authentication, or no peer authentication was established during SSL handshaking.
Action	See the description of the exception for more information. We can also request the identity of the peer.

Explanation	A bad SSL key was encountered.
Action	This problem usually indicates that there is a server configuration problem, or there is a problem with a client's SSL certificate and private key. See the description of the exception for more information.

Explanation	This problem usually indicates that an SSL subsystem detected an error.
Action	Verify that the SSL configuration is setup correctly.

Explanation	An I/O exception has occurred. The specified class is the general class of exceptions produced by failed or interrupted I/O operations.
Action	See the description of the exception for more information.

Explanation	This list indicates the client keystore aliases that can be selected.
Action	No action required.

Explanation	This list indicates the server keystore aliases that can be selected.
Action	No action required.

Explanation	The client alias specified in the SSL configuration is not in the client keystore.
Action	Make sure that the specified client alias is correct, and that this client alias exists in the client keystore.

Explanation	The server alias specified in the SSL configuration is not in the server keystore.
Action	Make sure that the specified server alias is correct and that this server alias exists in the server keystore.

Explanation	The specified client alias is the client alias that will be used to make the SSL connection.
Action	No action required.

Explanation	The specified server alias is the server alias that will be used to make the SSL connection.
Action	No action required.

Explanation	The file type specified for either the keystore or the truststore file is not valid.
Action	Modify the SSL configuration such that a valid file type is specified for the keystore or truststore file. The current file type is not valid. We can use the Application Server's IKeyMan tool to check the file type currently specified for the keystore and the truststore files.

Explanation	A pkcs keystore file has been initialized in the indicated library.
Action	No action required.

Explanation	A PKCS keystore instance cannot be obtained.
Action	Make sure the Cryptographic token configuration is valid.

Explanation	The specified keystore file or URL exists, but the program is unable to open the file.
Action	Make sure that the specified file name is the name of a valid keystore file and that the file is accessible. If the file name is valid and the file is accessible, make sure that the URL being used to access this file is also valid and accessible.

Explanation	The specified keystore file has a file size of zero bytes.
Action	Make sure that the specified file name is the name of a valid keystore file and that the file is accessible.

Explanation	Either the specified keystore file does not exist, or URL specification used to access this file is incorrect.
Action	Make sure that the specified file name is the name of a valid keystore file and that the file is accessible. If the file name is valid and the file is accessible, make sure that the URL being used to access this file is also valid and accessible.

Explanation	The Application Server runtime does not have the proper permissions to access the specified keystore file.
Action	Make sure that the Application Server runtime has the proper security policy to access the specified file.