[ANNOUNCE] Apache Jackrabbit Oak 1.2.2 released
The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit Oak 1.2.2. The release is available for download at: http://jackrabbit.apache.org/downloads.html See the full release notes below for details about this release. Release Notes -- Apache Jackrabbit Oak -- Version 1.2.2 Introduction Jackrabbit Oak is a scalable, high-performance hierarchical content repository designed for use as the foundation of modern world-class web sites and other demanding content applications. Apache Jackrabbit Oak 1.2.2 is a patch release that contains fixes and improvements over Oak 1.2. Jackrabbit Oak 1.2.x releases are considered stable and targeted for production use. The Oak effort is a part of the Apache Jackrabbit project. Apache Jackrabbit is a project of the Apache Software Foundation. Changes in Oak 1.2.2 Improvements [OAK-2726] - Avoid repository traversal for trivial node type changes [OAK-2755] - Consolidated JMX view of all EventListener related statistics [OAK-2789] - Enable timeout for MongoDB queries [OAK-2791] - Change default for oak.mongo.maxDeltaForModTimeIdxSecs [OAK-2806] - Provide property path in warning log for large multi value property [OAK-2818] - Log _lastRev background updates Bug fixes [OAK-2569] - LuceneIndex#loadDocs can throw IllegalArgumentException [OAK-2750] - Indexing for sorting can fail if value is too long [OAK-2780] - DocumentMK.commit() does not check if node exists on property patch [OAK-2782] - Tika not able to load class in case of custom config [OAK-2796] - Persistent cache: old files not removed sometimes [OAK-2798] - OakIndexInput should unset OakIndexFile's byte[] upon close [OAK-2803] - RepositoryUpgrade.copy() doesn't create correct templates for residual item definitions [OAK-2811] - Oak + data store: NPE in SegmentNodeStoreService.deactivate() leads to data store not shutting down properly [OAK-2815] - Persistent cache may block commit [OAK-2820] - SolrServerProviderService should leverage OakSolrServer Tests [OAK-2764] - ExternalSharedStoreIT occasionally fails on travis In addition to the above-mentioned changes, this release contains all changes included up to the Apache Jackrabbit Oak 1.2.1 release. For more detailed information about all the changes in this and other Oak releases, please see the Oak issue tracker at https://issues.apache.org/jira/browse/OAK Release Contents This release consists of a single source archive packaged as a zip file. The archive can be unpacked with the jar tool from your JDK installation. See the README.md file for instructions on how to build this release. The source archive is accompanied by SHA1 and MD5 checksums and a PGP signature that you can use to verify the authenticity of your download. The public key used for the PGP signature can be found at http://www.apache.org/dist/jackrabbit/KEYS. About Apache Jackrabbit Oak --- Jackrabbit Oak is a scalable, high-performance hierarchical content repository designed for use as the foundation of modern world-class web sites and other demanding content applications. The Oak effort is a part of the Apache Jackrabbit project. Apache Jackrabbit is a project of the Apache Software Foundation. For more information, visit http://jackrabbit.apache.org/oak About The Apache Software Foundation Established in 1999, The Apache Software Foundation provides organizational, legal, and financial support for more than 140 freely-available, collaboratively-developed Open Source projects. The pragmatic Apache License enables individual and commercial users to easily deploy Apache software; the Foundation's intellectual property framework limits the legal exposure of its 3,800+ contributors. For more information, visit http://www.apache.org/
buildbot failure in ASF Buildbot on oak-trunk
The Buildbot has detected a new failure on builder oak-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/oak-trunk/builds/1338 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-vm_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-oak-commit' triggered this build Build Source Stamp: [branch jackrabbit/oak/trunk] 1677804 Blamelist: angela,mduerig,mreutegg BUILD FAILED: failed compile Sincerely, -The Buildbot
[jira] [Resolved] (JCR-3878) Fix test case failure in jackrabbit-data
[
https://issues.apache.org/jira/browse/JCR-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank Gupta resolved JCR-3878.
-
Resolution: Fixed
Fix Version/s: 2.10.1
Fix Removed dependency on {{Y:}} drive.
Fixed in revision: 1677920.
Fix test case failure in jackrabbit-data
Key: JCR-3878
URL: https://issues.apache.org/jira/browse/JCR-3878
Project: Jackrabbit Content Repository
Issue Type: Bug
Affects Versions: 2.10.1
Reporter: Shashank Gupta
Assignee: Shashank Gupta
Priority: Critical
Fix For: 2.10.1
Test cases fail as they assume the presence of a drive named Y:
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (JCR-3878) Fix test case failure in jackrabbit-data
Shashank Gupta created JCR-3878: --- Summary: Fix test case failure in jackrabbit-data Key: JCR-3878 URL: https://issues.apache.org/jira/browse/JCR-3878 Project: Jackrabbit Content Repository Issue Type: Bug Reporter: Shashank Gupta Assignee: Shashank Gupta Priority: Critical Test cases fail as they assume the presence of a drive named Y: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build failed in Jenkins: Apache Jackrabbit Oak matrix » jdk1.8.0_11,Ubuntu,SEGMENT_MK,integrationTesting #124
See https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=SEGMENT_MK,profile=integrationTesting/124/changes Changes: [thomasm] OAK-2830 LIRS cache: avoid concurrent loading of the same entry if loading is slow [mreutegg] OAK-2685: Track root state revision when reading the tree Commit missing part of the patch [mreutegg] OAK-2685: Track root state revision when reading the tree [angela] fix indention [mduerig] OAK-2800: Make contributions to reference graph from TarWriter less conservative Correctly follow the segment graph through transitive dependencies inside the TarWriter [mduerig] OAK-2800: Make contributions to reference graph from TarWriter less conservative @Ignored test case [chetanm] OAK-2826 - Refactor ListeneableFutureTask to commons -- [...truncated 36 lines...] U oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/document/AbstractMongoConnectionTest.java U oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/document/AmnesiaDiffCache.java AU oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/document/util/RevisionsKeyTest.java U oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/document/DocumentNodeStoreTest.java U oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/document/DocumentNodeStoreDiffTest.java A oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/segment/file/TarWriterTest.java U oak-core/src/test/java/org/apache/jackrabbit/oak/cache/ConcurrentTest.java U oak-run/src/main/java/org/apache/jackrabbit/oak/fixture/OakRepositoryFixture.java At revision 1677916 [integrationTesting] $ /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.1/bin/mvn -Dnsfixtures=SEGMENT_MK -Dlabel=Ubuntu -Djdk=jdk1.8.0_11 -Dprofile=integrationTesting clean verify -PintegrationTesting -Dsurefire.skip.ut=true [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] Oak Parent POM [INFO] Oak Commons [INFO] Oak Blob Store [INFO] Oak Cloud Blob Store [INFO] Oak Core [INFO] Oak JCR Binding [INFO] Oak upgrade [INFO] Oak HTTP Binding [INFO] Oak Lucene [INFO] Oak Solr core [INFO] Oak Solr OSGi [INFO] Oak External Authentication Support [INFO] Oak LDAP Authentication Support [INFO] Oak TarMK Standby [INFO] Oak Runnable Jar [INFO] Oak Integration Tests for OSGi deployments [INFO] Oak Integration Tests [INFO] Oak PojoSR [INFO] Jackrabbit Oak [INFO] Oak CUG [INFO] [INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1 [INFO] [INFO] [INFO] Building Oak Parent POM 1.4-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oak-parent --- [INFO] [INFO] --- jacoco-maven-plugin:0.7.1.201405082137:prepare-agent (pre-unit-test) @ oak-parent --- [INFO] Skipping JaCoCo execution because property jacoco.skip is set. [INFO] test.opts.coverage set to empty [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ oak-parent --- [INFO] [INFO] --- jacoco-maven-plugin:0.7.1.201405082137:report (post-unit-test) @ oak-parent --- [INFO] Skipping JaCoCo execution because property jacoco.skip is set. [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ oak-parent --- [INFO] [INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ oak-parent --- [INFO] No tests to run. [INFO] [INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ oak-parent --- [INFO] No tests to run. [INFO] [INFO] [INFO] Building Oak Commons 1.4-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oak-commons --- [INFO] [INFO] --- jacoco-maven-plugin:0.7.1.201405082137:prepare-agent (pre-unit-test) @ oak-commons --- [INFO] Skipping JaCoCo execution because property jacoco.skip is set. [INFO] test.opts.coverage set to empty [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ oak-commons --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ oak-commons --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=SEGMENT_MK,profile=integrationTesting/ws/oak-commons/src/main/resources [INFO] Copying 3 resources [INFO]
Build failed in Jenkins: Apache Jackrabbit Oak matrix » jdk1.8.0_11,Ubuntu,DOCUMENT_RDB,integrationTesting #124
See https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=integrationTesting/124/changes Changes: [thomasm] OAK-2830 LIRS cache: avoid concurrent loading of the same entry if loading is slow [mreutegg] OAK-2685: Track root state revision when reading the tree Commit missing part of the patch [mreutegg] OAK-2685: Track root state revision when reading the tree [angela] fix indention [mduerig] OAK-2800: Make contributions to reference graph from TarWriter less conservative Correctly follow the segment graph through transitive dependencies inside the TarWriter [mduerig] OAK-2800: Make contributions to reference graph from TarWriter less conservative @Ignored test case [chetanm] OAK-2826 - Refactor ListeneableFutureTask to commons -- [...truncated 40 lines...] U oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/document/MeasureMemory.java U oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/document/LocalDiffCacheTest.java U oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/document/AbstractMongoConnectionTest.java A oak-core/src/test/java/org/apache/jackrabbit/oak/plugins/segment/file/TarWriterTest.java At revision 1677916 [integrationTesting] $ /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.2.1/bin/mvn -Dnsfixtures=DOCUMENT_RDB -Dlabel=Ubuntu -Djdk=jdk1.8.0_11 -Dprofile=integrationTesting clean verify -PintegrationTesting -Dsurefire.skip.ut=true [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] Oak Parent POM [INFO] Oak Commons [INFO] Oak Blob Store [INFO] Oak Cloud Blob Store [INFO] Oak Core [INFO] Oak JCR Binding [INFO] Oak upgrade [INFO] Oak HTTP Binding [INFO] Oak Lucene [INFO] Oak Solr core [INFO] Oak Solr OSGi [INFO] Oak External Authentication Support [INFO] Oak LDAP Authentication Support [INFO] Oak TarMK Standby [INFO] Oak Runnable Jar [INFO] Oak Integration Tests for OSGi deployments [INFO] Oak Integration Tests [INFO] Oak PojoSR [INFO] Jackrabbit Oak [INFO] Oak CUG [INFO] [INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder with a thread count of 1 [INFO] [INFO] [INFO] Building Oak Parent POM 1.4-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oak-parent --- [INFO] [INFO] --- jacoco-maven-plugin:0.7.1.201405082137:prepare-agent (pre-unit-test) @ oak-parent --- [INFO] Skipping JaCoCo execution because property jacoco.skip is set. [INFO] test.opts.coverage set to empty [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ oak-parent --- [INFO] [INFO] --- jacoco-maven-plugin:0.7.1.201405082137:report (post-unit-test) @ oak-parent --- [INFO] Skipping JaCoCo execution because property jacoco.skip is set. [INFO] [INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ oak-parent --- [INFO] [INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ oak-parent --- [INFO] No tests to run. [INFO] [INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ oak-parent --- [INFO] No tests to run. [INFO] [INFO] [INFO] Building Oak Commons 1.4-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ oak-commons --- [INFO] [INFO] --- jacoco-maven-plugin:0.7.1.201405082137:prepare-agent (pre-unit-test) @ oak-commons --- [INFO] Skipping JaCoCo execution because property jacoco.skip is set. [INFO] test.opts.coverage set to empty [INFO] [INFO] --- maven-remote-resources-plugin:1.4:process (default) @ oak-commons --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ oak-commons --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=integrationTesting/ws/oak-commons/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ oak-commons --- [INFO] Compiling 27 source files to https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=DOCUMENT_RDB,profile=integrationTesting/ws/oak-commons/target/classes [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
Jenkins build is back to normal : Apache Jackrabbit Oak matrix » jdk1.8.0_11,Ubuntu,DOCUMENT_NS,unittesting #124
See https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/jdk=jdk1.8.0_11,label=Ubuntu,nsfixtures=DOCUMENT_NS,profile=unittesting/124/changes
[jira] [Updated] (JCR-3878) Fix test case failure in jackrabbit-data
[ https://issues.apache.org/jira/browse/JCR-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashank Gupta updated JCR-3878: Affects Version/s: 2.10.1 Fix test case failure in jackrabbit-data Key: JCR-3878 URL: https://issues.apache.org/jira/browse/JCR-3878 Project: Jackrabbit Content Repository Issue Type: Bug Affects Versions: 2.10.1 Reporter: Shashank Gupta Assignee: Shashank Gupta Priority: Critical Fix For: 2.10.1 Test cases fail as they assume the presence of a drive named Y: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Jackrabbit-trunk - Build # 2300 - Still Failing
The Apache Jenkins build system has built Jackrabbit-trunk (build #2300) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2300/ to view the results.
Keeping Oak documentation upto date - Use label 'docs-impacting'
Hi Team, At times we introduce new config settings as part of some bug/feature implementation. The required details often remain only in the bug notes and not made part of documentation. I suggest that we mark any such issue with label 'docs-impacting' and at time of release make use of that to update the release notes and also ensure that documentation gets updated Chetan Mehrotra
[jira] [Commented] (JCR-3869) CachingDataStore for SAN or NFS mounted storage
[ https://issues.apache.org/jira/browse/JCR-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528622#comment-14528622 ] Julian Reschke commented on JCR-3869: - [~shgu...@adobe.com]] These changes break the build; they assume the presence of a drive named Y:. CachingDataStore for SAN or NFS mounted storage Key: JCR-3869 URL: https://issues.apache.org/jira/browse/JCR-3869 Project: Jackrabbit Content Repository Issue Type: Improvement Components: jackrabbit-data Affects Versions: 2.10 Reporter: Shashank Gupta Assignee: Shashank Gupta Fix For: 2.10.1 Attachments: JCR-3869.patch Leverage caching capabilities of CachingDataStore for SAN or NFS mounted storage -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: svn commit: r1671261 - in /jackrabbit/trunk: jackrabbit-aws-ext/src/test/java/org/apache/jackrabbit/aws/ext/ds/ jackrabbit-data/src/test/java/org/apache/jackrabbit/core/data/
On 2015-04-07 16:09, Angela Schreiber wrote: Hi Shashank This commit breaks the Oak build (tests in oak-blob-cloud) once we again change the Jackrabbit version to the latest snapshot. I just came across this because I started working on an API extension in Jackrabbit API and changed the Jackrabbit version in my local Oak checkout in order to be able to implement it in Oak. For the time being I will exclude the oak-blob-cloud module from my project in order not to be blocked. May I kindly ask you to revert this commit. Thanks kind regards Angela ... Furthermore, these changes break the Jackrabbit build as well (the unit tests assume the presence of a drive Y:). Best regards, Julian
[jira] [Created] (JCRVLT-89) JcrPackageImpl.uninstall() throws exception if snapshot is missing
Tobias Bocanegra created JCRVLT-89:
--
Summary: JcrPackageImpl.uninstall() throws exception if snapshot
is missing
Key: JCRVLT-89
URL: https://issues.apache.org/jira/browse/JCRVLT-89
Project: Jackrabbit FileVault
Issue Type: Bug
Components: Packaging
Reporter: Tobias Bocanegra
Priority: Minor
The package manager allows to install packages w/o snapshots using the
extract() method. such an installed package is marked 'installed' nevertheless.
a subsequent call to uninstall() will throw an exception:
{noformat}
Caused by: org.apache.jackrabbit.vault.packaging.PackageException: Unable to
uninstall package. No snapshot present.
at
org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.uninstall(JcrPackageImpl.java:587)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (JCR-3869) CachingDataStore for SAN or NFS mounted storage
[
https://issues.apache.org/jira/browse/JCR-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528779#comment-14528779
]
Shashank Gupta commented on JCR-3869:
-
[~julian.resc...@gmx.de] forgot to remove it. test case should work fine if you
remove path entry from {{fs.properties}}. i will fix it tomorrow.
CachingDataStore for SAN or NFS mounted storage
Key: JCR-3869
URL: https://issues.apache.org/jira/browse/JCR-3869
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-data
Affects Versions: 2.10
Reporter: Shashank Gupta
Assignee: Shashank Gupta
Fix For: 2.10.1
Attachments: JCR-3869.patch
Leverage caching capabilities of CachingDataStore for SAN or NFS mounted
storage
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: builder must be a org.apache.jackrabbit.oak.plugins.document.DocumentRootBuilder
Glad to be of help! Regards Julian On Tuesday, May 5, 2015, Torgeir Veimo torgeir.ve...@gmail.com wrote: Excellent, this was just what I needed! I had to add a null check condition on .withBlobStore(blobStore) and builder.setBlobStore(blobStore) so that it didn't fail on NPE when no blob store was configured, but otherwise it worked flawlessly on converting my 800MB test repository. On 5 May 2015 at 19:56, Julian Sedding jsedd...@gmail.com javascript:; wrote: Hi Torgeir Take a look at OAK-2643[0], that may help. You can copy the repository on the NodeStore level, similar to the upgrade scenario. Regards Julian [0] https://issues.apache.org/jira/browse/OAK-2643 On Tue, May 5, 2015 at 2:20 AM, Torgeir Veimo torgeir.ve...@gmail.com javascript:; wrote: Had a look in the source, and it appears this is due to the merge() method only being available in the DocumentRootBuilder, not in the NodeBuilder interface? Is there any other way to move a repository from tar storage to mongodb without regenerating UUID / identifier values? On 4 May 2015 at 23:26, Torgeir Veimo torgeir.ve...@gmail.com javascript:; wrote: I didn't have much luck on the users list with this problem. Is there any work towards upgrading from tarmk to documentmk easier? I'm trying to move a repository from tarmk to mongodb, and am using the oak-run restore command, but am getting an exception; spazzo:oak-run torgeir$ java -jar ./target/oak-run-1.2.1.jar restore mongodb://localhost/oak ~/oak-repository-backup-20150427a Apache Jackrabbit Oak 1.2.1 Exception in thread main java.lang.IllegalArgumentException: builder must be a org.apache.jackrabbit.oak.plugins.document.DocumentRootBuilder at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.asDocumentRootBuilder(DocumentNodeStore.java:2232) at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.merge(DocumentNodeStore.java:1490) [...] Looking at the mailing list it might be due to OAK-2049. I've tried running the node count script in oak console to find the offending node, but it detects no errors. http://oak-dev.jackrabbit.apache.narkive.com/KVUViR6K/cannot-backup-and-restore-aem-tar-repository Are there any other things I need to fix in the repository? I've run the check, compact and then backup commands on the repository prior to trying to restore it to mongodb. -- -Tor -- -Tor -- -Tor
[jira] [Created] (JCR-3877) XML bootstrap import: Bad if conditions when resolving UUID conflicts
David Caviedes created JCR-3877:
---
Summary: XML bootstrap import: Bad if conditions when resolving
UUID conflicts
Key: JCR-3877
URL: https://issues.apache.org/jira/browse/JCR-3877
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
Affects Versions: 2.8
Environment: Windows 7 64 bits // Java 1.7.0_67
Reporter: David Caviedes
There is a bad if condition in class
org.apache.jackrabbit.core.xml.SessionImporter when trying to resolve UUID
conflicts at line 377:
{code:title=SessionImporter .java|borderStyle=solid}// edge case: colliding
node does have same uuid
// (see http://issues.apache.org/jira/browse/JCR-1128)
if (!(existing.getId().equals(id)
(uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REMOVE_EXISTING
|| uuidBehavior ==
ImportUUIDBehavior.IMPORT_UUID_COLLISION_REPLACE_EXISTING))) {
throw new ItemExistsException(
Node with the same UUID exists: + existing);
}{code}
In our case, the old id is filled and the new id is null, so
existing.getId().equals(id) will always return false so the if condition
will always be true, what is not correct, because uuids are not the same (as
the exception says).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: builder must be a org.apache.jackrabbit.oak.plugins.document.DocumentRootBuilder
Excellent, this was just what I needed! I had to add a null check condition on .withBlobStore(blobStore) and builder.setBlobStore(blobStore) so that it didn't fail on NPE when no blob store was configured, but otherwise it worked flawlessly on converting my 800MB test repository. On 5 May 2015 at 19:56, Julian Sedding jsedd...@gmail.com wrote: Hi Torgeir Take a look at OAK-2643[0], that may help. You can copy the repository on the NodeStore level, similar to the upgrade scenario. Regards Julian [0] https://issues.apache.org/jira/browse/OAK-2643 On Tue, May 5, 2015 at 2:20 AM, Torgeir Veimo torgeir.ve...@gmail.com wrote: Had a look in the source, and it appears this is due to the merge() method only being available in the DocumentRootBuilder, not in the NodeBuilder interface? Is there any other way to move a repository from tar storage to mongodb without regenerating UUID / identifier values? On 4 May 2015 at 23:26, Torgeir Veimo torgeir.ve...@gmail.com wrote: I didn't have much luck on the users list with this problem. Is there any work towards upgrading from tarmk to documentmk easier? I'm trying to move a repository from tarmk to mongodb, and am using the oak-run restore command, but am getting an exception; spazzo:oak-run torgeir$ java -jar ./target/oak-run-1.2.1.jar restore mongodb://localhost/oak ~/oak-repository-backup-20150427a Apache Jackrabbit Oak 1.2.1 Exception in thread main java.lang.IllegalArgumentException: builder must be a org.apache.jackrabbit.oak.plugins.document.DocumentRootBuilder at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.asDocumentRootBuilder(DocumentNodeStore.java:2232) at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.merge(DocumentNodeStore.java:1490) [...] Looking at the mailing list it might be due to OAK-2049. I've tried running the node count script in oak console to find the offending node, but it detects no errors. http://oak-dev.jackrabbit.apache.narkive.com/KVUViR6K/cannot-backup-and-restore-aem-tar-repository Are there any other things I need to fix in the repository? I've run the check, compact and then backup commands on the repository prior to trying to restore it to mongodb. -- -Tor -- -Tor -- -Tor
Event Handling
Hi, We are using Oak in one of our applications, and have come up with a problem that I can’t seem to find an answer to. We have an Event Listener registered to listen for changes to properties in a node. It is always notified of the events properly. Upon notification, the listener retrieves the Node from the session, and performs various actions depending on the properties set on the node. However, if the node is versioned, the node that is retrieved from the JCR is not always up-to-date, even if a new session is used to retrieve it. I assume that this is because versioning introduces a delay in the “save”. Is there a way to work around this, short of forcing an arbitrary wait before attempting to retrieve the node? Thanks Jim
[jira] [Commented] (JCR-1348) simple-webdav: DAV:auto-version property not handled properly
[ https://issues.apache.org/jira/browse/JCR-1348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14528134#comment-14528134 ] Stefan Thieme commented on JCR-1348: Angela, I am adding your thoughts you have given in response to file issues on webdav on the users mailing list, as this is related. http://jackrabbit.markmail.org/message/7qgliawhouiz4ee6?q=auto-version+list:org.apache.jackrabbit.users#query:auto-version%20list%3Aorg.apache.jackrabbit.users+page:1+mid:7qgliawhouiz4ee6+state:results Angela wrote Oct 21, 2008 7:26:44 am: sure. there are some thoughts in the issue regarding the resolution. some prerequisites i didn't mention: in order to be able to set custom properties on a webdav resource the underlying jcr file node must not have it's jcr:content node being nt:resource (by default it's nt:unstructured in the simple dav server). further more: if the DAV:auto-version property was present in the JCR repository, performing the automated checkout/checkin or lock/unlock could be done in the handlers for resource updates/creation. but note, that this is just a rough guideline. i didn't carefully think about all the details of the implementation. simple-webdav: DAV:auto-version property not handled properly - Key: JCR-1348 URL: https://issues.apache.org/jira/browse/JCR-1348 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-jcr-server Reporter: angela rfc 3253 defines the effect of the DAV:auto-version property ([1], [2]). the version-support implemented in the simple server adds the auto-version property to the property-list but does - not prohibit changing the value (which currently would be the correct) - nor behave properly if the value is modified (auto-version not yet implemented) - nor does it check if the prop-value is valid. [1] http://www.webdav.org/specs/rfc3253.html#rfc.section.2.2.2 [2] http://www.webdav.org/specs/rfc3253.html#PROPERTY_auto-version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (JCR-3876) POM dependencies to jackrabbit-data test-jar are not test-scoped
Cédric Damioli created JCR-3876: --- Summary: POM dependencies to jackrabbit-data test-jar are not test-scoped Key: JCR-3876 URL: https://issues.apache.org/jira/browse/JCR-3876 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core, jackrabbit-data Affects Versions: 2.10, 2.9.1, 2.9, 2.8, 2.7.5 Reporter: Cédric Damioli Since JCR-3729, jackrabbit-data POM exports test classes and jackrabbit-core POM use it without scopetest/scope It's certainly not a problem for maven users, but we use Ivy, and it seems that Ivy don't know how to manage two times the same dependency with the same scope, resulting in jackrabbit-data not being transitively get through jackrabbit-core. If I add scopetests/scope to the dependency, all tests still run fine and Ivy becomes happy. Anybody objects ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JCR-2598) Saving concurrent sessions executing random operations causes a corrupt JCR
[ https://issues.apache.org/jira/browse/JCR-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14529184#comment-14529184 ] Sam Stange commented on JCR-2598: - Thanks Unico for the link to the standalone checker. We already reverted to a point in time back-up, so it would be rather difficult to run the tool at this point. Could you explain what the validatehierarchy parameter is checking and how it prevents repository corruptions? Saving concurrent sessions executing random operations causes a corrupt JCR --- Key: JCR-2598 URL: https://issues.apache.org/jira/browse/JCR-2598 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabbit-core Affects Versions: 1.6.1, 2.0 Reporter: Stephan Huttenhuis Assignee: Jukka Zitting Fix For: 1.6.4, 2.0.3, 2.1.1, 2.2 Attachments: ConcurrencyTest3.java, JCR-2598-II.patch, JCR-2598.patch, Output after patch.txt, Output before patch.txt, org.apache.jackrabbit.core.ConcurrencyTest3.txt Run the attached unit test. Several concurrent sessions add, move, and remove nodes. Then the index is removed and the repository is again started. The repository is in an inconsistent state and the index cannot be rebuild. Also a lot of exceptions occur. See (see Output before patch.txt). Note that the unit test also suffers from the deadlock of issue http://issues.apache.org/jira/browse/JCR-2525 about half the time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: builder must be a org.apache.jackrabbit.oak.plugins.document.DocumentRootBuilder
Hi Torgeir Take a look at OAK-2643[0], that may help. You can copy the repository on the NodeStore level, similar to the upgrade scenario. Regards Julian [0] https://issues.apache.org/jira/browse/OAK-2643 On Tue, May 5, 2015 at 2:20 AM, Torgeir Veimo torgeir.ve...@gmail.com wrote: Had a look in the source, and it appears this is due to the merge() method only being available in the DocumentRootBuilder, not in the NodeBuilder interface? Is there any other way to move a repository from tar storage to mongodb without regenerating UUID / identifier values? On 4 May 2015 at 23:26, Torgeir Veimo torgeir.ve...@gmail.com wrote: I didn't have much luck on the users list with this problem. Is there any work towards upgrading from tarmk to documentmk easier? I'm trying to move a repository from tarmk to mongodb, and am using the oak-run restore command, but am getting an exception; spazzo:oak-run torgeir$ java -jar ./target/oak-run-1.2.1.jar restore mongodb://localhost/oak ~/oak-repository-backup-20150427a Apache Jackrabbit Oak 1.2.1 Exception in thread main java.lang.IllegalArgumentException: builder must be a org.apache.jackrabbit.oak.plugins.document.DocumentRootBuilder at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.asDocumentRootBuilder(DocumentNodeStore.java:2232) at org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.merge(DocumentNodeStore.java:1490) [...] Looking at the mailing list it might be due to OAK-2049. I've tried running the node count script in oak console to find the offending node, but it detects no errors. http://oak-dev.jackrabbit.apache.narkive.com/KVUViR6K/cannot-backup-and-restore-aem-tar-repository Are there any other things I need to fix in the repository? I've run the check, compact and then backup commands on the repository prior to trying to restore it to mongodb. -- -Tor -- -Tor
