Hi David,
This is not really load balancing but mainly for failover with stickyness. The feature we use this for is 2 DB2 Databases with Q-replication . Here is a presentation our DBAs gave on how we use Q-Replication. https://www-950.ibm.com/events/wwe/iod/iod10cms.nsf/download/ke17c18673b943b9412badbbabb6/$FILE/IOD2010_TLU-2027.pdf I believe DB2 driver knows how to failover once it knows server list....I will confirm that on Monday. Thanks Anish On Fri, Apr 26, 2013 at 8:02 PM, David Blevins <[email protected]>wrote: > Noticed the work going on with TOMEE-912 and wanted to make sure it hit > the dev list. > > Anish, if you have any insight on this feature request that'd be > wonderful. Some questions: > > - Is this feature intended for use involving database writes and > transactions? > - Is this really load balancing rather than failure recovery? I.e. when > should the functionality kick in, a or b or both? > a) Load-balancing scenario: before starting a transaction, pick a > datbase using some selection strategy (round-robin, random, sticky, etc.) > b) Failure scenario: while in a transaction communicating with a > databse, if it fails to respond then failover to another database using > some selection strategy (round-robin, random, sticky, etc.) > > > I can see A being very doable. Doing B could also possibly be doable as > long as no writes were involved. > > If you have any information you can share about your setup that'd be > wonderful. > > > -David > > > >
