You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "chad davis (JIRA)" <ji...@apache.org> on 2011/07/20 00:37:01 UTC

[jira] [Updated] (JCR-3027) JCR Server has concurrency issues on JcrWebdavServer.SessionCache internal HashMap caches

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

chad davis updated JCR-3027:
----------------------------


My fixes were done on 2.2.5.  In the next couple of days I'll port my work to the trunk and attach the patches to this ticket. 

> 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
>    Affects Versions: 2.2.5
>            Reporter: chad davis
>              Labels: dav, davex, performance, remote
>             Fix For: 2.3.0
>
>
> 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 better.  

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