Hi again,
i have verified, that the durable subscriber on reconnect is configured
correctly,
when I set keepDurableSubsActive to false on the broker.
Best regards
Andreas
On 02/10/14 12:03, Andreas Gies wrote:
Thanks Gary,
to me it looks like configure is not being called when the subscribe
Thanks Gary,
to me it looks like configure is not being called when the subscriber
reconnects.
I ll try to trace that later.
I'll create a JIRA for now.
Thanks
Andreas
On 02/10/14 11:40, Gary Tully wrote:
that looks like a bug and you should raise a jira.
however the broker config will onl
that looks like a bug and you should raise a jira.
however the broker config will only override the default value, so a client
provided value will take precedence if it is specified.
It seems the client does not specify a value, the broker 5 is used the
first time, and the default on subsequent r
Hi,
i forgot to paste the output of the test earlier, as you can see the
test fails when checking the prefetch size for
the reconnected subscriber.
Best regards
Andreas
Discovery starting.
Discovery completed in 374 milliseconds.
Run starting. Expected test count is: 1
PrefetchSizeSpec:
2014-
Hello,
I am using Active MQ 5.10 within a Karaf based application and have
spent the last couple of days
investigating an OOM Exception we were getting occasionally.
It turned out, that the OOM happens occasionallly when we reconnect a
durable subscriber that
would have a large amount of data
