known behaviour. Fixes:
- use the 3.2.x branch, or
- don't re-acquire a new remote for each call, or
- use the random load-balancing policy
> known behaviour. Fixes:
> - use the 3.2.x branch, or
> - don't re-acquire a new remote for each call, or
> - use the random load-balancing policy
I have the same problem. (At least I need to force two threads in a client test program to use different servers in order check transactional behaviour.) Anyway, I cannot find your random load-balancing policy. Checking the jar file jbossha.jar, I find no such class.
Maybe I can get this to work anyway. But I just want to know what you really meant here.
It is in 3.2 only. However, if you client is not in the same VM as the server, it will work.