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.
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.
> 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
What happened to InvalidateOnError attribute?
Can you show how can I get this example (link) please. It will be greately appreated.
it's in every binary distro and source download
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.