Hornetq 2.3.0 final -Fail-over does not work as expected after a fail-back

[caro82]

I'm using two stand-alone servers (having the same config as the ones from 'multiple-failover-failback' example - a pair of live - bk servers).

I'm triggering a fail-over and a fail-back afterwards.

If I'm  triggering a second fail-over, I'm unable to retrieve the queue and  getting the following exception

     javax.naming.NameNotFoundException: queue not bound

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

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

    ....

However, I'm able to connect using jconsole and inspect the queue attributes.

This sound similar to (HORNETQ-1047-Fail-over after fail-back doesn't work in JBoss AS ).

I'm not using jboss.  Should I expect this to work with 2.3.0 final? Or what are the configs that I can check on my side.

Tnx. I would appreciate some hints/advice.

[jbertram]

I thought HORNETQ-1047 only applied to HornetQ running with EAP 5.x but now that I look at how standalone is doing this I see that it applies there as well.  That being the case, it's not surprising that this doesn't work for you.  JNDI is broken on the backup when failing over after failing back.  I'll get this fixed on the master branch for the next release of HornetQ (should be 2.4.x).

[caro82]

Tnx for your quick response.