[jira] [Commented] (ARTEMIS-919) Issues creating jms queues in core config in broker.xml

[ https://issues.apache.org/jira/browse/ARTEMIS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822379#comment-15822379 ] Justin Bertram commented on ARTEMIS-919: I just tested this on 1.5.1 and I don't see any issues

[jira] [Closed] (AMQ-6559) MultiKahaDBPersistenceAdapter crash

[ https://issues.apache.org/jira/browse/AMQ-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-6559. - Resolution: Cannot Reproduce Old version with no reproducer to test on new releases. Recommend an update

[jira] [Closed] (AMQ-6558) Constant reconnecting after ActiveMQ restart with HTTP Layer

[ https://issues.apache.org/jira/browse/AMQ-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-6558. - Resolution: Duplicate > Constant reconnecting after ActiveMQ restart with HTTP Layer >

[jira] [Assigned] (ARTEMIS-919) Issues creating jms queues in core config in broker.xml

[ https://issues.apache.org/jira/browse/ARTEMIS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-919: -- Assignee: Justin Bertram > Issues creating jms queues in core config in broker.xml >

[jira] [Closed] (AMQ-6496) levelDB log files fill up disk on 5.14.0 & 5.14.1 releases

[ https://issues.apache.org/jira/browse/AMQ-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-6496. - Resolution: Won't Fix LevelDB support has been deprecated and is not longer being developed by the

[jira] [Resolved] (AMQ-6563) MessageDatabase.load could leave writeLock incorrectly locked

[ https://issues.apache.org/jira/browse/AMQ-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-6563. --- Resolution: Fixed Fix Version/s: 5.14.4 5.15.0 > MessageDatabase.load could

[jira] [Commented] (AMQ-6563) MessageDatabase.load could leave writeLock incorrectly locked

[ https://issues.apache.org/jira/browse/AMQ-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821975#comment-15821975 ] ASF subversion and git services commented on AMQ-6563: -- Commit

[jira] [Commented] (AMQ-6563) MessageDatabase.load could leave writeLock incorrectly locked

[ https://issues.apache.org/jira/browse/AMQ-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821974#comment-15821974 ] ASF subversion and git services commented on AMQ-6563: -- Commit

[jira] [Created] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

Gary Tully created AMQ-6562: --- Summary: WARN TopicStorePrefetch cursor got duplicate from store Key: AMQ-6562 URL: https://issues.apache.org/jira/browse/AMQ-6562 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

[ https://issues.apache.org/jira/browse/AMQ-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821598#comment-15821598 ] Gary Tully commented on AMQ-6562: - The WARN is expected when the cache is exhausted and page in begins at

[jira] [Commented] (AMQ-5249) "cursor got duplicate" error after upgrade

[ https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821635#comment-15821635 ] Gary Tully commented on AMQ-5249: - For the durable topic sub case the scenario is captures in

[jira] [Commented] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

[ https://issues.apache.org/jira/browse/AMQ-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821633#comment-15821633 ] ASF subversion and git services commented on AMQ-6562: -- Commit

[jira] [Resolved] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

[ https://issues.apache.org/jira/browse/AMQ-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6562. - Resolution: Fixed > WARN TopicStorePrefetch cursor got duplicate from store >

[jira] [Comment Edited] (AMQ-5249) "cursor got duplicate" error after upgrade

[ https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821635#comment-15821635 ] Gary Tully edited comment on AMQ-5249 at 1/13/17 11:12 AM: --- For the durable topic

[jira] [Comment Edited] (AMQ-5249) "cursor got duplicate" error after upgrade

[ https://issues.apache.org/jira/browse/AMQ-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821635#comment-15821635 ] Gary Tully edited comment on AMQ-5249 at 1/13/17 11:13 AM: --- For the durable topic

[jira] [Comment Edited] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

[ https://issues.apache.org/jira/browse/AMQ-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821598#comment-15821598 ] Gary Tully edited comment on AMQ-6562 at 1/13/17 10:51 AM: --- The WARN is expected

[jira] [Comment Edited] (AMQ-6562) WARN TopicStorePrefetch cursor got duplicate from store

[ https://issues.apache.org/jira/browse/AMQ-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821598#comment-15821598 ] Gary Tully edited comment on AMQ-6562 at 1/13/17 10:50 AM: --- The WARN is expected

[jira] [Created] (ARTEMIS-919) Issues creating jms queues in core config in broker.xml

Thorsten Kunz created ARTEMIS-919: - Summary: Issues creating jms queues in core config in broker.xml Key: ARTEMIS-919 URL: https://issues.apache.org/jira/browse/ARTEMIS-919 Project: ActiveMQ Artemis

[jira] [Created] (AMQ-6563) MessageDatabase.load could leave writeLock incorrectly locked

james created AMQ-6563: -- Summary: MessageDatabase.load could leave writeLock incorrectly locked Key: AMQ-6563 URL: https://issues.apache.org/jira/browse/AMQ-6563 Project: ActiveMQ Issue Type: Bug