Return-Path: 
 <dev-return-42705-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 238AE10AA6
	for <apmail-activemq-dev-archive@www.apache.org>;
 Thu, 16 Jan 2014 18:25:24 +0000 (UTC)
Received: (qmail 60655 invoked by uid 500); 16 Jan 2014 18:25:20 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 60559 invoked by uid 500); 16 Jan 2014 18:25:20 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 60548 invoked by uid 99); 16 Jan 2014 18:25:20 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jan 2014 18:25:20 +0000
Date: Thu, 16 Jan 2014 18:25:20 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12545345.1331043597492.17334.1389896720081@arcas>
In-Reply-To: <JIRA.12545345.1331043597492@arcas>
References: <JIRA.12545345.1331043597492@arcas>
Subject: [jira] [Updated] (AMQ-3758) Recover scheduler database option
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Timothy Bish updated AMQ-3758:
------------------------------

    Fix Version/s:     (was: 5.10.0)
                   5.11.0

> Recover scheduler database option
> ---------------------------------
>
>                 Key: AMQ-3758
>                 URL: https://issues.apache.org/jira/browse/AMQ-3758
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Message Store
>    Affects Versions: 5.5.0
>            Reporter: Sergei Sokolov
>              Labels: scheduler
>             Fix For: 5.11.0
>
>
> I am not sure why, but Scheduler database got corrupted, and some messages couldn't be delivered to a broker. I got many exceptions similar to:
> {code}
> 2012-03-02 03:26:08,234 | ERROR | JMS Failed to schedule job | org.apache.activemq.broker.scheduler.JobSchedulerImpl | JobScheduler:JMS 
> java.io.IOException: Could not locate data file <correct-file-path>\db-2.log 
>         at org.apache.kahadb.journal.Journal.getDataFile(Journal.java:350) 
>         at org.apache.kahadb.journal.Journal.read(Journal.java:597) 
>         at org.apache.activemq.broker.scheduler.JobSchedulerStore.getPayload(JobSchedulerStore.java:315) 
>         at org.apache.activemq.broker.scheduler.JobSchedulerImpl.fireJob(JobSchedulerImpl.java:421) 
>         at org.apache.activemq.broker.scheduler.JobSchedulerImpl.mainLoop(JobSchedulerImpl.java:473) 
>         at org.apache.activemq.broker.scheduler.JobSchedulerImpl.run(JobSchedulerImpl.java:429) 
>         at java.lang.Thread.run(Unknown Source) 
> {code}
> The problem is that there is no way to restore the database like you can if you are working with the main ActiveMQ database. You can fix the main database by specifying the following configuration:
> {code}
> <persistenceAdapter>  
>             <kahaDB directory="${activemq.base}/data/kahadb" 
>                     ignoreMissingJournalfiles="true" 
>                     checkForCorruptJournalFiles="true" 
>                     checksumJournalFiles="true" />  
> </persistenceAdapter>
> {code}
> It would be nice to have the same feature for the scheduler database.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)