[
https://issues.apache.org/jira/browse/AMQ-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon resolved AMQ-6285.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 5.13.4
5.14.0
The scheduler is properly nulled out on store close now.
> MessageDatabase doesn't properly cleanup the checkpoint scheduler on shutdown
> -----------------------------------------------------------------------------
>
> Key: AMQ-6285
> URL: https://issues.apache.org/jira/browse/AMQ-6285
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, KahaDB
> Affects Versions: 5.13.3
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Minor
> Fix For: 5.14.0, 5.13.4
>
>
> On KahaDB store close the checkpoint scheduler service is shutdown but it is
> not set to null. This is an issue because on startup of the store, the
> scheduler is checked for null and only started if it is null. Therefore, if
> a store was previously started and shutdown, when started again the thread
> would not re-start.
> This would not normally cause a problem for the usual use case as a store is
> typically only closed when the broker is shut down, however it is a good idea
> to fix it as this behavior could change in the future plus the start/stop
> methods are public on the store so it is possible to start/stop the store
> even though it isn't normally done.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
