On 10/06/2015 07:25 PM, kbr wrote:
- I enabled more info in the log files. I see a 1.0 connection being made but it disconnects due to no response from the server. It logs: "No protocol received after 10s, closing". Which is correct, I see the WireShark capture and don't see a response from the service bus. But when I use a Proton client, the service bus responds as expected.
It sounds to me like something is not quite aligned at the TLS layer, but that it isn't resulting in an outright error (at least as far as qpidd can see; the service bus logs might have more information)
You could try connection using qpid::messaging, as an experiment. At the very least it would be a bit more directly comparable to connecting with a proton client, and the differences might suggest lines of further enquiry.
- is is the command I use to launch qpidd: sudo ./qpidd --config /etc/qpidd.conf --load-module /home/user/workspace/AMQP/qpid-cpp-0.34/build/src/amqp.so --ssl-cert-db /etc/certs/ --ssl-cert-name user --ssl-cert-password-file /etc/certs/pw_file --log-enable trace+:Security --log-enable trace+:Protocol --log-enable info+ - When I list the certs here is what I get: user@user-VirtualBox:/etc$ sudo certutil -L -d /etc/certs Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI user CTu,u,u
Is that the certificate that identifies the qpidd broker? Or does it identify the service bus? Or is it a CA who signed the service bus cert? (You need one or other of the last two; the first is optional)
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
