Re: HA DataSource

In the JTA case, the getConnection method must return the same connection associated with the transaction. No failing over. -David On Apr 27, 2013, at 1:20 PM, Romain Manni-Bucau wrote: > @David: works with jta case since connection is kind of singleton for this > case > > but clearly design

Re: Thank you Gerhard!

hi david, most details you need are at [1], [2] and [3]. it's a very condensed example -> you would copy ~80% of the java-code to show a complete overview. regards, gerhard [1] https://svn.apache.org/repos/asf/tomee/tomee/trunk/examples/myfaces-codi-demo/src/main/webapp/pages/index.xhtml [2] ht

Re: HA DataSource

@David: works with jta case since connection is kind of singleton for this case but clearly designed for read case that said a lot of db support better solution and service ip is easier to handle if you have an admin team *Romain Manni-Bucau* *Twitter: @rmannibucau

Re: HA DataSource

Had a quick look through the code and, definitely, it could only be used for read-only cases where no JTA transaction or transaction of any kind was needed. Anish, this doesn't sound at all like what you are after. You seem to be after a way to configure a feature on your DB2 driver itself. Fr

Re: HA DataSource

I suspect no. If using HADR, DB high availability wouldn't be exposed up to the application server and thus you could implement HA for both the DBMS and the app server independently. If I get it right you could as well use InfoSphere Change Data Capture to do the mere replication part. Cheers Dani

Re: HA DataSource

Are we talking about a DB2 HADR setup here? Cheers Daniel On Sat, Apr 27, 2013 at 3:15 PM, Anish Khanzode wrote: > 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 pre

Re: HA DataSource

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/ke17c18673b943

Re: HA DataSource

And some uses service ip but for others that's needed Le 27 avr. 2013 10:21, "dsh" a écrit : > Some JDBC drivers already have that behaviour built-in and thus it becomes > transparent to the client. > > Cheers > Daniel > > > On Sat, Apr 27, 2013 at 10:07 AM, Romain Manni-Bucau > wrote: > > > Hi >

Re: HA DataSource

Some JDBC drivers already have that behaviour built-in and thus it becomes transparent to the client. Cheers Daniel On Sat, Apr 27, 2013 at 10:07 AM, Romain Manni-Bucau wrote: > Hi > > Reproduced jboss behavior by.default. concretely: if getconnection fails > then try next db. > > I added strat

Re: HA DataSource

Hi Reproduced jboss behavior by.default. concretely: if getconnection fails then try next db. I added strategy for read only cases (rdbms have an issue with write case by design) Le 27 avr. 2013 02:02, "David Blevins" a écrit : > Noticed the work going on with TOMEE-912 and wanted to make sure