Update of /cvsroot/proxool/proxool
In directory sc8-pr-cvs1:/tmp/cvs-serv27140
Modified Files:
CHANGES.txt
Log Message:
Index: CHANGES.txt
===================================================================
RCS file: /cvsroot/proxool/proxool/CHANGES.txt,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** CHANGES.txt 12 Feb 2003 00:33:51 -0000 1.15
--- CHANGES.txt 21 Feb 2003 11:50:51 -0000 1.16
***************
*** 6,10 ****
$Author$
! 0.7 - scheduled for February 12, 2003
- We have dropped the dependency on commons-logging.jar
--- 6,10 ----
$Author$
! 0.7 - scheduled for February, 2003
- We have dropped the dependency on commons-logging.jar
***************
*** 12,20 ****
the Jakarta team, naturally).
! - New monitor package provides statistical
and snapshot information so you can measure how well Proxool, and
your database, is doing.
! - New MonitorServlet provides statistical
information for your web application.
--- 12,20 ----
the Jakarta team, naturally).
! - New admin package provides statistical
and snapshot information so you can measure how well Proxool, and
your database, is doing.
! - New AdminServlet provides statistical
information for your web application.
***************
*** 35,38 ****
--- 35,44 ----
reliable shutdown of the pools when the JVM stops.
+ - Removed ReloadMonitor (added in 0.5) because it made use of
+ SystemProperties and this is prohbited by J2SE. You are now responsible
+ for ensuring Proxool is shutdown if your application is reloaded within
+ the same environment (as can sometimes happen in a web application).
+ See ProxoolFacade.shutdown().
+
- Fixed bug when you asked DatabaseMetaData for the connection. It
now gives you back the Proxool connection, not the underlying delegate
***************
*** 41,44 ****
--- 47,55 ----
- Fixed bug where if you registered, removed and then re-registered a pool
then the new pool would not notice the Properties passed to it.
+
+ - If a connection encounters a fatal SQLException (as defined by the
+ fatal-sql-exception property) it now wakes up the house keeper thread
+ so other connections are tested as soon as possible (with the
+ house-keeper-test-sql) rather than waiting for the next scheduled sweep.
0.6 (January 23, 2003)
|
