When a system is slow, there's always something (or several somethings,
rotating between them) that is the limiting resource. I'd start by trying
to determine what that resource is, using standard OS monitoring tools (top
and the like). If you can tell that CPU is a primary bottleneck, use a
profil
The version is 5.14.3
On 4/22/17 6:55 PM, Timothy Bish wrote:
On 04/22/2017 05:56 PM, Steve Hill wrote:
We now realize that the number after the @ is the file number being
processed and after the colon is the offset in the file. Eg,
97226:18610005 means db-97226.log is being processed. Based
On 04/22/2017 05:56 PM, Steve Hill wrote:
We now realize that the number after the @ is the file number being
processed and after the colon is the offset in the file. Eg,
97226:18610005 means db-97226.log is being processed. Based on this at
least we now know how far we are through the startup
We now realize that the number after the @ is the file number being
processed and after the colon is the offset in the file. Eg,
97226:18610005 means db-97226.log is being processed. Based on this at
least we now know how far we are through the startup. It looks like it
will take a further 2
Hi!
Can anyone provide guidance on why restarting ActiveMQ can take hours?
We were seeing lots of message not found in sequence and it is currently
at 5.9M entries recovered. Is there a way to know how many entries
there are so we have an idea when it might finish?
There are currently abou
Did anyone get a chance to look at this ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-kahaDB-recovery-tp4680998p4681049.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
urnalFiles, ignoreMissingJournalfiles. Default values are
here
Thanks,
Anuj
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-kahaDB-recovery-tp4680998.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
we maybe got a corrupt scheduler after running activemq
under high load a while.
The symptom is:
0) ls -l scheduler/
total 181652
-rw-r--r-- 1 root root 33554516 2012-11-01 20:20 db-1.log
-rw-r--r-- 1 root root 33554677 2012-11-02 13:24 db-2.log
-rw-r--r-- 1 root root 33554541 2012-11-02 1
