You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2014/11/26 16:59:13 UTC
[jira] [Comment Edited] (AMQ-5458) MBean to help testing replicated
levelDB
[ https://issues.apache.org/jira/browse/AMQ-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224801#comment-14224801 ]
Hiram Chirino edited comment on AMQ-5458 at 11/26/14 3:58 PM:
--------------------------------------------------------------
Implemented. New mbean will be registered with the same ObjectName as the leveldb mbean but with ',view=Test' attribute appended when the system property org.apache.activemq.leveldb.test=true'.
was (Author: chirino):
Implemented. New mbean will be registered with the same ObjectName as the leveldb mbean but with ',test=test' attribute appended when the system property org.apache.activemq.leveldb.test=true'.
> MBean to help testing replicated levelDB
> ----------------------------------------
>
> Key: AMQ-5458
> URL: https://issues.apache.org/jira/browse/AMQ-5458
> Project: ActiveMQ
> Issue Type: New Feature
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 5.11.0
>
>
> Would be nice if you set a system property like 'org.apache.activemq.leveldb.test=true' that you then get a MBean for leveldb stores that allows you to suspend/resume calls around the journal writes, deletes and force operations so you can more easily write tests that validate consistency and recovery.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)