activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AMQ-6285) MessageDatabase doesn't properly cleanup the checkpoint scheduler on shutdown
Date Mon, 09 May 2016 19:08:13 GMT


ASF subversion and git services commented on AMQ-6285:

Commit db3f8b3554a1ecf5c9fcf917948d10e5fa8de28e in activemq's branch refs/heads/master from
[;h=db3f8b3 ]

Revert ""

This reverts commit 60b0c4f85ada06875e09b1bc3fbefac0f9fb6156.

Inadvertantly commited a bunch of changes by mistake

> MessageDatabase doesn't properly cleanup the checkpoint scheduler on shutdown
> -----------------------------------------------------------------------------
>                 Key: AMQ-6285
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, KahaDB
>    Affects Versions: 5.13.3
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>            Priority: Minor
> 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

View raw message