Dear devs,
Recently I dove into some issues that plagued our production systems,
where consistency checks regularly showed that some nodes are not quite as
they should be. Mainly orphaned nodes (nodes no longer being referenced
from their supposed parent), but also missing child nodes (nodes
On Tue, Dec 6, 2011 at 4:40 PM, Berry van Halderen
b.vanhalde...@1hippo.com wrote:
We've run into log messages that have come us to suspect one of our
practices, namely to reregister node types. The reregistering occurs
in a clustered environment, where other clustered nodes keep on using
the
Hi,
On Fri, Jan 27, 2012 at 9:50 AM, Berry van Halderen
b.vanhalde...@1hippo.com wrote:
Before a JCR save action, the journal table in the database is
consulted. If there are logged actions performed by other Jackrabbit
instances in the cluster than these actions are imported/replayed first
Hi,
On Fri, Jan 27, 2012 at 10:35 AM, Berry van Halderen
b.vanhalde...@1hippo.com wrote:
I've fixed this in our own code, but still I'm a bit worried about this change
of behavior It used to be impossible to unregister a node type when it
was still in use (or at least never to unregister a
On Fri, Jan 27, 2012 at 10:35 AM, Berry van Halderen
b.vanhalde...@1hippo.com wrote:
On Tue, Dec 6, 2011 at 4:40 PM, Berry van Halderen
b.vanhalde...@1hippo.com wrote:
We've run into log messages that have come us to suspect one of our
practices, namely to reregister node types. The
On Fri, Jan 27, 2012 at 11:30 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Hi,
On Fri, Jan 27, 2012 at 10:35 AM, Berry van Halderen
b.vanhalde...@1hippo.com wrote:
I've fixed this in our own code, but still I'm a bit worried about this
change
of behavior It used to be impossible to
[
https://issues.apache.org/jira/browse/JCR-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13194663#comment-13194663
]
Jukka Zitting commented on JCR-3222:
This is wrong.
That's what the
On Fri, Jan 27, 2012 at 11:30 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
On Fri, Jan 27, 2012 at 10:35 AM, Berry van Halderen
b.vanhalde...@1hippo.com wrote:
That should still be the case. The
NodeTypeRegistry.unregisterNodeTypes() method calls the protected
[
https://issues.apache.org/jira/browse/JCR-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13194699#comment-13194699
]
Felix Meschberger commented on JCR-3222:
That's what the
On Fri, Jan 27, 2012 at 11:15 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
On Fri, Jan 27, 2012 at 9:50 AM, Berry van Halderen
That shouldn't be possible since the first cluster node should be
holding the cluster lock during the entire update-persist operation.
Thus another cluster node
Hi,
On Fri, Jan 27, 2012 at 2:26 PM, Berry van Halderen
b.vanhalde...@1hippo.com wrote:
Small investigation shows that some fix for JCR-2587 inadvertently
contained this change, which was reverted (much) later on the trunk,
but after the 2.1.x and 2.2.x branch were made.
Argh, we definitely
Disallow unregistering of node types still (possibly) in use
Key: JCR-3223
URL: https://issues.apache.org/jira/browse/JCR-3223
Project: Jackrabbit Content Repository
Issue Type:
[
https://issues.apache.org/jira/browse/JCR-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berry van Halderen resolved JCR-3223.
-
Resolution: Fixed
Simple fix by aligning code to actual code on trunk.
On Fri, Jan 27, 2012 at 3:29 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
Please do so. I'm all set to cut the 2.2.11 release candidate, and
having this fix in would be great.
Go ahead, it's committed.
Thx,
\Berry
See https://builds.apache.org/job/Jackrabbit-2.2/58/changes
Changes:
[halderen] JCR-3223, JCR-2587: revert accidental commit which causes
unregistering of node types to be allowed even though possibly still in use.
--
[...truncated 4034 lines...]
AU
[
https://issues.apache.org/jira/browse/JCR-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3223:
---
Fix Version/s: 2.4
Thanks!
Since this accidental feature has been out for quite a while in Jackrabbit
[
https://issues.apache.org/jira/browse/JCR-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13194865#comment-13194865
]
Rohit Nijhawan commented on JCR-3221:
-
The real bug is in NodePropBundle.java and
See https://builds.apache.org/job/Jackrabbit-2.2/59/changes
SystemSession#createSession should return SessionImpl again
---
Key: JCR-3224
URL: https://issues.apache.org/jira/browse/JCR-3224
Project: Jackrabbit Content Repository
Issue Type: Bug
[
https://issues.apache.org/jira/browse/JCR-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-3224:
Fix Version/s: 2.4
SystemSession#createSession should return SessionImpl again
[
https://issues.apache.org/jira/browse/JCR-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela reassigned JCR-3224:
---
Assignee: angela
SystemSession#createSession should return SessionImpl again
[
https://issues.apache.org/jira/browse/JCR-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-3222:
---
Attachment: 0001-JCR-3222-Allow-servlet-filters-to-specify-custom-ses.patch
But I don't like this --
[
https://issues.apache.org/jira/browse/JCR-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-3224.
-
Resolution: Fixed
SystemSession#createSession should return SessionImpl again
[
https://issues.apache.org/jira/browse/JCR-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13194970#comment-13194970
]
Jukka Zitting commented on JCR-3221:
Sounds like you may have some other Jackrabbit
[
https://issues.apache.org/jira/browse/JCR-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3222.
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Jukka Zitting
OK, I've now combined
[
https://issues.apache.org/jira/browse/JCR-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13195164#comment-13195164
]
Rohit Nijhawan commented on JCR-3221:
-
I've been at it for 10 full days and have looked
26 matches
Mail list logo
