Re: [opennms-devel] Change default connection pool size to less than 100? Was: [opennms-discuss] 1.3.11 Hangs after hours of running
David Hustace <[email protected]>
| Newsgroups | gmane.network.opennms.bugs |
|---|---|
| Message-ID | <[email protected]> |
On Mar 3, 2008, at 3:58 AM, DJ Gregor wrote: > Should we change the default connection pool size to something > other than 100? The default is actually 50. We have it set to: c3p0.initialPoolSize=50 c3p0.maxPoolSize=50 c3p0.minPoolSize=50 Because of that stupid PostgreSQL bug that we have forever run up against when the blocking getConnection() call is made when more connections are required in the pool. If that wasn't a problem then we could have better pool configuration. > > That happens to be _exactly_ the postgresql default, which seems > particularly troubling (oh, you wanted to run 'psql' while opennms > is running? Sorry.). Also, 100 concurrent connections just seems > absolutely huge for all but the largest sites. The default is 50 and even that is huge for smaller sites. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel