jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3027) JCR Server has concurrency issues on JcrWebdavServer.SessionCache internal HashMap caches
Date Wed, 27 Jul 2011 09:33:09 GMT

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

angela updated JCR-3027:

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

applied slightly modified patch.

running the tests i noticed however the following warning:

10:30:57.694 WARN  [14745440@qtp-1360221-0] SessionState.java:236 Attempt to close session-admin-45364
while another thread is concurrently accessing this session. Blocking until the other thread
is finished using this session. Please review your code to avoid concurrent use of a session.

i will open a new issue for that.

> JCR Server has concurrency issues on JcrWebdavServer.SessionCache internal HashMap caches
> -----------------------------------------------------------------------------------------
>                 Key: JCR-3027
>                 URL: https://issues.apache.org/jira/browse/JCR-3027
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jcr-server, jackrabbit-webapp
>    Affects Versions: 2.2.5
>            Reporter: chad davis
>            Assignee: angela
>              Labels: dav, davex, performance, remote
>             Fix For: 2.3.0
>         Attachments: JCR-3027_JCRWebdavServer.java.patch, JCR-3027_JCRWebdavServerServlet.java.patch,
> After doing the davex remoting performance work outlined in JCR-3026, the increased concurrency
on my jcr server exposed a lot of errors related to getting and putting from the JcrWebdavServer.SessionCache's
internal HashMap's.  This problem with HashMap's is a well known concurrency error and was
easily fixed by upgrading these maps to ConcurrentHashMaps.  Performance seems dramatically
> The fix includes exposure of a tuning parameter that allows the user to set the expected
concurrency level.  This is the number of concurrent requests you expect the server to be
handling.  In the typical davex remoting scenario, this means you should tune this server
side value to match the total max connections of all clients pointed at the server.  See JCR-3026.

> USAGE:  Set the 'concurrency-level' init param for the JcrRemotingServlet, via the web.xml
of the jackabbit-webapp component.  Default value is 50.  Or you can intervene in a lower
level api if appropriate.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message