Re: Urgent !!! Problem to get TOMCAT/4.1.24 cluster running withsticky session support.

2003-08-29 Thread John Turner 
A couple of things:

1.  Your workers.properties file (to me) seems needlessly complex.  I 
would cut it down to match Pascal's example.

2.  In your server.xml, you have "jmvRoute".  I don't load balance, but 
as far as I know it should be "jvmRoute" (note spelling).

3.  You only sent one server.xml...there should be two.

John

[EMAIL PROTECTED] wrote:
Hi people, I still have no any progress , I've installed the newest 
version of tomcat 4.1.27 and build mod_jk from the sources.
Still the same : all requests are sent to one tomcat , but if I shutdown 
it apache redirects the work to another one
No error messages, in mod_jk.log I see that two balanced workers were 
found.
Lots of  web links say that load-balancing work , but in reallity they all 
point to one from Pascal Forget. 

I even cannot see anything added by tomcat to my session cookie. 



There are some conf files bellow.

Any help or suggestion would be highly appreciated.

P.S. My topic is still not in tomcat-users list. So what are criterias to 
put it there?
--
Yefym 



MOD_JK.LOG

[Fri Aug 29 08:21:47 2003]  [jk_uri_worker_map.c (321)]: Into 
jk_uri_worker_map_t::uri_worker_map_open, match rule 
/ping/servlet/=loadbalancer was added
[Fri Aug 29 08:21:47 2003]  [jk_uri_worker_map.c (299)]: Into 
jk_uri_worker_map_t::uri_worker_map_open, suffix rule 
/ping/.jsp=loadbalancer was added
[Fri Aug 29 08:21:47 2003]  [jk_uri_worker_map.c (299)]: Into 
jk_uri_worker_map_t::uri_worker_map_open, suffix rule 
/ping/.do=loadbalancer was added
[Fri Aug 29 08:21:47 2003]  [jk_uri_worker_map.c (408)]: Into 
jk_uri_worker_map_t::uri_worker_map_open, there are 33 rules
[Fri Aug 29 08:21:47 2003]  [jk_uri_worker_map.c (422)]: 
jk_uri_worker_map_t::uri_worker_map_open, done
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (88)]: Into wc_open
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (222)]: Into build_worker_map, 
creating 3 workers
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (228)]: build_worker_map, 
creating worker tomcat-worker-01
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (148)]: Into wc_create_worker
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (162)]: wc_create_worker, about 
to create instance tomcat-worker-01 of ajp13
[Fri Aug 29 08:21:47 2003]  [jk_ajp13_worker.c (108)]: Into 
ajp13_worker_factory
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (171)]: wc_create_worker, about 
to validate and init tomcat-worker-01
[Fri Aug 29 08:21:47 2003]  [jk_ajp_common.c (1219)]: Into 
jk_worker_t::validate
[Fri Aug 29 08:21:47 2003]  [jk_ajp_common.c (1239)]: In 
jk_worker_t::validate for worker tomcat-worker-01 contact is 
172.31.7.20:5007
[Fri Aug 29 08:21:47 2003]  [jk_ajp_common.c (1267)]: Into 
jk_worker_t::init
[Fri Aug 29 08:21:47 2003]  [jk_ajp_common.c (1287)]: In 
jk_worker_t::init, setting socket timeout to 300
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (187)]: wc_create_worker, done
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (238)]: build_worker_map, 
removing old tomcat-worker-01 worker 
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (228)]: build_worker_map, 
creating worker tomcat-worker-02
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (148)]: Into wc_create_worker
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (162)]: wc_create_worker, about 
to create instance tomcat-worker-02 of ajp13
[Fri Aug 29 08:21:47 2003]  [jk_ajp13_worker.c (108)]: Into 
ajp13_worker_factory
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (171)]: wc_create_worker, about 
to validate and init tomcat-worker-02
[Fri Aug 29 08:21:47 2003]  [jk_ajp_common.c (1219)]: Into 
jk_worker_t::validate
[Fri Aug 29 08:21:47 2003]  [jk_ajp_common.c (1239)]: In 
jk_worker_t::validate for worker tomcat-worker-02 contact is 
172.31.7.12:6007
[Fri Aug 29 08:21:47 2003]  [jk_ajp_common.c (1267)]: Into 
jk_worker_t::init
[Fri Aug 29 08:21:47 2003]  [jk_ajp_common.c (1287)]: In 
jk_worker_t::init, setting socket timeout to 300
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (187)]: wc_create_worker, done
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (238)]: build_worker_map, 
removing old tomcat-worker-02 worker 
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (228)]: build_worker_map, 
creating worker loadbalancer
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (148)]: Into wc_create_worker
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (162)]: wc_create_worker, about 
to create instance loadbalancer of lb
[Fri Aug 29 08:21:47 2003]  [jk_lb_worker.c (586)]: Into lb_worker_factory
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (171)]: wc_create_worker, about 
to validate and init loadbalancer
[Fri Aug 29 08:21:47 2003]  [jk_lb_worker.c (420)]: Into 
jk_worker_t::validate
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (148)]: Into wc_create_worker
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (162)]: wc_create_worker, about 
to create instance tomcat-worker-01 of ajp13
[Fri Aug 29 08:21:47 2003]  [jk_ajp13_worker.c (108)]: Into 
ajp13_worker_factory
[Fri Aug 29 08:21:47 2003]  [jk_worker.c (171)]: wc_create_worker

Re: Urgent !!! Problem to get TOMCAT/4.1.24 cluster running withsticky session support.

2003-08-28 Thread Vladyslav Kosulin 
[EMAIL PROTECTED] wrote:

Hi , some additional information .
I've got with mozilla LiveHTTPHeaders that my session cookie doesn't recieve Jvmroute parameter , so apache 
doesn't know anything about load-balancing . 
Cookie: JSESSIONID=5387242C819757A9BC12B2FAF1AF2AD8; 

Does anybody have any suggestion or idea?
Is your web application ?
I don't know how Tomcat handles this, but Jetty does not attach jvmRoute for 
distributable applications assuming that sticky sessions are meaningless in this 
case.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Urgent !!! Problem to get TOMCAT/4.1.24 cluster running withsticky session support.

2003-08-27 Thread Vladyslav Kosulin 
[EMAIL PROTECTED] wrote:
Hi guys here is detail description:
I have Apache/2.0.45 running on the server A 
If your Apache is running on UNIX/Linux/BSD/MacOS X, load balancing with sticky 
sessions will work only if you use worker MPM. At least this is correct for 
mod_jk2, and may be the same is the cause for mod_jk.
By default Apache is been compiled with prefork MPM on UNIX/Linux/BSD.
Check with
   httpd -l
If you see prefork.c, you have to recompile Apache using
./configure --with-mpm=worker ...

Hope this will help.

Vlad

And two tomcat workers are running on B and C
The problem is that I cannot get Tomcat cluster load 
balanced , playing around with workers.properties on 
Apache gave me two different situations.
1.if I have local_worker parameter equal to 1, then 
I have no lost sessions but also no loadbalancing . But 
cluster is still fail safe, if one tomcat dies - another 
one gets all incoming requests. 
2. if I have local_worker=0 then I have a simple round- 
robin balancer without session affinity. So my session got lost. 

configuration example workers.properties: 
worker.list=tomcat-worker-01,tomcat-worker-02,router 
worker.tomcat-worker-02.port=4007
worker.tomcat-worker-02.host=xxx.xx.x.12
worker.tomcat-worker-02.type=ajp13
worker.tomcat-worker-02.lbfactor=50
worker.tomcat-worker-02.cachesize=10
worker.tomcat-worker-02.cache_timeout=600
worker.tomcat-worker-02.socket_timeout=300
worker.tomcat-worker-02.local_worker=1
worker.tomcat-worker-01.port=5007
worker.tomcat-worker-01.host=xxx.xx.x.20
worker.tomcat-worker-01.type=ajp13
worker.tomcat-worker-01.lbfactor=50
worker.tomcat-worker-01.cachesize=10
worker.tomcat-worker-01.cache_timeout=600
worker.tomcat-worker-01.socket_timeout=300
worker.tomcat-worker-01.local_worker=1
worker.router.type=lb
worker.router.balanced_workers=tomcat-worker-01,tomcat-worker-02
worker.router.sticky_session =1
worker.router.local_worker_only=1

P.S. I checked the previous discussions related to server.xmlS 
configuration.
I had there:
 
 
--
Yefym Dmukh 
developer
email: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]