Problem | Potential solution / explanation |
---|---|
Algorithm Not Supported/Algorithm 'SSL' not available | This error occurs when the SSL version specified
in the connector configurator is not supported by your JSSE provider.
Solution: check JSSE provider's documentation for the supported
SSL versions. For IBM JSSE make sure your java.security file in
the ProductDir/lib/security directory has
the following entry
security.provider.<number>=com.ibm.jsse. IBMJSSEProviderwhere <number> is the preference order for loading the security provider. |
Error loading keystore:Keystore file path:"<path>" incorrectly specified:KeyStore not found | This error occurs if you specify an incorrect path for the keystore and/or truststore files. Solution: check the keystore file path specified in the SSL->KeyStore property in the Connector configurator. Also, if you are using truststore, check the truststore file path specified in SSL->TrustStore property in the Connector configurator. |
KeyManagementError: KeyStore is tampered with, KeyManagement error | This error occurs if your keystore and/or truststore have been tampered with or otherwise corrupted. This error may also occur if you have specified an incorrect value for the password. Solution: ensure that the keystore has not been tampered. Try recreating the keystore. Also make sure you have entered a correct password in the SSL->KeyStorePassword and SSL->TrustStorePassword connector properties. |
Error loading certificates from keystore | This error occurs if your certificates and/or keystore, truststore have been tampered with. This error may also occur if you have specified an incorrect value for the password. Solution: check to see if the certificate, keystore or truststore have been tampered with. Also, ensure that you have specified a correct password in the SSL->KeyStorePassword and SSL->TruststorePassword connector properties. |
Error creating the server socket, terminating: error | This error occurs if the HTTP or HTTPS protocol listener cannot bind to the port specified in connector properties. Solution: check the ports specified for all of the HTTP and HTTPS protocol listeners. If the same port is specified for more than one listener, only one of the listeners can start up. Additionally, check if you have any other service running on that port. If so, then you may want to choose a different port for the protocol listeners. |
KeyManagementError:UnrecoverableKeyException, Keys could not be recovered | This error occurs if the keystore or truststore cannot be used. Solution: create a new keystore. |
SSL Handshake Exception: Unknown CA | This occurs if you do not have a CA certificate in your truststore. Solution: check whether the CA's certificate, as well as its self-signed certificates, reside in the truststore. Also, ensure that the DN of the certificate has the host name (preferably the IP address). |
You notice excessive JSSE logging in your log file. | If you do not want to see all of the underlying JSSE details on your console, set the value of SSL->SSLDebug property in the connector configurator to false. |
You have specified a protocol listener but
the listener is not getting initialized; you see the following warning message
in the connector:
Skipping Protocol Listener Property Set "SOME_LISTENER_NAME" with protocol property "": unable to determine the protocol listener class.] |
The connector was unable to extract a valid value for the Protocol property of the protocol listener. Valid values are http or https. Solution: this is not an error condition. However, if you want the connector to use this listener, specify a valid Protocol property value. |
You have specified a protocol handler, but
it is not
getting initialized; you see following warning message in the connector. Unable to determine the type of the handler; skipping initializing of current handler. Handler property details: Name: <Handler Name>; Value: Name: Protocol; Value: Name: ResponseWaitTimeout; Value: Name: ReplyToQueue; Value: .] |
The connector was unable to extract a valid value for the Protocol property of the handler. Valid values are http and https. Solution: This is not an error condition. However, if you want connector to use this handler, specify a valid Protocol property value. |