[jira] [Updated] (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:all-tabpanel ] Claus Ibsen updated AMQ-4399: - Issue Type: Improvement (was: Bug) > 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 > 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.1#6144)
[jira] [Updated] (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:all-tabpanel ] Claus Ibsen updated AMQ-4399: - Fix Version/s: 5.10.0 > 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 > 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.1#6144)
[jira] [Updated] (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: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
