-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brooke,
On 3/4/12 10:29 AM, Brooke Hedrick wrote: > There are cases where either or both get restarted, but the issue > is only when the @otherdb is restarted and not the primary. So, you have a setup like this: DBCP --- jdbc ---> Primary --- Oracle --> Secondary The secondary db is restarted and thus the "Oracle" link essentially goes down. The next time you make a query across the "jdbc" link to the secondary database, you get an error. IMO you can't fix this at the Tomcat end without using a validation query that tests the end-to-end connection. It really seems like the wrong place to fix it, anyway. What you really need to fix is the "Oracle" link, which is surely configured somewhere in Oracle. Suppose if you could kill the whole pool, you'll get new connections, but won't the "Oracle" link still be dead? Or, does a db-link co-exist with the connection to the primary db? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9U40MACgkQ9CaO5/Lv0PDWlQCgr98eLBsOmFezC8o0OogeeKa2 T14An29FLIVaFbRFaTqfEAdeZt5LWlod =U8gU -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
