On Mar 11, 2010, at 13:04, Rico Jansen wrote:
> <...>
> I have searched the list and google, and found some references to
> connect_timeout and
> DataSources. But most of them are quite old, and on the wiki
> (http://wiki.magnolia-cms.com/display/WIKI/Changing+Jackrabbit+PersistenceManager)
> It says that using a datasource is not the default way.
> 
> So I'm quite confused, using a datasources is not recommended, and using 
> direct
> connections is. Yet this does not seem to work for us with Mysql which
> is strange
> since Mysql is recommended.

Actually, using DataSources is support in Jackrabbit since at least JR 1.6 - 
the information that was on this page referred to a 3rd party PM which was 
quite outdated; i just removed it.
This should tell you how to configure it:
 http://wiki.apache.org/jackrabbit/UsingJNDIDataSource

As for the log messages, they're admittedly worrying, but if you look at the 
source of ConnectionRecoveryManager, you'll see that it's "normal". What 
happens there is that a query or statement gets executed, fails because the 
connection was lost (which is normal, your connection times out after a while), 
the connection is refetched by ConnRecMan, and the query gets reexecuted. This 
can happen up to 3 times until JackRabbit chokes for real. Meantime, for every 
try, the errors are logged, and since MySQL's exception messages tend to be 
big, this gets scary.

Now my question: do you get these when using a DataSource or a direct 
connection ? If a DS, how and where did you configure the DS? If a direct 
connection, then there's no worry to be had if those are the only exceptions 
you get - after the 3 trials, they get thrown up for real (and not just 
logged), and at that point, you'd probably see much more exceptions in your 
logs.

Cheers,

-g
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to