[Netarchivesuite-devel] About the DBConnect class, running out of connections

Søren Vejrup Carlsen svc at kb.dk
Fri Mar 25 15:09:08 CET 2011

Hi Nicolas.
You could be right about NAS never closing the database connections. But the connections to the database timeout automatically,
don't they?

We've had similar problems with derby in our production environment running 3.14.1.

But we didn't see in our test-environment.
Are you running the database on the same server as the processes running?

Best Regards

Fra: netarchivesuite-devel-bounces at lists.gforge.statsbiblioteket.dk [mailto:netarchivesuite-devel-bounces at lists.gforge.statsbiblioteket.dk] På vegne af Nicolas Giraud
Sendt: 25. marts 2011 14:57
Til: netarchivesuite-devel at lists.gforge.statsbiblioteket.dk
Emne: [Netarchivesuite-devel] About the DBConnect class, running out of connections


On our new production environment, we have run into a error where the DB has too many open connections. I've started investigating on this, by looking at the DBConnect class.

First the "connection pool" in it seems bugged, as if any Thread in the WeakHashMap is garbage collected, the associated connection might still be open and is not closed. Also I don't see anywhere in all of the code a call to Connection#close(), except in DomainDBDao#close() which by the way is never called.

Where are DB connections closed ? It seems they are never closed, unless I have completely misunderstood the code.

Any help will be greatly appreciated.


Nicolas Giraud
Développeur Archives du Web - Bibliothèque Nationale de France
Web Archiving Developper - National Library of France
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.sbforge.org/pipermail/netarchivesuite-devel/attachments/20110325/e50df8e1/attachment-0002.html>

More information about the Netarchivesuite-devel mailing list