[
https://issues.apache.org/jira/browse/JCR-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500059
]
Ian Boston commented on JCR-929:
--------------------------------
That appears to have fixed this problem, in the internal lock and unlock
methods I have added an effective lockAndSync if and only if the event channel
is notified of the lock or unlock which would cause a lock and sync after the
lock manager jvm lock had been aquired. So deadlocks can't happen as you
predicted.
I notice there may be some more places where this can happen.
The NodeTypeRegistry and the NameSpaceRegistry
I have some additional errors appearing when the path can't be built due to
nonexistant child nodes, leading me to believe that something might be being
dropped.
Unfortunately, I don't have net access and my blackberry won't hook up to OSX
so I can't send a patch till Saturday at the earliest. Sorry
Ian
Sent from my Pearl, sorry about the briefness and spelling!
> Under Heavy load in a Cluster HTTP Threads Block and stall requests
> -------------------------------------------------------------------
>
> Key: JCR-929
> URL: https://issues.apache.org/jira/browse/JCR-929
> Project: Jackrabbit
> Issue Type: Bug
> Components: core
> Affects Versions: 1.3
> Environment: 2 Node Cluster, OSX, JDK 1.5 with DatabaseJournal,
> DatabasePersistanceManager, all content in DB, using WebDAV to load
> Reporter: Ian Boston
> Assignee: Dominique Pfister
> Attachments: catalina.out.node1.txt, catalina.out.node2.txt
>
>
> Under Heavy load created by mounting both nodes in the cluster in OSX Finder
> and then uploading large numebers of files to each node at the same time ( a
> few 1000), eventually one of the nodes stops responding and the Finder mount
> timesout and disconnects.
> Once that happens that node becomes unusable.
> More mount attempts will prompt for a password indicating HTTP is still
> running, but will timeout once the connection is authenticated.
> Access by the Web Browser will prompt for a password, conenct and provide a
> once only listing of any collection in the workspace. If you try to refresh
> that collection, the HTTP request hangs forever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
