qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <minf...@sharp.fm>
Subject Re: Coaxing an error message out of qpid-cpp - unable to connect
Date Thu, 10 Oct 2013 13:42:58 GMT
On 10 Oct 2013, at 2:56 PM, Graham Leggett <minfrin@sharp.fm> wrote:

> When the client tries the connect, the qpid-client v0.24 reports a "java.net.SocketException:
Broken pipe" and then hangs solid, the hang solid most probably due to bug https://issues.apache.org/jira/browse/QPID-5113.
What I am after is why the "java.net.SocketException: Broken pipe".

Digging further with ssldump, I find that the SSL connections are completing successfully,
the client and server then try to negotiate the protocol, and the server puts the phone down
on the connection as follows:

1 5  6.8968 (0.0001)  C>S  ChangeCipherSpec
1 6  7.0251 (0.1282)  C>S  Handshake
      Finished
1 7  7.0273 (0.0022)  S>C  ChangeCipherSpec
1 8  7.0273 (0.0000)  S>C  Handshake
      Finished
1 9  7.0349 (0.0075)  C>S  application_data
    ---------------------------------------------------------------
    41 4d 51 50 00 01 00 00                            AMQP....
    ---------------------------------------------------------------
1 10 7.1535 (0.1185)  S>C  application_data
    ---------------------------------------------------------------
    41 4d 51 50 01 01 00 0a                            AMQP....
    ---------------------------------------------------------------
1 11 7.2002 (0.0467)  S>C  Alert
    level           warning
    value           close_notify
1    7.2011 (0.0008)  S>C  TCP FIN
1 12 7.2405 (0.0394)  C>S  application_data
    ---------------------------------------------------------------
    00 00 00 50 02 00 00 00 00 53 10 c0 43 04 a1 1d    ...P.....S..C...
    6c 6f 63 61 6c 68 6f 73 74 2e 6c 6f 63 61 6c 64    localhost.locald
    6f 6d 61 69 6e 28 35 32 33 39 29 3a 32 a1 19 61    omain(5239):2..a
    6d 71 70 2e 73 61 6e 64 62 6f 78 2e xx xx xx xx    mqp.sandbox.xxxx
    xx xx xx xx 2e 6e 65 74 70 00 01 00 00 60 00 ff    xxxx.netp....`..
    ---------------------------------------------------------------
1    7.5397 (0.2992)  C>S  TCP RST

Is this a mismatch between the protocol on client and server?

The client says "41 4d 51 50 00 01 00 00", the server then responds "41 4d 51 50 01 01 00
0a" and puts the phone down. Am I right in assuming that "00 01 00 00" and "01 01 00 0a" are
protocol version numbers?

The client jars are as follows:

-rw-r--r-- 1 root transcode  471270 Oct 10 05:40 qpid-client-0.24.jar
-rw-r--r-- 1 root transcode 1379470 Oct 10 05:41 qpid-common-0.24.jar
-rw-r--r-- 1 root transcode   25942 Oct 10 05:41 slf4j-api-1.6.4.jar

Are these compatible with a v0.18 qpid-cpp server?

Regards,
Graham
--


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message