I'm not clear from the question if you're asking about the number of task
threads as Tim has explained, or the number of http listener threads, for that
use:
Server httpServer = new Server(Protocol.HTTP, port);
serviceComponent.getServers().add(httpServer);
Oh ... that's probably what the original question was asking about. I just
jumped reflexively on the phrase thread pool. Sorry...
--tim
On Thu, Jul 28, 2011 at 8:40 AM, Matt Kennedy stinkym...@gmail.com wrote:
I'm not clear from the question if you're asking about the number of task
threads
Hi,
I read several threads about this problem now (including this one) and still
can't figure out how to solve the issues (My Restlet Version is 2.0.8). May
someone point me to the relevant tutorial or show some code on how to increase
the thread pool size on the RESTlet Server?
Thanks and
You can set the pool size of the executor used by the TaskService with
org.restlet.service.TaskService.setPoolSize.
Or you can provide your own TaskService and override
createExecutorService.to return an ExecutorService tuned exactly the way you
want.
--tim
On Wed, Jul 27, 2011 at 8:14 AM,
19:15
*À :* discuss@restlet.tigris.org
*Objet :* Re: ClientResource leaves inactive thread
My earlier mail said something wrong, or at least misleading:
...defaulting coreThreads=1 and maxThreads=255 with a SynchronousQueue
seems like it's asking for trouble* with CPU count 255.*
I
: discuss@restlet.tigris.org
Objet : Re: ClientResource leaves inactive thread
My earlier mail said something wrong, or at least misleading:
...defaulting coreThreads=1 and maxThreads=255 with a SynchronousQueue seems
like it's asking for trouble with CPU count 255.
I shouldn't have
My earlier mail said something wrong, or at least misleading:
...defaulting coreThreads=1 and maxThreads=255 with a SynchronousQueue
seems like it's asking for trouble* with CPU count 255.*
I shouldn't have included that last italicized phrase with CPU count
255. The point was that
@restlet.tigris.org
Objet : Re: ClientResource leaves inactive thread
Tim Peierls wrote:
On Thu, Jun 24, 2010 at 11:52 AM, Nina Jeliazkova n...@acad.bg wrote:
Tim Peierls wrote:
What was the date of that snapshot? It looks like there's a fix as of June
11, revision 6696 in svn.
Not sure about the date
As long as you're part of the decision-making process for Restlet,
then I'm OK with it.
The caveat is that people don't always understand how to use the
configuration parameters of ThreadPoolExecutor. There was an exchange
on the concurrency-interest mailing list recently that brought this
Tim Peierls wrote:
What was the date of that snapshot? It looks like there's a fix as of
June 11, revision 6696 in svn.
Not sure about the date, it's the snapshot, available in the maven
repository,
http://maven.restlet.org/org/restlet/jee/org.restlet/2.0-SNAPSHOT/org.restlet-2.0-SNAPSHOT.pom
10 matches
Mail list logo
