You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Clemens Wyss (JIRA)" <ji...@apache.org> on 2010/12/09 16:19:02 UTC
[jira] Created: (JCR-2839) o.a.jr.c.p.pool.DerbyPersistenceManager
not "compatible" with o.a.jr.c.p.db.DerbyPersistenceManager
o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with o.a.jr.c.p.db.DerbyPersistenceManager
---------------------------------------------------------------------------------------------------
Key: JCR-2839
URL: https://issues.apache.org/jira/browse/JCR-2839
Project: Jackrabbit Content Repository
Issue Type: Bug
Affects Versions: 2.1.1, 2.3.0
Reporter: Clemens Wyss
I create a copy of a jackrabbit repository with org.apache.jackrabbit.core.RepositoryCopier (using org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager).
Trying to access this copy with org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
fails.
Testcase:
1) create a repository.xml file with org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager
2) start/stop jackrabbit
3) change repository.xml to org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
4) start jackrabbit
or vice versa
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2839) o.a.jr.c.p.pool.DerbyPersistenceManager
not "compatible" with o.a.jr.c.p.db.DerbyPersistenceManager
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg resolved JCR-2839.
------------------------------------
Resolution: Not A Problem
o.a.jr.c.p.pool.DerbyPersistenceManager is a SimpleDbPersistenceManager
(every node and property is stored in a single record)
o.a.jr.c.p.db.DerbyPersistenceManager is a BundleDbPersistenceManager
(a node and its properties are 'bundled' in 1 record)
apparently, they use different schemas to store the content. they were
never meant to be compatible.
> o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with o.a.jr.c.p.db.DerbyPersistenceManager
> ---------------------------------------------------------------------------------------------------
>
> Key: JCR-2839
> URL: https://issues.apache.org/jira/browse/JCR-2839
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Affects Versions: 2.1.1, 2.3.0
> Reporter: Clemens Wyss
>
> I create a copy of a jackrabbit repository with org.apache.jackrabbit.core.RepositoryCopier (using org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager).
> Trying to access this copy with org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
> fails.
> Testcase:
> 1) create a repository.xml file with org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager
> 2) start/stop jackrabbit
> 3) change repository.xml to org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
> 4) start jackrabbit
> or vice versa
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2839)
o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with
o.a.jr.c.p.db.DerbyPersistenceManager
Posted by "Justin Edelson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969818#action_12969818 ]
Justin Edelson commented on JCR-2839:
-------------------------------------
To be clear, it's actually the reverse...
o.a.jr.c.p.db.DerbyPersistenceManager is a SimpleDbPersistenceManager
(every node and property is stored in a single record)
o.a.jr.c.p.pool.DerbyPersistenceManager is a BundleDbPersistenceManager
(a node and its properties are 'bundled' in 1 record)
just in case someone comes across this issue in the future.
> o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with o.a.jr.c.p.db.DerbyPersistenceManager
> ---------------------------------------------------------------------------------------------------
>
> Key: JCR-2839
> URL: https://issues.apache.org/jira/browse/JCR-2839
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Affects Versions: 2.1.1, 2.3.0
> Reporter: Clemens Wyss
>
> I create a copy of a jackrabbit repository with org.apache.jackrabbit.core.RepositoryCopier (using org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager).
> Trying to access this copy with org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
> fails.
> Testcase:
> 1) create a repository.xml file with org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager
> 2) start/stop jackrabbit
> 3) change repository.xml to org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
> 4) start jackrabbit
> or vice versa
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2839)
o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with
o.a.jr.c.p.db.DerbyPersistenceManager
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969864#action_12969864 ]
Stefan Guggisberg commented on JCR-2839:
----------------------------------------
> To be clear, it's actually the reverse...
mea culpa, sorry
justin is of course right
> o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with o.a.jr.c.p.db.DerbyPersistenceManager
> ---------------------------------------------------------------------------------------------------
>
> Key: JCR-2839
> URL: https://issues.apache.org/jira/browse/JCR-2839
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Affects Versions: 2.1.1, 2.3.0
> Reporter: Clemens Wyss
>
> I create a copy of a jackrabbit repository with org.apache.jackrabbit.core.RepositoryCopier (using org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager).
> Trying to access this copy with org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
> fails.
> Testcase:
> 1) create a repository.xml file with org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager
> 2) start/stop jackrabbit
> 3) change repository.xml to org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
> 4) start jackrabbit
> or vice versa
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2839)
o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with
o.a.jr.c.p.db.DerbyPersistenceManager
Posted by "Clemens Wyss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969768#action_12969768 ]
Clemens Wyss commented on JCR-2839:
-----------------------------------
The exception occurs in RepositoryImpl#create. Putting the exception stack trace togethre from within the debugger:
org.apache.jackrabbit.core.state.ItemStateException: failed to write bundle: deadbeef-face-babe-cafe-babecafebabe
caused by:
Unable to read index for string: versionStorage
caused by:
Borrow prepareStatement from pool failed
caused by:
Table/View 'VERSION_NAMES' does not exist.
> o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with o.a.jr.c.p.db.DerbyPersistenceManager
> ---------------------------------------------------------------------------------------------------
>
> Key: JCR-2839
> URL: https://issues.apache.org/jira/browse/JCR-2839
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Affects Versions: 2.1.1, 2.3.0
> Reporter: Clemens Wyss
>
> I create a copy of a jackrabbit repository with org.apache.jackrabbit.core.RepositoryCopier (using org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager).
> Trying to access this copy with org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
> fails.
> Testcase:
> 1) create a repository.xml file with org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager
> 2) start/stop jackrabbit
> 3) change repository.xml to org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
> 4) start jackrabbit
> or vice versa
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.