Oh, I am very sorry for misunderstanding.
You are partly right.
Thanks!
--
Bongjae Chang
----- Original Message -----
From: "Minoru Nitta" <minoru.nitta_at_jp.fujitsu.com>
To: <dev_at_grizzly.dev.java.net>
Sent: Friday, May 15, 2009 4:15 PM
Subject: Re: DefaultThreadPool
> Hi Bongjae
>
>
> Thank you for your response.
>
>> Hi Minoru,
>>
>> I don't think that, because some test cases or modules are using "new DefaultThreadPool()" and setting it with "controller.setThreadPool()".
>>
>> e.g. RoundRobinSelectorHandlerTest.java
>
>
> I meant DefaultThreadPool constructor with parameters, not default constructor
> (no parameter). I meant,
>
> public DefaultThreadPool(int corePoolSize, int maximumPoolSize,
> int maxTasksCount, long keepAliveTime, TimeUnit unit)
>
> should be something like
>
> public DefaultThreadPool(int maxTasksCount, long keepAliveTime, TimeUnit unit)
>
>
>
>> So, I think that it is still needed.
>>
>> Thanks.
>> --
>> Bongjae Chang
>>
>>
>> ----- Original Message -----
>> From: "Minoru Nitta" <minoru.nitta_at_jp.fujitsu.com>
>> To: <dev_at_grizzly.dev.java.net>
>> Sent: Friday, May 15, 2009 3:52 PM
>> Subject: DefaultThreadPool
>>
>>
>> > Salut,
>> >
>> >
>> > Now thread pool size is automatically configured in Controller class.
>> > So maximum pool size and core pool size parameters of DefaultThreadPool
>> > conctructor are actually ignored. These parameters should be removed
>> > from the constructor. What do you think?
>> >
>> >
>> > Minoru
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> > For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>> >
>> >
>> >
>> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
>
>
>