[
https://issues.apache.org/jira/browse/QPID-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117415#comment-14117415
]
Rob Godfrey edited comment on QPID-6031 at 9/2/14 12:22 PM:
------------------------------------------------------------
OK - I tried this out myself by attempting to connect on an SSL connection
where the server certificate is not trusted, and I got the error you see. This
seems to be because Oracle's JRE / Runtime libraries don't throw a very helpful
error message in this situation.
By changing the connection code a bit to explicitly ask it to start the initial
SSL handshake I can provoke it to give a more useful exception instead... but I
wouldn't consider this a bug in the client - more a bug in the JRE. I don't
think it's a blocker for 0.30 (it's better to fail than to hang forever as it
used to). But I shall try to get the change to provide a better error message
in to the first release candidate
was (Author: rgodfrey):
OK - I tried this out myself by attempting to connect on an SSL connection
where the server certificate is not trusted, and I got the error you see. This
seems to be because Oracle's JRE / Runtime libraries don't through a very
helpful error message in this situation.
By changing the connection code a bit to explicitly ask it to start the initial
SSL handshake I can provoke it to give a more useful exception instead... but I
wouldn't consider this a bug in the client - more a bug in the JRE. I don't
think it's a blocker for 0.30 (it's better to fail than to hang forever as it
used to). But I shall try to get the change to provide a better error message
in to the first release candidate
> [JMS 1.0 Client] If attempting to connect over SSL to a server whose
> certificate is not trusted, ensure a meaningful error message is generated.
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-6031
> URL: https://issues.apache.org/jira/browse/QPID-6031
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 1.0 Client
> Affects Versions: 0.28
> Environment: AMQP JMS 1.0 client: AMQP 0.28
> AMQP broker: windows server service bus 1.1
> JDK: 1.7
> Reporter: Yong Deng
> Assignee: Rob Godfrey
> Fix For: 0.30
>
> Attachments: deadlock_threaddump.txt, log_exception.log
>
>
> 1. The azure service bus on premise is installed on windows server 2008 R2
> and uses a self signed SSL certificate. The SSL certificate is not trusted by
> JAVA by default
> 2. Write a JMS client following the guide with URL
> http://azure.microsoft.com/en-us/documentation/articles/service-bus-java-how-to-use-jms-api-amqp/
> 3. The JMS connection will hang. During the precedure, you will see an
> exception log print on console. Also I dump the JVM thread dump. You can
> refer to the attachments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
