os García
Asunto: Re: Sticky sessions not working at get_most_suitable_worker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Carlos,
On 6/30/18 4:12 AM, Carlos García wrote:
> I' m working on a LB configuration with Apache/2.4.18 (Ubuntu)
> mod_jk/1.2.41 and not getting wanted resu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Carlos,
On 6/30/18 4:12 AM, Carlos García wrote:
> I' m working on a LB configuration with Apache/2.4.18 (Ubuntu)
> mod_jk/1.2.41 and not getting wanted results.
>
>
> My workers config is:
>
>
> worker.list=balanceFFG, jk-status # tomcat-pro-0
Hello.
I' m working on a LB configuration with Apache/2.4.18 (Ubuntu) mod_jk/1.2.41
and not getting wanted results.
My workers config is:
worker.list=balanceFFG, jk-status
# tomcat-pro-03 por COLT
worker.FFG1.host=tomcat-pro-03
worker.FFG1.port=8009
worker.FFG1.type=ajp13
worker.FFG1.stick
Thank you all for your responses. We found that sticky was set up
properly. The problem was with the application and how it handles
clustering. Thanks again...
On Fri, Sep 21, 2012 at 11:51 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicolas,
On 9/21/12 12:58 AM, Nicolas Sarazin wrote:
> Add : worker.node1.route=node1
>
> And : worker.node2.route=node2
>
> To use sticky session. These directives attach name route at the
> end of JSESSIONID.
That shouldn't be necessary, as the w
Hello,
Add :
worker.node1.route=node1
And :
worker.node2.route=node2
To use sticky session. These directives attach name route at the end of
JSESSIONID.
Best regards,
Nicolas SARAZIN
Le vendredi 21 septembre 2012, Lou Henry a écrit :
> I'm running Apache Tomcat 7.0.14 and Apache 2.2.21 (mo
I'm running Apache Tomcat 7.0.14 and Apache 2.2.21 (mod_jk1.2.37). I
am trying to load balance two Tomcat Servers and sticky sessions are
not working. I am running
a two-factor authentication package and it looks like my LB
configuration is directing the user to one Tomcat for part of the
transac
The system i'm currently testing with is only a little test system,
it is not inteded to go productive in that configuration ;-)
But thanks for the tip you anyway. The jk.log has no error messages,
and here is the log grepped for "found best worker":
[Tue Oct 25 15:52:23 2005] [28304:49172] [debug
Doehler, Thomas wrote:
Hi,
IMO having 10 connections limit is way too low for any serious usage.
I would suggest that you rise maxProcessor to at least 100.
Also do you observe any error messages in mod_jk.log?
Regards,
Mladen.
--
Hi,
here the requested files:
workers properties:
---
#
# wokers.properties - configuration for mod_jk
#
# configure path separator
ps=/
# list of workers by name
worker.list=loadbalancer
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=debi1, debi2
worker.load
Doehler, Thomas wrote:
Hi,
thanks for the quick response, jvmRoute is configured on both instances.
We do not use the standard tomcat url rewriting (which is
http://...;jsessionid=...?x=y),
we use simply a standard http paramter and do our own url rewriting.
Right, but it would be good that
Hi,
thanks for the quick response, jvmRoute is configured on both instances.
We do not use the standard tomcat url rewriting (which is
http://...;jsessionid=...?x=y),
we use simply a standard http paramter and do our own url rewriting.
Regards,
Tom
> Did you set the jvmRoute="your worker name"
Doehler, Thomas wrote:
Hi list,
I'm using apache 2.0.54 + mod_jk 1.2.14 on a debian 3.1 server.
I have 2 tomcat workers running on different machines.
Although I configured the load balancing worker with sticky_session=1, all
requests get spread over the tomcat workers in round robin.
My ques
Hi list,
I'm using apache 2.0.54 + mod_jk 1.2.14 on a debian 3.1 server.
I have 2 tomcat workers running on different machines.
Although I configured the load balancing worker with sticky_session=1, all
requests get spread over the tomcat workers in round robin.
My question is, how does mod_jk
14 matches
Mail list logo
