Hi Rama,
>> There are constructors which take ThreadFactory as parameter if the
>> default WorkerThreadImpl dont cut it.
>>
>> I have never used the TestThreadPool myself, only compiled it.
>> Comet uses the Fixed one though.
>
>
> So at the moment isn't possible to test this threadpool with
> grizzlywebserver out of the box?
> The idea was to be able to have a grizzlywebserver embedded with
> something like
> ws.getSelectorThread().setMaxThreads(40);
> ws.getSelectorthread().setthreadpool(new superthreadpool());
>
> if this is not the case, how is possible to use the work done with the
> new executor+ new thread pool?
Grizzly HTTP module expects ThreadPool to operate with the specific
Thread types.
The way how you can use the custom thread pool is following:
ws.getSelectorThread().setThreadPool(new FixedThreadPool(10, new
ThreadPoolFactory() {
public Thread newThread(Runnable r) {
Thread thread = new HttpWorkerThread(null, name, r,
initialByteBufferSize);
thread.setPriority(priority);
return thread;
});
});
Please let me know if it works for you.
WBR,
Alexey.