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 02:50:22 UTC

[jira] Created: (DIRSERVER-740) Re-enable thread pool max size parameter using new MINA executor

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
            Priority: Blocker


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

        

[jira] Closed: (DIRSERVER-740) Re-enable thread pool max size parameter using new MINA executor

Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
     [ 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

        

[jira] Updated: (DIRSERVER-740) Re-enable thread pool max size parameter using new MINA executor

Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DIRSERVER-740?page=all ]

Alex Karasulu updated DIRSERVER-740:
------------------------------------

    Fix Version/s: 1.0

> 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

        

[jira] Commented: (DIRSERVER-740) Re-enable thread pool max size parameter using new MINA executor

Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/DIRSERVER-740?page=comments#action_12434335 ] 
            
Trustin Lee commented on DIRSERVER-740:
---------------------------------------

Here's the example code:

ThreadPoolExecutor executor = new ThreadPoolExecutor();
// configure the executor here
...

SocketAcceptorConfig cfg = new SocketAcceptorConfig();
...

ExecutorThreadModel threadModel = ExecutorThreadModel.getInstance("LDAP");
threadModel.setExecutor( executor );
cfg.setThreadModel( threadModel );
...

acceptor.bind(new InetSocketAddress(port), handler, cfg);

You don't need to add any ExecutorFilter by yourself.

> 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

        

[jira] Assigned: (DIRSERVER-740) Re-enable thread pool max size parameter using new MINA executor

Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/DIRSERVER-740?page=all ]

Alex Karasulu reassigned DIRSERVER-740:
---------------------------------------

    Assignee: Alex Karasulu

> 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