http://www.tutorialspoint.com/white-papers/load-balancing-and-scalability-via-tomcat-clusters.htm
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
This is my workers.properties file too.
Thanks
Phil
# workers.properties
ps=/
# list the workers by name
worker.list=tomcat1,tomcat2,tomcat3,loadbalancer
#
# Specifies the load balance factor when used with
# a load balancing worker.
# Note:
# lbfactor must be 0
# Low lbfactor
: nohacks [mailto:philipfwil...@gmail.com]
Sent: Wednesday, April 08, 2009 4:11 PM
To: users@tomcat.apache.org
Subject: Re: Tomcat 6 Cluster with Apache 2.2.9 issues
This is my workers.properties file too.
Thanks
Phil
# workers.properties
ps=/
# list the workers by name
worker.list=tomcat1,tomcat2
thanks for the reply.
I updated my workers.properties file to
worker.list=loadbalancer
still get this in my mod_jk.log.
[Wed Apr 08 17:21:46.840 2009] [29811:3075569408] [warn]
jk_map_validate_property::jk_map.c (410): The attribute
'worker.loadbalancer.balanced_workers' is deprecated -
On 08.04.2009 23:23, nohacks wrote:
thanks for the reply.
I updated my workers.properties file to
worker.list=loadbalancer
still get this in my mod_jk.log.
[Wed Apr 08 17:21:46.840 2009] [29811:3075569408] [warn]
jk_map_validate_property::jk_map.c (410): The attribute
Look for the replacement of balanced_workers in
http://tomcat.apache.org/connectors-doc/reference/workers.html
Also remove the ps line from workers.properties. It has no meaning.
Furthermore look at the page
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
to learn more
inline:
Manu_SF wrote:
Hi,
After some digging through and still not able to get it work, I thought of
posting it here... Here's what I am trying to accomplish:
* Have Apache as a Loadbalancer for 2 Tomcat 6 instances - All running on
the same Linux box
* Implement the session persistence
Thanks a ton, Filip.
Here are the details about the 3 questions you asked. Please tell me what am
I missing here?
1. distributable tag:
There's no Context attribute in either web.xml or server.xml, but however
context.xml in the same conf directory had Context tag, for which I added
the
Manu_SF wrote:
Thanks a ton, Filip.
Here are the details about the 3 questions you asked. Please tell me what am
I missing here?
1. distributable tag:
There's no Context attribute in either web.xml or server.xml, but however
context.xml in the same conf directory had Context tag, for which I
That error is ok, since you're shutting down, we closing the socket
forcefully. It's a mistake of me to print the error message
Filip
Zachariah Zachariah wrote:
Thanks Filip. I found that changing the Host name to localhost from
the actual node names made it to work properly. So in my case
Thanks Filip. I found that changing the Host name to localhost from the
actual node names made it to work properly. So in my case z2 and z3 were
the actual node names that the OS (Solaris) knew them to be. I changed
Engine and Host elements of the server.xml in these nodes to point to
have you by any chance deployed your apps in Host elements with a
different name?
Filip
Zachariah Zachariah wrote:
Hi,
I am trying to set up a cluster of tomcat servers to serve up my
dynamic content with session replication. Although failover seems to
be working with each node aware of
Hi again,
After some weeks, Mr. Hanik help us solving the problem.
And he found it!
The problem was the sticky sessions, and our balancer: pen.
Pen, (http://siag.nu/pen/) it's a simple load balancer, and it doesn't care
about sessions between nodes.
That provokes dead locks at tomcat.
The
you probably have a 5.5 instance running on the same multicast address
somewhere, and so your 6.0.16 instance is getting packages from a node
you don't know about
give you TC6 instances a new multicast address or port
Filip
Martin Kristensen wrote:
Hi,
I am trying to upgrade two Tomcat 5.5
original-
De: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 17 de enero de 2008 19:01
Para: Tomcat Users List
Asunto: Re: Tomcat 6 - Cluster error.
already replied to your old thread
ok, it looks like you might have ended up with a rogue socket,
and what happens
[mailto:[EMAIL PROTECTED]
Enviado el: lunes, 28 de enero de 2008 1:45
Para: Tomcat Users List
Asunto: Re: Tomcat 6 - Cluster error.
I'd set keepAliveTime to 10 as well,
Filip
Raúl García wrote:
Hi Again, once again thanks for your time, but we still have problems,
We applied
===
-Mensaje original-
De: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 17 de enero de 2008 19:01
Para: Tomcat Users List
Asunto: Re: Tomcat 6 - Cluster error.
already replied to your old thread
ok, it looks like you might have ended up with a rogue socket,
and what
:[EMAIL PROTECTED]
Enviado el: jueves, 17 de enero de 2008 19:01
Para: Tomcat Users List
Asunto: Re: Tomcat 6 - Cluster error.
already replied to your old thread
ok, it looks like you might have ended up with a rogue socket,
and what happens is that any message sent to that socket just gets lost
: viernes, 18 de enero de 2008 11:23
Para: 'Tomcat Users List'
Asunto: RE: Tomcat 6 - Cluster error.
Hi Filip,
Thank you for that suggestion. We are going to try it now.
On the other side, if You want to reproduce the error:
We have used a server here configured with the same config.xml files
PROTECTED]
Enviado el: viernes, 18 de enero de 2008 11:23
Para: 'Tomcat Users List'
Asunto: RE: Tomcat 6 - Cluster error.
Hi Filip,
Thank you for that suggestion. We are going to try it now.
On the other side, if You want to reproduce the error:
We have used a server here configured with the same
more you need.
Thank you for the response.
We will see the real results in 13 days, I'll update.
Best Regards
Raúl.
-Mensaje original-
De: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 17 de enero de 2008 19:01
Para: Tomcat Users List
Asunto: Re: Tomcat 6
Holy smokes! I didn't even see that. Thanks for better at reading than me.
:(
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 16, 2008 4:53 PM
To: Tomcat Users List
Subject: Re: Tomcat 6 cluster
it would be very strange to how
already replied to your old thread
ok, it looks like you might have ended up with a rogue socket,
and what happens is that any message sent to that socket just gets lost
in the ether, since it doesn't have any interest ops.
There is a workaround for this, turn off keep alives all together, or
it would be very strange to how the cluster would have anything to do
with this :)
the error you are getting is:
Caused by: java.net.UnknownHostException: lexecfin
the JDBC driver is unable to resolve that name, put the name in your hosts
file, or put the IP address instead of hostname for
Filip,
Thanks for that. We'll be patient and wait for the new version.
Regards
Mark
-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 08 August 2007 21:41
To: Tomcat Users List
Subject: Re: Tomcat 6 cluster management
Mark Faircloth wrote:
The Tomcat
Mark Faircloth wrote:
The Tomcat 6 documentation says that the MBean values 'type=Cluster' and
'type=Cluster,host=${HOST}' should be available like they were in Tomcat
5.5. However, they are not visible via jmx using jconsole or Probe.
Does anyone know how to view Cluster information in
26 matches
Mail list logo
