You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/11/18 07:54:44 UTC
DO NOT REPLY [Bug 40996] New: - Tomcat Connectors 1.2.19 sticky sessions not sticky
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40996>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40996
Summary: Tomcat Connectors 1.2.19 sticky sessions not sticky
Product: Tomcat 5
Version: Unknown
Platform: Other
OS/Version: Linux
Status: NEW
Severity: major
Priority: P2
Component: Connector:AJP
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: simon.lorenz@fresca.co.uk
Since upgrading from Tomcat Connectors 1.2.15 to 1.2.19 we find that session
affinity between apache and a tomcat/jboss instance is lossed. It appears that
the connector will quite frequently direct traffic to the first worker in a LB
pool rather than the one with the correct JVMRoute for the session.
Rolling back to 1.2.15 has resolved this issue. No other conf changes were made
as part of this upgrade.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 40996] - Tomcat Connectors 1.2.19 sticky sessions not sticky
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40996>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40996
m.turra@kion.it changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution| |INVALID
------- Additional Comments From m.turra@kion.it 2007-01-10 08:44 -------
Sorry, I misspelled jvm with jmv!
Now it works fine.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 40996] - Tomcat Connectors 1.2.19 sticky sessions not sticky
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40996>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40996
------- Additional Comments From m.turra@kion.it 2007-01-10 06:20 -------
I have the same problem with JK 1.2.20.
I have this strange behaviors I found in mod_jk.log
Stick session is true and my session is on jvm_web1 route, because I found this:
> 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'
But it found jvm_web2 as best worker!
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 40996] - Tomcat Connectors 1.2.19 sticky sessions not sticky
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40996>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40996
rainer.jung@kippdata.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
Component|Connector:AJP |Native:JK
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 40996] - Tomcat Connectors 1.2.19 sticky sessions not sticky
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40996>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40996
rainer.jung@kippdata.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
------- Additional Comments From rainer.jung@kippdata.de 2006-11-18 03:26 -------
Please attach your config (relevant parts of httpd.conf or included files,
workers.properties, uriworkermap.properties, relevant parts of server.xml) and
give details on the versions of apache, tomcat and opertaing system you use.
Furthermore:
Are there any error messages in apache logfiles, especially in the mod_jk.log?
Can you reproduce the problem?
Does your application use URL rewriting or Cookies to establish sessions?
To collect some more runtime information, please add the following to your
Apache LogFormat:
\"%{Set-Cookie}i\" \"%{Cookies}o\" %{JK_WORKER_NAME}n %{JK_WORKER_TYPE}n
%{JK_REQUEST_DURATION}n %{JK_LB_FIRST_NAME}n %{JK_LB_FIRST_VALUE}n
%{JK_LB_FIRST_ACCESSED}n %{JK_LB_FIRST_ERRORS}n %{JK_LB_FIRST_BUSY}n
%{JK_LB_FIRST_STATE}n %{JK_LB_LAST_NAME}n %{JK_LB_LAST_VALUE}n
%{JK_LB_LAST_ACCESSED}n %{JK_LB_LAST_ERRORS}n %{JK_LB_LAST_BUSY}n
%{JK_LB_LAST_STATE}n %D
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org