Re: mod_jk sticky session still not working

2007-02-23 Thread Scott Danforth
P.S. I see a mention of "cluster" in the documentation for jvmRoute. Do 
I need to configure a "cluster" perhaps?


   -- Scott.


Scott Danforth wrote:


Mladen Turk wrote:


Scott Danforth wrote:

I'm trying to use jk1.2.20 mod_jk with Apache 1.3 for load balancing 
two tomcat services and sticky sessions aren't working.




You don't have session affinity mark
For each instance add jvmRoute="tomcat1" or
jvmRoute="tomcat2 for a second instance. See:
http://tomcat.apache.org/tomcat-5.5-doc/config/engine.html




Thanks for your help. That sounds very reasonable, and I modifed the 
two server.xml Engine elements as suggested, but it appears to make no 
difference.


Below are 3 segments from mod_jk.log.

The first segment shows the initial request coming in without a 
sessionid. The request is routed to tomcat1 with route=tomcat1.


The second segment shows the response coming back from tomcat1, with a 
new session id.


The third segment shows the second request coming in with the expected 
session id, and shows tomcat2 being selected with route=tomcat2.


You say I don't have session affinity mark. How would that show up in 
the log? Is the "partial sessionid" an indication of the problem?


   -- Scott.


[Fri Feb 23 09:08:53 2007] [6000:] [debug] 
map_uri_to_worker::jk_uri_worker_map.c (575): Attempting to map URI 
'/servlets/Build' from 1 maps
[Fri Feb 23 09:34:59 2007] [6266:] [debug] 
map_uri_to_worker::jk_uri_worker_map.c (587): Attempting to map 
context URI '/servlets/*=loadbalancer' source 'JkMount'
[Fri Feb 23 09:34:59 2007] [6266:] [debug] 
map_uri_to_worker::jk_uri_worker_map.c (602): Found a wildchar match 
'/servlets/*=loadbalancer'
[Fri Feb 23 09:34:59 2007] [6266:] [debug] 
wc_get_worker_for_name::jk_worker.c (114): found a worker loadbalancer
[Fri Feb 23 09:34:59 2007] [6266:] [debug] 
wc_maintain::jk_worker.c (321): Maintaining worker loadbalancer
[Fri Feb 23 09:34:59 2007] [6266:] [debug] 
wc_get_name_for_type::jk_worker.c (290): Found worker type 'lb'
[Fri Feb 23 09:34:59 2007] [6266:] [debug] 
init_ws_service::mod_jk.c (561): Service protocol=HTTP/1.1 method=GET 
host=(null) addr=192.168.1.50 name=build port=8008 auth=(null) 
user=(null) laddr=192.168.1.7 raddr=192.168.1.50
[Fri Feb 23 09:34:59 2007] [6266:] [debug] service::jk_lb_worker.c 
(840): service sticky_session=1 id='empty'
[Fri Feb 23 09:34:59 2007] [6266:] [debug] 
get_most_suitable_worker::jk_lb_worker.c (785): found best worker 
tomcat1 (tomcat1) using method 'Request'
[Fri Feb 23 09:34:59 2007] [6266:] [debug] service::jk_lb_worker.c 
(860): service worker=tomcat1 route=tomcat1


...

[Fri Feb 23 09:35:00 2007] [6266:] [debug] 
ajp_unmarshal_response::jk_ajp_common.c (603): status = 200
[Fri Feb 23 09:35:00 2007] [6266:] [debug] 
ajp_unmarshal_response::jk_ajp_common.c (610): Number of headers is = 2
[Fri Feb 23 09:35:00 2007] [6266:] [debug] 
ajp_unmarshal_response::jk_ajp_common.c (666): Header[0] [Set-Cookie] 
= [JSESSIONID=9E36E3DC58A09ED9045B25F839E37A2C; Path=/]
[Fri Feb 23 09:35:00 2007] [6266:] [debug] 
ajp_unmarshal_response::jk_ajp_common.c (666): Header[1] 
[Content-Type] = [text/html;charset=ISO-8859-1]
[Fri Feb 23 09:35:00 2007] [6266:] [debug] 
ajp_connection_tcp_get_message::jk_ajp_common.c (1029): received from 
ajp13 pos=0 len=2309 max=8192


...

[Fri Feb 23 09:35:10 2007] [6266:] [debug] 
map_uri_to_worker::jk_uri_worker_map.c (575): Attempting to map URI 
'/servlets/Build' from 1 maps
[Fri Feb 23 09:35:10 2007] [6266:] [debug] 
map_uri_to_worker::jk_uri_worker_map.c (587): Attempting to map 
context URI '/servlets/*=loadbalancer' source 'JkMount'
[Fri Feb 23 09:35:10 2007] [6266:] [debug] 
map_uri_to_worker::jk_uri_worker_map.c (602): Found a wildchar match 
'/servlets/*=loadbalancer'
[Fri Feb 23 09:35:10 2007] [6266:] [debug] 
wc_get_worker_for_name::jk_worker.c (114): found a worker loadbalancer
[Fri Feb 23 09:35:10 2007] [6266:] [debug] 
wc_get_name_for_type::jk_worker.c (290): Found worker type 'lb'
[Fri Feb 23 09:35:10 2007] [6266:] [debug] 
init_ws_service::mod_jk.c (561): Service protocol=HTTP/1.1 method=POST 
host=(null) addr=192.168.1.50 name=build port=8008 auth=(null) 
user=(null) laddr=192.168.1.7 raddr=192.168.1.50
[Fri Feb 23 09:35:10 2007] [6266:] [debug] service::jk_lb_worker.c 
(840): service sticky_session=1 id='9E36E3DC58A09ED9045B25F839E37A2C'
[Fri Feb 23 09:35:10 2007] [6266:] [debug] 
get_most_suitable_worker::jk_lb_worker.c (733): searching worker for 
partial sessionid 9E36E3DC58A09ED9045B25F839E37A2C
[Fri Feb 23 09:35:10 2007] [6266:] [debug] 
get_most_suitable_worker::jk_lb_worker.c (785): found best worker 
tomcat2 (tomcat2) using method 'Request'
[Fri Feb 23 09:35:10 2007] [6266:] [debug] service::jk_lb_worker.c 
(860): service worker=tomcat2 route=tomcat2




-
To start a new topic, e-mail: users@tomcat.apa

Re: mod_jk sticky session still not working

2007-02-23 Thread Mladen Turk

Scott Danforth wrote:

Mladen Turk wrote:


Thanks for your help. That sounds very reasonable, and I modifed the two 
server.xml Engine elements as suggested, but it appears to make no 
difference.


get_most_suitable_worker::jk_lb_worker.c (733): searching worker for 
partial sessionid 9E36E3DC58A09ED9045B25F839E37A2C


You still don't have jvmRoute appended.
Check if jvmRoute (param name is case sensitive!) is
correctly set up.
Also, if you use JBoss add true
see:
http://www.jboss.org/wiki/Wiki.jsp?page=UsingMod_jk1.2WithJBoss


Regards,
Mladen.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: mod_jk sticky session still not working

2007-02-23 Thread Scott Danforth

Hi Mladen,

I really appreciate your help, and am happy that you're seeing a problem 
in the log output.


I think I've got the Engine attributes specified correctly, and the two 
different jvmRoute values do show up in the mod_jk log.


jvmRoute="tomcat1" />
jvmRoute="tomcat2" />   

Maybe if I give the Engines different names? It sounds like we're 
expecting the jvmRoute to be appended to the sessionId that is returned 
in the Set-Cookie header? If so, I guess mod_jk is working as expected, 
and I'm just not getting the right sessionid created by Tomcat.


I'm not using Boss. Just Apache and Tomcat on a single Solaris machine.

   -- Scott.


Mladen Turk wrote:


Scott Danforth wrote:


Mladen Turk wrote:


Thanks for your help. That sounds very reasonable, and I modifed the 
two server.xml Engine elements as suggested, but it appears to make 
no difference.


get_most_suitable_worker::jk_lb_worker.c (733): searching worker for 
partial sessionid 9E36E3DC58A09ED9045B25F839E37A2C



You still don't have jvmRoute appended.
Check if jvmRoute (param name is case sensitive!) is
correctly set up.
Also, if you use JBoss add true
see:
http://www.jboss.org/wiki/Wiki.jsp?page=UsingMod_jk1.2WithJBoss


Regards,
Mladen.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--

Scott Danforth, Ph.D.
Director of Technology
ePath Learning, Inc.
70 Howard Street, Suite C
New London, CT 06320
Phone: (860) 444-6989 ext. 3
Fax: (215) 243-7454
email: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: mod_jk sticky session still not working

2007-02-27 Thread rasool.asal
Scott

Ensure that the following line is commented out. You may have already
done this


 


And uncomment


 


Hope that will help.

Rasool Asal

-Original Message-
From: Scott Danforth [mailto:[EMAIL PROTECTED] 
Sent: 23 February 2007 15:04
To: Tomcat Users List
Subject: Re: mod_jk sticky session still not working

P.S. I see a mention of "cluster" in the documentation for jvmRoute. Do
I need to configure a "cluster" perhaps?

-- Scott.


Scott Danforth wrote:

> Mladen Turk wrote:
>
>> Scott Danforth wrote:
>>
>>> I'm trying to use jk1.2.20 mod_jk with Apache 1.3 for load balancing

>>> two tomcat services and sticky sessions aren't working.
>>
>>
>>
>> You don't have session affinity mark
>> For each instance add jvmRoute="tomcat1" or
>> jvmRoute="tomcat2 for a second instance. See:
>> http://tomcat.apache.org/tomcat-5.5-doc/config/engine.html
>
>
>
> Thanks for your help. That sounds very reasonable, and I modifed the 
> two server.xml Engine elements as suggested, but it appears to make no

> difference.
>
> Below are 3 segments from mod_jk.log.
>
> The first segment shows the initial request coming in without a 
> sessionid. The request is routed to tomcat1 with route=tomcat1.
>
> The second segment shows the response coming back from tomcat1, with a

> new session id.
>
> The third segment shows the second request coming in with the expected

> session id, and shows tomcat2 being selected with route=tomcat2.
>
> You say I don't have session affinity mark. How would that show up in 
> the log? Is the "partial sessionid" an indication of the problem?
>
>-- Scott.
>
>
> [Fri Feb 23 09:08:53 2007] [6000:] [debug] 
> map_uri_to_worker::jk_uri_worker_map.c (575): Attempting to map URI 
> '/servlets/Build' from 1 maps [Fri Feb 23 09:34:59 2007] [6266:] 
> [debug] map_uri_to_worker::jk_uri_worker_map.c (587): Attempting to 
> map context URI '/servlets/*=loadbalancer' source 'JkMount'
> [Fri Feb 23 09:34:59 2007] [6266:] [debug] 
> map_uri_to_worker::jk_uri_worker_map.c (602): Found a wildchar match 
> '/servlets/*=loadbalancer'
> [Fri Feb 23 09:34:59 2007] [6266:] [debug] 
> wc_get_worker_for_name::jk_worker.c (114): found a worker loadbalancer

> [Fri Feb 23 09:34:59 2007] [6266:] [debug] 
> wc_maintain::jk_worker.c (321): Maintaining worker loadbalancer [Fri 
> Feb 23 09:34:59 2007] [6266:] [debug] 
> wc_get_name_for_type::jk_worker.c (290): Found worker type 'lb'
> [Fri Feb 23 09:34:59 2007] [6266:] [debug] 
> init_ws_service::mod_jk.c (561): Service protocol=HTTP/1.1 method=GET
> host=(null) addr=192.168.1.50 name=build port=8008 auth=(null)
> user=(null) laddr=192.168.1.7 raddr=192.168.1.50 [Fri Feb 23 09:34:59 
> 2007] [6266:] [debug] service::jk_lb_worker.c
> (840): service sticky_session=1 id='empty'
> [Fri Feb 23 09:34:59 2007] [6266:] [debug] 
> get_most_suitable_worker::jk_lb_worker.c (785): found best worker
> tomcat1 (tomcat1) using method 'Request'
> [Fri Feb 23 09:34:59 2007] [6266:] [debug] service::jk_lb_worker.c
> (860): service worker=tomcat1 route=tomcat1
>
> ...
>
> [Fri Feb 23 09:35:00 2007] [6266:] [debug] 
> ajp_unmarshal_response::jk_ajp_common.c (603): status = 200 [Fri Feb 
> 23 09:35:00 2007] [6266:] [debug] 
> ajp_unmarshal_response::jk_ajp_common.c (610): Number of headers is = 
> 2 [Fri Feb 23 09:35:00 2007] [6266:] [debug] 
> ajp_unmarshal_response::jk_ajp_common.c (666): Header[0] [Set-Cookie] 
> = [JSESSIONID=9E36E3DC58A09ED9045B25F839E37A2C; Path=/] [Fri Feb 23 
> 09:35:00 2007] [6266:] [debug] 
> ajp_unmarshal_response::jk_ajp_common.c (666): Header[1] 
> [Content-Type] = [text/html;charset=ISO-8859-1] [Fri Feb 23 09:35:00 
> 2007] [6266:] [debug] 
> ajp_connection_tcp_get_message::jk_ajp_common.c (1029): received from
> ajp13 pos=0 len=2309 max=8192
>
> ...
>
> [Fri Feb 23 09:35:10 2007] [6266:] [debug] 
> map_uri_to_worker::jk_uri_worker_map.c (575): Attempting to map URI 
> '/servlets/Build' from 1 maps [Fri Feb 23 09:35:10 2007] [6266:] 
> [debug] map_uri_to_worker::jk_uri_worker_map.c (587): Attempting to 
> map context URI '/servlets/*=loadbalancer' source 'JkMount'
> [Fri Feb 23 09:35:10 2007] [6266:] [debug] 
> map_uri_to_worker::jk_uri_worker_map.c (602): Found a wildchar match 
> '/servlets/*=loadbalancer'
> [Fri Feb 23 09:35:10 2007] [6266:] [debug] 
> wc_get_worker_for_name::jk_worker.c (114): found a worker loadbalancer

> [Fri Feb 23 09:35:10 2007] [6266:] [debug] 
> wc_

Re: mod_jk sticky session still not working

2007-02-27 Thread Scott Danforth

Hi, Rasool.

Yes,  I missed the actual Engine element that follows the comment.

   Thanks,
   -- Scott.


[EMAIL PROTECTED] wrote:


Scott

Ensure that the following line is commented out. You may have already
done this






And uncomment





Hope that will help.

Rasool Asal

-Original Message-
From: Scott Danforth [mailto:[EMAIL PROTECTED] 
Sent: 23 February 2007 15:04

To: Tomcat Users List
Subject: Re: mod_jk sticky session still not working

P.S. I see a mention of "cluster" in the documentation for jvmRoute. Do
I need to configure a "cluster" perhaps?

   -- Scott.


Scott Danforth wrote:

 


Mladen Turk wrote:

   


Scott Danforth wrote:

 


I'm trying to use jk1.2.20 mod_jk with Apache 1.3 for load balancing
   



 


two tomcat services and sticky sessions aren't working.
   



You don't have session affinity mark
For each instance add jvmRoute="tomcat1" or
jvmRoute="tomcat2 for a second instance. See:
http://tomcat.apache.org/tomcat-5.5-doc/config/engine.html
 



Thanks for your help. That sounds very reasonable, and I modifed the 
two server.xml Engine elements as suggested, but it appears to make no difference.
   




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]