2 Replies Latest reply on Feb 23, 2012 9:04 AM by Massimiliano Pardini

    Problems with hornetq and jboss esb in live-backup mode

    Massimiliano Pardini Newbie

      Hi everyone,

      I've tried to run two istances of jboss AS 5.1 with jboss ESB 4.9 and hornetq 2.2.5 using the example of "multiple failover" found on hornetq examples.


      The first node runs normally, without any error.

      When I try to launch the second node, everything goes fine, it successfully became a backup node but when the jbossesb starts deploying, and obviously also my esb application, I get this error:

       

       

      15:09:45,541 INFO  [JmsConnectionPool] Received NamingException, refreshing context.

      15:09:46,546 WARN  [MessageAwareListener] Error processing courier, backing off for 4000 milliseconds

      15:09:48,566 INFO  [JmsConnectionPool] Received NamingException, refreshing context.

      15:09:48,962 ERROR [AbstractKernelController] Error installing to Start: name=jboss.esb.vfszip:/home/max2thousand/jboss_hornetq/jboss/server/node2/deploy/socialProxy.esb/ state=Create

      org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleException: Unexpected configuration exception from prepareMessageReceiver

          at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:126)

          at org.jboss.soa.esb.listeners.lifecycle.AbstractManagedLifecycle.initialise(AbstractManagedLifecycle.java:133)

          at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.initialiseInstances(ManagedLifecycleController.java:109)

          at org.jboss.soa.esb.listeners.lifecycle.ManagedLifecycleController.start(ManagedLifecycleController.java:66)

          at org.jboss.soa.esb.listeners.deployers.mc.EsbDeployment.start(EsbDeployment.java:223)

          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

          at java.lang.reflect.Method.invoke(Method.java:616)

          at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)

          at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)

          at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)

          at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)

          at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)

          at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)

          at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)

          at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)

          at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)

          at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)

          at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)

          at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)

          at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)

          at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)

          at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)

          at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)

          at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)

          at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

          at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)

          at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)

          at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

          at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

          at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

          at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)

          at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

          at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

          at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

          at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

          at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

          at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)

          at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)

          at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

          at org.jboss.Main.boot(Main.java:221)

          at org.jboss.Main$1.run(Main.java:556)

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

      Caused by: org.jboss.soa.esb.ConfigurationException: Failed to obtain queue session from pool

          at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.prepareMessageReceiver(JmsGatewayListener.java:420)

          at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:114)

          ... 63 more

      Caused by: javax.naming.NameNotFoundException: ConnectionFactory not bound

          at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)

          at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)

          at org.jnp.server.NamingServer.getObject(NamingServer.java:785)

          at org.jnp.server.NamingServer.lookup(NamingServer.java:443)

          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)

          at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)

          at javax.naming.InitialContext.lookup(InitialContext.java:409)

          at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getFactoryConnection(JmsConnectionPool.java:323)

          at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.internalGetSession(JmsConnectionPool.java:226)

          at org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool.getSession(JmsConnectionPool.java:198)

          at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.prepareMessageReceiver(JmsGatewayListener.java:415)

          ... 64 more

      15:09:48,966 INFO  [EsbDeployment] Destroying 'socialProxy.esb'

       

      The curious thing is that if I run the two nodes in a load-balanced way (following the other example from hornetq "clustered-queue"), they run normally, and the messages produced are consumed from the two servers in round-robin way.

       

      I've tried also to search over and over with google and also in this forum, without an answer to my problem.

       

      Someone suggests to use the load-balanced way and persist messages, I've tried to persist them, but when the node that is gone down is going up again the messages that the node started to handle before it dies are lost forever.

       

      I've also used a shared file system, as the messaging failover example suggests, without success...

       

      Now I'm totally lost, I've switched from jboss messaging to hornetq, that guarantees transparent failover!

       

      I hope you can help.

      Thanks,

      Massimiliano

        • 1. Re: Problems with hornetq and jboss esb in live-backup mode
          Massimiliano Pardini Newbie

          Sorry, I forgot my hornetq configuration file for jms:

           

          hornetq-configuration for live node, that is located in deploy/hornetq.sar

          <!--

            ~ Copyright 2009 Red Hat, Inc.

            ~  Red Hat licenses this file to you under the Apache License, version

            ~  2.0 (the "License"); you may not use this file except in compliance

            ~  with the License.  You may obtain a copy of the License at

            ~     http://www.apache.org/licenses/LICENSE-2.0

            ~  Unless required by applicable law or agreed to in writing, software

            ~  distributed under the License is distributed on an "AS IS" BASIS,

            ~  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or

            ~  implied.  See the License for the specific language governing

            ~  permissions and limitations under the License.

            -->

           

          <configuration xmlns="urn:hornetq"

                         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                         xsi:schemaLocation="urn:hornetq /schema/hornetq-configuration.xsd">

           

             <!--  Don't change this name.

                   This is used by the dependency framework on the deployers,

                   to make sure this deployment is done before any other deployment -->

            <!-- <name>HornetQ.main.config</name>-->

           

             <clustered>true</clustered>

           

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

             <!--we kill the server process so don't need this set to true-->

             <failover-on-shutdown>false</failover-on-shutdown>

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

           

           

             <log-delegate-factory-class-name>org.hornetq.integration.logging.Log4jLogDelegateFactory</log-delegate-factory-class-name>

           

             <bindings-directory>${jboss.server.data.dir}/hornetq/bindings</bindings-directory>

           

             <journal-directory>${jboss.server.data.dir}/hornetq/journal</journal-directory>

           

             <journal-min-files>10</journal-min-files>

           

             <large-messages-directory>${jboss.server.data.dir}/hornetq/largemessages</large-messages-directory>

           

             <paging-directory>${jboss.server.data.dir}/hornetq/paging</paging-directory>

             <connectors>

                <connector name="netty">

                   <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>

                   <param key="host"  value="${jboss.bind.address:localhost}"/>

                   <param key="port"  value="5445"/>

                </connector>

                <!--

                <connector name="netty-throughput">

                   <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>

                   <param key="host"  value="${jboss.bind.address:localhost}"/>

                   <param key="port"  value="${hornetq.remoting.netty.batch.port:5455}"/>

                   <param key="batch-delay" value="50"/>

                </connector>

           

                <connector name="in-vm">

                   <factory-class>org.hornetq.core.remoting.impl.invm.InVMConnectorFactory</factory-class>

                   <param key="server-id" value="${hornetq.server-id:0}"/>

                </connector>

          -->

             </connectors>

           

             <acceptors>

                <acceptor name="netty">

                   <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>

                   <param key="host"  value="${jboss.bind.address:localhost}"/>

                   <param key="port"  value="5445"/>

                </acceptor>

                <!--

                <acceptor name="netty-throughput">

                   <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>

                   <param key="host"  value="${jboss.bind.address:localhost}"/>

                   <param key="port"  value="${hornetq.remoting.netty.batch.port:5455}"/>

                   <param key="batch-delay" value="50"/>

                   <param key="direct-deliver" value="false"/>

                </acceptor>

           

                <acceptor name="in-vm">

                  <factory-class>org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory</factory-class>

                  <param key="server-id" value="0"/>

                </acceptor>

          -->

             </acceptors>

           

             <broadcast-groups>

                <broadcast-group name="bg-group1">

                   <group-address>231.7.7.7</group-address>

                   <group-port>9876</group-port>

                   <broadcast-period>5000</broadcast-period>

                   <connector-ref>netty</connector-ref>

                </broadcast-group>

             </broadcast-groups>

           

             <discovery-groups>

                <discovery-group name="dg-group1">

                   <group-address>231.7.7.7</group-address>

                   <group-port>9876</group-port>

                   <refresh-timeout>10000</refresh-timeout>

                </discovery-group>

             </discovery-groups>

           

             <cluster-connections>

                <cluster-connection name="my-cluster">

                   <address>jms</address>    

                   <connector-ref>netty</connector-ref>

                  <!-- <retry-interval>500</retry-interval>

                   <use-duplicate-detection>true</use-duplicate-detection>

                   <forward-when-no-consumers>true</forward-when-no-consumers>

                   <max-hops>1</max-hops>

                   -->

                    <discovery-group-ref discovery-group-name="dg-group1"/>

                </cluster-connection>

             </cluster-connections>

             <!--

            <large-messages-directory>../all-with-hornetq/data/large-messages</large-messages-directory>

             <bindings-directory>../all-with-hornetq/data/bindings</bindings-directory>

             <journal-directory>../all-with-hornetq/data/journal</journal-directory>

             <paging-directory>../all-with-hornetq/data/paging</paging-directory>

          -->

             <security-settings>

                <security-setting match="#">

                   <permission type="createNonDurableQueue" roles="guest"/>

                   <permission type="deleteNonDurableQueue" roles="guest"/>

                   <permission type="consume" roles="guest"/>

                   <permission type="send" roles="guest"/>

                </security-setting>

             </security-settings>

          <!--

             <address-settings>

                default for catch all

                <address-setting match="#">

                   <dead-letter-address>jms.queue.DLQ</dead-letter-address>

                   <expiry-address>jms.queue.ExpiryQueue</expiry-address>

                   <redelivery-delay>0</redelivery-delay>

                   <max-size-bytes>10485760</max-size-bytes>      

                   <message-counter-history-day-limit>10</message-counter-history-day-limit>

                   <address-full-policy>BLOCK</address-full-policy>

                </address-setting>

             </address-settings>

          -->

           

          </configuration>

           

          hornetq-configuration for backup node, that is located in deploy/hornetq.sar

          <!--

            ~ Copyright 2009 Red Hat, Inc.

            ~  Red Hat licenses this file to you under the Apache License, version

            ~  2.0 (the "License"); you may not use this file except in compliance

            ~  with the License.  You may obtain a copy of the License at

            ~     http://www.apache.org/licenses/LICENSE-2.0

            ~  Unless required by applicable law or agreed to in writing, software

            ~  distributed under the License is distributed on an "AS IS" BASIS,

            ~  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or

            ~  implied.  See the License for the specific language governing

            ~  permissions and limitations under the License.

            -->

           

          <configuration xmlns="urn:hornetq"

                         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                         xsi:schemaLocation="urn:hornetq /schema/hornetq-configuration.xsd">

           

             <!--  Don't change this name.

                   This is used by the dependency framework on the deployers,

                   to make sure this deployment is done before any other deployment -->

            <!-- <name>HornetQ.main.config</name>-->

           

             <clustered>true</clustered>

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

           

             <!--we kill the server process so don't need this set to true-->

             <failover-on-shutdown>false</failover-on-shutdown>

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

             <backup>true</backup>

           

          <!--

             <log-delegate-factory-class-name>org.hornetq.integration.logging.Log4jLogDelegateFactory</log-delegate-factory-class-name>

           

             <bindings-directory>${jboss.server.data.dir}/hornetq/bindings</bindings-directory>

           

             <journal-directory>${jboss.server.data.dir}/hornetq/journal</journal-directory>

           

             <journal-min-files>10</journal-min-files>

           

             <large-messages-directory>${jboss.server.data.dir}/hornetq/largemessages</large-messages-directory>

           

             <paging-directory>${jboss.server.data.dir}/hornetq/paging</paging-directory>

             -->

             <connectors>

                <connector name="netty">

                   <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>

                   <param key="host"  value="${jboss.bind.address:localhost}"/>

                   <param key="port"  value="5446"/>

                </connector>

                <!--

                <connector name="netty-throughput">

                   <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>

                   <param key="host"  value="${jboss.bind.address:localhost}"/>

                   <param key="port"  value="${hornetq.remoting.netty.batch.port:5455}"/>

                   <param key="batch-delay" value="50"/>

                </connector>

           

                <connector name="in-vm">

                   <factory-class>org.hornetq.core.remoting.impl.invm.InVMConnectorFactory</factory-class>

                   <param key="server-id" value="${hornetq.server-id:0}"/>

                </connector>

          -->

             </connectors>

           

             <acceptors>

                <acceptor name="netty">

                   <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>

                   <param key="host"  value="${jboss.bind.address:localhost}"/>

                   <param key="port"  value="5446"/>

                </acceptor>

                <!--

                <acceptor name="netty-throughput">

                   <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>

                   <param key="host"  value="${jboss.bind.address:localhost}"/>

                   <param key="port"  value="${hornetq.remoting.netty.batch.port:5455}"/>

                   <param key="batch-delay" value="50"/>

                   <param key="direct-deliver" value="false"/>

                </acceptor>

           

                <acceptor name="in-vm">

                  <factory-class>org.hornetq.core.remoting.impl.invm.InVMAcceptorFactory</factory-class>

                  <param key="server-id" value="0"/>

                </acceptor>

          -->

             </acceptors>

           

             <broadcast-groups>

                <broadcast-group name="bg-group1">

                   <group-address>231.7.7.7</group-address>

                   <group-port>9876</group-port>

                   <broadcast-period>5000</broadcast-period>

                   <connector-ref>netty</connector-ref>

                </broadcast-group>

             </broadcast-groups>

           

             <discovery-groups>

                <discovery-group name="dg-group1">

                   <group-address>231.7.7.7</group-address>

                   <group-port>9876</group-port>

                   <refresh-timeout>10000</refresh-timeout>

                </discovery-group>

             </discovery-groups>

           

             <cluster-connections>

                <cluster-connection name="my-cluster">

                   <address>jms</address>    

                   <connector-ref>netty</connector-ref>

                   <retry-interval>500</retry-interval>

                   <use-duplicate-detection>true</use-duplicate-detection>

                   <forward-when-no-consumers>true</forward-when-no-consumers>

                   <max-hops>1</max-hops>

                    <discovery-group-ref discovery-group-name="dg-group1"/>

                </cluster-connection>

             </cluster-connections>

           

            <large-messages-directory>/home/max2thousand/jboss_hornetq/jboss/server/all-with-hornetq/data/large-messages</large-messages-directory>

             <bindings-directory>/home/max2thousand/jboss_hornetq/jboss/server/all-with-hornetq/data/bindings</bindings-directory>

             <journal-directory>/home/max2thousand/jboss_hornetq/jboss/server/all-with-hornetq/data/journal</journal-directory>

             <paging-directory>/home/max2thousand/jboss_hornetq/jboss/server/all-with-hornetq/data/paging</paging-directory>

           

             <security-settings>

                <security-setting match="#">

                   <permission type="createNonDurableQueue" roles="guest"/>

                   <permission type="deleteNonDurableQueue" roles="guest"/>

                   <permission type="consume" roles="guest"/>

                   <permission type="send" roles="guest"/>

                </security-setting>

             </security-settings>

          <!--

             <address-settings>

                default for catch all

                <address-setting match="#">

                   <dead-letter-address>jms.queue.DLQ</dead-letter-address>

                   <expiry-address>jms.queue.ExpiryQueue</expiry-address>

                   <redelivery-delay>0</redelivery-delay>

                   <max-size-bytes>10485760</max-size-bytes>      

                   <message-counter-history-day-limit>10</message-counter-history-day-limit>

                   <address-full-policy>BLOCK</address-full-policy>

                </address-setting>

             </address-settings>

          -->

           

          </configuration>

           

           

          hornetq-jms for both node, that is located in deploy/hornetq.sar in the two nodes

           

          <configuration xmlns="urn:hornetq"

                      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

                      xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd">

             <connection-factory name="ConnectionFactory">

                <ha>true</ha>

                <!-- Pause 1 second between connect attempts -->

                <retry-interval>1000</retry-interval>

           

                <!-- Multiply subsequent reconnect pauses by this multiplier. This can be used to

                implement an exponential back-off. For our purposes we just set to 1.0 so each reconnect

                pause is the same length -->

                <retry-interval-multiplier>1.0</retry-interval-multiplier>

                <!-- Try reconnecting an unlimited number of times (-1 means "unlimited") -->

                <reconnect-attempts>-1</reconnect-attempts>

                <connectors>

                   <connector-ref connector-name="netty"/>

                </connectors>

                <entries>

                   <entry name="ConnectionFactory"/>

                </entries>

             </connection-factory>

             <queue name="DLQ">

                <entry name="/queue/DLQ"/>

             </queue>

           

             <queue name="ExpiryQueue">

                <entry name="/queue/ExpiryQueue"/>

             </queue>

           

          </configuration>

           

          hornetq-jms for both node, that is located in deploy/jbossesb.esb in the two nodes for jbossesb

           

          <configuration xmlns="urn:hornetq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd">

           

             <connection-factory name="ConnectionFactory">

                <connectors>

                   <connector-ref connector-name="netty"/>

                </connectors>

                <entries>

                   <entry name="ConnectionFactory"/>

                </entries>

          <ha>true</ha>

                <!-- Pause 1 second between connect attempts -->

                <retry-interval>1000</retry-interval>

           

                <!-- Multiply subsequent reconnect pauses by this multiplier. This can be used to

                implement an exponential back-off. For our purposes we just set to 1.0 so each reconnect

                pause is the same length -->

                <retry-interval-multiplier>1.0</retry-interval-multiplier>

           

                <!-- Try reconnecting an unlimited number of times (-1 means "unlimited") -->

                <reconnect-attempts>-1</reconnect-attempts>

           

           

             </connection-factory>

             <queue name="DeadMessageQueue">

                <entry name="/queue/DeadMessageQueue"/>

             </queue>

           

             <queue name="DataCollectorQueue">

                <entry name="/queue/DataCollectorQueue"/>

             </queue>

           

             <queue name="OperationsCollectorQueue">

                <entry name="/queue/OperationsCollectorQueue"/>

             </queue>

           

             <queue name="OperationsResultCollectorQueue">

                <entry name="/queue/OperationsResultCollectorQueue"/>

             </queue>

           

          </configuration>

           

           

           

          I've tried also to add this part that here is commented:

            <!--  Don't change this name.

                   This is used by the dependency framework on the deployers,

                   to make sure this deployment is done before any other deployment -->

            <!-- <name>HornetQ.main.config</name>-->

          ...without success

          • 2. Re: Problems with hornetq and jboss esb in live-backup mode
            Massimiliano Pardini Newbie

            No one can help me?:(

            Is it possible that hornetq live-backup doesn't work with jbossesb?I'm really desperate, please help

            Bye,

            Massimiliano