Live Backup pair with replication issue - queue does not seem to replicate

[alzamir]

Hi,

I'm a hornetQ newvbie, just started evaluating the platform.

I want to test the replication feature with live/ backup pair of standalone, non clustered servers, as explained in chapter 39 of user manual.

I use jmx as a monitor tool for the server queue state.

After the basic test, it seems like the replication feature is not working as it should be.I'd like to know whether its a configuration problem.

the test:

1. start backup server

2. start live (main) server

3. client connects to main server and produceses a message in the queue ( note that there are no defined consumer for this queue)

4. via jmx / jconsole, I see the queue's MessageCount and MessagesAdded properties increase ( from  0 to 1):

- org.hornetq

-------    Acceptor

--------------- Queue

----------------- Core

----------------------- queue name

---------------------------  ( queue attributes)

5. browsing the backup server via jmx /jconsole, I only see the following in the mbeans tree:

- org.hornetq

-------    Acceptor

     ---------------- Core

( without any of the queue information )

However, If my client producees a message directly to the backup server, I do see the Queue mbean in the mbeans tree, but it does not look like there was any replication taking place.

client code ( injection via spring):

@Test

    public void testSpringJMSTemplate(){

       this.jmsTemplate.send("bbb", new MessageCreator() {

            public Message createMessage(Session session) throws JMSException {

              TextMessage text = session.createTextMessage("hello  world");

                return text;

            }

        });

    }

configuration of client:

<bean name="connectionFactory" class="org.hornetq.jms.client.HornetQConnectionFactory" >

     <constructor-arg>

      <bean class="org.hornetq.api.core.TransportConfiguration">

   <constructor-arg value="org.hornetq.core.remoting.impl.netty.NettyConnectorFactory" />

       <constructor-arg>

        <map key-type="java.lang.String" value-type="java.lang.Object">

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

         <entry key="host" value="server1"></entry>

        </map>

       </constructor-arg>

      </bean>

     </constructor-arg>

    </bean>

    <bean name="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">

     <property name="connectionFactory" ref="connectionFactory"></property>

   </bean>

servers configurations are supposed to be the same as chapter 39 in the usermanual:

I'd thanks,

Alon

[ataylor]

Your config looks ok but you are using spring, i would suggest getting a simple example working and then add spring later.

[ataylor]

take a look at the non-transacted-failover example

[alzamir]

the following is a simple example without any external deps.

I tried both transacted + commit and non transacted without commit, same result.

public class HornetQTest {

    public static void main(String[] args) throws JMSException {

        Map<String, Object> params = new HashMap<String,Object>();

        params.put("host","server1");

        HornetQConnectionFactory fact =  HornetQJMSClient.createConnectionFactory(    new org.hornetq.api.core.TransportConfiguration("org.hornetq.core.remoting.impl.netty.NettyConnectorFactory",params));

        Connection conn =  fact.createConnection();

        Session sess  = conn.createSession(true, Session.AUTO_ACKNOWLEDGE);

        Queue queue = sess.createQueue("bbb");

        MessageProducer mp =  sess.createProducer(queue);

        mp.send( sess.createTextMessage("hello world!!!"));

        mp.close();

        sess.commit();

        sess.close();

        conn.close();

    }

}

[ataylor]

does the example i pointed you at work?

are your queues durable?

[alzamir]

yes, the queue is durable - can be seen from the jmx monitor

the example is using JNDI which I'm trying to avoid, since I intend to use hornetQ embedded in a non jee env

forgot to mention - hornetQ version I use is 2.1.2.Final

[ataylor]

the reason im asking you to run the example is that we use them as soak tests before we release, so if the example doesn't work then you have an environmental problem, if it does then you can alter it incremently until you get your desired config