Re: Tomcat 5.5 Clustering
On 09/06/2011 15:02, Tauqir Akhtar wrote: Hi I am running two Tomcat (5.5.27) Instances on two different machines deploying the same Java Application. If this is a new request for help, rather than a reply to Tomcat 6 Clustering vs. Tomcat 5.5 clustering please start a new thread, rather than replying to an existing email just editing the subject body. This is called thread hijacking. p signature.asc Description: OpenPGP digital signature
RE: Tomcat 5.5 Clustering
Sorry abt that. I have created a new request now. Thanks Tauqir Akhtar -Original Message- From: Pid [mailto:p...@pidster.com] Sent: Thursday, June 09, 2011 10:27 AM To: Tomcat Users List Subject: Re: Tomcat 5.5 Clustering On 09/06/2011 15:02, Tauqir Akhtar wrote: Hi I am running two Tomcat (5.5.27) Instances on two different machines deploying the same Java Application. If this is a new request for help, rather than a reply to Tomcat 6 Clustering vs. Tomcat 5.5 clustering please start a new thread, rather than replying to an existing email just editing the subject body. This is called thread hijacking. p ## NOTICE: The contents of this e-mail and any attachments to it may contain privileged and confidential information from The Jones Group Inc. or its affiliates. This information is only for the viewing or use of the intended recipient. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of, or the taking of any action in reliance upon, the information contained in this e-mail, or any of the attachments to this e-mail, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this message and delete it from your system. ### - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat(5.5) Clustering and Load Balancing.
On 04/01/2011 06:47, Harsimranjit singh Kler wrote: So this means tomcat alone have not sufficent support for Load Balancing and clustering?. Correct. Tomcat does not provide a reverse proxy implementation. You main only way to achive is to use apache server HTTPD and connector, mod_jk things ?. You can use any reverse proxy you like. httpd + mod_jk is just one option. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat(5.5) Clustering and Load Balancing.
Hi
Here is details:
*Tomcat version*: 5.5.27
*OS*:Window XP
*JDK*:1.6
*Environment Trying to Create* :Load balancing and Clustering on single
Machine using tomcat instances only(balancer Feature) .
*What i have Achieved*:i am running 4 instances of tomcat on ports
8080,9080,10080,11080.So port 8080 tomcat work as balancer and other works
as cluster.(Using Multicasting IP and Port {check server.xml} it works
fine).
attached find server.xml,web.xml,rule.xml of balancer tomcat(8080).
So using balancer feature in tomcat and rule.xml and some customized
classes requests are successfully redirected to one of cluster ie 9080,10080
or 11080 instance.
*Issue*:when request redirected from tomcat balancer(on 8080 port) to any
cluster (tomcat instance on 9080,10080 or 11080 port) URL in address bar
also changed. i dont want to display cluster URL.So how i can achive this?.
i think org.apache.webapp.balancer.BalancerFilter class internally use
SendRedirect() method .
I tried with requestDispatcher..Forward() but it accept only realtive
address.
so please suggest me
Thanks in advance
Regards
Harsimran
On Tue, Dec 28, 2010 at 9:23 PM, David Smith david.sm...@cornell.eduwrote:
On 12/28/2010 8:33 AM, Pid wrote:
On 12/27/10 4:11 AM, Harsimranjit singh Kler wrote:
Hi
i have testing tomcat clustering on single machine.What i am able to do
is i
hv 4 tomcat instances 1 work as balancer and 3 as cluster.using Rule.xml
in
balancer with round robin approach.all requests hits on balancer
redirected
to on one cluster which is on some different port.
when redirecting using sendredirect it display new url that is of
cluster.i
want some alternate so all request shoud handled at balancer and URL at
adress bar not changed.
i have tried forward from servelet but that is not accept only realtive
URL.
I'm sorry, I don't have any idea what you're actually asking.
Please read:
http://www.catb.org/~esr/faqs/smart-questions.html
When you reply, please precisely detail your Tomcat, JVM and OS
versions, also include an accurate description of the environment you
have created and are trying to create.
From what I read in the message, it appears the balancer is sending the
browser a redirect (one of the 30x responses) which in turn changes the
url in the browser's address bar. The OP (if I understand correctly)
would like the url in the browser's address bar not to change at all (no
30x redirect response). The only way I can imagine that working is if
the balancer acts as a reverse proxy, sending each request back to a
different back-end worker. I think we need to see the balancer's config
before we could even begin to offer suggestions.
--David
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
--
Regards
Harsimranjit Singh Kler
?xml version=1.0 encoding=UTF-8?
rules
!-- Redirect to server instance based on RoundRobinRule --
rule className=org.apache.webapp.balancer.rules.RoundRobinRule
serverInstance=1
maxServerInstances=3
tcpListenAddress=127.0.0.1
tcpListenPort=4001
testWebPage=http://localhost:9080/clusterapp/test.jsp;
redirectUrl=http://10.58.116.16:8080/WorkFlowEngine/; /
rule className=org.apache.webapp.balancer.rules.RoundRobinRule
serverInstance=2
maxServerInstances=3
tcpListenAddress=127.0.0.1
tcpListenPort=4002
testWebPage=http://localhost:10080/clusterapp/test.jsp;
redirectUrl=http://10.58.116.16:8080/WorkFlowEngine/; /
rule className=org.apache.webapp.balancer.rules.RoundRobinRule
serverInstance=3
maxServerInstances=3
tcpListenAddress=127.0.0.1
tcpListenPort=4003
testWebPage=http://localhost:11080/clusterapp/test.jsp;
redirectUrl=http://10.58.116.16:8080/WorkFlowEngine/; /
!-- Default redirect if none of the above rules match --
rule className=org.apache.webapp.balancer.rules.AcceptEverythingRule
redirectUrl=http://localhost:8080/balancer/testLB.jsp; /
/rules
?xml version=1.0 encoding=UTF-8?
!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the License); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an AS IS BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--
!-- Example Server Configuration File --
!-- Note that component elements are
Re: Tomcat(5.5) Clustering and Load Balancing.
Harsimranjit singh Kler wrote:
Hi
Here is details:
*Tomcat version*: 5.5.27
*OS*:Window XP
*JDK*:1.6
*Environment Trying to Create* :Load balancing and Clustering on single
Machine using tomcat instances only(balancer Feature) .
*What i have Achieved*:i am running 4 instances of tomcat on ports
8080,9080,10080,11080.So port 8080 tomcat work as balancer and other works
as cluster.(Using Multicasting IP and Port {check server.xml} it works
fine).
attached find server.xml,web.xml,rule.xml of balancer tomcat(8080).
So using balancer feature in tomcat and rule.xml and some customized
classes requests are successfully redirected to one of cluster ie 9080,10080
or 11080 instance.
*Issue*:when request redirected from tomcat balancer(on 8080 port) to any
cluster (tomcat instance on 9080,10080 or 11080 port) URL in address bar
also changed. i dont want to display cluster URL.So how i can achive this?.
i think org.apache.webapp.balancer.BalancerFilter class internally use
SendRedirect() method .
I tried with requestDispatcher..Forward() but it accept only realtive
address.
I believe that David already gave you the basic answer.
From what I read in the message, it appears the balancer is sending the
browser a redirect (one of the 30x responses) which in turn changes the
url in the browser's address bar. The OP (if I understand correctly)
would like the url in the browser's address bar not to change at all (no
30x redirect response). The only way I can imagine that working is if
the balancer acts as a reverse proxy, sending each request back to a
different back-end worker.
I don't think that what you want to achieve can be done (yet) with Tomcat alone.
As a bit of an outsider's answer, I'll add this : from browsing the Tomcat cluster on-line
documentation, it looks to me as a very impresive piece of work, but also as quite a
complex setup.
If your main purpose is to balance the load between a number of back-end Tomcat engines, I
believe that using an Apache httpd front-end with either of the mod_proxy_ajp or the
mod_jk connector, would be much easier to set up, and would provide exactly what you want
: a single hostname:port for the clients, and load-balancing, and fail-over capabilities.
It does that, because it would act like David indicates above, as a reverse proxy. In
this kind of configuration, the clients (browsers e.g.) always talk to the same front-end
server, and receive the responses from that front-end server. The front-end server in
turn passes the requests to one of several back-end servers, and gets the response from
them, which they then send back to the client.
The clients always talk to the front-end server, and see only that one; they never even
know that there are back-end servers, and never see the hostname:port of these back-end
servers.
Maybe the Tomcat cluster configuration does additional things which the front-end balancer
setup cannot do. But that is an area that I really don't know, and maybe someone else can
comment on that.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat(5.5) Clustering and Load Balancing.
On 1/3/11 9:40 AM, Harsimranjit singh Kler wrote: using tomcat instances only(balancer Feature) Why? http://tomcat.apache.org/tomcat-5.5-doc/balancer-howto.html#Using_the_balancer_webapp This is a simple implementation of a rules-based load balancer. It was not designed as a replacement for other load-balancing mechanisms used for high traffic environments. IMHO I'd suggest that it's not suitable for most environments. Just use HTTPD and mod_jk. p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: Tomcat(5.5) Clustering and Load Balancing.
So this means tomcat alone have not sufficent support for Load Balancing and clustering?. but i am able to check successfully: 1)Session maintaince2)Auto Deployment Only thing i am not able to achive to hide Cluster URL on redirection. You main only way to achive is to use apache server HTTPD and connector, mod_jk things ?. On Mon, Jan 3, 2011 at 7:44 PM, Pid p...@pidster.com wrote: On 1/3/11 9:40 AM, Harsimranjit singh Kler wrote: using tomcat instances only(balancer Feature) Why? http://tomcat.apache.org/tomcat-5.5-doc/balancer-howto.html#Using_the_balancer_webapp This is a simple implementation of a rules-based load balancer. It was not designed as a replacement for other load-balancing mechanisms used for high traffic environments. IMHO I'd suggest that it's not suitable for most environments. Just use HTTPD and mod_jk. p -- Regards Harsimranjit Singh Kler
Re: Tomcat(5.5) Clustering and Load Balancing.
On 12/27/10 4:11 AM, Harsimranjit singh Kler wrote: Hi i have testing tomcat clustering on single machine.What i am able to do is i hv 4 tomcat instances 1 work as balancer and 3 as cluster.using Rule.xml in balancer with round robin approach.all requests hits on balancer redirected to on one cluster which is on some different port. when redirecting using sendredirect it display new url that is of cluster.i want some alternate so all request shoud handled at balancer and URL at adress bar not changed. i have tried forward from servelet but that is not accept only realtive URL. I'm sorry, I don't have any idea what you're actually asking. Please read: http://www.catb.org/~esr/faqs/smart-questions.html When you reply, please precisely detail your Tomcat, JVM and OS versions, also include an accurate description of the environment you have created and are trying to create. p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: Tomcat(5.5) Clustering and Load Balancing.
On 12/28/2010 8:33 AM, Pid wrote: On 12/27/10 4:11 AM, Harsimranjit singh Kler wrote: Hi i have testing tomcat clustering on single machine.What i am able to do is i hv 4 tomcat instances 1 work as balancer and 3 as cluster.using Rule.xml in balancer with round robin approach.all requests hits on balancer redirected to on one cluster which is on some different port. when redirecting using sendredirect it display new url that is of cluster.i want some alternate so all request shoud handled at balancer and URL at adress bar not changed. i have tried forward from servelet but that is not accept only realtive URL. I'm sorry, I don't have any idea what you're actually asking. Please read: http://www.catb.org/~esr/faqs/smart-questions.html When you reply, please precisely detail your Tomcat, JVM and OS versions, also include an accurate description of the environment you have created and are trying to create. From what I read in the message, it appears the balancer is sending the browser a redirect (one of the 30x responses) which in turn changes the url in the browser's address bar. The OP (if I understand correctly) would like the url in the browser's address bar not to change at all (no 30x redirect response). The only way I can imagine that working is if the balancer acts as a reverse proxy, sending each request back to a different back-end worker. I think we need to see the balancer's config before we could even begin to offer suggestions. --David - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat(5.5) Clustering and Load Balancing.
Hi i have testing tomcat clustering on single machine.What i am able to do is i hv 4 tomcat instances 1 work as balancer and 3 as cluster.using Rule.xml in balancer with round robin approach.all requests hits on balancer redirected to on one cluster which is on some different port. when redirecting using sendredirect it display new url that is of cluster.i want some alternate so all request shoud handled at balancer and URL at adress bar not changed. i have tried forward from servelet but that is not accept only realtive URL. regards HArry
Re: tomcat 5.5 clustering with JAAS
I add anything to support clustering, dont know if there is a special
configuration for JAAS,
you mean jaas.conf?
JaasConf {
package.MyLoginModule required;
};
thanks
Gustavo Araujo wrote:
Can you send us the logs and the conf. files?
Thanks
2008/11/14 lmk [EMAIL PROTECTED]
Hello,
I use tomcat clustering with session replication, and JAAS module
authentication;
when tomcat instance loose session, the other cannot authenticate the
user.
how I keep the user authenticated on all the tomcat instance?
thanks!
--
View this message in context:
http://www.nabble.com/tomcat-5.5-clustering-with-JAAS-tp20502551p20502551.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Gustavo Campos Araujo
--
View this message in context:
http://www.nabble.com/tomcat-5.5-clustering-with-JAAS-tp20502551p20577077.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 5.5 clustering with JAAS
no ideas..? lmk wrote: Hello, I use tomcat clustering with session replication, and JAAS module authentication; when tomcat instance loose session, the other cannot authenticate the user. how I keep the user authenticated on all the tomcat instance? thanks! -- View this message in context: http://www.nabble.com/tomcat-5.5-clustering-with-JAAS-tp20502551p20557469.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 5.5 clustering with JAAS
Can you send us the logs and the conf. files? Thanks 2008/11/14 lmk [EMAIL PROTECTED] Hello, I use tomcat clustering with session replication, and JAAS module authentication; when tomcat instance loose session, the other cannot authenticate the user. how I keep the user authenticated on all the tomcat instance? thanks! -- View this message in context: http://www.nabble.com/tomcat-5.5-clustering-with-JAAS-tp20502551p20502551.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gustavo Campos Araujo
RE: Tomcat 5.5 Clustering issues
Is the multicast heartbeat picked up over the multicast IP or the Receiver address that is broadcasted? I assume it is the multicast IP as the Receiver is supposedly used for replication only. Andrew R Feller, Analyst Subversion Administrator University Information Systems Louisiana State University [EMAIL PROTECTED] (office) 225.578.3737 -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 9:55 AM To: Tomcat Users List Subject: Re: Tomcat 5.5 Clustering issues the disappeared message appears 3seconds after the member added message. 3 seconds is the timeout you have set, ie, if no multicast heartbeat is received after 3 seconds, consider the member dead. so it seems like multicasting is not working properly on your system. Filip Andrew R Feller wrote: Good morning everyone, I have been trying to get Tomcat clustering between two Tomcat instances set up, but I have run into some issues. After opening the necessary ports in the firewall, routing the broadcast messages to the correct network interface (eth0), and setting up server.xml with the necessary membership information, I get the following from my Tomcat logs: 2007-07-03 09:16:37,247 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.184.173 :4001,catalina,130.39.184.173,4001, alive=30318] 2007-07-03 09:16:37,256 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.184.173:4,001] 2007-07-03 09:16:40,724 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 84.173:4001,catalina,130.39.184.173,4001, alive=30318] What could be the cause of cluster members disappearing immediately after being added? Am I missing anything necessary for setting up clustering / session replication? Relative information about the server is below. Thank you, Andrew Tomcat: 5.5.23 Server: RHEL 5 Server.xml: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster managerClassName=org.apache.catalina.cluster.session.DeltaManager expireSessionsOnShutdown=false useDirtyFlag=true Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=239.39.184.173 mcastPort=45564 mcastFrequency=500 mcastDropTime=3000 / Receiver className=org.apache.catalina.cluster.tcp.ReplicationListener tcpListenAddress=auto tcpListenPort=4001 tcpSelectorTimeout=100 tcpThreadCount=6 / Sender className=org.apache.catalina.cluster.tcp.ReplicationTransmitter replicationMode=synchronous / Valve className=org.apache.catalina.cluster.tcp.ReplicationValve filter=.*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt; / ClusterListener className=org.apache.catalina.cluster.session.ClusterSessionListener / /Cluster IP table rules: -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 4001 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 45564 -d 239.39.184.173 -j ACCEPT No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.9.14/884 - Release Date: 7/2/2007 3:35 PM - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5.5 Clustering issues
correct, on the multicast IP Filip Andrew R Feller wrote: Is the multicast heartbeat picked up over the multicast IP or the Receiver address that is broadcasted? I assume it is the multicast IP as the Receiver is supposedly used for replication only. Andrew R Feller, Analyst Subversion Administrator University Information Systems Louisiana State University [EMAIL PROTECTED] (office) 225.578.3737 -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 9:55 AM To: Tomcat Users List Subject: Re: Tomcat 5.5 Clustering issues the disappeared message appears 3seconds after the member added message. 3 seconds is the timeout you have set, ie, if no multicast heartbeat is received after 3 seconds, consider the member dead. so it seems like multicasting is not working properly on your system. Filip Andrew R Feller wrote: Good morning everyone, I have been trying to get Tomcat clustering between two Tomcat instances set up, but I have run into some issues. After opening the necessary ports in the firewall, routing the broadcast messages to the correct network interface (eth0), and setting up server.xml with the necessary membership information, I get the following from my Tomcat logs: 2007-07-03 09:16:37,247 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.184.173 :4001,catalina,130.39.184.173,4001, alive=30318] 2007-07-03 09:16:37,256 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.184.173:4,001] 2007-07-03 09:16:40,724 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 84.173:4001,catalina,130.39.184.173,4001, alive=30318] What could be the cause of cluster members disappearing immediately after being added? Am I missing anything necessary for setting up clustering / session replication? Relative information about the server is below. Thank you, Andrew Tomcat: 5.5.23 Server: RHEL 5 Server.xml: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster managerClassName=org.apache.catalina.cluster.session.DeltaManager expireSessionsOnShutdown=false useDirtyFlag=true Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=239.39.184.173 mcastPort=45564 mcastFrequency=500 mcastDropTime=3000 / Receiver className=org.apache.catalina.cluster.tcp.ReplicationListener tcpListenAddress=auto tcpListenPort=4001 tcpSelectorTimeout=100 tcpThreadCount=6 / Sender className=org.apache.catalina.cluster.tcp.ReplicationTransmitter replicationMode=synchronous / Valve className=org.apache.catalina.cluster.tcp.ReplicationValve filter=.*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt; / ClusterListener className=org.apache.catalina.cluster.session.ClusterSessionListener / /Cluster IP table rules: -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 4001 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 45564 -d 239.39.184.173 -j ACCEPT No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.9.14/884 - Release Date: 7/2/2007 3:35 PM - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 5.5 Clustering issues
Filip, Perhaps you can explain why each of these log messages are happening every 10 minutes? If this isn't controlled behavior, which I doubt, then something is going on here. =P Thanks for the help, Andy 2007-07-09 09:30:09,497 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=248399] 2007-07-09 09:30:09,509 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 09:30:14,646 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=248399] 2007-07-09 09:40:09,733 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=848625] 2007-07-09 09:40:09,733 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 09:40:15,064 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=848625] 2007-07-09 09:50:09,935 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=150900] 2007-07-09 09:50:09,939 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 09:50:15,362 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=150900] 2007-07-09 10:10:10,800 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=1351729] 2007-07-09 10:10:10,800 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 10:10:15,840 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=1351729] 2007-07-09 10:20:10,832 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=1951799] 2007-07-09 10:20:10,833 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 10:20:16,061 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=1951799] Andrew R Feller, Analyst Subversion Administrator University Information Systems Louisiana State University [EMAIL PROTECTED] (office) 225.578.3737 -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Monday, July 09, 2007 9:34 AM To: Tomcat Users List Subject: Re: Tomcat 5.5 Clustering issues correct, on the multicast IP Filip Andrew R Feller wrote: Is the multicast heartbeat picked up over the multicast IP or the Receiver address that is broadcasted? I assume it is the multicast IP as the Receiver is supposedly used for replication only. Andrew R Feller, Analyst Subversion Administrator University Information Systems Louisiana State University [EMAIL PROTECTED] (office) 225.578.3737 -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 9:55 AM To: Tomcat Users List Subject: Re: Tomcat 5.5 Clustering issues the disappeared message appears 3seconds after the member added message. 3 seconds is the timeout you have set, ie, if no multicast heartbeat is received after 3 seconds, consider the member dead. so it seems like multicasting is not working properly on your system. Filip Andrew R Feller wrote: Good morning everyone, I have been trying to get Tomcat clustering between two Tomcat instances set up, but I have run into some issues. After opening the necessary ports in the firewall, routing the broadcast messages to the correct network interface (eth0), and setting up server.xml with the necessary membership information, I get the following from my Tomcat logs: 2007-07-03 09:16:37,247 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.184.173 :4001,catalina,130.39.184.173,4001, alive=30318] 2007-07-03 09:16:37,256 DEBUG
Re: Tomcat 5.5 Clustering issues
not really, try to lower your mcastFrequency value, and increase your mcastDropTime value Filip Andrew R Feller wrote: Filip, Perhaps you can explain why each of these log messages are happening every 10 minutes? If this isn't controlled behavior, which I doubt, then something is going on here. =P Thanks for the help, Andy 2007-07-09 09:30:09,497 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=248399] 2007-07-09 09:30:09,509 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 09:30:14,646 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=248399] 2007-07-09 09:40:09,733 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=848625] 2007-07-09 09:40:09,733 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 09:40:15,064 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=848625] 2007-07-09 09:50:09,935 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=150900] 2007-07-09 09:50:09,939 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 09:50:15,362 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=150900] 2007-07-09 10:10:10,800 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=1351729] 2007-07-09 10:10:10,800 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 10:10:15,840 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=1351729] 2007-07-09 10:20:10,832 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.186.177 :9001,catalina,130.39.186.177,9001, alive=1951799] 2007-07-09 10:20:10,833 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.186.177:9,001] 2007-07-09 10:20:16,061 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 86.177:9001,catalina,130.39.186.177,9001, alive=1951799] Andrew R Feller, Analyst Subversion Administrator University Information Systems Louisiana State University [EMAIL PROTECTED] (office) 225.578.3737 -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Monday, July 09, 2007 9:34 AM To: Tomcat Users List Subject: Re: Tomcat 5.5 Clustering issues correct, on the multicast IP Filip Andrew R Feller wrote: Is the multicast heartbeat picked up over the multicast IP or the Receiver address that is broadcasted? I assume it is the multicast IP as the Receiver is supposedly used for replication only. Andrew R Feller, Analyst Subversion Administrator University Information Systems Louisiana State University [EMAIL PROTECTED] (office) 225.578.3737 -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 9:55 AM To: Tomcat Users List Subject: Re: Tomcat 5.5 Clustering issues the disappeared message appears 3seconds after the member added message. 3 seconds is the timeout you have set, ie, if no multicast heartbeat is received after 3 seconds, consider the member dead. so it seems like multicasting is not working properly on your system. Filip Andrew R Feller wrote: Good morning everyone, I have been trying to get Tomcat clustering between two Tomcat instances set up, but I have run into some issues. After opening the necessary ports in the firewall, routing the broadcast messages to the correct network interface (eth0), and setting up server.xml with the necessary membership information, I get the following from my Tomcat logs: 2007-07-03 09:16:37,247 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member
Re: Tomcat 5.5 Clustering issues
the disappeared message appears 3seconds after the member added message. 3 seconds is the timeout you have set, ie, if no multicast heartbeat is received after 3 seconds, consider the member dead. so it seems like multicasting is not working properly on your system. Filip Andrew R Feller wrote: Good morning everyone, I have been trying to get Tomcat clustering between two Tomcat instances set up, but I have run into some issues. After opening the necessary ports in the firewall, routing the broadcast messages to the correct network interface (eth0), and setting up server.xml with the necessary membership information, I get the following from my Tomcat logs: 2007-07-03 09:16:37,247 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Replication member added:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.184.173 :4001,catalina,130.39.184.173,4001, alive=30318] 2007-07-03 09:16:37,256 DEBUG [org.apache.catalina.cluster.tcp.DataSender] - Create sender [/130.39.184.173:4,001] 2007-07-03 09:16:40,724 INFO [org.apache.catalina.cluster.tcp.SimpleTcpCluster] - Received member disappeared:org.apache.catalina.cluster.mcast.McastMember[tcp://130.39.1 84.173:4001,catalina,130.39.184.173,4001, alive=30318] What could be the cause of cluster members disappearing immediately after being added? Am I missing anything necessary for setting up clustering / session replication? Relative information about the server is below. Thank you, Andrew Tomcat: 5.5.23 Server: RHEL 5 Server.xml: Cluster className=org.apache.catalina.cluster.tcp.SimpleTcpCluster managerClassName=org.apache.catalina.cluster.session.DeltaManager expireSessionsOnShutdown=false useDirtyFlag=true Membership className=org.apache.catalina.cluster.mcast.McastService mcastAddr=239.39.184.173 mcastPort=45564 mcastFrequency=500 mcastDropTime=3000 / Receiver className=org.apache.catalina.cluster.tcp.ReplicationListener tcpListenAddress=auto tcpListenPort=4001 tcpSelectorTimeout=100 tcpThreadCount=6 / Sender className=org.apache.catalina.cluster.tcp.ReplicationTransmitter replicationMode=synchronous / Valve className=org.apache.catalina.cluster.tcp.ReplicationValve filter=.*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt; / ClusterListener className=org.apache.catalina.cluster.session.ClusterSessionListener / /Cluster IP table rules: -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 4001 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 45564 -d 239.39.184.173 -j ACCEPT No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.9.14/884 - Release Date: 7/2/2007 3:35 PM - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5.5 Clustering Problem
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/onjava/2004/04/14/clustering.html)
Which version of tomcat 5.5 you use? Please, use Tomcat 5.5.17 or
better coming 5.5.20.
regards,
peter
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 tomcat.
2006-09-25 22:11:43,718 (WebPortalLogger.java:44) - 923014548 : 1
2006-09-25 22:11:43,718 (WebPortalLogger.java :44) - Requested server
instance did not match..
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - getServerInstance
() : 1
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) -
getMaxServerInstances()
: 3
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - 1876138717 : 2
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - Requested server
instance did not match..
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - getServerInstance
() : 2
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) -
getMaxServerInstances()
: 3
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - 747657098 : 3
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - Requested server
instance did not match..
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - getServerInstance
() : 3
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) -
getMaxServerInstances()
: 3
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - 388758323 : 3
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - Requested server
instance match..
java.lang.IllegalArgumentException: Required property
mcastClusterDomain
is missing.
at org.apache.catalina.cluster.mcast.McastService.hasProperty (
McastService.java:252)
at org.apache.catalina.cluster.mcast.McastService.setProperties(
McastService.java:140)
at common.utilities.ServerUtil.isServerAlive(ServerUtil.java:36)
at
org.apache.webapp.balancer.rules.BaseLoadBalancingRule.isServerAlive (
BaseLoadBalancingRule.java:89)
at org.apache.webapp.balancer.rules.RandomRedirectRule.matches(
RandomRedirectRule.java:41)
at org.apache.webapp.balancer.RuleChain.evaluate
(RuleChain.java:100)
at org.apache.webapp.balancer.BalancerFilter.doFilter(
BalancerFilter.java:118)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter (
ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(
StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(
StandardContextValve.java :178)
at org.apache.catalina.core.StandardHostValve.invoke(
StandardHostValve.java:126)
at
org.apache.catalina.cluster.session.JvmRouteBinderValve.invoke(
JvmRouteBinderValve.java:208)
at org.apache.catalina.cluster.tcp.ReplicationValve.invoke (
ReplicationValve.java:346)
at org.apache.catalina.valves.ErrorReportValve.invoke(
ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(
StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(
CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(
Http11Processor.java:869)
at
org.apache.coyote.http11.Http11BaseProtocol
$Http11ConnectionHandler.processConnection(
Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(
PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(
LeaderFollowerWorkerThread.java :80)
at org.apache.tomcat.util.threads.ThreadPool
$ControlRunnable.run(
ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) - Time taken to check
connection: 0 ms.
** THE SERVER IS NOT AVAILABLE **
2006-09-25 22:11:43,734 (WebPortalLogger.java:44) -
RandomRedirectRule --
isAlive : false
Below is my server.xml configuration for Tomcat 5.5: (only the
receiver.tcpListenPort was modified for the other instances.)
Server port=8011
shutdown=SHUTDOWN
GlobalNamingResources
Resource name=UserDatabase auth=Container
type=org.apache.catalina.UserDatabase
description=User database that can be updated
and saved
factory=
org.apache.catalina.users.MemoryUserDatabaseFactory
pathname=conf/tomcat-users.xml /
/GlobalNamingResources
Service
