Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (athena.apache.org: domain of rob.j.godfrey@gmail.com
 designates 209.85.216.49 as permitted sender)
MIME-Version: 1.0
Date: Mon, 1 Sep 2014 15:44:55 +0200
Message-ID: 
 <CACsaS965Y-u_u8AAE=LGmV1J9PStDktpeEfnPHZtupnJzG9UwQ@mail.gmail.com>
Subject: Request for Inclusion in 0.30
From: Rob Godfrey <rob.j.godfrey@gmail.com>
To: "users@qpid.apache.org" <users@qpid.apache.org>,
 Justin Ross <justin.ross@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c160864b906b05020135ed

--001a11c160864b906b05020135ed
Content-Type: text/plain; charset=UTF-8

Hi Justin,

another small one:

https://issues.apache.org/jira/browse/QPID-6031 : If attempting to connect
over SSL to a server whose certificate is not trusted, ensure a meaningful
error message is generated.

https://svn.apache.org/r1621767

It's a one line change with no impact other than to the JMS AMQP 1.0 client
when it is attempting to connect over SSL.  By forcing an explicit request
to start the SSL handshake, the connection is closed with

javax.jms.JMSException: javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target"

rather than

java.net.SocketException: Socket Closed
at
java.net.AbstractPlainSocketImpl.setOption(AbstractPlainSocketImpl.java:206)

The issue was discovered by a user.

- Rob

--001a11c160864b906b05020135ed--