Hi, The current version of Jackrabbit should actually re-connect to the database automatically. Which version do you use? What is the stack trace?
Thomas On 1/26/07, Java Prog <[EMAIL PROTECTED]> wrote:
Similar issue arises for MySQL. Jackrabbit uses only on connection to the DB that is established at the startup. Some databases drop that connection after a period of time if connection is idle. I have created timer task that add simple node, remove it and call session.save() (to actually call DB). Task is executed in the period that is lesser than database idle timeout. It works fast, and keep connection alive. Regardas, J On 1/25/07, Brian Thompson <[EMAIL PROTECTED]> wrote: > Hello, > > I'm using Jackrabbit in a project running on Tomcat. It's using > SimpleDbPersistenceManager, connecting to a SQL Server database to > persist nodes. > > The application works fine until I leave it running idle for more than > half an hour or so - then when I try to reload pages that access the > repository, I get exceptions telling me that the database connection has > been closed! > > Jackrabbit is being configured via SpringModules for this project. > > None of the docs I've googled so far mention anything about connection > timeouts. Has anyone had to deal with this type of thing before? > > Regards, > > Brian Thompson > > >
