You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Lu Jiang (JIRA)" <ji...@apache.org> on 2009/11/17 10:36:40 UTC

[jira] Created: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

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


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		
# Loads the Jakarta Tomcat Connector module

JkWorkersFile conf/workers.properties
# Tells the module the location of the workers.properties file

JkLogFile     logs/mod_jk.log
# Specifies the location for this module's specific log file

JkLogLevel    debug
# Sets the module's log level to info

JkMount /* loadbalancer
# Sets a mount point from a context to a Tomcat worker. In this case will allow access (forward the request) to the console.

3.
For NODE02:

  (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
     ClusterNodeName=NODE02
  (2)Modify GERONIMO_HOME/var/catalina/server.xml.
<Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
    

   For NODE03:
  (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
     ClusterNodeName=NODE03
  (2)Modify GERONIMO_HOME/var/config/config.xml.
<Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 


     
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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
Refer to the attachment:excerptFromConfig1.xml and excertFromConfig2.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 Simple servlet-examples-cluster-plan2.xml as a deploy plan.
deploy the application servlet-examples-cluster-server3.war using Simple 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Attachment:     (was: servlet-examples-cluster-plan2.xml)

> 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
>         Attachments: node02ExcerptFromConfig.xml.txt, node03ExcerptFromConfig.xml.txt, realm.xml, servlet-examples-cluster-plan2.xml, servlet-examples-cluster-plan3.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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Attachment: servlet-examples-cluster-server3.war
                servlet-examples-cluster-server2.war
                realm.xml

Deploy The realm.xml before deploy the servlet cluster example application.


> 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
>         Attachments: realm.xml, servlet-examples-cluster-server2.war, servlet-examples-cluster-server3.war
>
>
> 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		
> # Loads the Jakarta Tomcat Connector module
> JkWorkersFile conf/workers.properties
> # Tells the module the location of the workers.properties file
> JkLogFile     logs/mod_jk.log
> # Specifies the location for this module's specific log file
> JkLogLevel    debug
> # Sets the module's log level to info
> JkMount /* loadbalancer
> # Sets a mount point from a context to a Tomcat worker. In this case will allow access (forward the request) to the console.
> 3.
> For NODE02:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE02
>   (2)Modify GERONIMO_HOME/var/catalina/server.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> Refer to the attachment:excerptFromConfig1.xml and excertFromConfig2.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 Simple servlet-examples-cluster-plan2.xml as a deploy plan.
> deploy the application servlet-examples-cluster-server3.war using Simple 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Attachment: servlet-examples-cluster-plan3.xml
                servlet-examples-cluster-plan2.xml

Hi,Ivan
  According to your suggestion,I have updated the deploy plan. 
  (1)A TomcatClusterManager gbean is is defined. 
	<gbean class="org.apache.geronimo.tomcat.cluster.ClusterManagerGBean" name="TomcatClusterManager" >
            <attribute name="className">org.apache.catalina.ha.session.DeltaManager</attribute>
            <attribute name="initParams">name=${clusterName}
        channelSendOptions=6
        expireSessionsOnShutdown=false
        notifyListenersOnReplication=true
        mapSendOptions=6</attribute>
        </gbean>
    (2)In CatalinaClusterGBean,delete managerclassname attribute and give a refernce to ClusterManager Gbean.
<reference name="ClusterManager">
            <name>TomcatClusterManager</name>
        </reference>
  Howerver,session replication still fails.

> 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
>         Attachments: node02ExcerptFromConfig.xml.txt, node03ExcerptFromConfig.xml.txt, realm.xml, servlet-examples-cluster-plan2.xml, servlet-examples-cluster-plan3.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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Description: 
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.
<Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
    

   For NODE03:
  (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
     ClusterNodeName=NODE03
  (2)Modify GERONIMO_HOME/var/config/config.xml.
<Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 


     
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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
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

  was:
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		
# Loads the Jakarta Tomcat Connector module

JkWorkersFile conf/workers.properties
# Tells the module the location of the workers.properties file

JkLogFile     logs/mod_jk.log
# Specifies the location for this module's specific log file

JkLogLevel    debug
# Sets the module's log level to info

JkMount /* loadbalancer
# Sets a mount point from a context to a Tomcat worker. In this case will allow access (forward the request) to the console.

3.
For NODE02:

  (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
     ClusterNodeName=NODE02
  (2)Modify GERONIMO_HOME/var/catalina/server.xml.
<Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
    

   For NODE03:
  (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
     ClusterNodeName=NODE03
  (2)Modify GERONIMO_HOME/var/config/config.xml.
<Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 


     
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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
Refer to the attachment:excerptFromConfig1.xml and excertFromConfig2.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 Simple servlet-examples-cluster-plan2.xml as a deploy plan.
deploy the application servlet-examples-cluster-server3.war using Simple 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


> 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
>         Attachments: realm.xml, servlet-examples-cluster-server2.war, servlet-examples-cluster-server3.war
>
>
> 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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Attachment:     (was: servlet-examples-cluster-plan3.xml)

> 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
>         Attachments: node02ExcerptFromConfig.xml.txt, node03ExcerptFromConfig.xml.txt, realm.xml, servlet-examples-cluster-plan2.xml, servlet-examples-cluster-plan3.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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Resolved: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Ivan (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan resolved GERONIMO-4955.
----------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.5

For 2.1.4, it should be fixed after merging the patch of Geronimo-4187 to 2.1 branch.

> 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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Attachment: servlet-examples-cluster-plan3.xml
                servlet-examples-cluster-plan2.xml

> 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
>         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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Attachment:     (was: servlet-examples-cluster-plan3.xml)

> 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
>         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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Closed: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
     [ 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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Commented: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Ivan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778879#action_12778879 ] 

Ivan commented on GERONIMO-4955:
--------------------------------

Hi, Lu Jiang:
Just try it with Geronimo 2.2, the unicast does work from my side. But some configurations need to be updated
1. For Geronimo 2.2, so far, I think that you should only set cluster on the web application level, which means that all the configurations are in the deployement plans.
2. For some API changes in Tomcat 6.0.20, setManagerClassName method is deprecated, so you need to define clustermanager gbean in the plan file, not use the managerclassname attribute in the CatalinaClusterGBean defintion.

> 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
>         Attachments: node02ExcerptFromConfig.xml.txt, node03ExcerptFromConfig.xml.txt, realm.xml, servlet-examples-cluster-plan2.xml, servlet-examples-cluster-plan3.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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Attachment: simple-servlet-examples-cluster-plan2.xml
                node03ExcerptFromConfig.xml.txt
                node02ExcerptFromConfig.xml.txt

> 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
>         Attachments: node02ExcerptFromConfig.xml.txt, node03ExcerptFromConfig.xml.txt, realm.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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Attachment: servlet-examples-cluster-plan3.xml

> 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
>         Attachments: node02ExcerptFromConfig.xml.txt, node03ExcerptFromConfig.xml.txt, realm.xml, servlet-examples-cluster-plan2.xml, servlet-examples-cluster-plan3.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.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE03" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> 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.


[jira] Updated: (GERONIMO-4955) Tomcat Clustering via Uni Cast doesn't work

Posted by "Lu Jiang (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lu Jiang updated GERONIMO-4955:
-------------------------------

    Comment: was deleted

(was: Deploy The realm.xml before deploy the servlet cluster example application.
)

> 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
>         Attachments: realm.xml, servlet-examples-cluster-server2.war, servlet-examples-cluster-server3.war
>
>
> 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		
> # Loads the Jakarta Tomcat Connector module
> JkWorkersFile conf/workers.properties
> # Tells the module the location of the workers.properties file
> JkLogFile     logs/mod_jk.log
> # Specifies the location for this module's specific log file
> JkLogLevel    debug
> # Sets the module's log level to info
> JkMount /* loadbalancer
> # Sets a mount point from a context to a Tomcat worker. In this case will allow access (forward the request) to the console.
> 3.
> For NODE02:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE02
>   (2)Modify GERONIMO_HOME/var/catalina/server.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>     
>    For NODE03:
>   (1)Modify GERONIMO_HOME/var/config/config-substitutions.properties
>      ClusterNodeName=NODE03
>   (2)Modify GERONIMO_HOME/var/config/config.xml.
> <Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE02" > 
>      
> 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<module name="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car"> 
> Refer to the attachment:excerptFromConfig1.xml and excertFromConfig2.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 Simple servlet-examples-cluster-plan2.xml as a deploy plan.
> deploy the application servlet-examples-cluster-server3.war using Simple 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.