Hi,
I almost forgot about this one :-)
- Original Message
> From: Filip Hanik - Dev Lists
> To: Tomcat Users List
> Sent: Tue, June 7, 2011 1:07:20 AM
> Subject: Re: Tomcat 6 Clustering vs. Tomcat 5.5 clustering
>
> On 5/23/2011 6:50 AM, Martin Knobl
On 5/23/2011 6:50 AM, Martin Knoblauch wrote:
Hi,
while moving an application from Tomcat 5.5 to Tomcat 6 I found some
differences in clustering, that I could not resolve myself:
e. G. What happened to replicationMode, ackTimeout waitForAck? In TC 5.5 I had:
channelSendOptions
h
Hi,
while moving an application from Tomcat 5.5 to Tomcat 6 I found some
differences in clustering, that I could not resolve myself:
e. G. What happened to replicationMode, ackTimeout waitForAck? In TC 5.5 I had:
Are they still available with
"org.apache.catalina.tribes.transport
Hi,
while moving an application from Tomcat 5.5 to Tomcat 6 I found some
differences in clustering, that I could not resolve myself:
e. G. What happened to replicationMode, ackTimeout waitForAck? In TC 5.5 I had:
Are they still available with
"org.apache.catalina.tribes.transpo
On 09/14/2009 03:42 AM, Davy NESTOR wrote:
It didn't work.
I used the sessionExample.jsp page from the tomcat exemple directory.
does it use serializable attributes?
I go to http://serv-1/sessionExample.jsp and
http://serv-2/sessionExample.jsp to check if my session if the same.
Is it the g
It didn't work.
I used the sessionExample.jsp page from the tomcat exemple directory.
I go to http://serv-1/sessionExample.jsp and
http://serv-2/sessionExample.jsp to check if my session if the same.
Is it the good way ?
On Sun, Sep 13, 2009 at 5:56 PM, Filip Hanik - Dev Lists wrote:
> did you
did you try with path
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Hello
I'm trying to set up a session replciation between my tomcat hosts.
I have to use the static method to describe the member of the cluster.
I had the same error that this thread:
http://www.opensubscriber.com/message/users@tomcat.apache.org/9810630.html
I tried to modify my configuration, e
x27;, what does that actually
mean in this case? Availability of Tomcat on a node, or the
availability of the service to respond to requests?
-Original Message-
From: Sumedh Sakdeo [mailto:sumedhsak...@gmail.com]
Sent: 08 September 2009 10:49
To: Tomcat Users List
Subject: Re: Tomcat 6 C
Hi Darren,
For our setup tomcat 6 is able to handle failover to healthy node
with proper session replication. I assume you have loaded load balancer
module, updated worker.properties, made cluster changes to server.xml of
tomcat 6. My problem is next step of yours.
http://www.mail-archive.
Hi All,
I've come across some interesting scenarios with a clustered Tomcat6
environment and I'm wondering what the most common (or best) approach to
configuration would be.
Basically, in a 2 node cluster, with a front-end Apache Web Server using
mod_jk balancer (on availability, with equal
Oh, I think you got me wrong. As I said, by "non-existing name" I meant a
DNS name or definition in /etc/hosts file, something that is known to ie.
OS.
In all examples there were either "localhost" or "www.somesite.tld", so I
thought that it needs to be either DNS or /etc/hosts.
But it seem that a
> wrote:
From: Ossi [mailto:los...@gmail.com]
Subject: Tomcat 6 clustering and engine's defaulthost
Looks like if configuring a Tomcat 6 cluster Engine's and host's
default host must be "localhost", ie.
If having something else than localhost, an error is logged:
> From: Ossi [mailto:los...@gmail.com]
> Subject: Re: Tomcat 6 clustering and engine's defaulthost
>
>
> Problem occurred when we had in server 1:
> jvmRoute="route1">
> and in server 2:
> jvmRoute="route2">
Fragments of server.xm
> Yes, it will be harmful.
>
How it is harmful?
In my example the non-existing name (not in DNS nor hosts file) is matches
the name attribute of the only Host element, so that is as manual instructs.
And btw, we're using Apache httpd in front of Tomcat cluster, if that
happens to matter in this c
On 13/08/2009 10:55, Ossi wrote:
On Wed, Aug 12, 2009 at 5:26 PM, Caldarale, Charles R<
chuck.caldar...@unisys.com> wrote:
From: Ossi [mailto:los...@gmail.com]
Subject: Tomcat 6 clustering and engine's defaulthost
Looks like if configuring a Tomcat 6 cluster Engine's and hos
On Wed, Aug 12, 2009 at 5:26 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Ossi [mailto:los...@gmail.com]
> > Subject: Tomcat 6 clustering and engine's defaulthost
> >
> > Looks like if configuring a Tomcat 6 cluster Engine&#x
> From: Ossi [mailto:los...@gmail.com]
> Subject: Tomcat 6 clustering and engine's defaulthost
>
> Looks like if configuring a Tomcat 6 cluster Engine's and host's
> default host must be "localhost", ie.
>
> If having something else than localhost,
hi!
Looks like if configuring a Tomcat 6 cluster Engine's and host's default
host must be "localhost", ie.
If having something else than localhost, an error is logged:
2009-04-03 12:48:15,492 WARN [pool-2-thread-1]
(org.apache.catalina.ha.ClusterListener) Context manager doesn't
exist:priv
Ya... I got that message when I stopped the tomcat ( it shuts down with a
warning )
4th step in below is the scenario is where I got that warning
1) Start tomcat 1
2) Start tomcat 2
3) create atleast once session on tomcat 1 and tomcat 2 by accessing the
web application
4) kill any tom
this message
2008-11-20 17:08:29.999 [main] [INFO]
org.apache.coyote.http11.Http11Protocol - Stopping Coyote HTTP/1.1 on http-8080
tells us that you stopped the tomcat instance
Filip
rohit aman wrote:
Hi,
I have a tomcat cluster ( with tomcat 1 and tomcat 2 ) with a hardware
load balanc
Hi,
I have a tomcat cluster ( with tomcat 1 and tomcat 2 ) with a hardware
load balancer infront. Session replication only works in some scenario and
does not in others. Here is the scenario where it works...
1) Start tomcat 1
2) access the web application ( session gets created in tom
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
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
apache.catalina.cluster.session.ClusterSessionListener"/>
>
>
>className="org.apache.catalina.ha.context.ReplicatedContext"
> path="/MyApp" docBase="G:\RealNetworks\apache-tomcat-6.0.16\webapps\MyApp"
> crossContext="
wrote:
>> Hi guys, I am configuring Tomcat 6 clustering to have more than one
>> instance
>> access to each others ServletContext attributes. It's said that
>> ServletContext is clustered by default when Tomcat 6 is clustered, but my
>> servlets in 2 different ins
you'd need to define
Hi guys, I am configuring Tomcat 6 clustering to have more than one instance
access to each others ServletContext attributes. It's said that
ServletContext is clustered by default when Tomcat 6 is clustered, but my
servlets in 2 different instances are not able
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gangadhar,
gangadhar p wrote:
| Hi guys, I am configuring Tomcat 6 clustering to have more than one
instance
| access to each others ServletContext attributes.
It's not going to happen. See the servlet specification:
"
SRV.4.4.1 Context
Hi guys, I am configuring Tomcat 6 clustering to have more than one instance
access to each others ServletContext attributes. It's said that
ServletContext is clustered by default when Tomcat 6 is clustered, but my
servlets in 2 different instances are not able to access each o
ED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>
>>
>>
>> -
>> To start a new topic, e-mail: us
can you check that you don't have the "" element in your
conf/context.xml
this will override the default settings from below
Filip
Filip Hanik - Dev Lists wrote:
I'll take a look at this today or tomorrow
filip
Timothy Wonil Lee wrote:
Dear list,
I have a cluster of Tomcat 6.0.14 using Del
I'll take a look at this today or tomorrow
filip
Timothy Wonil Lee wrote:
Dear list,
I have a cluster of Tomcat 6.0.14 using DeltaManager.
Session replication works fine while both instances are running.
I can test this by for example, logging-in to one of the webapps on a Tomcat
instance in t
Dear list,
I have a cluster of Tomcat 6.0.14 using DeltaManager.
Session replication works fine while both instances are running.
I can test this by for example, logging-in to one of the webapps on a Tomcat
instance in the cluster, then kill the process of that tomcat. Then I get
transferred to an
t - JK: ajp13 listening on /0.0.0.0:8010
--> INFO JkMain::start - Jk running ID=0 time=0/191 config=null
--> INFO Catalina::start - Server startup in 62216 ms
-Message d'origine-
De : Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Envoyé : mardi 30 octobre 2007 00:54
À
Message d'origine-
De : Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Envoyé : lundi 29 octobre 2007 16:44
À : Tomcat Users List
Objet : Re: Tomcat 6 clustering without mulicast
yes, that's what you wanted. Then you have to add the sta
anik - Dev Lists [mailto:[EMAIL PROTECTED]
Envoyé : lundi 29 octobre 2007 16:44
À : Tomcat Users List
Objet : Re: Tomcat 6 clustering without mulicast
yes, that's what you wanted. Then you have to add the static membership
interceptors to add static members since you don't have multicast
List
Objet : Re: Tomcat 6 clustering without mulicast
yes, that's what you wanted. Then you have to add the static membership
interceptors to add static members since you don't have multicast
heartbeats anymore
Filip
SANCHEZ, Michel wrote:
> Thanks Filip
>
> I added the D
---Message d'origine-
De : Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 26 octobre 2007 19:13
À : Tomcat Users List
Objet : Re: Tomcat 6 clustering without mulicast
it is absolutely possible, but now when you mention it, the ability to
not start the multicasting pie
state transfer. No
members active in cluster group.
I carry on investigating
Michel.
-Message d'origine-
De : Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 26 octobre 2007 19:13
À : Tomcat Users List
Objet : Re: Tomcat 6 clustering without mulicast
rote:
Hi all
I would like to know if it is possible to do tomcat 6 clustering without
multicast IP.
In other words by defining a full static cluster in which all the heartbeat
stuff is done by unicast.
If yes please coluld you tel me how to configure it.
I tried a SimpleTcpCluster wit
Hi all
I would like to know if it is possible to do tomcat 6 clustering without
multicast IP.
In other words by defining a full static cluster in which all the heartbeat
stuff is done by unicast.
If yes please coluld you tel me how to configure it.
I tried a SimpleTcpCluster without
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
change
channelSendOptions="6"
to
channelSendOptions="0"
and see how that works for you
Filip
Prabhu wrote:
We have enabled tomcat 6 clustering with two machines. After doing
that we
noticed two things.
1. Tomcat is taking atleast 5 minutes to start. There are only 5
We have enabled tomcat 6 clustering with two machines. After doing that we
noticed two things.
1. Tomcat is taking atleast 5 minutes to start. There are only 5 webapps
in total.
2. useDirtyFlag="false" in Cluster tag, doesn't seem to work.
I am posting our clu
Original Message-
> From: Kristian Rink [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 31, 2007 9:52 AM
> To: users@tomcat.apache.org
> Subject: Re: tomcat 6, clustering, FarmDeployer
>
>
> Filip;
>
> first off, thanks loads for your hint. So by now I can at least stop
&g
Filip;
first off, thanks loads for your hint. So by now I can at least stop
playing with the FarmWarDeveloper and focus on other things...
[Filip Hanik - Dev Lists <[EMAIL PROTECTED]> @ Thu, 31 May 2007
15:44:59 +0200]
> hi Kristian, Farm deployer is currently broken, has been for a while
> and
hi Kristian, Farm deployer is currently broken, has been for a while and
needs to be completely revised.
Filip
Kristian Rink wrote:
Folks;
being knee-deep into building a test system to see whether our
clustered applications also will work in a tc 6.0 clustered environment
(currently they ru
Folks;
being knee-deep into building a test system to see whether our
clustered applications also will work in a tc 6.0 clustered environment
(currently they run atop 5.5), and the cluster configuration (having an
apache2+mod-jk in front) seems to work well having an application that
already runs
on the servers that is running tomcat you need to match
with
so for the member that listens to 51077, you need to configure the
port="51077"
also to avoid conflict, you might want to turn on the membership, which
I think I forgot to add in a flag for, I'll do that right now.
Filip
Mike Pr
I'm trying to cluster two Tomcat 6.0.7 instances across a network that
does not support multicasting. I've added the StaticMember elements
under the StaticMembershipInterceptor.
I've also opened up ports 4000 and 51077.
When I use netstat to see which ports Tomcat is listening on, it does
no
63 matches
Mail list logo
