[jira] [Commented] (JCR-2483) Out of memory error while adding a new host due to large number of revisions

[ https://issues.apache.org/jira/browse/JCR-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728690#comment-14728690 ] Bart van der Schans commented on JCR-2483: -- Hi. This issue and JCR-3905 are indeed related. I

[jira] [Commented] (JCR-2483) Out of memory error while adding a new host due to large number of revisions

[ https://issues.apache.org/jira/browse/JCR-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728691#comment-14728691 ] Bart van der Schans commented on JCR-2483: -- Please see also my comment in JCR-2483 > Out of memory

[jira] [Commented] (JCR-3905) Journal sync after full re-index does not save journal revision

[ https://issues.apache.org/jira/browse/JCR-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728692#comment-14728692 ] Bart van der Schans commented on JCR-3905: -- Please see also my comment in JCR-2483 > Journal sync

[jira] [Issue Comment Deleted] (JCR-2483) Out of memory error while adding a new host due to large number of revisions

[ https://issues.apache.org/jira/browse/JCR-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2483: - Comment: was deleted (was: Please see also my comment in JCR-2483) > Out of memory error

[jira] [Commented] (JCR-3632) Test failed under Java 8

[ https://issues.apache.org/jira/browse/JCR-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14655110#comment-14655110 ] Bart van der Schans commented on JCR-3632: -- It's unclear to me why this is failing,

[jira] [Commented] (JCR-3504) ConcurrentImportTest failure

[ https://issues.apache.org/jira/browse/JCR-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566404#comment-13566404 ] Bart van der Schans commented on JCR-3504: -- Hi Jukka, The test succeeds for me. Do

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13508846#comment-13508846 ] Bart van der Schans commented on JCR-3440: -- Hi Luca, Sorry to hear that. There

[jira] [Commented] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507239#comment-13507239 ] Bart van der Schans commented on JCR-3445: -- Thanks for testing. I'll apply the

[jira] [Resolved] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans resolved JCR-3445. -- Resolution: Fixed PostgreSQL error with setValidationQueryTimeout

[jira] [Commented] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507241#comment-13507241 ] Bart van der Schans commented on JCR-3445: -- Committed in trunk in r1415574 and in

[jira] [Commented] (JCR-3465) JcrUtils.getOrCreateByPath() creates a whole subtree instead of a single branch

[ https://issues.apache.org/jira/browse/JCR-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505404#comment-13505404 ] Bart van der Schans commented on JCR-3465: -- Shouldn't it just fail if a/b or c/d

[jira] [Commented] (JCR-3463) Configurable stopDelay

[ https://issues.apache.org/jira/browse/JCR-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505599#comment-13505599 ] Bart van der Schans commented on JCR-3463: -- Hi Marcel, Just for my understanding:

[jira] [Commented] (JCR-3463) Configurable stopDelay

[ https://issues.apache.org/jira/browse/JCR-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505626#comment-13505626 ] Bart van der Schans commented on JCR-3463: -- Ok, thx. Configurable

[jira] [Commented] (JCR-3465) JcrUtils.getOrCreateByPath() creates a whole subtree instead of a single branch

[ https://issues.apache.org/jira/browse/JCR-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506033#comment-13506033 ] Bart van der Schans commented on JCR-3465: -- From the linux/unix perspective: - if

[jira] [Commented] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13502761#comment-13502761 ] Bart van der Schans commented on JCR-3445: -- Yes, looks good to me. Luca, can you

[jira] [Commented] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500154#comment-13500154 ] Bart van der Schans commented on JCR-3445: -- Hi Luca, Thanks for explaining and the

[jira] [Reopened] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans reopened JCR-3445: -- PostgreSQL error with setValidationQueryTimeout

[jira] [Commented] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13493922#comment-13493922 ] Bart van der Schans commented on JCR-3445: -- Hi Luca, I suspect you have configured

[jira] [Updated] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-3440: - Fix Version/s: 2.6 Deadlock on LOCAL_REVISION table in clustering environment

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13492419#comment-13492419 ] Bart van der Schans commented on JCR-3440: -- Hi Alex, Thanks for looking into this

[jira] [Reopened] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans reopened JCR-3440: -- Re-opening to address the backwards compatibility issue. Deadlock on

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13492462#comment-13492462 ] Bart van der Schans commented on JCR-3440: -- I do want to backport this to 2.4 and

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490595#comment-13490595 ] Bart van der Schans commented on JCR-3440: -- Hi Luca, I've committed a slightly

[jira] [Updated] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-3440: - Resolution: Fixed Assignee: Bart van der Schans Status: Resolved (was: Patch

[jira] [Created] (JCR-3455) Events should be dispatched after the global cluster lock is freed in the SharedItemStateManager

Bart van der Schans created JCR-3455: Summary: Events should be dispatched after the global cluster lock is freed in the SharedItemStateManager Key: JCR-3455 URL:

[jira] [Resolved] (JCR-3455) Events should be dispatched after the global cluster lock is freed in the SharedItemStateManager

[ https://issues.apache.org/jira/browse/JCR-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans resolved JCR-3455. -- Resolution: Fixed Events should be dispatched after the global cluster lock is

[jira] [Commented] (JCR-3449) Improved performance for concurrent read-only access

[ https://issues.apache.org/jira/browse/JCR-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13490647#comment-13490647 ] Bart van der Schans commented on JCR-3449: -- Hi Lars, When running in these kinds

[jira] [Updated] (JCR-3449) Improved performance for concurrent read-only access

[ https://issues.apache.org/jira/browse/JCR-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-3449: - Resolution: Won't Fix Status: Resolved (was: Patch Available) Resolving as won't

[jira] [Commented] (JCR-3447) InternalValueFactory should use the DataStore whenever available

[ https://issues.apache.org/jira/browse/JCR-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13478938#comment-13478938 ] Bart van der Schans commented on JCR-3447: -- Nice one. I think we should apply the

[jira] [Assigned] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans reassigned JCR-3445: Assignee: Bart van der Schans PostgreSQL error with setValidationQueryTimeout

[jira] [Commented] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13478947#comment-13478947 ] Bart van der Schans commented on JCR-3445: -- Committed in revision 1399612 in trunk.

[jira] [Commented] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13478949#comment-13478949 ] Bart van der Schans commented on JCR-3445: -- Merged in 2.4 in revision 1399616.

[jira] [Updated] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-3445: - Resolution: Fixed Status: Resolved (was: Patch Available) PostgreSQL error

[jira] [Commented] (JCR-3445) PostgreSQL error with setValidationQueryTimeout

[ https://issues.apache.org/jira/browse/JCR-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13478990#comment-13478990 ] Bart van der Schans commented on JCR-3445: -- Ah my mistake ;-) Thanks Claus!

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476868#comment-13476868 ] Bart van der Schans commented on JCR-3440: -- Hi Luca, Thanks for testing. That's in

[jira] [Updated] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-3440: - Attachment: fixAlwaysBatchMode.patch Deadlock on LOCAL_REVISION table in clustering

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476145#comment-13476145 ] Bart van der Schans commented on JCR-3440: -- Hi Luca, From what I see in the code

[jira] [Updated] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-3440: - Attachment: fixNoLockOnLocalRevisionsWIP.java Update a (WIP) patch. Luca, could you please

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474870#comment-13474870 ] Bart van der Schans commented on JCR-3440: -- Hi Luca, Usually patches are provided

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475027#comment-13475027 ] Bart van der Schans commented on JCR-3440: -- So it might be that one thread started

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474003#comment-13474003 ] Bart van der Schans commented on JCR-3440: -- Hi Luca, I tend to agree with Claus.

[jira] [Commented] (JCR-3440) Deadlock on LOCAL_REVISION table in clustering environment

[ https://issues.apache.org/jira/browse/JCR-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474277#comment-13474277 ] Bart van der Schans commented on JCR-3440: -- From the patch: To me the check

[jira] [Commented] (JCR-3435) NPE on parsing XPath query with child axis and star name at beginning (regression from 1.6.x)

[ https://issues.apache.org/jira/browse/JCR-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13468410#comment-13468410 ] Bart van der Schans commented on JCR-3435: -- Hi Jörg, Thanks for the patch! I've

[jira] [Assigned] (JCR-3435) NPE on parsing XPath query with child axis and star name at beginning (regression from 1.6.x)

[ https://issues.apache.org/jira/browse/JCR-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans reassigned JCR-3435: Assignee: Bart van der Schans NPE on parsing XPath query with child axis and

[jira] [Commented] (JCR-3426) Log warning when changes are performed with event notification thread

[ https://issues.apache.org/jira/browse/JCR-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13457112#comment-13457112 ] Bart van der Schans commented on JCR-3426: -- If there are valid (exceptional) use

[jira] [Commented] (JCR-3426) Log warning when changes are performed with event notification thread

[ https://issues.apache.org/jira/browse/JCR-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13457116#comment-13457116 ] Bart van der Schans commented on JCR-3426: -- Forgot to say that I like the idea ;-)

[jira] [Closed] (JCR-3417) Failed Journal lock not propagated

[ https://issues.apache.org/jira/browse/JCR-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans closed JCR-3417. Failed Journal lock not propagated --

[jira] [Commented] (JCR-3417) Failed Journal lock not propagated

[ https://issues.apache.org/jira/browse/JCR-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442442#comment-13442442 ] Bart van der Schans commented on JCR-3417: -- Makes sense to me and the patch looks

[jira] [Commented] (JCR-3406) Journal doUnlock sometimes not called on repository shutdown

[ https://issues.apache.org/jira/browse/JCR-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434956#comment-13434956 ] Bart van der Schans commented on JCR-3406: -- Ok, sounds fine to me.

[jira] [Commented] (JCR-3406) Journal doUnlock sometimes not called on repository shutdown

[ https://issues.apache.org/jira/browse/JCR-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13434121#comment-13434121 ] Bart van der Schans commented on JCR-3406: -- The if statements seem to be part of

[jira] [Commented] (JCR-3406) Journal doUnlock sometimes not called on repository shutdown

[ https://issues.apache.org/jira/browse/JCR-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431720#comment-13431720 ] Bart van der Schans commented on JCR-3406: -- I'm not sure if the STARTED check is

[jira] [Assigned] (JCR-3387) On heavy load we see occasional SQLException: closed statement: next

[ https://issues.apache.org/jira/browse/JCR-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans reassigned JCR-3387: Assignee: Bart van der Schans (was: Claus Köll) On heavy load we see

[jira] [Commented] (JCR-3364) Moving of nodes requires read access to all parent nodes of the destination node

[ https://issues.apache.org/jira/browse/JCR-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406993#comment-13406993 ] Bart van der Schans commented on JCR-3364: -- Hi Thomas, The problem is that in the

[jira] [Updated] (JCR-3364) Moving of nodes requires read access to all parent nodes of the destination node

[ https://issues.apache.org/jira/browse/JCR-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-3364: - Summary: Moving of nodes requires read access to all parent nodes of the destination node

[jira] [Commented] (JCR-3364) Moving of nodes requires read access to the whole tree

[ https://issues.apache.org/jira/browse/JCR-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13406394#comment-13406394 ] Bart van der Schans commented on JCR-3364: -- Hi Thomas, This might be a bit tricky.

[jira] [Commented] (JCR-3353) A DeadLock can occur if an Exception is thrown while unlocking the Journal

[ https://issues.apache.org/jira/browse/JCR-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398299#comment-13398299 ] Bart van der Schans commented on JCR-3353: -- Nice catch! We might want to port this

[jira] [Commented] (JCR-3303) ClusterNode's stopDelay should default to something other zero

[ https://issues.apache.org/jira/browse/JCR-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13290099#comment-13290099 ] Bart van der Schans commented on JCR-3303: -- Merged in 2.4 in 1346853.

[jira] [Updated] (JCR-3303) ClusterNode's stopDelay should default to something other zero

[ https://issues.apache.org/jira/browse/JCR-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-3303: - Fix Version/s: 2.4.2 2.2.13 ClusterNode's stopDelay should default

[jira] [Commented] (JCR-3040) JMX Stats for the Session

[ https://issues.apache.org/jira/browse/JCR-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13086955#comment-13086955 ] Bart van der Schans commented on JCR-3040: -- I would love to have more stats

[jira] [Commented] (JCR-2697) Add support for encrpted db password in repository.xml

[ https://issues.apache.org/jira/browse/JCR-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13080991#comment-13080991 ] Bart van der Schans commented on JCR-2697: -- Hi Jukka, It could be that I'm missing

[jira] [Updated] (JCR-2964) ItemSaveOperation should not swallow stacktrace

[ https://issues.apache.org/jira/browse/JCR-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2964: - Status: Patch Available (was: Open) ItemSaveOperation should not swallow stacktrace

[jira] [Updated] (JCR-2965) Show referencing nodes in debug log when trying to delete a node with references

[ https://issues.apache.org/jira/browse/JCR-2965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2965: - Status: Patch Available (was: Open) Show referencing nodes in debug log when trying to

[jira] [Created] (JCR-2965) Show referencing nodes in debug log when trying to delete a node with references

Show referencing nodes in debug log when trying to delete a node with references Key: JCR-2965 URL: https://issues.apache.org/jira/browse/JCR-2965 Project: Jackrabbit

[jira] [Updated] (JCR-2964) ItemSaveOperation should not swallow stacktrace

[ https://issues.apache.org/jira/browse/JCR-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2964: - Attachment: do-not-swallow-stack.patch ItemSaveOperation should not swallow stacktrace

[jira] Commented: (JCR-2910) Please add JackrabbitSession.isAdmin()

[ https://issues.apache.org/jira/browse/JCR-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13004479#comment-13004479 ] Bart van der Schans commented on JCR-2910: -- I agree with Felix. Many attempts have

[jira] Commented: (JCR-2877) Extend the consistency check in BundleDbPersistenceManager's to fix child-parent relations

[ https://issues.apache.org/jira/browse/JCR-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12992442#comment-12992442 ] Bart van der Schans commented on JCR-2877: -- We found two distinct cases: - a parent

[jira] Commented: (JCR-2877) Extend the consistency check in BundleDbPersistenceManager's to fix child-parent relations

[ https://issues.apache.org/jira/browse/JCR-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990083#comment-12990083 ] Bart van der Schans commented on JCR-2877: -- We have some code for this for the 1.5

[jira] Commented: (JCR-2639) consistencyCheck doesn't fix bad childnode

[ https://issues.apache.org/jira/browse/JCR-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12872985#action_12872985 ] Bart van der Schans commented on JCR-2639: -- There are two possible options: - remove

[jira] Updated: (JCR-2639) consistencyCheck doesn't fix bad childnode

[ https://issues.apache.org/jira/browse/JCR-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2639: - Attachment: orphan-fix.patch consistencyCheck doesn't fix bad childnode

[jira] Commented: (JCR-2639) consistencyCheck doesn't fix bad childnode

[ https://issues.apache.org/jira/browse/JCR-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871092#action_12871092 ] Bart van der Schans commented on JCR-2639: -- Hi Aleh, We had the same problem a

[jira] Updated: (JCR-2456) Repository is corrupt after concurrent changes with the same session

[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2456: - Attachment: patch-2456-b-1.6.txt Backport to 1.6 of the updated patch. Repository is

[jira] Commented: (JCR-2456) Repository is corrupt after concurrent changes with the same session

[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861799#action_12861799 ] Bart van der Schans commented on JCR-2456: -- The patch also applies to the 1.5

[jira] Commented: (JCR-2456) Repository is corrupt after concurrent changes with the same session

[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802231#action_12802231 ] Bart van der Schans commented on JCR-2456: -- Thanks for the heads up. I will create a

[jira] Commented: (JCR-2225) ORA-01460 ClusterNode: Unable to commit log entry

[ https://issues.apache.org/jira/browse/JCR-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801747#action_12801747 ] Bart van der Schans commented on JCR-2225: -- Hi, I found out wat our problem was. We

[jira] Commented: (JCR-2456) Repository is corrupt after concurrent changes with the same session

[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12800153#action_12800153 ] Bart van der Schans commented on JCR-2456: -- Could the same problem also exist in 1.5

[jira] Commented: (JCR-2456) Repository is corrupt after concurrent changes with the same session

[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12800162#action_12800162 ] Bart van der Schans commented on JCR-2456: -- Running with 1.5 and 10 threads I do see

[jira] Updated: (JCR-2456) Repository is corrupt after concurrent changes with the same session

[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2456: - Affects Version/s: (was: 2.0-beta4) 1.5.7 Status:

[jira] Commented: (JCR-2456) Repository is corrupt after concurrent changes with the same session

[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12800173#action_12800173 ] Bart van der Schans commented on JCR-2456: -- Hi Thomas, I ran the test with

[jira] Updated: (JCR-2456) Repository is corrupt after concurrent changes with the same session

[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2456: - Attachment: patch-2456-1.5.txt backport of patch-2456.txt Repository is corrupt after

[jira] Commented: (JCR-2456) Repository is corrupt after concurrent changes with the same session

[ https://issues.apache.org/jira/browse/JCR-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12800211#action_12800211 ] Bart van der Schans commented on JCR-2456: -- Running with 2 threads with different

[jira] Commented: (JCR-2225) ORA-01460 ClusterNode: Unable to commit log entry

[ https://issues.apache.org/jira/browse/JCR-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12800249#action_12800249 ] Bart van der Schans commented on JCR-2225: -- Lorenzo, Did you ever find I way around

[jira] Commented: (JCR-2443) AbstractSession should not synchronize on the session instance

[ https://issues.apache.org/jira/browse/JCR-2443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792491#action_12792491 ] Bart van der Schans commented on JCR-2443: -- We ran into exactly the same problem

[jira] Commented: (JCR-642) Support flat content hierarchies

[ https://issues.apache.org/jira/browse/JCR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12738316#action_12738316 ] Bart van der Schans commented on JCR-642: - Would it be an idea to store the

[jira] Commented: (JCR-642) Support flat content hierarchies

[ https://issues.apache.org/jira/browse/JCR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12738327#action_12738327 ] Bart van der Schans commented on JCR-642: - @Thomas, Stefan, Thanks for your

[jira] Commented: (JCR-2171) Deadlock in SharedItemStateManager on session.move and node.save

[ https://issues.apache.org/jira/browse/JCR-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12737074#action_12737074 ] Bart van der Schans commented on JCR-2171: -- Can this fix also be backported to the

[jira] Updated: (JCR-2169) BundleDbPersistenceManager consistencyFix doesn't fix missing non system childnode entries of the root node

[ https://issues.apache.org/jira/browse/JCR-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2169: - Attachment: BundleDbPersistenceManager.patch BundleDbPersistenceManager consistencyFix

[jira] Created: (JCR-2169) BundleDbPersistenceManager consistencyFix doesn't fix missing non system childnode entries of the root node

BundleDbPersistenceManager consistencyFix doesn't fix missing non system childnode entries of the root node Key: JCR-2169 URL:

[jira] Commented: (JCR-1999) Index curruption after XML import

[ https://issues.apache.org/jira/browse/JCR-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12688279#action_12688279 ] Bart van der Schans commented on JCR-1999: -- Especially on most linux systems the

[jira] Created: (JCR-2036) Set_property permission not checked when saving a new node

Set_property permission not checked when saving a new node -- Key: JCR-2036 URL: https://issues.apache.org/jira/browse/JCR-2036 Project: Jackrabbit Content Repository Issue Type: Bug

[jira] Updated: (JCR-2036) Set_property permission not checked when saving a new node

[ https://issues.apache.org/jira/browse/JCR-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-2036: - Attachment: ItemImpl.patch Set_property permission not checked when saving a new node

[jira] Commented: (JCR-1918) DbDataStore keeps ResultSets open

[ https://issues.apache.org/jira/browse/JCR-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12665815#action_12665815 ] Bart van der Schans commented on JCR-1918: -- Thx Thomas! DbDataStore keeps

[jira] Commented: (JCR-1918) DbDataStore keeps ResultSets open

[ https://issues.apache.org/jira/browse/JCR-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12661753#action_12661753 ] Bart van der Schans commented on JCR-1918: -- The code in 1.5 and trunk has clearly

[jira] Commented: (JCR-1572) DbDataStore connection does not always reconnect

[ https://issues.apache.org/jira/browse/JCR-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660056#action_12660056 ] Bart van der Schans commented on JCR-1572: -- Indeed it is! I somehow completely

[jira] Commented: (JCR-1572) DbDataStore connection does not always reconnect

[ https://issues.apache.org/jira/browse/JCR-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12659967#action_12659967 ] Bart van der Schans commented on JCR-1572: -- Thomas, Could this (almost) trivial

[jira] Created: (JCR-1918) DbDataStore keeps ResultSets open

DbDataStore keeps ResultSets open - Key: JCR-1918 URL: https://issues.apache.org/jira/browse/JCR-1918 Project: Jackrabbit Issue Type: Bug Components: jackrabbit-core Affects Versions: core 1.4.6

[jira] Updated: (JCR-1918) DbDataStore keeps ResultSets open

[ https://issues.apache.org/jira/browse/JCR-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-1918: - Attachment: dbdatastore_close_rs.patch DbDataStore keeps ResultSets open

[jira] Updated: (JCR-1366) DbDataStore: tablePrefix not accomodated during init test for existing DATASTORE table

[ https://issues.apache.org/jira/browse/JCR-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart van der Schans updated JCR-1366: - Attachment: datastore_prefix.patch The patch is quite trivial. It seems that the table

[jira] Commented: (JCR-1366) DbDataStore: tablePrefix not accomodated during init test for existing DATASTORE table

[ https://issues.apache.org/jira/browse/JCR-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12639051#action_12639051 ] Bart van der Schans commented on JCR-1366: -- I haven't confirmed this myself, but