[jira] Commented: (JCR-863) Patch to use FileLock for locking instead of empty file

[ https://issues.apache.org/jira/browse/JCR-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499269 ] Michael Neale commented on JCR-863: --- I agree with Marcel. This is getting really nasty if we want to support from 1.4

[jira] Updated: (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:all-tabpanel ] Ian Boston updated JCR-929: --- Attachment: catalina.out.node2.txt catalina.out.node1.txt 2 Log files, node 1 has locked up, It

[jira] Resolved: (JCR-947) XMLReader logs fatal error to system out

[ https://issues.apache.org/jira/browse/JCR-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-947. -- Resolution: Fixed Fixed in revision: 541737 > XMLReader logs fatal error to system out >

Re: jackrabbit-core maven build failure

Julian Reschke wrote: Marcel Reutegger wrote: no, you don't. this is a somewhat expected result. one of the tests tries to parse malformed XML and checks if an exception is thrown. one side effect using java 1.5 is the fatal error that is logged to system out by the parser itself. jackrabbit c

[jira] Created: (JCR-947) XMLReader logs fatal error to system out

XMLReader logs fatal error to system out Key: JCR-947 URL: https://issues.apache.org/jira/browse/JCR-947 Project: Jackrabbit Issue Type: Improvement Components: JCR TCK Affects Versions:

[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_12499181 ] Ian Boston commented on JCR-929: I am seeing some collisions on the revision numbers. Which causes the local cache to

[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_12499138 ] Ian Boston commented on JCR-929: The thread that is in the Abstract Journal aquired a lock in the LockManagerImpl at

[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_12499128 ] Ian Boston commented on JCR-929: Doing that causes the ClusterNode thread to timeout but the 2 http threads go into wai

[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_12499122 ] Ian Boston commented on JCR-929: Im not certain about this, but I think the aquire in te sync from the ClusterNode sh

[jira] Commented: (JCR-863) Patch to use FileLock for locking instead of empty file

[ https://issues.apache.org/jira/browse/JCR-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499112 ] Marcel Reutegger commented on JCR-863: -- > Also, I remember hearing some talk about this being done entirely in Luce

[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_12499116 ] Ian Boston commented on JCR-929: There is a stack trace of a node locked in waiting, the HTTP are locked and every req

[jira] Resolved: (JCR-946) Create a sample search page

[ https://issues.apache.org/jira/browse/JCR-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-946. -- Resolution: Fixed Fix Version/s: 1.4 Committed in revision: 541664 There's now a link on t

[jira] Created: (JCR-946) Create a sample search page

Create a sample search page --- Key: JCR-946 URL: https://issues.apache.org/jira/browse/JCR-946 Project: Jackrabbit Issue Type: New Feature Components: webapp Reporter: Marcel Reutegger

[jira] Resolved: (JCR-933) RepositoryImpl.acquireRepositoryLock() fails to detect that the file lock is already held by the current process

[ https://issues.apache.org/jira/browse/JCR-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Guggisberg resolved JCR-933. --- Resolution: Fixed fixed in svn r541651 by applying jukka's patch > RepositoryImpl.acquireRepos

[jira] Resolved: (JCR-945) Use correct version number in repository descriptor

[ https://issues.apache.org/jira/browse/JCR-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-945. -- Resolution: Fixed Fix Version/s: 1.4 Use resource filtering in jackrabbit-core and ${pom.ve

[jira] Created: (JCR-945) Use correct version number in repository descriptor

Use correct version number in repository descriptor --- Key: JCR-945 URL: https://issues.apache.org/jira/browse/JCR-945 Project: Jackrabbit Issue Type: Bug Components: core Affect

[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 no

[jira] Updated: (JCR-943) SQL Server support in clustering module

[ https://issues.apache.org/jira/browse/JCR-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-943: -- Affects Version/s: (was: 1.3) > SQL Server support in clustering module >

[jira] Resolved: (JCR-943) SQL Server support in clustering module

[ https://issues.apache.org/jira/browse/JCR-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-943. --- Committed the schema file in revision 541614. Thanks for the contribution! The commit failure was caused by

[jira] Updated: (JCR-943) SQL Server support in clustering module

[ https://issues.apache.org/jira/browse/JCR-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanta Gupta updated JCR-943: -- Attachment: mssql.ddl Attaching modified version of default.ddl which seems to work on SQL Server. > SQL

[jira] Created: (JCR-943) SQL Server support in clustering module

SQL Server support in clustering module --- Key: JCR-943 URL: https://issues.apache.org/jira/browse/JCR-943 Project: Jackrabbit Issue Type: Improvement Components: core Affects Versions: 1.3

[jira] Assigned: (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:all-tabpanel ] Dominique Pfister reassigned JCR-929: - Assignee: Dominique Pfister > Under Heavy load in a Cluster HTTP Threads Block and stall req

[jira] Resolved: (JCR-699) Clustering: re-registration of nodetypes is not synchronized

[ https://issues.apache.org/jira/browse/JCR-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister resolved JCR-699. --- Resolution: Fixed Thank you for providing your patch, Martijn! I applied it with some small mod

[jira] Assigned: (JCR-699) Clustering: re-registration of nodetypes is not synchronized

[ https://issues.apache.org/jira/browse/JCR-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister reassigned JCR-699: - Assignee: Dominique Pfister > Clustering: re-registration of nodetypes is not synchronized