tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cost...@covalent.net
Subject Re: mod_jk 1.2.0 workers pool
Date Thu, 20 Jun 2002 17:16:43 GMT
On Thu, 20 Jun 2002, Mladen Turk wrote:

> After spending with Henri two days of something that look like chasing a
> ghosts, we came up wit some ideas and would like to hear second
> opinions.
> 
> What we have now is single ajp worker that is called from multiple
> threads. Now there is almost no problems when the single client
> connection, but multiple are causing problems.
> 
> My proposal is to create a new copy of the worker if
> wc_get_worker_for_name returned worker is busy, and save that worker for
> future use.
> 
> Something like wc_get_worker_for_name returning the list of workers, or
> do that inside the wc_get_worker_for_name (IMO preferably).

+1.

I think in jk2 we should keep one worker, and make sure there is no state
( i.e. it is thread safe ). All state should be in the endpoint.

But I agree for jk1 it may be easier this way.

I'm curious what is creating the conflict - the worker is supposed to be
singleton and have the state in endpoint, and it seems to work fine in
IIS/iPlanet ( both multithreaded ).


Costin


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message