- Original Message -
> From: Nilesh - MiKu
> To: Tomcat Users List ; Mark Eggers
>
> Cc:
> Sent: Tuesday, June 14, 2011 4:01 AM
> Subject: Re: Tomcat 6.0.18 clustering problem
>
>T hanks Mark. :)
>
> My comments inlined...
>
> Over and above, th
ilesh - MiKu
> > To: users@tomcat.apache.org
> > Cc:
> > Sent: Monday, June 13, 2011 8:36 AM
> > Subject: Tomcat 6.0.18 clustering problem
> >
> > Hi people...
> >
> > Background :
> >
> > I have two nodes (say, n1 and n2) running 3 i
- Original Message -
> From: Nilesh - MiKu
> To: users@tomcat.apache.org
> Cc:
> Sent: Monday, June 13, 2011 8:36 AM
> Subject: Tomcat 6.0.18 clustering problem
>
> Hi people...
>
> Background :
>
> I have two nodes (say, n1 and n2) running 3 inst
Hi people...
Background :
I have two nodes (say, n1 and n2) running 3 instances of tomcat (say t1, t2,
t3), with n1 running t1, t3 and n2 running t2. (All running same
application.). I want to make clustering for n1-t1 and n2-t2.
Clustering cofig for n1-t1 is
Cluster
Dear users,
I am trying to setup tomcat clustering/session replication between two
tomcats of version 6.0.18. The following is the cluster snippet inserted
into server.xml of both servers:
Dear users,
I am trying to setup tomcat clustering/session replication between two
tomcats of version 6.0.18. The following is the cluster snippet inserted
into server.xml of both servers:
The first error
>java.util.ConcurrentModificationException
happens cause the membership changed in between. The error logs, but the
system is not interrupted.
The second error
>java.net.SocketTimeoutException: Read timed out
This means the node failed to respond. This means you got a problem.
Hi,
We are running our application in load balanced mode in Tomcat 6.0 with
session replication.
When we are starting the servers in load balanced mode, then in the console we
are getting the following error :
2010-04-14 11:47:51,078 (main) [ VfsLog.java:122:INFO ] Using
"C:\DOC
Hi,
I'm trying to implement a session listener so that I can check the
status of a session. Essentially, I need to maintain a Map of all the
sessions. I would add sessions to this map based on business logic.
The problem I have is that the behavior of the listeners is different
when clustering
Thanks for the reply...
The app is installed on node 2 as well. But, for some reason it looks at
the context path localhost#/ea where as the app is at localhost#/ . So,
Somehow I need to tell tomcat to look at localhost#/ instead of
localhost#/ea Any input is appreciated...Thanks
you need to deploy the app on node 2 as well, it says the app is not
installed there
Filip
rohit aman wrote:
*I have two tomcats (tomcat 6)** setup on two separate machines. I have a
hardware load balancer with scheduling method configured to round robin.*
**
*each tomcat recognizes the other
*I have two tomcats (tomcat 6)** setup on two separate machines. I have a
hardware load balancer with scheduling method configured to round robin.*
**
*each tomcat recognizes the other one by saying replication member added *
**
*I also made the "examples" web application (that comes with tomcat) a
János wrote:
Filip,
You are right. I called the session example wrongly via the
"bml0042.yalepath.org" host, but that was not configured. As soon as
I called it via the "localhost" host - which was
glad you got it working
configured - it worked fine. Here is the log from node3:
bml0042:/
Filip,
You are right. I called the session example wrongly via the
"bml0042.yalepath.org" host, but that was not configured. As soon as
I called it via the "localhost" host - which was configured - it
worked fine. Here is the log from node3:
bml0042:/usr/local/tomcat janos$ cat node3/l
write your own webapp, to make sure you actually replicate serializable data
Filip
János wrote:
Hi Filip,
I added it in the catalina.sh file on all three nodes and I am not
seeing the error. I also disabled IP6 in Network Preferences.
I added the distrubuted="true" to the context.xml file
Hi Filip,
I added it in the catalina.sh file on all three nodes and I am not
seeing the error. I also disabled IP6 in Network Preferences.
I added the distrubuted="true" to the context.xml file on all three
nodes and added the tag to the webapps/examples/WEB-
INF/web.xml on all 3 nodes a
try setting the
|-Djava.net.preferIPv4Stack=true
option for your tomcat launch
Filip
|
János wrote:
Hi,
I am trying to establish a 3 member cluster on the same machine. Here
is my server.xml copied from a sample I found on this list.
SSLEngine="on" />
className="org.apache.catali
Hi,
I am trying to establish a 3 member cluster on the same machine.
Here is my server.xml copied from a sample I found on this list.
className="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on" />
className="org.apache.catalina.mbeans.ServerLifecycleListener" />
cl
worked fine for me, here are my config files and example JSP files
http://people.apache.org/~fhanik/replicated-context-example.zip
Filip
gangadhar p wrote:
Hi Guys,
The Tomcat 6 documentation
(http://tomcat.apache.org/tomcat-6.0-doc/config/cluster.html) says that the
Context (ServletContext,
Hi Filip,
Yes my logs show those member discovery. The screenshots of logs of two
instances are given below:
*Log on Instance 1: (started first)*
Jun 3, 2008 11:13:52 AM org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Settin
Hi Filip,
Yes my logs show those member discovery. The screenshots of logs of two
instances are given below:
*Log on Instance 1: (started first)*
Jun 3, 2008 11:13:52 AM org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Settin
POST your log, does it show member discovery?
Filip
Gangadhar Prusty wrote:
Hi,
My logs don't show any error/warning messages.
But it still doesn't replicate/share the ServletContext attributes.
Does the addition of below element in the *context.xml* mean that the *
ServletContext* attribute
Hi,
My logs don't show any error/warning messages.
But it still doesn't replicate/share the ServletContext attributes.
Does the addition of below element in the *context.xml* mean that the *
ServletContext* attributes are replicated/shared across other cluster
members?
Thanks again.
On
what do your logs say?
gangadhar p wrote:
Hi Filip,
Thanks for your prompt response.
I added an attribute to the ServletContext object in one instance and tried
to access the same attribute in another instance and it returns null.
The (in server.xml) element has the attribute
managerClass
>
>> >
>> className="org.apache.catalina.cluster.session.ClusterSessionListener"/>
>>
>>
>> > docBase="G:\RealNetworks\apache-tomcat-6.0.16\webapps\ROOT"
>> crossContext="true" debug="0" reloadable="true&qu
Hi Filip,
Thanks for your prompt response.
I added an attribute to the ServletContext object in one instance and tried
to access the same attribute in another instance and it returns null.
Infact it seems that the session objects are also not replicated.
The (in server.xml) element has the att
what does your log say?
Filip
gangadhar p wrote:
Hi Guys,
The Tomcat 6 documentation
(http://tomcat.apache.org/tomcat-6.0-doc/config/cluster.html) says that the
Context (ServletContext, right ?) attributes are replicated across cluster
members when the below element is added in either
\conf\se
Hi Guys,
The Tomcat 6 documentation (
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster.html) says that the
Context (ServletContext, right ?) attributes are replicated across cluster
members when the below element is added in either *
\conf\server.xml* or *\conf\context.xml* file.
**
*But act
config.xml file is given below:
Any modifications required?
Any suggestions would be highly appreciated.
Thanks in advance.
--
View this message in context:
http://www.nabble.com/Tomcat-6-clustering-problem-tp17609817p17609817.html
Sent from the Tomcat - User mailing list archive at Nabble.com
Filip
thanks for the help. I am not familiar with how to run route. (sorry
just a small business admin hack)
could you please suggest the command
thanks
Randy
On Feb 5, 2008 2:16 PM, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
> the broadcast happens on the 228.0.0.9 address. however, if
the broadcast happens on the 228.0.0.9 address. however, if you're boxes
have multiple nics, the system will pick one to send out the info.
you should be able to add an entry to your routing table to force it to
send the 228.0.0.9 broadcasts over the nic you designate.
Filip
Randy Paries wrote
Hello,
I have posted this problem before , but have made some headway but i
am still having problems.
I will try to describe this a briefly as possible but give enough info
needed to help
Some basic info:
3 Linux boxes
Tomcat 5.5.15
jdk1.5.0_11
Box1 and Box2 are one public Class C
Box3 is on a se
take a look at the example
http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html
you copied a 5.5 config into 6
Filip
[EMAIL PROTECTED] wrote:
Hallo
i have uncomment the element in server.xml of tomcat6 and write
this config in:
className="org.apache.catal
Hallo
i have uncomment the element in server.xml of tomcat6 and write
this config in:
My problem is now, that at startup of tomcat this message appears:
org.apache.catalina.ha.tcp.SimpleTcpCluster setProper
Strange!
mcastClusterDomain is set a McastService constructor
public McastService() {
properties.setProperty("mcastClusterDomain", "catalina");
}
Please don't use a real loadbalancer like apache with mod_jk instead the
crazy redirect thing at
http://www.onjava.com/pub/a/onj
I'm trying to perform a simple cluster setup with Tomcat 5.5 and been
running into some problems.
Here's the link to the tutorial that I'm trying to follow:
http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html.
Below is an excerpt of the stack trace, I'm using the balancer application
from
t: Tuesday, August 01, 2006 2:22 PM
To: 'Tomcat Users List'
Subject: RE: clustering problem
I have a question of the architecture you created..i am interseting in it.
Do you have a document how you did this?
thx
Maarten
-Oorspronkelijk bericht-
Van: Sharma, Siddharth [mai
: clustering problem
Hi
We have a 4 machine configuration.
Each machine has:
1. 3 Tomcat instances (so total 12 instances) 2. 1 Apache with mod_jk (so
total 4 Apaches)
The Apaches/mod_jks are fronted by a hardware load balancer.
Each mod_jk load balances across all 12 tomcats.
In other words, you could hit
o: Tomcat Users List
Subject: Re: clustering problem
Have a look at our new version mod_jk 1.2.18, especially at the worker
attribute "distance". This should be used in combination with an lb
worker. It enables you to define preferences.
If you want to route to different tomcats for prob
Have a look at our new version mod_jk 1.2.18, especially at the worker
attribute "distance". This should be used in combination with an lb
worker. It enables you to define preferences.
If you want to route to different tomcats for probing, configure
jvmRoute on the Tomcats (most likely you already
Hi
We have a 4 machine configuration.
Each machine has:
1. 3 Tomcat instances (so total 12 instances)
2. 1 Apache with mod_jk (so total 4 Apaches)
The Apaches/mod_jks are fronted by a hardware load balancer.
Each mod_jk load balances across all 12 tomcats.
In other words, you could hit any one of
Shades of embarrassment.
Our server clocks weren't sync'd.
It all works, just like it says it ought to.
Which was nice.
Pid wrote:
>
> We're running the following:
>
> Apache2.2 + Tomcat5.5.17
> mod_proxy, mod_proxy_ajp, mod_proxy_balancer
> on 2 linux boxes (one of which has a DB)
>
> Serv
We're running the following:
Apache2.2 + Tomcat5.5.17
mod_proxy, mod_proxy_ajp, mod_proxy_balancer
on 2 linux boxes (one of which has a DB)
Server #1 has the DB & the 2nd Tomcat.
Server #2 is the main Apache load balancer, with 1st Tomcat.
There are virtualhosts/subdomains in both apache & tomc
43 matches
Mail list logo