1 Reply Latest reply on Aug 23, 2011 8:47 AM by ataylor

    Jbossas 6.1.0-Final + HornetQ 2.2.5

    srazza

      Hi,

      we'd like to setup two nodes with HornetQ 2.2.5 (integrated in jbossas 6.1.0-Final) in HA in Live/Backup mode.

      Both node mount a shared file system where I setup the journal file system.

      I've used the following configuration for the LIVE node:

       

         <shared-store>true</shared-store>

         <journal-directory>/global/share/HQ/journal</journal-directory>

         <journal-type>NIO</journal-type>

         <persistence-enabled>true</persistence-enabled>

       

      I've used the following configuration for the BACKUP node:

       

         <shared-store>true</shared-store>

         <backup>true</backup>

         <journal-directory>/global/share/HQ/journal</journal-directory>

         <journal-type>NIO</journal-type>

         <persistence-enabled>true</persistence-enabled>

       

      Both jbossas instances start correctly (I've started both with the same partition name) and the cluster views seems to work correctly, but when I try to access the admin-console of the backup node, I get the following error in the jbossas log:

       

      10:32:10,938 WARN  [org.rhq.core.pc.inventory.InventoryManager] Failure during discovery for [JMS Manager] Resources - failed after 22 ms.: java.lang.Exception: Discovery component invocation failed.

              at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:283) [:3.0.0]

              at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_25]

              at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_25]

              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25]

              at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]

      Caused by: java.lang.NullPointerException

              at org.jboss.as.integration.hornetq.jopr.JMSManagerDiscoveryComponent.getVersion(JMSManagerDiscoveryComponent.java:75)

              at org.jboss.as.integration.hornetq.jopr.JMSManagerDiscoveryComponent.discoverResources(JMSManagerDiscoveryComponent.java:48)

              at sun.reflect.GeneratedMethodAccessor306.invoke(Unknown Source) [:1.6.0_25]

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_25]

              at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_25]

              at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:279) [:3.0.0]

              ... 5 more

       

      And I can't view the JMS section in the admin console of backup node.

       

      I tried to shutdown the live node, in this case the second node server log traces the new cluster view display only the backup one, but it doesn't seem that the backup hornetQ instance changes its status to live.

       

      Have I missed some configuration options?


      Thanks in advance.

        • 1. Re: Jbossas 6.1.0-Final + HornetQ 2.2.5
          ataylor

          The admin console error is not really hornetq issue but and admin console issue, however im guessing its because the server hasnt been started.

           

          as for the backup starting, can you see the locks being aquired correctly in the logs