cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 2645] - db-authenticator wont reuse pool connections
Date Thu, 19 Jul 2001 17:34:34 GMT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2645

*** shadow/2645	Mon Jul 16 17:11:37 2001
--- shadow/2645.tmp.5177	Thu Jul 19 10:34:33 2001
***************
*** 9,15 ****
  +----------------------------------------------------------------------------+
  |  Assigned To: cocoon-dev@xml.apache.org                                    |
  |  Reported By: ryanagler@hotmail.com                                        |
- |      CC list: Cc:                                                          |
  +----------------------------------------------------------------------------+
  |          URL:                                                              |
  +============================================================================+
--- 9,14 ----
***************
*** 21,24 ****
  cocoon.xconf), errors in the logfile say:
   "org.apache.avalon.excalibur.datasource.JdbcConnection: could not be 
  instantiated. java.lang.InstantiationException: Ran out of resources to 
! instantiate"
--- 20,37 ----
  cocoon.xconf), errors in the logfile say:
   "org.apache.avalon.excalibur.datasource.JdbcConnection: could not be 
  instantiated. java.lang.InstantiationException: Ran out of resources to 
! instantiate"
! 
! ------- Additional Comments From karl_hallowell@hp.com  2001-07-19 10:34 -------
! I duplicated this on my platform. I'm running Cocoon 2.0 beta on Tomcat 4.0b5 
! and am using the HSQL database. It appears that two things are going on. First, 
! I can connect again after a number of seconds (about five to ten seconds), 
! which I guess to be the time that an excess unused connection lasts before 
! being released. In particular, there's no indication that a connection is being 
! reused.
! 
! Second, No connections are created past the maximum. Is this the correct 
! behavior when the maximum number of connections is achieved? I thought that 
! default behavior was that temporary pool connections could still be created 
! after this point, but these pool connections were released as soon as the 
! connection was closed.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message