Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 72296 invoked from network); 4 Feb 2010 07:08:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Feb 2010 07:08:52 -0000 Received: (qmail 98366 invoked by uid 500); 4 Feb 2010 07:08:51 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 98221 invoked by uid 500); 4 Feb 2010 07:08:50 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 98212 invoked by uid 99); 4 Feb 2010 07:08:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Feb 2010 07:08:50 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Feb 2010 07:08:49 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 1A3D229A0028 for ; Wed, 3 Feb 2010 23:08:29 -0800 (PST) Message-ID: <1980794887.31581265267309106.JavaMail.jira@brutus.apache.org> Date: Thu, 4 Feb 2010 07:08:29 +0000 (UTC) From: "Rex Wang (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Closed: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work In-Reply-To: <468879777.1258450600128.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang closed GERONIMO-4955. ------------------------------ closing it. > Tomcat Clustering via Uni Cast doesn't work > ------------------------------------------- > > Key: GERONIMO-4955 > URL: https://issues.apache.org/jira/browse/GERONIMO-4955 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Clustering > Affects Versions: 2.1.4, 2.2 > Environment: Server 1: > OS:Windows Vista amd64 6.0 build 6001 Service Pack 1 > Geronimo: 2.2-SNAPSHOT Build 2009.09.28-12:26:20.913+0800 > JVM: JDK 6 > Server 2: > OS: Windows Server 2008 amd64 Version 6.0 build 6002 Service Pack 2 > Geronimo:2.2-SNAPSHOT 2009.09.28-12:26:20.913+0800 > JVM:JDK 6 > Reporter: Lu Jiang > Fix For: 2.1.5 > > Attachments: node02ExcerptFromConfig.xml.txt, node03ExcerptFromConfig.xml.txt, realm.xml, servlet-examples-cluster-plan2.xml, servlet-examples-cluster-plan3.xml, servlet-examples-cluster-server2.war, servlet-examples-cluster-server3.war, simple-servlet-examples-cluster-plan2.xml > > > Below is a senario: > 1.Install geronimo 2.2 on two machines,namely 9.186.10.60(NODE02),9.186.10.89(NODE03). > 2.Configure Apache http server. > (1)add mod_jk.so to ApacheHttpServer_HOME/modules. > (2)add or modify workers.properties under ApacheHttpServer_HOME/conf like > worker.list=loadbalancer,status > worker.maintain=60 > worker.NODE02.port=8009 > worker.NODE02.host=9.186.10.60 > worker.NODE02.type=ajp13 > worker.NODE02.lbfactor=1 > worker.NODE03.port=8009 > worker.NODE03.host=9.186.10.89 > worker.NODE03.type=ajp13 > worker.NODE03.lbfactor=1 > worker.loadbalancer.type=lb > worker.loadbalancer.balance_workers=NODE02,NODE03 > worker.loadbalancer.sticky_session=1 > worker.status.type=status > (3)add information below to ApacheHttpServer_HOME/conf/ > LoadModule jk_module modules/mod_jk.so > JkWorkersFile conf/workers.properties > JkLogFile logs/mod_jk.log > JkLogLevel debug > JkMount /* loadbalancer > 3. > For NODE02: > (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties > ClusterNodeName=NODE02 > (2)Modify GERONIMO_HOME/var/catalina/server.xml. > > > For NODE03: > (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties > ClusterNodeName=NODE03 > (2)Modify GERONIMO_HOME/var/config/config.xml. > > > 3. > I tried two ways to enable unicast clustering..One is to enable it in config.xml and the other is to enable it in the deploy plan. > (Deploy the ream.xml first cause we have security realm configuration in the application ) > The first way:(enable it in config.xml) > On the two server,separately add GBean information under > Refer to the attachment:node02ExcerptFromConfig.xml and node03ExcertFromConfig.xml > Then deploy the application servlet-examples-cluster-server2.war using Simple simple-servlet-examples-cluster-plan2.xml as a deploy plan. > deploy the application servlet-examples-cluster-server3.war using Simple simple-servlet-examples-cluster-plan3.xml as a deploy plan. > The second way:(enable it in deploy plan) > Without modification to config.xml,deploy the application directly. > deploy the application servlet-examples-cluster-server2.war using servlet-examples-cluster-plan2.xml as a deploy plan. > deploy the application servlet-examples-cluster-server3.war using servlet-examples-cluster-plan3.xml as a deploy plan. > Expected: > Session will be replicated .When node 02 fails,the node 03 will be the back up.and vice versa. > But currently both way don't work, when node2 fails ,session is not replicated to node03 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.