Hi,
I've configured Tyrex in Tomcat 4.1.24 to use client-initiated JTA transactions from my JSPs. I retrieve db connections from the connection pool Tyrex is managing via a JNDI lookup. Everything is working fine until de db server goes down ( too often the db server box is restarted ), then connections objects begun to throw SQLException and my app won't reach the database anymore because connections in the pool aren't recycled.
Who's responsible for recycling these connections, the JDBC driver DataSource implementation, or Tyrex ? Is it possible to configure Tyrex to use jakarta DBCP instead ?
Thanks,
Patricio.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did someone find the solution to this??
My app gets broken connection from Tyrex if the database was recycled.. I need to get new valid connections after the database is up, without restarting my app..
Any ideas??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I've configured Tyrex in Tomcat 4.1.24 to use client-initiated JTA transactions from my JSPs. I retrieve db connections from the connection pool Tyrex is managing via a JNDI lookup. Everything is working fine until de db server goes down ( too often the db server box is restarted ), then connections objects begun to throw SQLException and my app won't reach the database anymore because connections in the pool aren't recycled.
Who's responsible for recycling these connections, the JDBC driver DataSource implementation, or Tyrex ? Is it possible to configure Tyrex to use jakarta DBCP instead ?
Thanks,
Patricio.
Did someone find the solution to this??
My app gets broken connection from Tyrex if the database was recycled.. I need to get new valid connections after the database is up, without restarting my app..
Any ideas??