jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-929) Under Heavy load in a Cluster HTTP Threads Block and stall requests
Date Wed, 06 Jun 2007 09:26:26 GMT

     [ https://issues.apache.org/jira/browse/JCR-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dominique Pfister updated JCR-929:

    Attachment: patch.544769

Hi Ian,

I implemented your changes, introducing a new interface ClusterOperation that hides the details
of locking (unlocking) the journal before (after) some cluster operation starts (ends), which
will be useful for nodetype/namespace operations as well. I've attached a patch file that
should be directly applied to the jackrabbit 1.3 sources (patch -p0 < patch.544769) and
I'd be grateful if you could test whether this patch resolves this issue.

Kind regards

> 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, JCR-929.patch, patch.544769
> 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.

View raw message