You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2006/09/18 03:00:22 UTC

[jira] Closed: (DIRMINA-178) ThreadPoolFilter.minimumPoolSize

     [ http://issues.apache.org/jira/browse/DIRMINA-178?page=all ]

Trustin Lee closed DIRMINA-178.
-------------------------------


> ThreadPoolFilter.minimumPoolSize
> --------------------------------
>
>                 Key: DIRMINA-178
>                 URL: http://issues.apache.org/jira/browse/DIRMINA-178
>             Project: Directory MINA
>          Issue Type: Improvement
>            Reporter: Trustin Lee
>
> Greg Duffy <gd...@gmail.com> wrote:
> Would it be possible/prudent to allow a minimum thread pool size in the TheadPoolFilter? After periods of inactivity I notice a small bit of latency when new threads are being created, and it'd be nice to have some control over it. My "clients" (actually automated processes) are impatient and tend to retransmit if I don't send something back quickly enough (and I need to do it in a separate connection, which means more latency if I'm using different ThreadPoolFilter(s) for that). For my purposes, retransmits are not fatal, but it would be nice to avoid them nonetheless.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira