[jira] [Commented] (OAK-10654) Build Jackrabbit/jackrabbit-oak-trunk #1363 failed
[ https://issues.apache.org/jira/browse/OAK-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817976#comment-17817976 ] Hudson commented on OAK-10654: -- Previously failing build now is OK. Passed run: [Jackrabbit/jackrabbit-oak-trunk #1367|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1367/] [console log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1367/console] > Build Jackrabbit/jackrabbit-oak-trunk #1363 failed > -- > > Key: OAK-10654 > URL: https://issues.apache.org/jira/browse/OAK-10654 > Project: Jackrabbit Oak > Issue Type: Bug > Components: continuous integration >Reporter: Hudson >Priority: Major > > No description is provided > The build Jackrabbit/jackrabbit-oak-trunk #1363 has failed. > First failed run: [Jackrabbit/jackrabbit-oak-trunk > #1363|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/] > [console > log|https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-oak-trunk/1363/console] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10643) MongoDocumentStore: improve diagnostics for too large docs
[ https://issues.apache.org/jira/browse/OAK-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-10643: - Labels: (was: candidate_oak_1_22) > MongoDocumentStore: improve diagnostics for too large docs > -- > > Key: OAK-10643 > URL: https://issues.apache.org/jira/browse/OAK-10643 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Fix For: 1.62.0 > > > Log or add to exception message (or both): > - attempted UpdateOp > - statistics about the document that was too large to be updated (that would > require a read from Mongo) > Later on, we may want to extend this to that higher layers > (DocumentNodeStore) can try some kind of recovery. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-10643) MongoDocumentStore: improve diagnostics for too large docs
[ https://issues.apache.org/jira/browse/OAK-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817488#comment-17817488 ] Julian Reschke edited comment on OAK-10643 at 2/16/24 11:14 AM: trunk: [d679f33de2|https://github.com/apache/jackrabbit-oak/commit/d679f33de2c9e41f75e9f05e8779df3810890d87] [32462bde8b|https://github.com/apache/jackrabbit-oak/commit/32462bde8b1b5fb4ab9e15d37c1d0322605ff3bb] [66b8bef296|https://github.com/apache/jackrabbit-oak/commit/66b8bef296b132e821a26b2486cfa5339393395b] was (Author: reschke): trunk: [32462bde8b|https://github.com/apache/jackrabbit-oak/commit/32462bde8b1b5fb4ab9e15d37c1d0322605ff3bb] [66b8bef296|https://github.com/apache/jackrabbit-oak/commit/66b8bef296b132e821a26b2486cfa5339393395b] > MongoDocumentStore: improve diagnostics for too large docs > -- > > Key: OAK-10643 > URL: https://issues.apache.org/jira/browse/OAK-10643 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > > Log or add to exception message (or both): > - attempted UpdateOp > - statistics about the document that was too large to be updated (that would > require a read from Mongo) > Later on, we may want to extend this to that higher layers > (DocumentNodeStore) can try some kind of recovery. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-10643) MongoDocumentStore: improve diagnostics for too large docs
[ https://issues.apache.org/jira/browse/OAK-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817488#comment-17817488 ] Julian Reschke edited comment on OAK-10643 at 2/16/24 11:10 AM: trunk: [32462bde8b|https://github.com/apache/jackrabbit-oak/commit/32462bde8b1b5fb4ab9e15d37c1d0322605ff3bb] [66b8bef296|https://github.com/apache/jackrabbit-oak/commit/66b8bef296b132e821a26b2486cfa5339393395b] was (Author: reschke): trunk: [32462bde8b|https://github.com/apache/jackrabbit-oak/commit/32462bde8b1b5fb4ab9e15d37c1d0322605ff3bb] [66b8bef296|https://github.com/apache/jackrabbit-oak/commit/66b8bef296b132e821a26b2486cfa5339393395b] > MongoDocumentStore: improve diagnostics for too large docs > -- > > Key: OAK-10643 > URL: https://issues.apache.org/jira/browse/OAK-10643 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: documentmk >Reporter: Julian Reschke >Assignee: Julian Reschke >Priority: Major > Labels: candidate_oak_1_22 > Fix For: 1.62.0 > > > Log or add to exception message (or both): > - attempted UpdateOp > - statistics about the document that was too large to be updated (that would > require a read from Mongo) > Later on, we may want to extend this to that higher layers > (DocumentNodeStore) can try some kind of recovery. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (OAK-10655) Improve warning emitted for Unexpected changes performed on a non-default mount
[
https://issues.apache.org/jira/browse/OAK-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned OAK-10655:
-
Assignee: Konrad Windszus
> Improve warning emitted for Unexpected changes performed on a non-default
> mount
> ---
>
> Key: OAK-10655
> URL: https://issues.apache.org/jira/browse/OAK-10655
> Project: Jackrabbit Oak
> Issue Type: Improvement
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
>
> Currently the feature provided in OAK-9208 emits WARNs like the following
> {code}
> 5.02.2024 11:46:49.748 *WARN* [ResourceResolverFactory registration]
> org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$ChangeReporter
> Unexpected changes (38) performed on a non-default mount. Printing at most
> 50_- /apps : Changed_-
> java.lang.RuntimeException: null
> at
> org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver$CountingDiff.report(NonDefaultMountWriteReportingObserver.java:106)
> at
> org.apache.jackrabbit.oak.composite.impl.NonDefaultMountWriteReportingObserver.contentChanged(NonDefaultMountWriteReportingObserver.java:88)
> at
> org.apache.jackrabbit.oak.spi.commit.CompositeObserver.contentChanged(CompositeObserver.java:51)
> at
> org.apache.jackrabbit.oak.spi.commit.ChangeDispatcher.contentChanged(ChangeDispatcher.java:79)
> at
> org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler$ObservableLockBasedScheduler.contentChanged(LockBasedScheduler.java:394)
> at
> org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.execute(LockBasedScheduler.java:303)
> at
> org.apache.jackrabbit.oak.segment.scheduler.LockBasedScheduler.schedule(LockBasedScheduler.java:270)
> at
> org.apache.jackrabbit.oak.segment.SegmentNodeStore.merge(SegmentNodeStore.java:211)
> at
> org.apache.jackrabbit.oak.core.MutableRoot.commit(MutableRoot.java:262)
> at
> org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate$WorkspaceCopy.perform(WorkspaceDelegate.java:130)
> at
> org.apache.jackrabbit.oak.jcr.delegate.WorkspaceDelegate.copy(WorkspaceDelegate.java:99)
> at
> org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl$2.performVoid(WorkspaceImpl.java:163)
> at
> org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.performVoid(SessionDelegate.java:299)
> at
> org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:150)
> at
> org.apache.jackrabbit.oak.jcr.session.WorkspaceImpl.copy(WorkspaceImpl.java:132)
> at
> .
> {code}
> It would be useful to add a dedicated exception message to the throwable (or
> prevent logging it) and indicate that this only indicates where the JCR
> session has been committed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (OAK-10652) Repository writes in SegmentStoreMigrator blocked when migrating to Azure segment store
[ https://issues.apache.org/jira/browse/OAK-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miroslav Smiljanic resolved OAK-10652. -- Fix Version/s: 1.62.0 Resolution: Fixed > Repository writes in SegmentStoreMigrator blocked when migrating to Azure > segment store > --- > > Key: OAK-10652 > URL: https://issues.apache.org/jira/browse/OAK-10652 > Project: Jackrabbit Oak > Issue Type: Bug > Components: segment-azure >Affects Versions: 1.60.0 >Reporter: Miroslav Smiljanic >Assignee: Miroslav Smiljanic >Priority: Major > Fix For: 1.62.0 > > > SegmentStoreMigrator is not using FileStore, where the repository lock is > usually obtained and writes allowed by calling > WriteAccessController#enableWriting. Instead, archive manager is used > directly, and repo writes are never enabled. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (OAK-10616) Make error messages from o.a.j.o.namepath.JcrNameParser/JcrPathParser consistent and less misleading
[ https://issues.apache.org/jira/browse/OAK-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke resolved OAK-10616. -- Resolution: Fixed > Make error messages from o.a.j.o.namepath.JcrNameParser/JcrPathParser > consistent and less misleading > - > > Key: OAK-10616 > URL: https://issues.apache.org/jira/browse/OAK-10616 > Project: Jackrabbit Oak > Issue Type: Task > Components: core-spi >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Minor > Fix For: 1.62.0 > > > JcrPathParser delegates name parsing to JcrNameParser, which may lead to > error messages not including the path (contrary to all other error messages > from the JcrPathParser). > JcrPathParser fails with a bogus error message in the case of an unexpected > EOF (trying to insert EOF into the human readable error message). > Also in the case of an empty local name in a prefixed JCR name, the error > message depends on the following characters and is misleading. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (OAK-10616) Make error messages from o.a.j.o.namepath.JcrNameParser/JcrPathParser consistent and less misleading
[ https://issues.apache.org/jira/browse/OAK-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-10616: - Fix Version/s: 1.62.0 > Make error messages from o.a.j.o.namepath.JcrNameParser/JcrPathParser > consistent and less misleading > - > > Key: OAK-10616 > URL: https://issues.apache.org/jira/browse/OAK-10616 > Project: Jackrabbit Oak > Issue Type: Task > Components: core-spi >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Minor > Fix For: 1.62.0 > > > JcrPathParser delegates name parsing to JcrNameParser, which may lead to > error messages not including the path (contrary to all other error messages > from the JcrPathParser). > JcrPathParser fails with a bogus error message in the case of an unexpected > EOF (trying to insert EOF into the human readable error message). > Also in the case of an empty local name in a prefixed JCR name, the error > message depends on the following characters and is misleading. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OAK-10616) Make error messages from o.a.j.o.namepath.JcrNameParser/JcrPathParser consistent and less misleading
[ https://issues.apache.org/jira/browse/OAK-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17809935#comment-17809935 ] Manfred Baedke edited comment on OAK-10616 at 2/16/24 9:41 AM: --- trunk (1.62.0): [4d29e3f7|https://github.com/apache/jackrabbit-oak/commit/4d29e3f7838458f4a5627d93bc0f7831ff8bd6bf] was (Author: baedke): trunk: [4d29e3f7|https://github.com/apache/jackrabbit-oak/commit/4d29e3f7838458f4a5627d93bc0f7831ff8bd6bf] > Make error messages from o.a.j.o.namepath.JcrNameParser/JcrPathParser > consistent and less misleading > - > > Key: OAK-10616 > URL: https://issues.apache.org/jira/browse/OAK-10616 > Project: Jackrabbit Oak > Issue Type: Task > Components: core-spi >Reporter: Manfred Baedke >Assignee: Manfred Baedke >Priority: Minor > Fix For: 1.62.0 > > > JcrPathParser delegates name parsing to JcrNameParser, which may lead to > error messages not including the path (contrary to all other error messages > from the JcrPathParser). > JcrPathParser fails with a bogus error message in the case of an unexpected > EOF (trying to insert EOF into the human readable error message). > Also in the case of an empty local name in a prefixed JCR name, the error > message depends on the following characters and is misleading. -- This message was sent by Atlassian Jira (v8.20.10#820010)
