jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2226) Exceptions using DB based repository with WAS 6.1
Date Tue, 29 Sep 2009 15:57:16 GMT

     [ https://issues.apache.org/jira/browse/JCR-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jukka Zitting updated JCR-2226:

    Priority: Minor  (was: Blocker)

Not a blocker as this only affects specific environments.

As a workaround, you may want to consider configuring a direct database connection instead
of the externally managed DataSource.

The connection pooling work from JCR-1456 should nicely solve this issue.

> Exceptions using DB based repository with WAS 6.1 
> --------------------------------------------------
>                 Key: JCR-2226
>                 URL: https://issues.apache.org/jira/browse/JCR-2226
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: clustering
>    Affects Versions: 1.5.4
>            Reporter: Rajiv Kasera
>            Priority: Minor
> We are using Jackrabbit 1.5.4 in a cluster deployment with DB based repository. Here
is how the repository.xml looks like:
>    <DataStore class="org.apache.jackrabbit.core.data.db.DbDataStore">
> 	<param name="driver" value="javax.naming.InitialContext"/>
> 	<param name="url" value="jdbc/dbjournal"/>	
> 	<param name="databaseType" value="oracle"/>
> 	<param name="minRecordLength" value="1024"/>
> 	<param name="copyWhenReading" value="true"/>
> 	<param name="tablePrefix" value="JR_"/>
> 	<param name="maxConnections" value="10"/>
>     </DataStore>
> Same datasource is being used for journal and persistence manager as well.
> With this deployment we keep getting the following exceptions in the WAS logs:
> org.apache.jackrabbit.core.cluster.ClusterNode:590)  - Unable to create log entry.
> org.apache.jackrabbit.core.journal.JournalException: Unable to lock global revision table.
> (org.apache.jackrabbit.core.persistence.bundle.util.ConnectionRecoveryManager:453)  -
could not execute statement, reason: DSRA9110E: Statement is closed., state/code: null/0
> [7/21/09 20:08:18:247 CDT] 0000003c SystemOut     O 2009-07-21 20:08:18,246 ERROR (org.apache.jackrabbit.core.persistence.db.OraclePersistenceManager:239)
 - failed to write property state: 4d80415d-d65b-4e01-93da-b16d15883058/{http://www.jcp.org/jcr/1.0}data
> com.ibm.websphere.ce.cm.ObjectClosedException: DSRA9110E: Statement is closed.
> This is a big blocker for our project since in some cases the document fails to upload
in the db. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message