Re: Qpid dispatch unstable inter-router connections

On Wed, Apr 11, 2018 at 11:47 PM, Ted Ross wrote: > This is a pretty low-level framing issue that definitely should not be > happening. Also, your configuration should be fine. Is there > anything unusual about the network over which the inter-router > connections are

Re: Qpid dispatch unstable inter-router connections

On Wed, Apr 11, 2018 at 11:21 PM, Ganesh Murthy wrote: > > > message: Connection to router-2:55672 failed: amqp:session:invalid-field > > sequencing error, expected delivery-id 7, got 6 > > > Is it complaining about the same delivery id (7 got 6) every time in the > sequencing

Qpid dispatch unstable inter-router connections

Hi all, I am running a three node fully connected mesh of dispatch routers with 1 attached clients and I am seeing some unstable inter-router connections (I am sending around 1000 message per second through the network). The inter-router connections fail every so many seconds with the

Dispatch router 1.0.0 seems to not always propagate link credit when using link routing

I am experiencing a problem while using the dispatch router as a proxy to the artemis broker. I have done some investigation and it looks like the dispatch router is not always forwarding link credit to the broker. I have the following setup: proton clients 0.9.0 (old, i know :p) <---> qdrouterd

Re: Messenger doesn't seem to have any clean way to recover from errors.

I think the main problem here is not in the messenger but a problem in the protocol engine I discovered a while ago: https://issues.apache.org/jira/browse/PROTON-644?filter=-2 ... there is no way for the messenger to recover or handle the error because it can not see the connection fail. --

Re: proton Messenger error handling/recovery REQUEST FEEDBACK!

On Tue, Sep 9, 2014 at 5:22 PM, Alan Conway acon...@redhat.com wrote: Given that engine is already a more complete and flexible API (in the sense of offering full low-level access to the entire AMQP protocol), and that people are demonstrating that it can be made easier to use by layering

Re: High memory footprint of proton-j in ActiveMQ

, Marcel Meulemans m.meulem...@tkhinnovations.com wrote: I have been experiencing high (resident) memory usage when using ActiveMQ with large amounts of AMQP connections. After some investigation I have traced this memory usage back to proton-j. The cause is that by default ActiveMQ

High memory footprint of proton-j in ActiveMQ

I have been experiencing high (resident) memory usage when using ActiveMQ with large amounts of AMQP connections. After some investigation I have traced this memory usage back to proton-j. The cause is that by default ActiveMQ defines a maxFrameSize of 1MB for the AmqpWireFormat and in proton-j

proton-j messenger stopped function

When calling messenger.stopped() directly after messenger.start() it returns true ... until you do some messaging. This was not what I would expect. Looking at the code the stopped function reads: public boolean stopped() { return _allClosed.test(); } I was wondering if this should not be