UPDATE:things improved dramatically for us after I did a clean
recompile of DSpace, making sure to use the right version of
Java. ;-)
We still had masses of errors showing in the tomcat log, as
before, but tomcat at least did not fall over every five
minutes. In fact, it remained up all day. (
I found a thread on dspace-tech about this (typically unresolved) with
the suggestion to tweak the db.maxconnections and db.maxidle parameters.
So ... changed db.maxconnection from 30 to 50, and db.maxidle from -1 to 5.
Also changed maxconnections in postgresql.conf from 100 to 150.
Unfortunate
More problems following the 1.4.2 upgrade:
We're getting heaps of errors from tomcat, like this:
17/03/2008 13:05:14 org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet mydspace threw exception
java.util.NoSuchElementException: Timeout waiting for idle objec
3 matches
Mail list logo