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

Posted to dev@tapestry.apache.org by "Marcus Schulte (JIRA)" <de...@tapestry.apache.org> on 2008/03/30 19:05:24 UTC

[jira] Resolved: (TAPESTRY-1436) Ability to configure the number of threads used by GenericPool

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

Marcus Schulte resolved TAPESTRY-1436.
--------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 4.1.6)
                   4.1.5
         Assignee: Marcus Schulte

Should be unnecessary by now. Commons-pool uses only one thread in its current version. Apart from that, TAPESTRY-2071 did away with a lot of unnecessary pool-instances

> Ability to configure the number of threads used by GenericPool
> --------------------------------------------------------------
>
>                 Key: TAPESTRY-1436
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1436
>             Project: Tapestry
>          Issue Type: New Feature
>    Affects Versions: 4.1.2
>            Reporter: Lionel Touati
>            Assignee: Marcus Schulte
>             Fix For: 4.1.5
>
>
> Tapestry spawns a big number of threads because of commons pools. 
> It'd be nice to be configurable in production

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org