They seem fair enough and quite related.
As a side note, I have a bug with the dispatch router 0.6.1 but I haven't
submitted it yet because I haven't reduced the test case yet.
In resume, when I connect 2 dispatchers (inter-router) and then delete the
connector/listener of "inter-router". If
Sorry, those Jira numbers and descriptions are mismatched. Here's the
correct list:
- DISPATCH-496 - Activation of an autolink does not result in issuing
credit to a blocked sender
- DISPATCH-505 - Eventual loss of credit on inter-router control
On 09/29/2016 10:47 AM, Adel Boutros wrote:
They seem fair enough and quite related.
As a side note, I have a bug with the dispatch router 0.6.1 but I haven't
submitted it yet because I haven't reduced the test case yet.
In resume, when I connect 2 dispatchers (inter-router) and then
Hi,
I'm trying to set up two concurrent receiver links on the same broker: one
to listen to messages from a queue (e.g. `test.queue`) as a
consumer/worker, another to listen to the same queue but with a
distribution mode of `copy` in order to passively track some information
without corrupting
On 09/24/2016 05:32 AM, Adel Boutros wrote:
We are indeed in favor of a minor release as long as the latest version is
still 0.6.x and we are willing to re-launch our tests and give feedback on the
release candidate once provided (It shouldn't take us more than a day to
compile and test).
Do
On Thu, Sep 29, 2016 at 5:16 PM, Gordon Sim wrote:
> On 29/09/16 15:43, Matt Broadstone wrote:
>
>> I'm trying to set up two concurrent receiver links on the same broker:
>> one
>> to listen to messages from a queue (e.g. `test.queue`) as a
>> consumer/worker, another to listen
On 29/09/16 15:43, Matt Broadstone wrote:
I'm trying to set up two concurrent receiver links on the same broker: one
to listen to messages from a queue (e.g. `test.queue`) as a
consumer/worker, another to listen to the same queue but with a
distribution mode of `copy` in order to passively