-
1. Re: Reconnecting after RDBMS failure
davidjencks Oct 9, 2002 8:21 PM (in response to cerber)There's no easy fast way to do this automatically that I can think of.
You should be able to throw out the old connections by stopping and starting the pool mbean in the jmx-console. -
2. Re: Reconnecting after RDBMS failure
cerber Oct 12, 2002 7:18 AM (in response to cerber)Thank you David for your answer.
I'm sure there should be an easy way to resolve this problem. I hope so. In other case there's no much sence in connection pooling... Well, I mean load balancing, fail over etc. -
3. Re: Reconnecting after RDBMS failure
sun100 Feb 10, 2003 11:45 AM (in response to cerber)> There's no easy fast way to do this automatically
> that I can think of.
>
> You should be able to throw out the old connections
> by stopping and starting the pool mbean in the
> jmx-console.
What happened to InvalidateOnError attribute? -
4. Re: Reconnecting after RDBMS failure
paul91801 Apr 1, 2003 3:11 PM (in response to cerber)Can you show how can I get this example (link) please. It will be greately appreated.
-
5. Re: Reconnecting after RDBMS failure
davidjencks Apr 2, 2003 12:20 AM (in response to cerber)it's in every binary distro and source download
binary: docs/...
source: connector/src/etc/example-config
There are several improvements recently.
1. By including the OracleExceptiionsSorter, many errors will result in the connection being closed.
2. you can specify sql to be executed each time before the cx is handed out using the TestValidConnectionSQL. slow but fairly effective.