You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by moffatrp <ri...@thomsonreuters.com> on 2018/08/15 10:37:54 UTC
Scheduler not cleaning up with 5.15.2
The individual managing AMQ recently left the company and I was volunteered
to take over. So I'm new to AMQ. I've spent a couple of weeks trying to
chase this down and need some help.
I'm seeing huge growth in the number of scheduler DB files. I'm currently
using amq 5.15.2 (recent updrade from 5.9). Turning on logging shows the
following messages (and lots of them):
2018-08-15 00:34:36,829 | TRACE | A remove in log 6727 has an add still in
existance in 6726. |
org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl | ActiveMQ
Journal Checkpoint Worker
2018-08-15 00:34:36,829 | TRACE | A remove in log 6728 has an add still in
existance in 6726. |
org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl | ActiveMQ
Journal Checkpoint Worker
2018-08-15 00:34:36,829 | TRACE | A remove in log 6729 has an add still in
existance in 6728. |
org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl | ActiveMQ
Journal Checkpoint Worker
2018-08-15 00:34:36,829 | TRACE | A remove in log 6730 has an add still in
existance in 6726. |
org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl | ActiveMQ
Journal Checkpoint Worker
2018-08-15 00:34:36,829 | TRACE | A remove in log 6731 has an add still in
existance in 6727. |
org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl | ActiveMQ
Journal Checkpoint Worker
2018-08-15 00:34:36,829 | TRACE | A remove in log 6732 has an add still in
existance in 6729. |
org.apache.activemq.store.kahadb.scheduler.JobSchedulerStoreImpl | ActiveMQ
Journal Checkpoint Worker
New log files are being added faster then they get cleaned up and eventually
the 500gig disk fills with obvious catastrophic results.
I did see a ticket for this issue (
http://activemq.2283324.n4.nabble.com/activemq-git-commit-https-issues-apache-org-jira-browse-AMQ-6152-tp4725246.html
<http://activemq.2283324.n4.nabble.com/activemq-git-commit-https-issues-apache-org-jira-browse-AMQ-6152-tp4725246.html>
) that indicated it was resolved in 5.14.0.
Anyone have a suggestion?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html