1 Reply Latest reply on Jun 15, 2011 1:01 PM by Clebert Suconic

    I fixed "connect timed out" error, but I don't know why

    Joe Kutner Newbie

      I had a hornetq cluster setup using 2.1.2 (with torquebox) and static connector-refs.  Something like this:

       

        <cluster-connections>

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

               <address>jms</address>

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

            </cluster-connection>

         </cluster-connections>

       

      Everything worked, but I was getting the follow error fairly often on all nodes:

      ERROR [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-0 (group:HornetQ-server-threads14766501-31607439)) Failed to create netty connection

      java.net.SocketTimeoutException: connect timed out

       

      However, everything was pretty much working - despite the errors in the logs.  So I changed my configuration to somthing like what I have below (because I saw it in the examples), and the error seems to go away:

       

        <cluster-connections>

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

               <address>jms</address>

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

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

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

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

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

            </cluster-connection>

         </cluster-connections>

       

      But I don't understand why it went away.  Can someone explain what in this config fixed the problem (or am I possibly mistaken)?

       

      Thanks!