1 Reply Latest reply on Nov 21, 2013 6:19 PM by synclpz

    Error in failback on adding some configurations in hornetq-configuration.xml

    Manu Srivastava Newbie

      Hi,

       

      I have a hornetq failover/failback setup (using replication feature available in 2.3.0.Final release) which works fine normally. However when I add some configurations related to journal settings, after that only failover works fine. An error keeps coming during failback in live server logs (please note that a few times I just got the Connection Failure log, and after that failback worked...but I didn't see 'backup announced' in logs):

       

      11:41:42,199 INFO  [org.hornetq.integration.bootstrap] HQ101000: Starting HornetQ Server

      11:41:43,272 WARN  [org.hornetq.core.server] HQ222018: AIO was not located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

      11:41:43,364 INFO  [org.hornetq.core.server] HQ221000: live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=false,journalDirectory=/mnt/jms/mqtt/journal,bindingsDirectory=/mnt/jms/mqtt/bindings,largeMessagesDirectory=/mnt/jms/mqtt/large-messages,pagingDirectory=/mnt/jms/mqtt/paging)

      11:41:43,584 WARN  [org.hornetq.core.server] HQ222162: Moving data directory /mnt/jms/mqtt/bindings to /mnt/jms/mqtt/bindings1

      11:41:43,585 WARN  [org.hornetq.core.server] HQ222162: Moving data directory /mnt/jms/mqtt/journal to /mnt/jms/mqtt/journal1

      11:41:43,586 WARN  [org.hornetq.core.server] HQ222162: Moving data directory /mnt/jms/mqtt/paging to /mnt/jms/mqtt/paging1

      11:41:43,587 WARN  [org.hornetq.core.server] HQ222162: Moving data directory /mnt/jms/mqtt/large-messages to /mnt/jms/mqtt/large-messages1

      11:41:43,606 INFO  [org.hornetq.core.server] HQ221013: Using NIO Journal

      11:41:43,609 WARN  [org.hornetq.core.server] HQ222007: Security risk! HornetQ is running with the default cluster admin user and default password. Please see the HornetQ user guide, cluster chapter, for instructions on how to change this.

      11:41:43,772 INFO  [org.hornetq.core.server] HQ221109: HornetQ Backup Server version 2.3.0.SNAPSHOT (colonizer, 123) [null] started, waiting live to fail before it gets active

      11:41:49,045 WARN  [org.hornetq.core.client] HQ212037: Connection failure has been detected: HQ119015: The connection was disconnected because of server shutdown [code=DISCONNECTED]

      11:41:49,643 ERROR [org.hornetq.core.server] HQ224000: Failure in initialisation: HornetQException[errorType=ILLEGAL_STATE message=HQ119026: Backup Server was not yet in sync with live]

              at org.hornetq.core.server.impl.HornetQServerImpl$SharedNothingBackupActivation.run(HornetQServerImpl.java:2430) [hornetq-server.jar:]

              at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]

       

       

      HornetQException[errorType=ILLEGAL_STATE message=HQ119026: Backup Server was not yet in sync with live]

              at org.hornetq.core.server.impl.HornetQServerImpl$SharedNothingBackupActivation.run(HornetQServerImpl.java:2430)

              at java.lang.Thread.run(Thread.java:722)

      ^C11:41:56,067 INFO  [org.hornetq.integration.bootstrap] HQ101001: Stopping HornetQ Server

      11:41:56,104 INFO  [org.hornetq.core.server] HQ221002: HornetQ Server version 2.3.0.SNAPSHOT (colonizer, 123) [ddbe4401-4b8e-11e3-add7-3d7449fe1f06] stopped

       

      Given below is the list of configuration I am adding to hornetq-configuration.xml on both live and backup servers:

       

          <id-cache-size>10000</id-cache-size>

         <connection-ttl-override>-1</connection-ttl-override>

         <scheduled-thread-pool-max-size>50</scheduled-thread-pool-max-size>

         <thread-pool-max-size>-1</thread-pool-max-size>

         <journal-file-size>50485760</journal-file-size>

         <journal-sync-non-transactional>false</journal-sync-non-transactional>

         <journal-sync-transactional>false</journal-sync-transactional>

         <journal-buffer-timeout>100000000</journal-buffer-timeout>

         <journal-max-io>50000</journal-max-io>

       

      Any idea what can be causing this?

      FYI: We are running hornetq on an 8 core 32 GB machine.