[
https://issues.apache.org/jira/browse/QPID-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092563#comment-14092563
]
Daniel Rååd commented on QPID-5810:
-----------------------------------
The hostname of the host running the AMQP broker had been changed without
restarting the AMQP broker.
This lead the AMQP broker to fail in the TLS handshake. Referring to the
attached tcpdump, the following TLS messages were exchanged
--> Client Hello
<-- Server Hello, Certificate, Server Key Exchange, Server Hello Done
--> Client Key Exchange
--> Change Cipher Spec, Encrypted Handshake Message
<-- Change Cipher Spec
<-- Encrypted Handshake Message
--> Application Data
<-- Encrypted Alert
--> Encrypted Alert
> QPID AMQP 1.0 JMS Client hangs after failing to establish TLS connection to
> AMQP broker
> ---------------------------------------------------------------------------------------
>
> Key: QPID-5810
> URL: https://issues.apache.org/jira/browse/QPID-5810
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 1.0 Client
> Affects Versions: 0.26
> Environment: Linux 2.6.32-431.el6.x86_64
> java version "1.7.0_45"
> OpenJDK Runtime Environment (rhel-2.4.3.3.el6-x86_64 u45-b15)
> OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)
> ActiveMQ 5.9.1 as AMQP broker
> Reporter: Daniel Rååd
> Assignee: Rob Godfrey
> Attachments: qpid-5810_tls_handshake_fails.pcap
>
>
> Trying to establish a connection to an AMQP broker over TLS transport, the
> TLS handshake happens to fail with the TLS server sending Alert.
> But the failed connection attempt is not reported to the user of the QPID JMS
> client, rather the calling thread hangs "forever" (I waited more than 40
> minutes).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
