[jira] Created: (JCR-963) Failed to build path error in cluster environment

Failed to build path error in cluster environment - Key: JCR-963 URL: https://issues.apache.org/jira/browse/JCR-963 Project: Jackrabbit Issue Type: Bug Affects Versions: 1.3

[jira] Commented: (JCR-929) Under Heavy load in a Cluster HTTP Threads Block and stall requests

[ https://issues.apache.org/jira/browse/JCR-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500761 ] Xiaohua Lu commented on JCR-929: I had a similar problem but the stack trace is slight different The setup is a 4

[jira] Closed: (JCR-944) potential memory leak

[ https://issues.apache.org/jira/browse/JCR-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaohua Lu closed JCR-944. -- Resolution: Invalid potential memory leak - Key: JCR-944

[jira] Created: (JCR-944) potential memory leak

potential memory leak - Key: JCR-944 URL: https://issues.apache.org/jira/browse/JCR-944 Project: Jackrabbit Issue Type: Bug Affects Versions: 1.3 Reporter: Xiaohua Lu we are doing some stress test and

[jira] Created: (JCR-940) add db connection autoConnect for BundleDbPersistenceManager.

add db connection autoConnect for BundleDbPersistenceManager. - Key: JCR-940 URL: https://issues.apache.org/jira/browse/JCR-940 Project: Jackrabbit Issue Type: Bug

[jira] Created: (JCR-937) CacheManager max memory size

CacheManager max memory size Key: JCR-937 URL: https://issues.apache.org/jira/browse/JCR-937 Project: Jackrabbit Issue Type: Bug Affects Versions: 1.3 Reporter: Xiaohua Lu I have ran into

[jira] Created: (JCR-934) Failed to reconnect to database after network connection was dropped

Failed to reconnect to database after network connection was dropped Key: JCR-934 URL: https://issues.apache.org/jira/browse/JCR-934 Project: Jackrabbit Issue Type: Bug

[jira] Created: (JCR-931) cluster synchronization NPE

cluster synchronization NPE --- Key: JCR-931 URL: https://issues.apache.org/jira/browse/JCR-931 Project: Jackrabbit Issue Type: Bug Affects Versions: 1.3 Reporter: Xiaohua Lu we have a 4 machines

[jira] Created: (JCR-829) XPath character escape problem

XPath character escape problem -- Key: JCR-829 URL: https://issues.apache.org/jira/browse/JCR-829 Project: Jackrabbit Issue Type: Bug Affects Versions: 1.2.2 Reporter: Xiaohua Lu I created a

[jira] Updated: (JCR-792) after enabling access manager, I can't createNode and setProperty without a node.save in the middle

[ https://issues.apache.org/jira/browse/JCR-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaohua Lu updated JCR-792: --- Attachment: jaas.config ntExts.txt JackrabbitTest.java

[jira] Reopened: (JCR-792) after enabling access manager, I can't createNode and setProperty without a node.save in the middle

[ https://issues.apache.org/jira/browse/JCR-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaohua Lu reopened JCR-792: please try the provided test code. after enabling access manager, I can't createNode and setProperty without a

[jira] Created: (JCR-792) after enabling access manager, I can't createNode and setProperty without a node.save in the middle

after enabling access manager, I can't createNode and setProperty without a node.save in the middle --- Key: JCR-792 URL:

[jira] Created: (JCR-758) QueryResult's RowIterator.getSize returned the wrong size of the results after I implemented my own AccessManager

QueryResult's RowIterator.getSize returned the wrong size of the results after I implemented my own AccessManager - Key: JCR-758 URL:

[jira] Updated: (JCR-619) CacheManager (Memory Management in Jackrabbit)

[ http://issues.apache.org/jira/browse/JCR-619?page=all ] Xiaohua Lu updated JCR-619: --- Attachment: stack.txt I have been running a concurrent test on Nov. 28th code base. A deadlock has been encouterred. The setup of the test is : 1. 6000 file nodes flat

[jira] Commented: (JCR-619) CacheManager (Memory Management in Jackrabbit)

[ http://issues.apache.org/jira/browse/JCR-619?page=comments#action_12454399 ] Xiaohua Lu commented on JCR-619: I managed to reproduce the deadlock with 2 concurrent query. both query are select all category nodes. the test data is the same