Yeah fair enough, was more curious if anyone had heard of this happening
before, nothing has really stood out in logs, but will keep looking and try
increasing logging level to see if anything stands out.
Thanks!
Stefan
On Tue, 2021-04-20 at 09:28 -0500, Matt Pavlovich wrote:
External Email: Us
Hi Stefan-
That can be difficult to troubleshoot without analyzing the logs and kahadb
files directly— which understandably can be problematic in enterprise use cases
where there is sensitive data stored.
That being said, if the issue was wide-spread there would be an expectation of
users rep
5.16.0, this was also happening in an older version 5.15.2
On Tue, 2021-04-20 at 09:07 -0500, Justin Bertram wrote:
> External Email: Use caution opening links & attachments.
>
>
> What version are you using?
>
>
> Justin
>
> On Tue, Apr 20, 2021 at 9:02 AM Stefan Lemdal
> wrote:
>
> > Every now
What version are you using?
Justin
On Tue, Apr 20, 2021 at 9:02 AM Stefan Lemdal wrote:
> Every now and then a queue after consuming a few million messages will end
> up showing a queue size of 0, but the message store size is above 0,
> indicating there are still messages in the queue but not
Every now and then a queue after consuming a few million messages will end up
showing a queue size of 0, but the message store size is above 0, indicating
there are still messages in the queue but not able to be seen or consumed. When
the server is restarted, the messages show up in the queue an
I think you're asking how to ensure that the broker will close a client
connection if that connection is idle for 60s or longer. If so, that
setting is the wireFormat.maxInactivityDuration element of the URIs you
provided, and you'll want to change the current value of 0 to 6
(milliseconds) for
