On 09/01/17 21:27, Gordon Sim wrote:
On 09/01/17 07:52, drasil wrote:
I am sorry, but I have to revoke my previous post. I just realized
that the
working setup is not really working. Without any other changes, the
client
either succeeds or not.
Yes, I confirm I also see occasional failures (less frequently than you,
but the frequency seems to decrease with broker logging, so likely a
timing thing).
I've verified that what proton gets is what is returned from cyrus sasl,
and I can't as yet see any other obvious clue as to whats going wrong
(failed case looks much the same as succeeding case), but there is
clearly a big somewhere.
I have a 'fix' for this - i.e. a change that appears to prevent it
occurring. If the broker waits after sending the sasl outcome for the
client to send a protocol header, then I see no failures even running in
a loop for an hour.
I wonder whether the proton client's sasl layer is somehow getting
(intermittently) upset if the last unencrypted frame and the first
encrypted frame arrive together...
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
