I see you submitted https://issues.apache.org/jira/browse/AMQ-6095 to capture this bug. Thanks.
I've never done anything with LevelDB, so what I know comes just from reading the documentation and the questions people like you post to this list. So I don't have any suggestions to offer, other than to say that your described configuration sounds reasonable as far as it goes, so I expect that the problem you're hitting stems from a bug rather than a misconfiguration on your end, which is why I suggested submitting a bug report in JIRA. Tim On Fri, Dec 18, 2015 at 11:17 AM, stephenschaeffer < step...@schaefferarts.com> wrote: > Hi Tim, > > First off, thanks for replying and the tip on JIRA. > > Does this configuration strike you as unusual in any way? Do you have any > suggestions on how we can reconfigure things to be either more robust or > more in line with best practices, if any exist? From our position of > relative ignorance this seemed like the way to set things up, but I'd be > happy to rework things. > > Thanks again for your help on this. > > Steph > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-failover-Java-level-deadlock-tp4705128p4705183.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
