You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2006/09/13 05:26:23 UTC
[jira] Closed: (DIRSERVER-740) Re-enable thread pool max size
parameter using new MINA executor
[ http://issues.apache.org/jira/browse/DIRSERVER-740?page=all ]
Alex Karasulu closed DIRSERVER-740.
-----------------------------------
Resolution: Fixed
Fixed on committed revision 442813:
http://svn.apache.org/viewvc?view=rev&revision=442813
> Re-enable thread pool max size parameter using new MINA executor
> ----------------------------------------------------------------
>
> Key: DIRSERVER-740
> URL: http://issues.apache.org/jira/browse/DIRSERVER-740
> Project: Directory ApacheDS
> Issue Type: Task
> Reporter: Alex Karasulu
> Assigned To: Alex Karasulu
> Priority: Blocker
> Fix For: 1.0
>
>
> Looks like there's no more ThreadPoolFilter in MINA and an Executor is used instead. I need to figure out from Trustin just how to set the max thread pool size now. I had to comment out some code in the ServerContextFactory on line 111 which needs to be re-enabled to allow for thread pool size configuration settings to hold.
--
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