[jboss-dev-forums] [Design of Clustering on JBoss (Clusters/JBoss)] - Re: Transaction Sticky LB policy for 4.2/trunk

[bstansberry@jboss.com]

anonymous wrote : So, I believe you suggest that I create different versions of TxLoadBalancePolicy which default on the ones mentioned above (as well as RR) if no transactions are running, correct?

Correct.

Re: the different invoker types, is it a big deal to do them all?  I suppose the biggest hassle is testing.  Do you think it's possible to unit test this with mock objects, letting you basically plug in the different invokers into the same test fixture without having to deploy to the AS?

One reason to fix them all is that I believe the current mechanism for checking if failover is allowed is broken; i.e it uses the Transaction from Invocation.getTransaction() rather than the TransactionPropagationContext.  Thus it misses the case where UserTransaction is used.  So, fixing that is a side benefit of JBAS-4555.

The JRMP/Pooled invokers still exist in trunk and are deployed.  They are gone from standard-jboss.xml though.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080097#4080097

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080097