[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385419#comment-14385419
]
Scott Feldstein commented on AMQ-5082:
--
I've been running with Jim's patch for several
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052614#comment-14052614
]
Scott Feldstein commented on AMQ-5082:
--
increasing the ticktime didn't solve the issue
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967073#comment-13967073
]
Scott Feldstein commented on AMQ-5082:
--
This can be reproduced by causing a network dis
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Feldstein updated AMQ-5082:
-
Attachment: 03-07.tgz
I've been doing some more digging on this. It turns out that there is a job
Scott Feldstein created AMQ-5082:
Summary: ActiveMQ replicatedLevelDB cluster breaks, all nodes stop
listening
Key: AMQ-5082
URL: https://issues.apache.org/jira/browse/AMQ-5082
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Feldstein updated AMQ-5082:
-
Attachment: mq-node2-cluster.failure
mq-node3-cluster.failure
zookee
