[bfach]

I am not failing over in this case. This is the case that there is only 1 node in the cluster and it dies. If there are 2+ nodes jboss will automatically failover when one node dies.

This is for the scenario when the last node in the cluster dies and giving the client the ability to reconnect.

Does this make sense? Is there are better way that I am not aware of?

[clebert.suconic]

Can you package your test in a JAR? I would take a look here.

I saw you posted the code on the first message.. but I would have to create a main, and a bunch of other things.

if you package a test I will take a look.

you can use my private email, as you will see on my profile here.

[clebert.suconic]

"bfach" wrote:
I am not failing over in this case. This is the case that there is only 1 node in the cluster and it dies. If there are 2+ nodes jboss will automatically failover when one node dies.

This is for the scenario when the last node in the cluster dies and giving the client the ability to reconnect.

Does this make sense? Is there are better way that I am not aware of?

When all the nodes have failed... are you downloading a new CF from the JNDI before you start the test again?

On this case you've downloaded the entire cluster, and I suspect the nodeList will be empty on the CF on the client.

[bfach]

Clebert,


After all nodes are dead in the cluster I do a initial context, lookup the Clustered Connection Factory and lookup the queue. If the new queue connection is also not good, the process is repeated until it is.

[bfach]

The following link details what I am attempting to do.

http://www.jboss.org/community/docs/DOC-10931