[jira] [Commented] (JCR-3537) Large number of SQL queries when adding nodes with version history

[ https://issues.apache.org/jira/browse/JCR-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13612507#comment-13612507 ] Marcel Reutegger commented on JCR-3537: --- bq. collection has 100's of items It's a bit

[jira] [Commented] (JCR-3537) Large number of SQL queries when adding nodes with version history

[ https://issues.apache.org/jira/browse/JCR-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13608774#comment-13608774 ] Marcel Reutegger commented on JCR-3537: --- The versioning behavior is defined by the

[jira] [Assigned] (JCR-3531) Borrow all available RepositoryHelpers

[ https://issues.apache.org/jira/browse/JCR-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned JCR-3531: - Assignee: Marcel Reutegger Borrow all available RepositoryHelpers

[jira] [Updated] (JCR-3495) Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout()

[ https://issues.apache.org/jira/browse/JCR-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3495: -- Resolution: Fixed Fix Version/s: 2.7 Status: Resolved (was: Patch Available)

[jira] [Resolved] (JCR-3519) Disable IOCounters based on log level

[ https://issues.apache.org/jira/browse/JCR-3519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3519. --- Resolution: Fixed Fix Version/s: 2.7 Implemented in revision: 1445134

[jira] [Created] (JCR-3519) Disable IOCounters based on log level

Marcel Reutegger created JCR-3519: - Summary: Disable IOCounters based on log level Key: JCR-3519 URL: https://issues.apache.org/jira/browse/JCR-3519 Project: Jackrabbit Content Repository

[jira] [Commented] (JCR-3509) Workspace maxIdleTime parameter not working

[ https://issues.apache.org/jira/browse/JCR-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13567622#comment-13567622 ] Marcel Reutegger commented on JCR-3509: --- Can you please provide a test class, which is

[jira] [Commented] (JCR-3509) Workspace maxIdleTime parameter not working

[ https://issues.apache.org/jira/browse/JCR-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13567663#comment-13567663 ] Marcel Reutegger commented on JCR-3509: --- Can be anything, TestNG, JUnit, ... as long

[jira] [Resolved] (JCR-3496) no search manager configured for this workspace

[ https://issues.apache.org/jira/browse/JCR-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3496. --- Resolution: Invalid Please do not use the issue tracker for general questions, use the users@

[jira] [Created] (JCR-3495) Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout()

Marcel Reutegger created JCR-3495: - Summary: Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout() Key: JCR-3495 URL: https://issues.apache.org/jira/browse/JCR-3495 Project:

[jira] [Updated] (JCR-3495) Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout()

[ https://issues.apache.org/jira/browse/JCR-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3495: -- Attachment: JCR-3495.patch Proposed changes. Unregister from PrivilegeRegistry

[jira] [Updated] (JCR-3495) Unregister from PrivilegeRegistry and NodeTypeRegistry on Session.logout()

[ https://issues.apache.org/jira/browse/JCR-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3495: -- Status: Patch Available (was: Open) Unregister from PrivilegeRegistry and NodeTypeRegistry

[jira] [Commented] (JCR-3402) getSize() returning too many often -1

[ https://issues.apache.org/jira/browse/JCR-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559700#comment-13559700 ] Marcel Reutegger commented on JCR-3402: --- Can you please update the patch with all the

[jira] [Updated] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3469: -- Fix Version/s: 2.4.4 Merged into 2.4 branch in revision: 1429838 Thread

[jira] [Created] (JCR-3482) SetValueVersionExceptionTest makes assumption about implementation

Marcel Reutegger created JCR-3482: - Summary: SetValueVersionExceptionTest makes assumption about implementation Key: JCR-3482 URL: https://issues.apache.org/jira/browse/JCR-3482 Project: Jackrabbit

[jira] [Resolved] (JCR-3482) SetValueVersionExceptionTest makes assumption about implementation

[ https://issues.apache.org/jira/browse/JCR-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3482. --- Resolution: Fixed Fixed in revision: 1420601 SetValueVersionExceptionTest

[jira] [Commented] (JCR-3481) NullPointerException in DescendantSelfAxisScorer#nextDoc

[ https://issues.apache.org/jira/browse/JCR-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13528919#comment-13528919 ] Marcel Reutegger commented on JCR-3481: --- bq. Any ideas on what could cause this?

[jira] [Commented] (JCR-3477) Lazy query result sets

[ https://issues.apache.org/jira/browse/JCR-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510422#comment-13510422 ] Marcel Reutegger commented on JCR-3477: --- IIRC, these kind of queries are special cased

[jira] [Resolved] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3469. --- Resolution: Fixed I'm able to reproduce this on Solaris 11.1 (x86). In contrast to NIO, the

[jira] [Commented] (JCR-3477) Lazy query result sets

[ https://issues.apache.org/jira/browse/JCR-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510340#comment-13510340 ] Marcel Reutegger commented on JCR-3477: --- At least my expectation is that Jackrabbit

[jira] [Reopened] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reopened JCR-3469: --- Assignee: Marcel Reutegger Test fails on Apache Jenkins. Thread interrupt

[jira] [Commented] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13508608#comment-13508608 ] Marcel Reutegger commented on JCR-3469: --- Disabled test for now in revision: 1416387

[jira] [Commented] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13508652#comment-13508652 ] Marcel Reutegger commented on JCR-3469: --- Looks like this is solaris specific. More

[jira] [Commented] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506329#comment-13506329 ] Marcel Reutegger commented on JCR-3469: --- I considered extending from an abstract test

[jira] [Created] (JCR-3466) NPE in SingletonTokenStream

Marcel Reutegger created JCR-3466: - Summary: NPE in SingletonTokenStream Key: JCR-3466 URL: https://issues.apache.org/jira/browse/JCR-3466 Project: Jackrabbit Content Repository Issue Type:

[jira] [Assigned] (JCR-3466) NPE in SingletonTokenStream

[ https://issues.apache.org/jira/browse/JCR-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned JCR-3466: - Assignee: Marcel Reutegger NPE in SingletonTokenStream ---

[jira] [Commented] (JCR-3466) NPE in SingletonTokenStream

[ https://issues.apache.org/jira/browse/JCR-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505328#comment-13505328 ] Marcel Reutegger commented on JCR-3466: --- This is what happens: - a thread triggers

[jira] [Resolved] (JCR-3466) NPE in SingletonTokenStream

[ https://issues.apache.org/jira/browse/JCR-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3466. --- Resolution: Fixed Fix Version/s: 2.5.3 Fixed in revision: 1414629 NPE

[jira] [Created] (JCR-3467) ConsistencyCheck.MissingAncestor#repair() should also log UUID

Marcel Reutegger created JCR-3467: - Summary: ConsistencyCheck.MissingAncestor#repair() should also log UUID Key: JCR-3467 URL: https://issues.apache.org/jira/browse/JCR-3467 Project: Jackrabbit

[jira] [Resolved] (JCR-3467) ConsistencyCheck.MissingAncestor#repair() should also log UUID

[ https://issues.apache.org/jira/browse/JCR-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3467. --- Resolution: Fixed Fix Version/s: 2.5.3 Implemented in revision: 1414632

[jira] [Created] (JCR-3469) Thread interrupt may result in closed index files

Marcel Reutegger created JCR-3469: - Summary: Thread interrupt may result in closed index files Key: JCR-3469 URL: https://issues.apache.org/jira/browse/JCR-3469 Project: Jackrabbit Content Repository

[jira] [Updated] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3469: -- Attachment: JCR-3469-test.patch Attached patch contains a test reproducing the issue.

[jira] [Updated] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3469: -- Attachment: JCR-3469.patch This patch adds a parameter to the SearchIndex and allows you to

[jira] [Commented] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505577#comment-13505577 ] Marcel Reutegger commented on JCR-3469: --- Please note the test will only fail on

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

[ https://issues.apache.org/jira/browse/JCR-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505624#comment-13505624 ] Marcel Reutegger commented on JCR-3463: --- In my experience twice the syncDelay (10

[jira] [Updated] (JCR-3469) Thread interrupt may result in closed index files

[ https://issues.apache.org/jira/browse/JCR-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3469: -- Attachment: JCR-3469.patch Good point. Thanks for the suggestion. Attached patch now contains

[jira] [Reopened] (JCR-3389) Implement a MultiDataStore

[ https://issues.apache.org/jira/browse/JCR-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reopened JCR-3389: --- Claus, I noticed that your changes use tabs instead of spaces for indentation. Can you please fix

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

[ https://issues.apache.org/jira/browse/JCR-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3463: -- Attachment: JCR-3463.patch Proposed changes: - introduce a stopDelay in the Cluster

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

[ https://issues.apache.org/jira/browse/JCR-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3463. --- Resolution: Fixed Fix Version/s: 2.5.3 Applied patch in revision: 1414093

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

Marcel Reutegger created JCR-3463: - Summary: Configurable stopDelay Key: JCR-3463 URL: https://issues.apache.org/jira/browse/JCR-3463 Project: Jackrabbit Content Repository Issue Type:

[jira] [Resolved] (JCR-3427) JCR-3138 may cause resource starvation

[ https://issues.apache.org/jira/browse/JCR-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3427. --- Resolution: Fixed Fix Version/s: 2.5.2 Committed patch in revision 1387021.

[jira] [Updated] (JCR-3427) JCR-3138 may cause resource starvation

[ https://issues.apache.org/jira/browse/JCR-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3427: -- Affects Version/s: 2.4 2.4.1 2.4.2

[jira] [Resolved] (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:all-tabpanel ] Marcel Reutegger resolved JCR-3426. --- Resolution: Fixed Fix Version/s: 2.5.2 Thanks for the review. Good point about the

[jira] [Updated] (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:all-tabpanel ] Marcel Reutegger updated JCR-3426: -- Component/s: jackrabbit-core Log warning when changes are performed with event notification

[jira] [Commented] (JCR-3428) Partial search terms are no longer highlighted in the excerpts

[ https://issues.apache.org/jira/browse/JCR-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13457706#comment-13457706 ] Marcel Reutegger commented on JCR-3428: --- I would rather do it right in trunk (with

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

Marcel Reutegger created JCR-3426: - Summary: Log warning when changes are performed with event notification thread Key: JCR-3426 URL: https://issues.apache.org/jira/browse/JCR-3426 Project:

[jira] [Created] (JCR-3427) JCR-3138 may cause resource starvation

Marcel Reutegger created JCR-3427: - Summary: JCR-3138 may cause resource starvation Key: JCR-3427 URL: https://issues.apache.org/jira/browse/JCR-3427 Project: Jackrabbit Content Repository

[jira] [Updated] (JCR-3427) JCR-3138 may cause resource starvation

[ https://issues.apache.org/jira/browse/JCR-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3427: -- Attachment: JCR-3427.patch Proposed changes. With those changes, the check for more records is

[jira] [Assigned] (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:all-tabpanel ] Marcel Reutegger reassigned JCR-3426: - Assignee: Marcel Reutegger Log warning when changes are performed with event

[jira] [Updated] (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:all-tabpanel ] Marcel Reutegger updated JCR-3426: -- Attachment: JCR-3426.patch Proposed changes. Log warning when changes are

[jira] [Updated] (JCR-3419) Overwriting Cache Entry Warnings

[ https://issues.apache.org/jira/browse/JCR-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3419: -- Resolution: Fixed Fix Version/s: 2.5.2 Status: Resolved (was: Patch Available)

[jira] [Commented] (JCR-3419) Overwriting Cache Entry Warnings

[ https://issues.apache.org/jira/browse/JCR-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449546#comment-13449546 ] Marcel Reutegger commented on JCR-3419: --- Had a chat with Stefan and he pointed out

[jira] [Commented] (JCR-3412) UserManager.findAuthorizables() does not work, if session does not have read access to /home

[ https://issues.apache.org/jira/browse/JCR-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448532#comment-13448532 ] Marcel Reutegger commented on JCR-3412: --- There was recently a discussion about adding

[jira] [Commented] (JCR-3412) UserManager.findAuthorizables() does not work, if session does not have read access to /home

[ https://issues.apache.org/jira/browse/JCR-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448600#comment-13448600 ] Marcel Reutegger commented on JCR-3412: --- You could also extend from the base class of

[jira] [Reopened] (JCR-3419) Overwriting Cache Entry Warnings

[ https://issues.apache.org/jira/browse/JCR-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reopened JCR-3419: --- Re-opening. I still see those warnings when Sessions concurrently read a property while another

[jira] [Updated] (JCR-3419) Overwriting Cache Entry Warnings

[ https://issues.apache.org/jira/browse/JCR-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3419: -- Status: Patch Available (was: Reopened) Overwriting Cache Entry Warnings

[jira] [Updated] (JCR-3419) Overwriting Cache Entry Warnings

[ https://issues.apache.org/jira/browse/JCR-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3419: -- Attachment: JCR-3419.patch Patch with a test that shows the warnings. It also contains a fix,

[jira] [Updated] (JCR-3419) Overwriting Cache Entry Warnings

[ https://issues.apache.org/jira/browse/JCR-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3419: -- Fix Version/s: (was: 2.5.2) Overwriting Cache Entry Warnings

[jira] [Assigned] (JCR-3419) Overwriting Cache Entry Warnings

[ https://issues.apache.org/jira/browse/JCR-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned JCR-3419: - Assignee: Marcel Reutegger Overwriting Cache Entry Warnings

[jira] [Created] (JCR-3419) Overwriting Cache Entry Warnings

Marcel Reutegger created JCR-3419: - Summary: Overwriting Cache Entry Warnings Key: JCR-3419 URL: https://issues.apache.org/jira/browse/JCR-3419 Project: Jackrabbit Content Repository Issue

[jira] [Resolved] (JCR-3419) Overwriting Cache Entry Warnings

[ https://issues.apache.org/jira/browse/JCR-3419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3419. --- Resolution: Fixed Fixed in revision: 1380499 Overwriting Cache Entry

[jira] [Updated] (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:all-tabpanel ] Marcel Reutegger updated JCR-3406: -- Fix Version/s: (was: 2.6) 2.5.2 Journal doUnlock sometimes not

[jira] [Resolved] (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:all-tabpanel ] Marcel Reutegger resolved JCR-3406. --- Resolution: Fixed Fixed in revision: 1378878 Journal doUnlock sometimes not

[jira] [Created] (OAK-289) Remove TreeImpl.Children

Marcel Reutegger created OAK-289: Summary: Remove TreeImpl.Children Key: OAK-289 URL: https://issues.apache.org/jira/browse/OAK-289 Project: Jackrabbit Oak Issue Type: Improvement

[jira] [Commented] (OAK-289) Remove TreeImpl.Children

[ https://issues.apache.org/jira/browse/OAK-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13444942#comment-13444942 ] Marcel Reutegger commented on OAK-289: -- See also discussion on oak-dev:

[jira] [Updated] (OAK-289) Remove TreeImpl.Children

[ https://issues.apache.org/jira/browse/OAK-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-289: - Attachment: OAK-289.patch Proposed simplification. Remove TreeImpl.Children

[jira] [Resolved] (OAK-282) Use random port in oak-run tests

[ https://issues.apache.org/jira/browse/OAK-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-282. -- Resolution: Fixed Fix Version/s: 0.5 Applied patch in revision: 1378923

[jira] [Resolved] (OAK-289) Remove TreeImpl.Children

[ https://issues.apache.org/jira/browse/OAK-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved OAK-289. -- Resolution: Fixed Fix Version/s: 0.5 Applied patch in revision: 1378944

[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=13444162#comment-13444162 ] Marcel Reutegger commented on JCR-3406: --- This change produces warnings on startup. It

[jira] [Comment Edited] (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=13444162#comment-13444162 ] Marcel Reutegger edited comment on JCR-3406 at 8/30/12 3:23 AM:

[jira] [Reopened] (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:all-tabpanel ] Marcel Reutegger reopened JCR-3406: --- Journal doUnlock sometimes not called on repository shutdown

[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=13443004#comment-13443004 ] Marcel Reutegger commented on JCR-3417: --- The exception is not logged in the core, but

[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=13443005#comment-13443005 ] Marcel Reutegger commented on JCR-3417: --- What we could do is reuse the existing

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

[ https://issues.apache.org/jira/browse/JCR-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3417: -- Resolution: Fixed Fix Version/s: 2.5.2 Status: Resolved (was: Patch Available)

[jira] [Updated] (OAK-282) Use random port in oak-run tests

[ https://issues.apache.org/jira/browse/OAK-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-282: - Attachment: OAK-282.patch Proposed changes. Use random port in oak-run tests

[jira] [Created] (OAK-284) Reduce memory usage of KernelNodeState

Marcel Reutegger created OAK-284: Summary: Reduce memory usage of KernelNodeState Key: OAK-284 URL: https://issues.apache.org/jira/browse/OAK-284 Project: Jackrabbit Oak Issue Type:

[jira] [Updated] (OAK-284) Reduce memory usage of KernelNodeState

[ https://issues.apache.org/jira/browse/OAK-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-284: - Attachment: OAK-284.patch Proposed change Reduce memory usage of KernelNodeState

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

Marcel Reutegger created JCR-3417: - Summary: Failed Journal lock not propagated Key: JCR-3417 URL: https://issues.apache.org/jira/browse/JCR-3417 Project: Jackrabbit Content Repository Issue

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

[ https://issues.apache.org/jira/browse/JCR-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reassigned JCR-3417: - Assignee: Marcel Reutegger Failed Journal lock not propagated

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

[ https://issues.apache.org/jira/browse/JCR-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3417: -- Attachment: JCR-3417.patch Proposed patch. Failed Journal lock not propagated

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

[ https://issues.apache.org/jira/browse/JCR-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3417: -- Status: Patch Available (was: Open) Failed Journal lock not propagated

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

[ https://issues.apache.org/jira/browse/JCR-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3417: -- Component/s: jackrabbit-core Failed Journal lock not propagated

[jira] [Resolved] (JCR-3413) Query with CONTAINS OR LIKE expression returns malformed result

[ https://issues.apache.org/jira/browse/JCR-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3413. --- Resolution: Won't Fix This kind of query with a jcr:path ORed together with the rest of

[jira] [Commented] (JCR-2950) CachingEntryCollector ineffective if number of accessed policies exceeds cache size

[ https://issues.apache.org/jira/browse/JCR-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409821#comment-13409821 ] Marcel Reutegger commented on JCR-2950: --- Tested the patch with the pool of system

[jira] [Commented] (JCR-2950) CachingEntryCollector ineffective if number of accessed policies exceeds cache size

[ https://issues.apache.org/jira/browse/JCR-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409824#comment-13409824 ] Marcel Reutegger commented on JCR-2950: --- Forgot to mention the 2.4 best case benchmark

[jira] [Updated] (JCR-3242) Update to Lucene 3.6

[ https://issues.apache.org/jira/browse/JCR-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3242: -- Summary: Update to Lucene 3.6 (was: Update to Lucene 3.5) Update to Lucene 3.6

[jira] [Updated] (JCR-3242) Update to Lucene 3.6

[ https://issues.apache.org/jira/browse/JCR-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3242: -- Attachment: JCR-3242.patch I reviewed the patch and looked at why the tests fail in the second

[jira] [Updated] (JCR-3374) Size estimate for AbstractBundlePersistenceManager.MISSING is too low

[ https://issues.apache.org/jira/browse/JCR-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3374: -- Resolution: Fixed Fix Version/s: 2.5.1 Status: Resolved (was: Patch Available)

[jira] [Updated] (JCR-3242) Update to Lucene 3.6

[ https://issues.apache.org/jira/browse/JCR-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3242: -- Attachment: JCR-3242.patch Updated patch, without the changes from JCR-3337.

[jira] [Updated] (JCR-3339) Log stack trace with warn message in ObservationDispatcher

[ https://issues.apache.org/jira/browse/JCR-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3339: -- Fix Version/s: 2.2.13 Merged into 2.2 branch in revision: 1357125 Log stack

[jira] [Created] (JCR-3374) Size estimate for AbstractBundlePersistenceManager.MISSING is too low

Marcel Reutegger created JCR-3374: - Summary: Size estimate for AbstractBundlePersistenceManager.MISSING is too low Key: JCR-3374 URL: https://issues.apache.org/jira/browse/JCR-3374 Project:

[jira] [Updated] (JCR-3374) Size estimate for AbstractBundlePersistenceManager.MISSING is too low

[ https://issues.apache.org/jira/browse/JCR-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3374: -- Attachment: JCR-3374.patch Proposed patch. Size estimate for

[jira] [Updated] (JCR-3374) Size estimate for AbstractBundlePersistenceManager.MISSING is too low

[ https://issues.apache.org/jira/browse/JCR-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3374: -- Status: Patch Available (was: Open) Size estimate for

[jira] [Resolved] (JCR-3345) ACL evaluation may return non-fresh results

[ https://issues.apache.org/jira/browse/JCR-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3345. --- Resolution: Fixed Fix Version/s: 2.5.1 Applied most recent patch in revision: 1357265

[jira] [Updated] (JCR-3337) Negated descendant node query with no results throws NPE

[ https://issues.apache.org/jira/browse/JCR-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3337: -- Fix Version/s: (was: 2.6) 2.5.1 Next release will be 2.5.1

[jira] [Reopened] (JCR-3337) Negated descendant node query with no results throws NPE

[ https://issues.apache.org/jira/browse/JCR-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger reopened JCR-3337: --- Hmm, to me it looks like the new test is wrong. The query is: SELECT a.* FROM [nt:base] as a

[jira] [Updated] (JCR-3337) Negated descendant node query with no results throws NPE

[ https://issues.apache.org/jira/browse/JCR-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3337: -- Attachment: JCR-3337.patch Proposed fix. Negated descendant node query with no

[jira] [Updated] (JCR-3337) Negated descendant node query with no results throws NPE

[ https://issues.apache.org/jira/browse/JCR-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated JCR-3337: -- Status: Patch Available (was: Reopened) Negated descendant node query with no results

[jira] [Commented] (JCR-3369) Garbage collector improvements

[ https://issues.apache.org/jira/browse/JCR-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13405699#comment-13405699 ] Marcel Reutegger commented on JCR-3369: --- +1 patch looks good. Applied it in revision:

[jira] [Commented] (JCR-3369) Garbage collector improvements

[ https://issues.apache.org/jira/browse/JCR-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13405708#comment-13405708 ] Marcel Reutegger commented on JCR-3369: --- One thing I noticed in the logs: the session

<    1   2   3   4   5   6   7   8   9   10   >