3 Replies Latest reply on Oct 26, 2010 1:18 PM by Clebert Suconic

    Backup server MUST be started before live server

    jeroen.v Newbie

      Hi all, we've successfully set up HornetQ 2.1.2.Final on 2 machines: srv1 and srv2.

      • Srv1 contains live node 1 and backup node 2.
      • Srv2 contains live node 2 and backup node 1.


      As you can guess the backup node 1 is backup for live node 1, same for node 2. The replication method that is used is data replication, not shared storage. We now want to add the startup scripts in the appropriate linux runlevel so that the HornetQ instances are started when the server is started.


      This is where we have a problem: if for example srv1 is first to start up backup node2 will come up ok, but live node1 will com up with the following error:

      Exception in thread "main" java.lang.IllegalStateException: Incompletely deployed:


        Deployment "JMSServerManager" is in error due to: HornetQException[errorCode=104 message=Backup server MUST be started before live server. Initialisation will not proceed.]


      For me it is ok that this is thrown as an error, however this situation should be resolved automatically once the backup server becomes available. And this is not the case.


      Is it possible to configure some kind of retry policy when starting up a live node with a backup connector? If not, is there any other workaround available?


      If this is a bug can it be added to https://jira.jboss.org/browse/HORNETQ-402?


      Thanks for your help.