Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 22 Mar 2013 00:35:15 +0000 (UTC)
From: "Jason Shepherd (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12638419.1363912400592.31682.1363912515882@arcas>
In-Reply-To: <JIRA.12638419.1363912400592@arcas>
References: <JIRA.12638419.1363912400592@arcas>
Subject: [jira] [Updated] (AMQ-4399) jdbcPersistenceAdapter takes a long
 time to shutdown, causing journal recovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jason Shepherd updated AMQ-4399:
--------------------------------

    Attachment: activemq.xml
    
> jdbcPersistenceAdapter takes a long time to shutdown, causing journal recovery
> ------------------------------------------------------------------------------
>
>                 Key: AMQ-4399
>                 URL: https://issues.apache.org/jira/browse/AMQ-4399
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.7.0
>         Environment: 5.7.0.fuse-71-047
> MySQL with Journal
>            Reporter: Jason Shepherd
>         Attachments: activemq.xml
>
>
> Using the attached configuration, we have configured JDBC persistence with a journal. After sending 30,000 messages to a queue, using persistent messages, we see that shutdown of the broker timeouts out and the process is killed by the OS.
> After restarting the broker, a journal recovery takes place, which takes a long time to complete. We would like to avoid such a long restart time in this scenario.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira