Re: qpid-jms-client-56.0 - Prod issue - consumer stopped receiving message without any connection failure and detached receiver error

Hi Robbie, Thanks a lot for quick reply. Can i assume that JMS Connection will be closed for "JmsConnectionRemotelyClosedException" or "ProviderConnectionRemotelyClosedException" exception. So whenever I got "JmsConnectionRemotelyClosedException" or "ProviderConnectionRemotelyClosedException"

Re: Dispatch Router TCP throughput test over fast link with 0, 1, and 2 routers

On Fri, 12 Mar 2021 at 16:07, Michael Goulish wrote: > > > > I am including complete setup details below, because I would > > > like some help making sure I did everything right. > > > > > > > *Robbie says:* > > *When you figure that out, perhaps it could drive adding some* > > * documentation so

Re: Dispatch Router TCP throughput test over fast link with 0, 1, and 2 routers

On Fri, Mar 12, 2021 at 11:13 AM Michael Goulish wrote: > > > I am including complete setup details below, because I would > > > like some help making sure I did everything right. > > > > > > > *Robbie says:* > > *When you figure that out, perhaps it could drive adding some* > > * documentation

Re: Dispatch Router TCP throughput test over fast link with 0, 1, and 2 routers

> > I am including complete setup details below, because I would > > like some help making sure I did everything right. > > > > *Robbie says:* *When you figure that out, perhaps it could drive adding some* > * documentation so others dont have the same issue.* I'd be happy to work with you on

Re: Dispatch Router TCP throughput test over fast link with 0, 1, and 2 routers

On Fri, 12 Mar 2021 at 11:10, Michael Goulish wrote: > > Dispatch Router TCP throughput test over a 40 Gbit/sec link, > with 0, 1, and 2 routers. > = > > > I am including complete setup details below, because I would > like some help

Re: qpid-jms-client-56.0 - Prod issue - consumer stopped receiving message without any connection failure and detached receiver error

I have looked at the reported issue multiple times for a significant period. I tried reproducing it and was unable to. I got a second opinion, they independently came to the same conclusion as I had. I've thus described why I dont believe the behaviour is occurring as you specified (you may need

Re: qpid-jms-client-56.0 - Prod issue - consumer stopped receiving message without any connection failure and detached receiver error

No, I dont know any ways of 'hacking' ServiceBus to do all things the test does with its peer. We use a test peer specifically because such things are often difficult or at least slow. You'd have to ask Microsoft for questions you have about ServiceBus in any case. See my mail from last time,

Re: Passthrough authentication with linkrouting

The qpid-dispatch network security model is connection based. The connection over which a user connects to the network determines that user's policy restrictions. Once a user has connected and performed an allowed operation at the ingress connection then the rest of the network passes the

Re: qpid-jms-client-56.0 - Prod issue - consumer stopped receiving message without any connection failure and detached receiver error

Hi Robbie, Thanks a lot for quick update. I looked on our codebase, logs and stacktrace, and I can confirm that 1. "javax.jms.ExceptionListener#onException()" is not getting called from any of our defined classes/methods. 2. ExceptionListener is used only by connection object We got this

Re: qpid-jms-client-56.0 - Prod issue - consumer stopped receiving message without any connection failure and detached receiver error

Hi Robbie, Thanks a lot for your quick reply and confirmation on this issue. I referred your test case "testRemotelyEndSessionWithMessageListener" and trying to replicate same test case with Azure ServiceBus, So I can replicate this issue and provide confirmation for fixes. Main challenge for

Re: Passthrough authentication with linkrouting

On 12/03/2021 11:05, André van der Heijden wrote: All right, thanks, good to know. I read in this Protocol Guide from Microsoft / Redhat about

Dispatch Router TCP throughput test over fast link with 0, 1, and 2 routers

Dispatch Router TCP throughput test over a 40 Gbit/sec link, with 0, 1, and 2 routers. = I am including complete setup details below, because I would like some help making sure I did everything right. *Basic idea * Two

Re: Passthrough authentication with linkrouting

All right, thanks, good to know. I read in this Protocol Guide from Microsoft / Redhat about claims-based authorisation. This seems more or less in

Re: Passthrough authentication with linkrouting

On 12/03/2021 07:50, André van der Heijden wrote: *The Question* Is there a way to pass the authentication of the initial consumer all the way through the link-route down to the end-station? This could be either username/password or something like an OAuth token or so. The point for us is that

Re: [DISCUSS/NOTICE] Renaming default git repo branches to "main"

+1 On Thu, 11 Mar 2021 at 12:22, Robbie Gemmell wrote: > > Hi folks, > > I would like to propose renaming our git repository default branches > from "master" to "main" in keeping with general efforts to remove > offensive language, and also aligning with it being the default naming > approach on

Re: Autopep8 for DISPATCH-1814

On Fri, Nov 6, 2020 at 3:15 PM Ken Giusti wrote: > On Fri, Nov 6, 2020 at 5:40 AM Robbie Gemmell > wrote: > > > On Thu, 5 Nov 2020 at 15:32, Jiri Daněk wrote: > > > > > > Hello folks, > > > > > > (https://issues.apache.org/jira/browse/DISPATCH-1814 Apply autofixes > to > > > resolve some

Passthrough authentication with linkrouting

Dear qpid developers, I have a question regarding a setup I have running, to test out link-routing. The topology looks as follows (simplified), where ZoneA is Azure and ZoneB is AWS: Edge Router (Zone A) → Mesh Router (Zone A) → Mesh Router (Zone B) → Edge Router (Zone B) à Edge Broker (Zone B)