Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2004-03-08 Thread Kurt Miller
Could one of the more senior jtc committers review this for me please? The problem was that jk_lb_refresh was being called for each channel parsed and adding all the workers to the workersTable each time. The result was that the first channel was added to the table n+1 times (where n = total numbe

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2004-03-08 Thread ax
This account does not exist - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-04 Thread Henri Gomez
> No, but extending one dtd would be better than reinventing everything. > I will try to make a cleanup as soon as I have time. (docs need a lot of > time). I confirm ;-) BTW, any DTD will be fine but we should take a look at what others jakarta and xml projects are using. -- To unsubscrib

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-03 Thread Costin Manolache
jean-frederic clere wrote: >> :-) Sorry about 'horrible'. >> >> What I meant is - the elements like and almost everything >> else have an identical meaning as the standard XHTML or docbook element. >> It's a mix of elements - to do something that is already done and >> standard and accepted. >

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-03 Thread jean-frederic clere
Costin Manolache wrote: > jean-frederic clere wrote: > > >>Costin Manolache wrote: >> >>>Mladen Turk wrote: >>> >>> >>> >-Original Message- >On Behalf Of Costin Manolache > >Are we documenting all those settings - and the details on >why/how :-) ? > > >>>

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-03 Thread Costin Manolache
jean-frederic clere wrote: > Costin Manolache wrote: >> Mladen Turk wrote: >> >> >>> -Original Message- On Behalf Of Costin Manolache Are we documenting all those settings - and the details on why/how :-) ? >>> >>>Sure, like everyone else ;). >> >> >> Ye

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-03 Thread jean-frederic clere
Costin Manolache wrote: > Mladen Turk wrote: > > >> >>>-Original Message- >>>On Behalf Of Costin Manolache >>> >>>Are we documenting all those settings - and the details on >>>why/how :-) ? >>> >>> >> >>Sure, like everyone else ;). > > > Yes, I know :-) > > I'll try to get over the ho

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-02 Thread Mladen Turk
> -Original Message- > > > > Sure, like everyone else ;). > > Yes, I know :-) > > I'll try to get over the horrible and nonstandard DTD that we > use and start documenting what I can still remember, and > anything new that I add. And I won't write any new jk code > until I finish a

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-02 Thread Costin Manolache
Mladen Turk wrote: > > >> -Original Message- >> On Behalf Of Costin Manolache >> >> Are we documenting all those settings - and the details on >> why/how :-) ? >> >> > > Sure, like everyone else ;). Yes, I know :-) I'll try to get over the horrible and nonstandard DTD that we use

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-02 Thread Mladen Turk
> -Original Message- > On Behalf Of Costin Manolache > > Are we documenting all those settings - and the details on > why/how :-) ? > > Sure, like everyone else ;). MT. -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-02 Thread Costin Manolache
Are we documenting all those settings - and the details on why/how :-) ? Mladen Turk wrote: > > It is disabled by default and never checked (if you don't set the > timeout=x inside the [lb]). > > >> I there any way to disable completely that timeout? >> >> Perhaps setting it to -1 or somet

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-02 Thread Mladen Turk
It is disabled by default and never checked (if you don't set the timeout=x inside the [lb]). > I there any way to disable completely that timeout? > > Perhaps setting it to -1 or something like that? > > This timeout disabled should be the default config.. > -- To unsubscribe, e-mail:

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-02 Thread Ignacio J. Ortega
> De: Mladen Turk [mailto:[EMAIL PROTECTED]] > Enviado el: 2 de octubre de 2002 17:50 I there any way to disable completely that timeout? Perhaps setting it to -1 or something like that? This timeout disabled should be the default config.. Saludos , Ignacio J. Ortega -- To unsubscribe, e-mai

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-10-02 Thread Mladen Turk
> -Original Message- > From: [EMAIL PROTECTED] > Modified:jk/native2/common jk_worker_lb.c > Log: > Introduced 3 new configuration parameters to the lb. > 1. attempts -- replaces harcoded MAX_ATTEMPTS > 2. recovery -- replaces hardcoded WAIT_BEFORE_RECOVER > 3. timeout

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-15 Thread Bernd Koecke
[EMAIL PROTECTED] wrote: > On Tue, 14 May 2002, Bernd Koecke wrote: > > >>Hi Costin, >> >>the new patch seems to work, but I'll test it more exactly tomorrow. Then I'll >>create the patches and the functional description. >> >>In short, the patched lb_worker uses an additinal flag on the other

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-14 Thread costinm
On Tue, 14 May 2002, Bernd Koecke wrote: > Hi Costin, > > the new patch seems to work, but I'll test it more exactly tomorrow. Then I'll > create the patches and the functional description. > > In short, the patched lb_worker uses an additinal flag on the other workers (e.g > worker.ajp13.loc

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-14 Thread Bernd Koecke
[EMAIL PROTECTED] wrote: [...] > > I'll implement the same thing in jk2, but I wait your patch for jk1. > Hi Costin, the new patch seems to work, but I'll test it more exactly tomorrow. Then I'll create the patches and the functional description. In short, the patched lb_worker uses an addi

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-14 Thread Bernd Koecke
[EMAIL PROTECTED] wrote: > On Tue, 14 May 2002, Bernd Koecke wrote: > > >>The '0' as lb_value is needed to determine which are the main/local-workers. If >>we don't have this special value we need an additional config-flag with a list >>of the local/main-workers like in Mathias patch. >> >>Sho

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-13 Thread costinm
On Tue, 14 May 2002, Bernd Koecke wrote: > The '0' as lb_value is needed to determine which are the main/local-workers. If > we don't have this special value we need an additional config-flag with a list > of the local/main-workers like in Mathias patch. > > Should I add an additional config-f

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-13 Thread Bernd Koecke
GOMEZ Henri wrote: >>The '0' as lb_value is needed to determine which are the >>main/local-workers. If >>we don't have this special value we need an additional >>config-flag with a list >>of the local/main-workers like in Mathias patch. >> >>Should I add an additional config-flag (I will take

RE: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-13 Thread GOMEZ Henri
>The '0' as lb_value is needed to determine which are the >main/local-workers. If >we don't have this special value we need an additional >config-flag with a list >of the local/main-workers like in Mathias patch. > >Should I add an additional config-flag (I will take it from >Mathias patch) o

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-13 Thread Bernd Koecke
[EMAIL PROTECTED] wrote: > On Mon, 13 May 2002, Bernd Koecke wrote: > > >>Sorry, I must say it again, for my environment it is an error, if a _switched >>off_ tomcat got a request without a sessionid or with a session from another >>node. Its not necessary that this tomact-apache tandem is > >

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-13 Thread costinm
On Mon, 13 May 2002, Bernd Koecke wrote: > Sorry, I must say it again, for my environment it is an error, if a _switched > off_ tomcat got a request without a sessionid or with a session from another > node. Its not necessary that this tomact-apache tandem is In the current code ( in jk2 ), if

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-13 Thread Bernd Koecke
Mathias Herberts wrote: > [EMAIL PROTECTED] wrote: > >> costin 02/05/09 14:06:48 >> >> Modified:jk/native2/common jk_worker_lb.c Log: That's the big one. >> >> Please review ! >> >> It changes the handling of lb_value to int. I also cleaned up the logic so >> it's easier ( I hop

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-10 Thread costinm
Hi Mathias, Thanks for the review. Few comments: > Configure all Apache instances so they see all Tomcat instances, assign > a higher priority to local workers on each Apache, therefore local What you set is the 'level' ( or proximity, distance, etc ) - lower numbers mean closer ( and higher

Re: cvs commit: jakarta-tomcat-connectors/jk/native2/common jk_worker_lb.c

2002-05-10 Thread Mathias Herberts
[EMAIL PROTECTED] wrote: > > costin 02/05/09 14:06:48 > > Modified:jk/native2/common jk_worker_lb.c > Log: > That's the big one. > > Please review ! > > It changes the handling of lb_value to int. I also cleaned up the logic so > it's easier ( I hope ) to understand what's