You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Arthur Naseef (JIRA)" <ji...@apache.org> on 2014/06/07 22:55:02 UTC

[jira] [Commented] (AMQ-4399) jdbcPersistenceAdapter takes a long time to shutdown, causing journal recovery

    [ https://issues.apache.org/jira/browse/AMQ-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020966#comment-14020966 ] 

Arthur Naseef commented on AMQ-4399:
------------------------------------

Git commit: https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=d77014aa5d8b8c9869c8ab7ba9f27edabb052496


> 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: Improvement
>          Components: Broker
>    Affects Versions: 5.7.0
>         Environment: 5.7.0.fuse-71-047
> MySQL with Journal
>            Reporter: Jason Shepherd
>            Assignee: Claus Ibsen
>             Fix For: 5.10.0
>
>         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 was sent by Atlassian JIRA
(v6.2#6252)