Christian Haul wrote: > > > Carsten, > I've only seen the mail on Leo CC'ed to cocoon-dev. This issue had > bitten me before and I had the very same questions. It was resolved by > using a different connection pool than the one used. > > Leif Mortenson wrote in http://marc.theaimsgroup.com/?l=avalon-dev&m=101615852003093&w=2 : > You might want to give the ResourceLimitingJdbcConnectionPool used by the > ResourceLimitingJdbcDataSource class over in the scratchpad. This pool > works a little differently > in that it does not try to pre allocate any connections during > initialization, but rather waits until they > are needed. This pool also handles the DB going down and then coming > back up without any > problems. > >So far, I believe, it worked alright. Both 2.0.3 and 2.1 use the >ResourceLinitingJdbcConnectionPool.
Interesting...hm, yes the ResourceLimitingJdbcConnectionPool is used, but it did not work! At least it did not work when everything is compiled using JDK 1.4 - perhaps that's the difference, I really don't know. With the latest patch, this problem is resolved and the components are initialized in a defined order, which is IMHO better. Thanks Carsten -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
