Re: MySql 5.0 & JackRabbit: Connection issues - Marcel May - org.apache.jackrabbit.users

12 messages in org.apache.jackrabbit.usersRe: MySql 5.0 & JackRabbit: Connectio...

From	Sent On	Attachments
sbarriba	Jul 13, 2007 1:41 am
Thomas Mueller	Jul 13, 2007 2:54 am
Marcel May	Jul 13, 2007 3:43 am
Thomas Mueller	Jul 13, 2007 4:25 am
sbarriba	Jul 15, 2007 9:32 am
Stefan Guggisberg	Jul 16, 2007 2:17 am
sbarriba	Oct 10, 2007 9:23 am
Jukka Zitting	Oct 11, 2007 1:05 am
sbarriba	Oct 12, 2007 7:30 am
Jukka Zitting	Oct 12, 2007 8:33 am
sbarriba	Jan 5, 2008 7:45 am
Jukka Zitting	Jan 5, 2008 1:29 pm

	Permalink for this message Paste this link in email or IM:
	Permalink for this thread 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 issues	Actions...
From:	Marcel May (marc...@consol.de)
Date:	Jul 13, 2007 3:43:04 am
List:	org.apache.jackrabbit.users

If you use an Java EE pool, be aware that the pool/datasource must be non managed, as the persistence managers and file systems for Jackrabbit do not use JTA. Otherwise, you will get problems when the Jackrabbit impl. directly invokes con.commit or con.setAutoCommit on a managed connection.

Using auto reconnect can be dangerous with mysql (imagine what happens with an open TX, and a reconnect is performed). There is an additional JDBC property for reconnecting only at the the end of a TX (reconnectAtTxEnd). An auto reconnect for mysql is not recommend (see the docs).

That mysql closes connections by default after 8hrs of inactivity is a pain. Some firewalls do this often enough, too, for any connection. BTW, the automatic connection closing is configurable on the mysql server, so you could inc. the timeout to prevent over the night/over the weekend timouts caused by inactivity.

There Cheers, Marcel

sbarriba wrote:

Hi all,

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". The full exception and our workspace persistence configuration are shown below. The app has to be restarted.

This situation prompts the question:

. 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)

. I notice Magnolia are using JNDI instead of the bundle persistence manager. In a previous thread Zukka confirmed "But if you just want to use JNDI to externalize the database configuration and understand the above-mentioned Jackrabbit usage pattern, then there is no downside to using JNDI" (http://mail-archives.apache.org/mod_mbox/jackrabbit-users/200705.mbox/%3C86 d42b...@mail.gmail.com%3E) . Can anyone confirm if the bundle persistence manager will be much more performant that the JNDI manager? If not, then JNDI would be much more consistent for us.

Any other guidance for configuring JackRabbit with MySql 5.0 is appreciated.

Regards,

Shaun

[Workspace Config]

</PersistenceManager>

[Exception Stack]

Caused by: org.apache.jackrabbit.core.state.ItemStateException: setting autocommit failed.

at org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager.sto re(BundleDbPersistenceManager.java:499)

at org.apache.jackrabbit.core.state.SharedItemStateManager$Update.end(SharedIte mStateManager.java:688)

at org.apache.jackrabbit.core.state.SharedItemStateManager.update(SharedItemSta teManager.java:855)

at org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemState Manager.java:326)

at org.apache.jackrabbit.core.state.XAItemStateManager.update(XAItemStateManage r.java:313)

at org.apache.jackrabbit.core.state.LocalItemStateManager.update(LocalItemState Manager.java:302)

at org.apache.jackrabbit.core.state.SessionItemStateManager.update(SessionItemS tateManager.java:306)

at org.apache.jackrabbit.core.ItemImpl.save(ItemImpl.java:1214)

... 65 more

Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: Connection.close() has already been called. Invalid operation in this state.

at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:888)

at com.mysql.jdbc.Connection.getMutex(Connection.java:3727)

at com.mysql.jdbc.Connection.setAutoCommit(Connection.java:5362)

at org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager.sto re(BundleDbPersistenceManager.java:494)

... 72 more

org.apache.jackrabbit.core.state.ItemStateException: setting autocommit failed.