[
https://issues.apache.org/jira/browse/QPID-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117285#comment-14117285
]
Rob Godfrey commented on QPID-6031:
-----------------------------------
Hi - so I can get the client to connect without problem to a site secured with
SSL...
The issue above seems to occur socket has already been closed at the point
where the client is trying to set the socket timeout. Which AMQP broker /
service are you trying to connect to? Was this test where you were trying to
connect to a site with a certificate that was not trusted, or had you installed
the certificate in your truststore?
> JMS client will hang when SSL handshake fail as remote host is not trusted
> --------------------------------------------------------------------------
>
> 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
> 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]
