activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-5227) Scheduler db-*.log files not being deleted
Date Wed, 06 Aug 2014 22:33:12 GMT

     [ https://issues.apache.org/jira/browse/AMQ-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-5227.
-----------------------------

    Resolution: Cannot Reproduce

There's no test case that reproduces this.  The scheduler was rewritten and will be all new
in the 5.11.0 release.

> Scheduler db-*.log files not being deleted
> ------------------------------------------
>
>                 Key: AMQ-5227
>                 URL: https://issues.apache.org/jira/browse/AMQ-5227
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Job Scheduler
>    Affects Versions: 5.9.0
>            Reporter: Eelco van Dijk
>             Fix For: WAITING_FOR_TEST
>
>         Attachments: scheduleDB.zip
>
>
> Many db log files are kept in the scheduler folder without references in the schedulerDb.
It seems like the db log files are kept but should have been deleted.
> The environment is configured with mysql message persistence and schedulersupport enabled.
> Our folder structure is as follows:
> first is: 
>  db-13.log
> and then a few other logs: 
>  db-....log
> last is:
>  db-62.log
>  scheduleDB.data
>  scheduleDB.redo
> Number of messages scheduled: 0.
> I think there should only be one db.log file present is this case. Why are there so many
db.log files present in the scheduler folder?
> The remove method is called from the main schedule loop.
> This remove method is called with a timestamp maybe some log files are skipped because
of this. When i call the remove method manually all the skipped log files are deleted from
the journal.
> I've attached the scheduleDB as a zip.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message