dev@grizzly.java.net

Re: testing threadpool

From: Oleksiy Stashok <Oleksiy.Stashok_at_Sun.COM>
Date: Wed, 08 Apr 2009 10:11:34 +0200

Hi Rama,

>
> Right now, it will compile (using fixedthread) and work.
>
> The testthreadpool is gone (maybe renamed, but it's late here, i'll
> check tomorrow) , so i have copy the old source code to have a
> little test.
I didn't find better name than PipelineThreadPool (which has logic of
former Pipeline implementation) :)


> Seems that this doesn't work as expected.
>
> if i use
> ws.getselthread().setthread(new testthread());
>
> the thread number is limit to 5
>
> if i do a ws.setmaxthread(100)
> it spawn 100 thread immediatly even using testthread (that was
> copied from the old src)
>
> maybe i am doing something of wrong, but what i expected is
> that the testthread (not the fixed one) will spawn minthread and
> then grow up to maxthread.
>
> tomorrow i'll do some more test!
Ok, I'll check it too.

Thanks.

WBR,
Alexey.

>
>
>
>
>> Sorry, forgot to commit 2 more changes:
>> Date: 2009-04-07 17:58:58+0000
>> New Revision: 2908
>>
>> Modified:
>> trunk/code/modules/grizzly/src/main/java/com/sun/grizzly/filter/
>> ReadFilter.java
>> trunk/code/modules/http/src/main/java/com/sun/grizzly/http/
>> SelectorThread.java
>>
>> Please try it one more time.
>>
>> Thank you.
>>
>> WBR,
>> Alexey.
>>
>> On Apr 7, 2009, at 19:02 , rama wrote:
>>
>>>
>>>> Did you try it with the latest sources?
>>>>
>>>> Alexey.
>>>
>>> i have try with this snapshot
>>> grizzly-http-webserver-1.9.11-20090407.120919-28.jar
>>>
>>>
>>
>