[ https://issues.jboss.org/browse/WFLY-1563?page=com.atlassian.jira.plugin.... ] Florin Slev updated WFLY-1563: ------------------------------ Description: I believe that it would be useful a feature for removing the HornetQ journal files in case of removing a Live-Backup configuration. Right now if you setup a HornetQ Live-Backup configuration using replication, both live and backup servers will have the same journal data. If you want to get rid of the live-backup configuration (via CLI: backup=false) in order to use the two servers as normal cluster nodes and restart them, they will be both seen as "live"s and will continuosly log warnings due to the fact they have same journal data. In order to remediate this problem, you have to manually remove the journal folders from the backup server in order to restart with a "fresh" journal. was: I believe that it would be useful a feature for removing the HornetQ journal files in case of removing a Live-Backup configuration. Right now if you setup a HornetQ Live-Backup configuration using replication, both live and backup servers will have the same journal data. When removing the live-backup configuration (via CLI: backup=false) and restart servers, they will be both seen as "live"s and will continuosly log warnings due to the fact they have same journal data. In order to remediate this problem, you have to manually remove the journal folders from the backup server in order to restart with a "fresh" journal. -- 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