You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Torgeir Veimo (JIRA)" <ji...@apache.org> on 2008/10/14 00:13:47 UTC
[jira] Created: (JCR-1808) deploying 1.5.0-b1 with existing DB from
1.4.6 throws exception
deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
---------------------------------------------------------------
Key: JCR-1808
URL: https://issues.apache.org/jira/browse/JCR-1808
Project: Jackrabbit
Issue Type: Bug
Components: jackrabbit-core
Affects Versions: 1.5.0
Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
Reporter: Torgeir Veimo
Priority: Blocker
Attachments: log.txt
Trying out the new jackrabbit build 1.5.0-b1 with an existing repository created with jackrabbit 1.4.*, throws exception on startup. Log output included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1808) deploying 1.5.0-b1 with existing DB
from 1.4.6 throws exception
Posted by "Torgeir Veimo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639641#action_12639641 ]
Torgeir Veimo commented on JCR-1808:
------------------------------------
My impression was that the repository.xml file was only taken into account when creating the repository, not on each subsequent instantiating.
> deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
> ---------------------------------------------------------------
>
> Key: JCR-1808
> URL: https://issues.apache.org/jira/browse/JCR-1808
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
> Reporter: Torgeir Veimo
> Priority: Blocker
> Attachments: log.txt, repository.xml
>
>
> Trying out the new jackrabbit build 1.5.0-b1 with an existing repository created with jackrabbit 1.4.*, throws exception on startup. Log output included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1808) deploying 1.5.0-b1 with existing DB from
1.4.6 throws exception
Posted by "Torgeir Veimo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Torgeir Veimo updated JCR-1808:
-------------------------------
Attachment: log.txt
stacktrace
> deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
> ---------------------------------------------------------------
>
> Key: JCR-1808
> URL: https://issues.apache.org/jira/browse/JCR-1808
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
> Reporter: Torgeir Veimo
> Priority: Blocker
> Attachments: log.txt
>
>
> Trying out the new jackrabbit build 1.5.0-b1 with an existing repository created with jackrabbit 1.4.*, throws exception on startup. Log output included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1808) deploying 1.5.0-b1 with existing DB
from 1.4.6 throws exception
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639410#action_12639410 ]
Jukka Zitting commented on JCR-1808:
------------------------------------
What does your repository configuration file look like? I'm especially interested in the <PersistenceManager/> entry within <Versioning/>.
I couldn't reproduce this with a default Jackrabbit 1.4 configuration.
> deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
> ---------------------------------------------------------------
>
> Key: JCR-1808
> URL: https://issues.apache.org/jira/browse/JCR-1808
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
> Reporter: Torgeir Veimo
> Priority: Blocker
> Attachments: log.txt
>
>
> Trying out the new jackrabbit build 1.5.0-b1 with an existing repository created with jackrabbit 1.4.*, throws exception on startup. Log output included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1808) deploying 1.5.0-b1 with existing DB from
1.4.6 throws exception
Posted by "Torgeir Veimo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Torgeir Veimo updated JCR-1808:
-------------------------------
Attachment: repository.xml
repository used when creating repository with 1.4.5.
> deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
> ---------------------------------------------------------------
>
> Key: JCR-1808
> URL: https://issues.apache.org/jira/browse/JCR-1808
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
> Reporter: Torgeir Veimo
> Priority: Blocker
> Attachments: log.txt, repository.xml
>
>
> Trying out the new jackrabbit build 1.5.0-b1 with an existing repository created with jackrabbit 1.4.*, throws exception on startup. Log output included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1808) deploying 1.5.0-b1 with existing DB
from 1.4.6 throws exception
Posted by "Torgeir Veimo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639635#action_12639635 ]
Torgeir Veimo commented on JCR-1808:
------------------------------------
It appears the repository.xml I'm using with JR 1.5 is different than the one used to create the 1.4.X repository. The new one declares the bundle persistence manager. Changing to the old persistence manager for the 1.5 repository.xml makes things work again;
< <PersistenceManager class="org.apache.jackrabbit.core.state.db.DerbyPersistenceManager">
< <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/>
< <param name="schemaObjectPrefix" value="${wsp.name}_"/>
---
> <PersistenceManager class="org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceManager">
> <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/>
> <param name="schemaObjectPrefix" value="${wsp.name}_"/>
> deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
> ---------------------------------------------------------------
>
> Key: JCR-1808
> URL: https://issues.apache.org/jira/browse/JCR-1808
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
> Reporter: Torgeir Veimo
> Priority: Blocker
> Attachments: log.txt, repository.xml
>
>
> Trying out the new jackrabbit build 1.5.0-b1 with an existing repository created with jackrabbit 1.4.*, throws exception on startup. Log output included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-1808) deploying 1.5.0-b1 with existing DB
from 1.4.6 throws exception
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639634#action_12639634 ]
Jukka Zitting commented on JCR-1808:
------------------------------------
I added a backwards compatibility test case based on your configuration, see revision 704725.
However, I'm still unable to reproduce the issue. Can you try running the compatibility test suite I've created? The command sequence is:
svn co https://svn.apache.org/repos/asf/jackrabbit/sandbox/jackrabbit-test-harness/compatibility
cd compatibility
mvn clean install
This test suite creates a sequence of repositories using different Jackrabbit versions and repository configurations. I've specified your configuration to be created using Jackrabbit 1.4. Then the test suite tries to open and access all those repositories using the latest trunk which at the moment is essentially the same as 1.5.0-b1.
If the test suite works (i.e. all tests pass) my next option would be to look at your classpath (mostly the Derby version).
> deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
> ---------------------------------------------------------------
>
> Key: JCR-1808
> URL: https://issues.apache.org/jira/browse/JCR-1808
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
> Reporter: Torgeir Veimo
> Priority: Blocker
> Attachments: log.txt, repository.xml
>
>
> Trying out the new jackrabbit build 1.5.0-b1 with an existing repository created with jackrabbit 1.4.*, throws exception on startup. Log output included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1808) deploying 1.5.0-b1 with existing DB
from 1.4.6 throws exception
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-1808.
--------------------------------
Resolution: Invalid
Assignee: Jukka Zitting
No, the configuration is an essential part of the repository throughout its life.
1.5.0-b1 surfaced some backwards compatibility issues with old repository configurations, but those should all now be resolved (in trunk and the 1.5 branch). The configuration you used to create a repository should work as-is on any later Jackrabbit 1.x version.
> deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
> ---------------------------------------------------------------
>
> Key: JCR-1808
> URL: https://issues.apache.org/jira/browse/JCR-1808
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
> Reporter: Torgeir Veimo
> Assignee: Jukka Zitting
> Priority: Blocker
> Attachments: log.txt, repository.xml
>
>
> Trying out the new jackrabbit build 1.5.0-b1 with an existing repository created with jackrabbit 1.4.*, throws exception on startup. Log output included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.