Hello,
Thank you for you answer.
I checked the doc of recommendations for Production that you linked, but in our
case, we have to use DB2, not PostgreSQL.
Yes, we have "BundleDbPersistenceManager" configured in the
default-repository-config.xml:
<PersistenceManager
class="org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager">
<param name="schema" value="db2"></param>
<param name="driver" value="com.ibm.db2.jcc.DB2Driver"/>
<param name="url" value="url"/>
<param name="user" value="username"/>
<param name="password" value="password"/>
<param name="schemaObjectPrefix" value="prefix"/>
<param name="externalBLOBs" value="true"/>
</PersistenceManager>
We use the default BundleDbPersistenceManager since there is no other
implementation for DB2 (like PostgreSQL, Oracle,...)
Would anyone have an idea how to configure JCR to reconnect when the connection
with the DB is lost?
Kind regards,
Céline
________________________________________
From: [email protected] [[email protected]] On Behalf Of
Julien CARSIQUE [[email protected]]
Sent: Monday, June 08, 2009 2:53 PM
To: [email protected]
Cc: [email protected]
Subject: Re: [Ecm] Problem opening folders or documents
Hello,
Look at http://lists.nuxeo.com/pipermail/ecm/2008-June/004684.html
<< For datasources, it's possible to work around it. Have a look at
docs/examples/jca/mysql-ds.xml in your JBoss distribution.
Check the line:
<valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
You should add this to your datasources, so that the connection pool can
check that a connection is still valid before handing it to the
application. >>
and
<< You can change the MySQL wait_timeout configuration parameter to
something bigger than the default (8 hours I think). >>
Have you a "BundleDbPersistenceManager" configured in your
default-repository-config.xml ?
If so, note that in a production environment, this configuration is not
recommended. Prefer to it a PostgreSQLPersistenceManager with PostgreSQL
for example.
See http://doc.nuxeo.org/xwiki/bin/view/Main/NuxeoProdSetup
and http://doc.nuxeo.org/5.1/books/nuxeo-book/html-single/#d1836e7541
Best regards,
Julien
[email protected] a écrit :
> Hello,
>
> I have almost everyday, when trying to open folders or documents (with Nuxeo
> 5.1.6), the following exception:
>
> ERROR
> [org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager]
> failed to read bundle: 09c7649f-02c4-4329-9d82-0da078efb1ac:
> com.ibm.db2.jcc.b.SqlException: Invalid operation: statement closed
> ERROR
> [org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager]
> Failed resetting PreparedStatement
> 2009-06-02 09:58:57,657 ERROR
> [org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager]
> Reason: Invalid operation: statement closed
> ERROR
> [org.apache.jackrabbit.core.persistence.bundle.BundleDbPersistenceManager]
> State/Code: null/-99999
>
> The only way I found to correct the problem is to restart the Nuxeo server.
> But this "solution" is not possible in production environnement. So I looked
> into adding a "check-valid-connection-sql" option in the datasources as
> follows:
>
> <check-valid-connection-sql>SELECT COUNT(*) FROM
> SYSIBM.SYSTABLES</check-valid-connection-sql>
>
> But it doesn't make any difference. Does anybody already got this problem
> and found a solution?
>
> Thanks in advance,
>
> Céline
> --
> Posted by "celine" at Nuxeo Discussions <http://nuxeo.org/discussions>
> View the complete thread:
> <http://www.nuxeo.org/discussions/thread.jspa?threadID=2514#6898>
> _______________________________________________
> ECM mailing list
> [email protected]
> http://lists.nuxeo.com/mailman/listinfo/ecm
> To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
>
--
Julien Carsique, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
[email protected] | Tel: +33 1 40 33 79 87
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
