[
https://issues.apache.org/jira/browse/QPID-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118128#comment-14118128
]
ASF subversion and git services commented on QPID-6031:
-------------------------------------------------------
Commit 1621970 from [~godfrer] in branch 'qpid/branches/0.30'
[ https://svn.apache.org/r1621970 ]
Merged QPID-6031 (r1621767) to 0.30 from trunk
> [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
> 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]
