cleaning up connections in websphere

[Fred Abbot]

hi
I am running a an application on websphere using connection pools to connect to an oracle database
and everything is great
except if the database goes down websphere is unaware that it went down and tries to connect using the old connections which are no longer in use the only way around it is to restart websphere there by getting new connections does any one know how to ensure that websphere removes old connections and makes new ones when a database goes down
thank you
Abe

[Rahul Mahindrakar]

Yes you are right Fred

if the database goes down websphere is unaware that it went down and tries to connect using the old connections which are no longer in use the only way around it is to restart websphere there by getting new connections does any one know how to ensure that websphere removes old connections and makes new ones when a database goes down

I wrote a simple servlet that connects to a Database [oracle to be precise] and then i stopped the oracle server. The servlet does not work. Then i restarted the oracle database. The servlet still does not work until the appserver is restarted.
I am going through documentation lets see.
Workaround --- Anybody???

[Fred Abbot]

there is a workaround provided by websphere in chapter 10 of the websphere handbook
it says to cacth a staleConnectionException which is in the package
com.ibm.ejs.cm.portability
the problem is i am using Visual Age for Java(IBM)
and it wont allow me to catch that particular exception
go figure