Richard: I do see "idle in transaction" messages. I don't see that many at any one time, and they clear up ( go to idle ), and most of the connections are usually idle. I think I've read it's fine to see the "idle in transaction" message.
If you were to set db.maxconnections to a low number ( perhaps the default ) in your production server, would you get this error message? Have you seen this happen at your site? I'm wondering if I have to change my configuration some how, as described in the following document: http://tomcat.apache.org/tomcat-5.5-doc/jndi-datasource-examples-howto.h tml Do you have these parameters set up: removeAbandoned="true" removeAbandonedTimeout="60" logAbandoned="true" Thanks! Jose -----Original Message----- From: Richard Jones [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 11, 2007 9:15 AM To: Blanco, Jose Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] (no subject) Hi Jose, Sometimes this happens because you have too many open connections to the database. This is if your system is under heavy usage, and the number of database connections requested exceeds the number allowed (as specified in dspace.cfg). It can also happen if there is a database connection leak in the code which is not releasing completed connections back to the pool. AFAIK, DSpace 1.4.2 does not have any connection leaks, but it may be worth checking, especially if you have added any of your own code. Check your process list for postgres jobs containing the text "idle in transaction" - this would indicate a problem. I have also heard tell of bugs in the pooling code, so you could look for an updated version of that (commons dbcp), but I don't expect that's your problem. Instead you probably want to increase the number of allowed connections in dspace.cfg: db.maxconnections = 30 In production I run mine with 300. Cheers, Richard > We have been getting this error periodically ( 4 or 5 times a month, > and a few of them at a time ): > > Exception: > org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, > pool exhausted > at > org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:183) > at java.sql.DriverManager.getConnection(DriverManager.java:582) > at > java.sql.DriverManager.getConnection(DriverManager.java:207) > > In looking at the log files, I don't see any pattern that indicates > anything in particular. I'm wondering now if I have an old jar file > that may need to be replaced - in particular postgresql.jar. Is there > a way for me to see the version of this jar file. Any one have any ideas? > I have version 1.4.2. > > Thanks, > > Jose > > ---------------------------------------------------------------------- > --- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for just about anything > Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > -- Richard Jones Research Engineer, HP Labs eml: [EMAIL PROTECTED] blg: http://chronicles-of-richard.blogspot.com/ ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
