tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1563) Need configuration for queue size w/ ParallelExecutor; as is, limited to pool core size threads, rather than pool max size
Date Mon, 27 Jun 2011 19:05:47 GMT

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

Howard M. Lewis Ship closed TAP5-1563.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.1

> Need configuration for queue size w/ ParallelExecutor; as is, limited to pool core size
threads, rather than pool max size
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1563
>                 URL: https://issues.apache.org/jira/browse/TAP5-1563
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: documentation, tapestry-ioc
>            Reporter: Andy Blower
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.3.1
>
>
> ParallelExecutor service is bound to the number of executor threads specified by THREAD_POOL_CORE_SIZE
rather than THREAD_POOL_MAX_SIZE, which means by default only three parallel tasks are executed
at once rather than the maximum of 20. This is unexpected behaviour for someone not familiar
with the ThreadPoolExecutor design, which is not intuitive. The documentation of ParallelExecutor
is very misleading and should be expanded to explain this correctly.
> This blog post I found explains it clearly:
> http://www.bigsoft.co.uk/blog/index.php/2009/11/27/rules-of-a-threadpoolexecutor-pool-size

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

        

Mime
View raw message