On Wed, Sep 05, 2007 at 04:27:27PM +0300, Mika Stenberg wrote: > LOG: unexpected EOF on client connection
This is a problem caused by DSpace not properly closing database connections. It's nothing to worry about really (although it is probably indicative of sloppy / incorrect use of the Context somewhere); all that has happened is that the postgres JDBC driver is trying to use a connection that it assumes is open when it's not. When the driver realised it's actually closed, it will just go hunting for another. I think this is in the list of "things that need cleaning up in the near future"... cheers, Jim -- James Rutherford | Hewlett-Packard Limited registered Office: Research Engineer | Cain Road, HP Labs | Bracknell, Bristol, UK | Berks +44 117 312 7066 | RG12 1HN. [EMAIL PROTECTED] | Registered No: 690597 England The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL". ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
