https://bz.apache.org/bugzilla/show_bug.cgi?id=64052
Bug ID: 64052
Summary: mod_jk set_session_cookie not sending new cookie after
node failover for sticky session
Product: Tomcat Connectors
Version: 1.2.46
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: mod_jk
Assignee: dev@tomcat.apache.org
Reporter: dotin.insura...@gmail.com
Target Milestone: ---
Hi
I have set up set_session_cookie and add a custom cookie for sticky session
management. It's working fine until I stop a specific node. The balancer would
redirect me to new node but it won't set new node name to the cookie.
This is what documentation says:
"Especially after a node failover we will send a new cookie to switch
stickyness to the new node."
But it is not working.
This is mod_jk log trace:
[Sun Jan 05 14:02:35.126 2020] [25699:140105601013504] [debug]
service::jk_lb_worker.c (1270): service sticky_session=1 id='.node1'
[Sun Jan 05 14:02:35.126 2020] [25699:140105601013504] [trace]
get_most_suitable_worker::jk_lb_worker.c (1037): enter
[Sun Jan 05 14:02:35.126 2020] [25699:140105601013504] [debug]
get_most_suitable_worker::jk_lb_worker.c (1078): searching worker for partial
sessionid .node1
[Sun Jan 05 14:02:35.126 2020] [25699:140105601013504] [debug]
get_most_suitable_worker::jk_lb_worker.c (1086): searching worker for session
route node1
[Sun Jan 05 14:02:35.126 2020] [25699:140105601013504] [debug]
get_most_suitable_worker::jk_lb_worker.c (1136): found best worker node2
(node2) using method 'Busyness'
[Sun Jan 05 14:02:35.126 2020] [25699:140105601013504] [trace]
get_most_suitable_worker::jk_lb_worker.c (1139): exit
[Sun Jan 05 14:02:35.126 2020] [25699:140105601013504] [debug]
service::jk_lb_worker.c (1315): service worker=node2 route=node2 failover=false
I read source of file "jk_lb_worker.c" and I think the s->sticky is setting
wrong value so when the node fails over the new cookie is not sending to
client.
Also I tested this behaviour in both 1.2.43 and 1.2.46 versions.
Hope to hear from you soon.
Sincerely,
Mohsen
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
