T3 maintains a cache of the connection and multiplexes all the sessions on this connection. The way to get around this is to use the configuration below...
h.put(Context.PROVIDER_URL, "t3://serverA,serverB:8001");
This is actually used for clustered servers but it does work for non-clustered...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.