On Tue, Mar 12, 2024 at 8:42 PM Timothy Bish wrote:
> On 3/12/24 16:25, Ciaran wrote:
> > On Tue, Mar 12, 2024 at 7:13 PM Timothy Bish
> wrote:
> >
> >> On 3/12/24 04:08, Ciaran wrote:
> >>> On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish
> >> wrote:
> The client re-connection logic treats a
On 3/12/24 16:25, Ciaran wrote:
On Tue, Mar 12, 2024 at 7:13 PM Timothy Bish wrote:
On 3/12/24 04:08, Ciaran wrote:
On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish
wrote:
The client re-connection logic treats a SASL authentication error as a
terminal state and will not continue reconnect
On Tue, Mar 12, 2024 at 7:13 PM Timothy Bish wrote:
> On 3/12/24 04:08, Ciaran wrote:
> > On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish
> wrote:
> >
> >>
> >> The client re-connection logic treats a SASL authentication error as a
> >> terminal state and will not continue reconnect attempts if it
On 3/12/24 04:08, Ciaran wrote:
On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish wrote:
The client re-connection logic treats a SASL authentication error as a
terminal state and will not continue reconnect attempts if it receives a
SASL outcome that indicates anything other than a temporary
On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish wrote:
>
>
> The client re-connection logic treats a SASL authentication error as a
> terminal state and will not continue reconnect attempts if it receives a
> SASL outcome that indicates anything other than a temporary failure
> state so it should
On 3/11/24 16:54, Ciaran wrote:
Hi all,
I'm taking a look at using ProtonJ2 to talk to Azure Service Bus and I've
successfully gotten everything up and running, with and without websockets,
now I'm turning my attention to the 'unhappy path' of network drop-outs and
misconfigurations leading to
Hi all,
I'm taking a look at using ProtonJ2 to talk to Azure Service Bus and I've
successfully gotten everything up and running, with and without websockets,
now I'm turning my attention to the 'unhappy path' of network drop-outs and
misconfigurations leading to connection failures.
Is it
