You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2012/05/27 11:59:23 UTC
[jira] [Updated] (JCR-3317) Set the MaxTotalConnections on
ConnectionManager to prevent bottleneck
[ https://issues.apache.org/jira/browse/JCR-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-3317:
-------------------------------
Fix Version/s: 2.5
Merged to the 2.4 branch in revision 1343019.
> Set the MaxTotalConnections on ConnectionManager to prevent bottleneck
> ----------------------------------------------------------------------
>
> Key: JCR-3317
> URL: https://issues.apache.org/jira/browse/JCR-3317
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi2dav
> Affects Versions: 2.4.1
> Reporter: Claus Köll
> Assignee: Claus Köll
> Fix For: 2.4.2, 2.5
>
>
> The changes from JCR-3026 and JCR-3027 made it possible to configure the "org.apache.jackrabbit.spi2dav.MaxConnections". This value will be set as DefaultMaxConnectionsPerHost on the connectionParams, but it must be also be set as MaxTotalConnections (default is 20)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira