Re: JDBC pool configuration bug/ugliness

This is a documentation bug, it should be: A connection is considered idle when it is returned to the pool by calling conn.close() So by setting maxIdle=0 you never get any connection in the pool effectively disabling the pooling. This is probably not what you want. In your case you want to us

[Launcher] release 1.0

Launcher was imported into jakarta commons almost 2 years ago (25 okt 2002) but never had a release. The thing missing was a simple example to get new users started. Alban Peignier contributed this example, I added it to CVS. So we're ready to release IMHO. The site is build using maven, the com

[DBCP][Pool] Release candidate build of DBCP/Pool v1.2 available

Hi guys, Both DBCP and Pool are moving towards a 1.2 release. Release candidates for testing are available from: http://jakarta.apache.org/commons/pool/downloads.html http://jakarta.apache.org/commons/dbcp/downloads.html Final release target is 31 May 2004. Send your feedback to commons-dev mailing

[launcher] Moving to a 1.0 release (was Re: [Launcher] Requested change in Launcher.getBootstrapFile)

Any issues concerning this patch? If not I will apply this change in a day or two. Also shouldn't a launcher get a proper 1.0 release? This minor issue is the first one I see and this component is in commons over 16 months. So I propose to apply this patch and then proceed with a 1.0 release. Com

Re: Need Consulting

You should first check if your OS is updated properly. Are you running on (Redhat) linux by any chance? If you do then you have to be carefull that your linux kernel, libc and JVM version are compatible (pre or post redhat 9) This is because the new thread library, Native POSIX Thread Library (NP

[ANNOUNCE][DBCP][Pool] Second set of Release Candidates available for the 1.1 releases of Commons DBCP & Pool

There are no significant changes for the commons-pool component. Only the license was updated (apache 1.1 license). The commons-DBCP component had the same license update and also an ant build file correction. Also the following issues were resolved since v1.1RC1: 22776 2003-09-30 NorFIX

Re: TOMCAT-fix for os/390??

Hi Anna I don't use tomcat on os390 but by reading you problem I suspect your problem is solved in cvs, you need at least revision 1.16.2.1 or

Re: DO NOT REPLY [Bug 22626] - Removing a webapp(context) doesn'tclose its datasources(resource)

"shutdown-xxx" (and contains the shutdown code for xxx) - configurable reflection solution - ... Lots of possebilities, you just have to find something that fits the general design. Dirk Remy Maucherat wrote: Dirk Verbeeck wrote: A more general solution then? ? By definition, all reso

Re: DO NOT REPLY [Bug 22626] - Removing a webapp(context) doesn'tclose its datasources(resource)

A more general solution then? Letting an application cleanup a resource created by the server is also not very nice. Dirk [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT

Removing a webapp(context) doesn't close its datasource (resource)

Hi Here at commons-dbcp we have an open issue about the datasource not being closed when the webapp context is removed. http://issues.apache.org/bugzilla/show_bug.cgi?id=21182 There is a workaround but I think it should be fixed inside the container. The BasicDataSource tomcat is using has a clo