how can the broadcast group find the backup connector

[jombo]

i have prepare two cluster servers as the live servers ,and two servers as their backup server. when one of the live servers go down between client communications ,it goes well . but when one of lives server go down, i start a communication, it break down. it seems cannt find the server,and the client is always waiting . it seems that the broadcast group can only find the live server who has gone down, but the backup one. any post is helpful.

my hornetq-configration.xml likes this:

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

   <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>
<clustered>true</clustered>

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

   <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="${hornetq.remoting.netty.port: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>

<connector name="backup-connector">
       <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>
       <param key="host" value="192.168.1.210"/>
       <param key="port" value="5565"/>
     </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="${hornetq.remoting.netty.port:5445}"/>
         <param key="direct-deliver" value="false"/>
      </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="my-broadcast-group">
         <group-address>231.7.7.7</group-address>
         <group-port>9876</group-port>
         <broadcast-period>100</broadcast-period>
         <connector-ref connector-name="netty"  backup-connector-name="backup-connector"/>
     </broadcast-group>
   </broadcast-groups>
  
   <discovery-groups>
      <discovery-group name="my-discovery-group">
         <group-address>231.7.7.7</group-address>
         <group-port>9876</group-port>
         <refresh-timeout>10000</refresh-timeout>
      </discovery-group>
   </discovery-groups>
     <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>314572800</max-size-bytes>     
     <message-counter-history-day-limit>10</message-counter-history-day-limit>           
   <address-full-policy>BLOCK</address-full-policy>
<redistribution-delay>100</redistribution-delay>
  
  </address-setting>
   </address-settings>

</configuration>

[clebert.suconic]

The connectors shouldn't find the backup server until it becomes live

The backup will be inactive until the first connection reaches it.

This is written on the user's manual. Please take a look and ask us any specific questions if you still have questions.

[jombo]

thanks for your reply.

i know that the back server need be actived. suppose that  i have active the backup server ,and my live servers are cluster. one of the live servers is down, and its backup server is actived ,then i send message , but the sender is blocked .  i debuged , it seems the broadcast group also return the down server info,not the its backup.

[clebert.suconic]

You probably have something miss configured there.

Can you check the examples.. maybe write a self contained standalone test if you think there's a bug.