On 08/05/2014 05:51 PM, Gordon Sim wrote:
On 08/05/2014 05:18 PM, Chris Richardson wrote:
Could a qpid dev please confirm this fix and, if approved, could we be
informed of when a fix will be released?
I'll get this in for the upcoming 0.30 release.
Fyi: I checked your fix into trunk as http
On 08/05/2014 05:18 PM, Chris Richardson wrote:
I think I've tracked this one down.
Good job! Thanks for chasing this down!
My theory is that the qpid::amqp_1_10::Connection::decode method, which
contains the code
if (isClient && !initialized) {
//read in protocol header
fra
I think I've tracked this one down.
My theory is that the qpid::amqp_1_10::Connection::decode method, which
contains the code
if (isClient && !initialized) {
//read in protocol header
framing::ProtocolInitiation pi;
if (pi.decode(in)) {
if(!(pi==version))
Hi,
As you see from the subject I'm trying to set up an SSL link between two
brokers (version 0.28). To cut to the chase, both brokers are able to
communicate locally over SSL - for instance I can use
qpid-stat -b amqps://localhost:5671 -e
and
qpid-stat -b amqps://localhost:5674 -e
(these being
