Consultor Eletrônico

SUMMARY:

This solution applies to SonicMQ 3.5 and 4.0. It describes common errors and exceptions that might occur when using SonicMQ with SSL and how to resolve them.

SOLUTION:

-- Case 1:

a) Exceptions from JMS Client:

error: Cannot connect to Broker - ssl://localhost
javax.jms.JMSException: java.io.IOException: An IOException occurred while collecting the handshake digests: Connection aborted by peer: socket write error: ssl://localhost
at progress.message.jimpl.JMSExceptionUtil.createJMSException(Unknown Source)
at progress.message.jimpl.Connection.<init>(Unknown Source)
at progress.message.jimpl.QueueConnection.<init>(Unknown Source)
at progress.message.jclient.QueueConnectionFactory.createQueueConnection (Unknown Source)
at Talk.talker(Talk.java:63)
at Talk.main(Talk.java:296)

b) Error from SonicMQ Explorer :

com.rsa.ssl.AlertedException: An Alert was received: Illegal Parameter:

Solution:

If SSL_CLIENT_AUTHENTICATION is set to TRUE, the above exceptions might be generated when the JMS Client has not implemented Client Certificate (see the example in the Sonic Knowledge Base #20586).

Specifying Username and Password with SSL will also generate the above exceptions if SSL_CLIENT_AUTHENTICATION is set to TRUE.

If Username and Password has to be used, set SSL_CLIENT_AUTHENTICATION to FALSE.


-- Case 2: Error/Exceptions from SonicMQ Explorer and JMS Client:

The connection was rejected by the broker - Did you forget to use ssl:// or http:// in your connect string.

Solution:

Use the syntax, ssl://<hostname>:[broker-port] when connecting to SonicMQ Broker.


-- Case 3: Exceptions from JMS Client:

javax.jms.JMSSecurityException: Inauthentic Client
at progress.message.jimpl.JMSExceptionUtil.createJMSSecurityException(Unknown Source)
at progress.message.jimpl.Connection.<init>(Unknown Source)
at progress.message.jimpl.QueueConnection.<init>(Unknown Source)
at progress.message.jclient.QueueConnectionFactory.createQueueConnection (Unknown Source)
at Talk.talker(Talk.java:63)
at Talk.main(Talk.java:296)

Solution:

If the SSL_CLIENT_AUTHENTICATION option is set to FALSE, specify a valid Username and Password that has privileges to access the SonicMQ Broker. (See SonicMQ 4 Configuration and Administration Guide, Chapter 4 for more details on users in a security-enabled Database.)


References to Written Documentation:

Sonic Knowledge Base Solution 20586, "SonicMQ: Example for SSL CLIENT AUTHENTICATION"

Version 4 SonicMQ Configuration And Administration Guide