Hi,
I think the core of the problem is that the memory node store doesn't
always behave properly when initialised with something else than a
MemoryNodeState. Consider:
NodeState base = new AlienNodeState();
NodeStore store = new MemoryNodeStore(base);
NodeBuilder builder =
Ignore that last message. I thought it was logging every node, not every 10,000
nodes :D
-Original Message-
From: Robert Haycock [mailto:robert.hayc...@artificial-solutions.com]
Sent: 22 September 2016 16:34
To: oak-dev@jackrabbit.apache.org
Subject: RE: oak-upgrade problems migrating
I've removed (for now) the large strings and now the upgrade has started.
I have to say, it's a lot slower than I anticipated but its running :)
Thanks.
-Original Message-
From: Robert Haycock [mailto:robert.hayc...@artificial-solutions.com]
Sent: 22 September 2016 15:33
To:
Hi Tomek,
We are aiming at having a cluster of Oaks . I'll see if I can find the
offending large string.
Thanks.
-Original Message-
From: Tomek Rekawek [mailto:reka...@adobe.com]
Sent: 22 September 2016 15:29
To: oak-dev@jackrabbit.apache.org
Subject: Re: oak-upgrade problems
Hi Robert,
I think the quoted exception may be caused by some long string stored in the
Jackrabbit 2 repository. In MongoMK all the strings are inlined in the Mongo
documents, while the binaries are extracted to the blob store. Therefore,
string properties longer than ~15MB are not supported.
I can't find any docs either under the project or online regarding this.
-Original Message-
From: Torgeir Veimo [mailto:torgeir.ve...@gmail.com]
Sent: 22 September 2016 15:10
To: oak-dev@jackrabbit.apache.org
Subject: Re: oak-upgrade problems migrating from Jackrabbit 2 to Oak
Maybe you
Maybe you can work around it by upgrading using tarmk, then copying to a
mongodb repository when it's all done.
On 23 September 2016 at 00:08, Robert Haycock <
robert.hayc...@artificial-solutions.com> wrote:
> Thanks Tomek,
>
> Getting closer!
>
> Looks like a setting somewhere needs
Thanks Tomek,
Getting closer!
Looks like a setting somewhere needs increasing...
Exception in thread "main" java.lang.RuntimeException:
javax.jcr.RepositoryException: Failed to copy content
at com.google.common.io.Closer.rethrow(Closer.java:149)
at
Hi Robert,
Thanks for the feedback.
> On 22 Sep 2016, at 15:13, Robert Munteanu wrote:
>
> Only thing I'm wondering is whether there is a scenario where
> performance would be greatly impacted since the NodeState contains lots
> of entries _and_ it's not a MemoryNodeState,
On Thu, 2016-09-22 at 12:49 +, Tomek Rekawek wrote:
> Hi,
>
> I’ve looked into this issue. I think it’s caused by the fact that the
> squeeze() method sometimes doesn’t wrap the passed node state with
> MemoryNodeStates, but return it as-is. I tried to wrap the state
> unconditionally in the
Hi,
I’ve looked into this issue. I think it’s caused by the fact that the squeeze()
method sometimes doesn’t wrap the passed node state with MemoryNodeStates, but
return it as-is. I tried to wrap the state unconditionally in the initializers
and it fixed the issue.
Michael, Robert - do you
Hi Robert,
thanks for noticing this. It seems you’ve run into another bug: OAK-4842[1]. I
fixed it. Also, I backported the previous fix to the 1.4 branch. Feel free to
try the SNAPSHOTs:
1.4 (preferred if you want to use Oak 1.4.x):
Hello team,
I'm planning to cut Oak 1.5.11 on 28th September AM BST.
If there are any objections please let me know. Otherwise I will
re-schedule any non-resolved issue for the next iteration.
Thanks
Davide
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build
#1169)
Status: Failure
Check console output at
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1169/ to view
the results.
Changes:
[reschke] OAK-4583: RDB*Store: update Tomcat JDBC pool dependency
14 matches
Mail list logo