12 messages in org.apache.jackrabbit.usersRe: MySql 5.0 & JackRabbit: Connectio...
FromSent OnAttachments
sbarribaJul 13, 2007 1:41 am 
Thomas MuellerJul 13, 2007 2:54 am 
Marcel MayJul 13, 2007 3:43 am 
Thomas MuellerJul 13, 2007 4:25 am 
sbarribaJul 15, 2007 9:32 am 
Stefan GuggisbergJul 16, 2007 2:17 am 
sbarribaOct 10, 2007 9:23 am 
Jukka ZittingOct 11, 2007 1:05 am 
sbarribaOct 12, 2007 7:30 am 
Jukka ZittingOct 12, 2007 8:33 am 
sbarribaJan 5, 2008 7:45 am 
Jukka ZittingJan 5, 2008 1:29 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: MySql 5.0 & JackRabbit: Connection issueActions...
From:Thomas Mueller (thom@gmail.com)
Date:Jul 13, 2007 2:54:51 am
List:org.apache.jackrabbit.users

Hi,

We're testing our application using JackRabbit 1.3 with MySql 5.0.27 and mysql-connector-java-5.0.6-bin.jar. After the application has been running for a period of time we start getting various persistence failures within JCR mainly referencing "Connection.close() has already been called".

This is the exception you usually get when the connection times out.

Are there any other connection related parameters that we should be using for MySql? Do I need "autoReconnect=true"? I note that this is 'false' by default from 5.0.3 onwards (http://dev.mysql.com/doc/connector/j/en/auto-reconnect.html)

There are a few problems with this flag. However with bundle persistence it should work as far as I know (because in this persistence manager, autoCommit is on when idle). My recommendation is to use it for BundleDbPersistenceManager.

Can anyone confirm if the bundle persistence manager will be much more
performant that the JNDI manager?

Bundle persistence is faster.

Thomas