activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3801) Job scheduler can lose data on forced kill
Date Thu, 05 Apr 2012 11:37:26 GMT

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

Dejan Bosanac resolved AMQ-3801.
--------------------------------

    Resolution: Fixed

Fixed with svn revision 1309780
                
> Job scheduler can lose data on forced kill
> ------------------------------------------
>
>                 Key: AMQ-3801
>                 URL: https://issues.apache.org/jira/browse/AMQ-3801
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.5.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.6.0
>
>
> The page file that keeps the index of jobs to be scheduled is using default write batch
size of 1000. That means that index could get into incorrect state when broker is killed (and
there's no recovery for this index). Turning off batching (as it's not needed for this low-volume
index) will ensure that changes are always persisted immediately. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message