On 30.06.2010 16:18, János Löbb wrote:
workers.properties
---
ps=/
worker.list=pub-app01, pub-app02, pub-app03, pub-app04, pub-app05, pub-lb
worker.pub-app01.type=ajp13
worker.pub-app01.host=app01
worker.pub-app01.port=8009
worker.pub-app01.socket_keepalive=1
worker.pub-app02.t
> workers.properties
> ---
> ps=/
>
> worker.list=pub-app01, pub-app02, pub-app03, pub-app04, pub-app05, pub-lb
>
> worker.pub-app01.type=ajp13
> worker.pub-app01.host=app01
> worker.pub-app01.port=8009
> worker.pub-app01.socket_keepalive=1
>
> worker.pub-app02.type=ajp13
> worke
I now have made the change and it seems to be working (fingers crossed).
I have a couple of people testing it out, so fingers crossed!
OK, it now works correctly. The only issue I have is that Apache is now
adding .number to the end of each request.
If I go to myapp/forum, the first time I g
On 30.06.2010 13:10, Gabriel Tabares wrote:
have you also set de directive in de workers.properties I suggested?
in your case that should look like
worker.pub-app01.domain=pub-app01
etc
My apologies, I am doing 10 things at the time and missed that bit.
I now have made the change and it s
I'm not sure if this is what you are looking for but I just checked how
our stuff is set up here and wondered if you have the jvm route mapped
in the server xml for the tomcat instances you want loadbalanced?
Paul
Tomcats:
All of them have a jvmRoute of pub-app0X, where X goes fro
have you also set de directive in de workers.properties I suggested?
in your case that should look like
worker.pub-app01.domain=pub-app01
etc
My apologies, I am doing 10 things at the time and missed that bit.
I now have made the change and it seems to be working (fingers crossed).
I have
On 30/06/2010 11:33, M.H.G. Emmerig wrote:
> you beat me to it I think
>
> regards
>
> Milko Emmerig
> I'm not sure if this is what you are looking for but I just checked how
> our stuff is set up here and wondered if you have the jvm route mapped
> in the server xml for the tomcat instances you
mRoute set:
for the first, server
for the second, etc.
>
> -Original Message-
> From: Gabriel Tabares [mailto:gabriel.taba...@roboreus.com]
> Sent: 30 June 2010 11:17
> To: users@tomcat.apache.org
> Subject: Hello and Tomcat issues with sticky sessions
>
> Hi everyb
y have the
jvmRoute set:
for the first, server
for the second, etc.
-Original Message-
From: Gabriel Tabares [mailto:gabriel.taba...@roboreus.com]
Sent: 30 June 2010 11:17
To: users@tomcat.apache.org
Subject: Hello and Tomcat issues with sticky sessions
Hi everybody,
I have be
Yes sorry! Slow morning here today.. :)
From: M.H.G. Emmerig [mailto:m.h.g.emme...@dnb.nl]
Sent: 30 June 2010 11:33
To: Tomcat Users List
Subject: RE: Hello and Tomcat issues with sticky sessions
you beat me to it I think
regards
Milko Emmerig
"Ockleford Paul (NHS Connecting for H
our
stuff is set up here and wondered if you have the jvm route mapped in the
server xml for the tomcat instances you want loadbalanced?
Paul
-Original Message-
From: Gabriel Tabares [mailto:gabriel.taba...@roboreus.com]
Sent: 30 June 2010 11:17
To: users@tomcat.apache.org
Subject: Hel
Hello gabriel
I think you should have the following in your configuration:
in de workers definition something like
worker.pub-app01.domain=pub-app01-jvm
and in your tomcat server.xml
regards
Milko Emmerig
.taba...@roboreus.com]
Sent: 30 June 2010 11:17
To: users@tomcat.apache.org
Subject: Hello and Tomcat issues with sticky sessions
Hi everybody,
I have been running Tomcat on production for a few years with no problem
but now, after moving to a new company, I am completely unable to get
session stick
Hi everybody,
I have been running Tomcat on production for a few years with no problem
but now, after moving to a new company, I am completely unable to get
session stickyness working.
The setup is as follows:
Apache 2.2.3 (CentOS 5.4 version) -> Tomcat 6.0.24.
I have tried all of mod_proxy
14 matches
Mail list logo
