jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chad davis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3026) davex remoting has a performance bottleneck due limit of 2 http connections
Date Tue, 19 Jul 2011 22:28:58 GMT

    [ https://issues.apache.org/jira/browse/JCR-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068022#comment-13068022

chad davis commented on JCR-3026:

I've already been testing my fixes on the 2.2.5 release.  I'm going to port them to the trunk,
and run my tests there before attaching the patch.

> davex remoting has  a performance bottleneck due limit of 2 http connections
> ----------------------------------------------------------------------------
>                 Key: JCR-3026
>                 URL: https://issues.apache.org/jira/browse/JCR-3026
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-spi2dav
>    Affects Versions: 2.2.5
>            Reporter: chad davis
>              Labels: dav, davex, performance, remoting
>             Fix For: 2.3.0
> The spi2dav service implementation use of HttpClient did not support configuration of
the maximum amount of http connections to the server.  The default value, in the HttpClient
code, is two. This was a performance bottleneck.  This work makes the number of connections
configurable via a parameter to the map passed to the repository factory.  
> It also fixes a concurrency issue which was exposed by the increased concurrency effected
by this work.  This fix is a replacement of a HashMap cache of client connections with a ConcurrentHashMap,
thanks to the java 1.5 available in Jackrabbit 2.x 

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


View raw message