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 1
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
message:
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 error ? I am hoping
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 communicating?
I think not
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 som
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 th
ent to me. We could possibly put in a
> threshold to let people choose their own tradeoff, e.g. below X buffer
> size we use one strategy, and above it we use another. Either way, I'd go
> ahead and file a JIRA with a pointer to your commit.
>
> --Rafael
>
>
> On Thu
Hi,
Support for idle timeout and the sending of heartbeat messages (as in
proton-c) seems to be missing from proton-j. As I have a need for it I
would like to look into adding it. Are there any ideas floating around as
to where this functionality should go?
- Sending and receiving idle timeout va
On Tue, Sep 9, 2014 at 5:22 PM, Alan Conway 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 tools on top, perha
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.
--
Marce
10 matches
Mail list logo