Sorry, Finally I got it.. I misspelled jvm_web1 with jmv_web1.
Now it works!

-----Original Message-----
From: Matteo Turra [mailto:mturra@(protected)]
Sent: mercoledì 10 gennaio 2007 17.28
To: Tomcat Users List
Subject: RE: JK 1.2.20 - Sticky session doesn't work properly

I did not. Here is my workers definition:

JkWorkerProperty worker.list=wlb, jvm_web1, jvm_web2

JkWorkerProperty worker.wlb.type=lb
JkWorkerProperty worker.wlb.balance_workers=jvm_web1, jvm_web2
JkWorkerProperty worker.wlb.sticky_session=True

JkWorkerProperty worker.jvm_web1.type=ajp13
JkWorkerProperty worker.jvm_web1.host=10.100.1.122
JkWorkerProperty worker.jvm_web1.port=10003
JkWorkerProperty worker.jvm_web1.socket_timeout=3 #in sec
JkWorkerProperty worker.jvm_web1.recycle_timeout=300
JkWorkerProperty worker.jvm_web1.reply_timeout=90000

JkWorkerProperty worker.jvm_web2.type=ajp13
JkWorkerProperty worker.jvm_web2.host=10.100.1.123
JkWorkerProperty worker.jvm_web2.port=10003
JkWorkerProperty worker.jvm_web2.socket_timeout=3 #in sec
JkWorkerProperty worker.jvm_web2.recycle_timeout=300
JkWorkerProperty worker.jvm_web2.reply_timeout=90000

web1 IP address is 10.100.1.122
web2 IP address is 10.100.1.123

on my server.xml files I have:
* jvmRoute="jvm_web1" on web1
* jvmRoute="jvm_web2" on web2

In mod_jk.log I found:

* searching worker for session route jmv_web1
* get_most_suitable_worker::jk_lb_worker.c (785): found best worker jvm_web2 (jvm_web2) using method 'Request'

It seams the ruote is properly stetted by tomcat, but the loadbalancer choose the wrong worker.

Matteo

-----Original Message-----
From: Henk Fictorie [mailto:henk.fictorie@(protected)]
Sent: mercoledì 10 gennaio 2007 16.10
To: users@(protected)
Subject: Re: JK 1.2.20 - Sticky session doesn't work properly


The session cookie is set to .....jmv_web1 while your worker is set to
jvm_web2. I guess you've go jmv and jvm mixed up.

Henk


Matteo Turra wrote:
>
> I upgraded my apache+jk+tomcat configuration with new JK connector
> 1.2.20
>
>
>
> My system is one Apache http server and two tomcat running on two
> different machines (say web1 and web2)
>
>
>
> I put sticky session in my load balancer worker (I can see it from Jk
> Status Manager page) but request jump between the two tomcat.
>
>
>
> I check jvmRoute in server.xml in both tomcat instance and they
> correspond to the workers names.
>
>
>
> I changed the jk loglevel to debug and I see the following messages:
>
>
>
> init_ws_service::mod_jk.c (584): Service protocol=HTTP/1.1 method=GET
> host=(null) addr=10.0.0.11 name=pippo port=80 auth=(null) user=(null)
> laddr=10.0.0.11 raddr=10.0.0.11
>
> service::jk_lb_worker.c (840): service sticky_session=1
> id='0D8CB99EBC3F747DA5B66183C67C8BF6.jmv_web1'
>
> get_most_suitable_worker::jk_lb_worker.c (733): searching worker for
> partial sessionid 0D8CB99EBC3F747DA5B66183C67C8BF6.jmv_web1
>
> get_most_suitable_worker::jk_lb_worker.c (741): searching worker for
> session route jmv_web1
>
> get_most_suitable_worker::jk_lb_worker.c (785): found best worker
> jvm_web2 (jvm_web2) using method 'Request'
>
> service::jk_lb_worker.c (860): service worker=jvm_web2 route=jvm_web2
>
> ajp_get_endpoint::jk_ajp_common.c (2315): acquired connection pool
> slot=0
>
> ajp_marshal_into_msgb::jk_ajp_common.c (548): ajp marshaling done
>
> ajp_service::jk_ajp_common.c (1771): processing jvm_web2 with 2 retries
>
>
>
> Does anybody knows why?
>
> __________________________________________________________
>
>  
>
> KION SpA                Matteo TURRA
>
> Via Cristoni, 84           Sviluppo Web
>
> 40033 Casalecchio di Reno (BO)
>
> Tel. +39 (051) 6111411       diretto +39 (051) 6111430
>
> Fax +39 (051) 570423
>
> http://www.kion.it <http://www.kion.it/>
> mailto:m.turra@(protected)>
>
>
>
>
>

--
Sent from the Tomcat - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)


---------------------------------------------------------------------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)


---------------------------------------------------------------------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)