Re: Database Connection Timeouts Using SimpleDbPersistenceManager

[Java Prog <ja...@gmail.com>]

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 <BT...@sewardinc.com> 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
>
>
>

Re: Database Connection Timeouts Using SimpleDbPersistenceManager

[Thomas Mueller <th...@gmail.com>]

Hi,

Hibernate is not used in the SimpleDbPersistenceManager and
DatabaseFileSystem. I'm not sure, but I think the auto-reconnect
feature is not implemented in the version you are using. In any case,
if you see the problem again please post the stack trace if possible.

Thomas


On 1/26/07, Brian Thompson <BT...@sewardinc.com> wrote:
> Hi,
>
> It looks like I'm using 1.1.1.  I'll try switching to the latest
> version.
>
> I don't have a stack trace saved, but it was very clearly a
> database-connection-closed error.  There was a mention of Hibernate
> partway down the stack trace, too, so I'm guessing Hibernate is used
> internally by SimpleDbPersistenceManager.
>
> Thanks,
>
> -Brian
>
>
>
> -----Original Message-----
> From: Thomas Mueller [mailto:thomas.tom.mueller@gmail.com]
> Sent: Friday, January 26, 2007 3:08 AM
> To: users@jackrabbit.apache.org
> Subject: Re: Database Connection Timeouts Using
> SimpleDbPersistenceManager
>
> 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 <ja...@gmail.com> 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 <BT...@sewardinc.com> 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
>

RE: Database Connection Timeouts Using SimpleDbPersistenceManager

[Brian Thompson <BT...@sewardinc.com>]

Hi,

It looks like I'm using 1.1.1.  I'll try switching to the latest
version.

I don't have a stack trace saved, but it was very clearly a
database-connection-closed error.  There was a mention of Hibernate
partway down the stack trace, too, so I'm guessing Hibernate is used
internally by SimpleDbPersistenceManager.

Thanks,

-Brian



-----Original Message-----
From: Thomas Mueller [mailto:thomas.tom.mueller@gmail.com] 
Sent: Friday, January 26, 2007 3:08 AM
To: users@jackrabbit.apache.org
Subject: Re: Database Connection Timeouts Using
SimpleDbPersistenceManager

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 <ja...@gmail.com> 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 <BT...@sewardinc.com> 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

Re: Database Connection Timeouts Using SimpleDbPersistenceManager

[Thomas Mueller <th...@gmail.com>]

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 <ja...@gmail.com> 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 <BT...@sewardinc.com> 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
> >
> >
> >
>