The broker does already have a variety of checks that attempt to warn you
defensively about certain potential problems and to prevent you from
running into them (producer flow control, for example), but I'm not aware
of a check specifically on the number of live KahaDB log files. In part,
I'm not a
Thanks for the detailed response. I generally agree it's not flawed and it
is likely my configuration, I'm trying to take steps to track down the
cause, but of course it is behaving now.
I do think some defensiveness to protect it from shutting down regardless
of configuration would be a good idea
Responses inline.
On Fri, Oct 20, 2017 at 5:46 AM, Lionel van den Berg
wrote:
> Hi, thanks for the response.
>
> Some questions on these points from the troubleshooting.
>
>
>1. *It contains a pending message for a destination or durable topic
>subscription*
>
> This seems a little flawe
Hi, thanks for the response.
Some questions on these points from the troubleshooting.
1. *It contains a pending message for a destination or durable topic
subscription*
This seems a little flawed, if a consumer who I have little control of is
mis-behaving then my ActiveMQ can end up shutt
The question I asked Lionel applies to you ad well.
On Sep 29, 2017 9:12 AM, "GlenWard" wrote:
> Facing the same problem. I had done all possible solutions but still
> problem
> remains unsolved
>
>
>
> http://www.menstwilight.com/kamagra.html
>
>
>
>
> --
> Sent
Facing the same problem. I had done all possible solutions but still problem
remains unsolved
http://www.menstwilight.com/kamagra.html
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Have you run the troubleshooting procedures in
http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html?
What did they indicate?
On Sep 12, 2017 8:27 PM, "Lionel van den Berg" wrote:
Hi all,
ActiveMQ 5.14.4 running on Suse enterprise 11 sp4
I'm having trouble with the log fi
Hi all,
ActiveMQ 5.14.4 running on Suse enterprise 11 sp4
I'm having trouble with the log files (like db-1.log) not being cleaned up
and after about 6 weeks of running ActiveMQ shuts down because there are
too many files in the directory (I think it was 3000), it cannot be
restarted we think due t
