qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lei.dai@airlink-software.com" <lei....@airlink-software.com>
Subject Re: Re: [Qpid C++ Broker] Why broker link state retains connecting when I setup Broker Federation in windows using qpid-route ?
Date Mon, 14 Nov 2016 10:35:49 GMT
Thanks for your hint but maybe it's not the reason I think.
Because I didn't configure qpid to do client authentication, so there is no need to provide
the client certificate even if SSL is used.
And in fact the result was same in both SSL mode and non-SSL mode (without SSL parameters).

I'm now reading the source code and doing some tracing.
And I hope to find the reason sometime if I'm lucky enough...... (- -;)

Regards,


Lei Dai
 
From: Chris Richardson
Date: 2016-11-14 17:57
To: users
Subject: Re: Re: [Qpid C++ Broker] Why broker link state retains connecting when I setup Broker
Federation in windows using qpid-route ?
I had some trouble setting this up too and one of my mistakes was that I
was using server-only certificates (as you state you are doing in your
original post). When a broker establishes a link it uses its configured
cert as a _client_ cert, so the cert must be valid for that purpose also.
 
HTH
 
 
On 13 November 2016 at 05:08, lei.dai@airlink-software.com <
lei.dai@airlink-software.com> wrote:
 
> Hi,
>
> Thank you for the reply.
>
> As you said, I tried to set "auth=on" and provide an ACL with only one
> line "acl allow all all", but got the same result.
> I also tried to read the logs, and found that when use linux version,
> there are logs like:
>
> 2016-11-11 18:27:34 [Broker] info [0x7f13f308e700]
> /home/alex/qpid-cpp-1.35.0/src/qpid/broker/Link.cpp:240: Inter-broker
> link established to 172.16.28.144:5672
> 2016-11-11 18:27:34 [Model] debug [0x7f13f308e700]
> /home/alex/qpid-cpp-1.35.0/src/qpid/broker/amqp_0_10/Connection.cpp:329:
> Create connection. user:@QPID rhost:qpid.tcp:172.16.28.144:5672
> 2016-11-11 18:27:34 [System] debug [0x7f13f308e700]
> /home/alex/qpid-cpp-1.35.0/src/qpid/sys/AsynchIOHandler.cpp:102: SENT
> [qpid.tcp:172.16.28.144:5672]: INIT(0-10)
>
> But when use windows version, these logs disappeared.
> It seems that the destination node didn't send protocol negotiation to the
> source node for some reasons in windows, but I don't know what the reasons
> are.
> Now I'm trying to read the source code of Qpid C++ Broker but it's a
> little difficult to me...
>
> Regards,
>
>
> Lei Dai
>
>
 
 
-- 
 
*Chris Richardson*, System Architect
cr@fourc.eu
 
 
*FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu
<http://www.fourc.eu/>*
 
*Follow us on LinkedIn <http://bit.ly/fourcli>, Facebook
<http://bit.ly/fourcfb>, Google+ <http://bit.ly/fourcgp> and Twitter
<http://bit.ly/fourctw>!*
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message