Re: Tomcat session replication/cluster

Peter Rossbach Thu, 22 Jun 2006 05:47:04 -0700

Hmm,

look at o.a.c.cluster.tcp.SimpleTcpCluster


L 626ff
    private String getManagerName(String name, Manager manager) {
        String clusterName = name ;
        if(getContainer() instanceof Engine) {
            Container context = manager.getContainer() ;
            if(context != null && context instanceof Context) {
                Container host = ((Context)context).getParent();
                if(host != null && host instanceof Host)
                    clusterName = host.getName()  + name ;
            }
        }
        return clusterName;
    }


You see we append "hostname + context" as cluster engine container.

Peter



Am 22.06.2006 um 10:32 schrieb Pid:

Filip Hanik - Dev Lists wrote:
if the cluster is put in the engine element, the context names are
prefixed with the engine name, since you can have multiplecontexts with
the same name in different host
when reloading a context, you'll get these errors cause thecontext is
not available during the reload
this will be fixed with the new Apache Tribes module
Filip
I understand that the context is not available during reload. After
reload has completed, the error persists.
My Engine name is Catalina, it looks like the cluster isn't sendingthe
engine name, but the context name, appended to itself.
You're implying that it should send Catalina+website1, but it'ssending
website1+website1 instead.

After startup:
Node1 sees Node2 send "website2"
Node2 sees Node1 send "website1"

After context on Node1 is finished reloading:
Node1 sees Node2 send "website2"
Node2 sees Node1 send "website1website1"

I think that the context name is being appended to itself.
Pid wrote:
I'm seeing an issue on 5.5.17 with a 2 node cluster config.
When a context is reloaded, it sends the context node nameincorrectly
to the cluster.
E.g. context is called "website1"

SEVERE: Context manager doesn't exist:website1website1
The config I'm using is exactly the same as the default fromserver.xml,
except the cluster is defined in Engine, rather than each Host.




Filip Hanik - Dev Lists wrote:
also, use Tomcat 5.5.17

Sean O'Reilly wrote:
Hi,
I am trying to get in-memory session replication working and amtesting
running 3 seperate tomcat instances on the same server.

I am using tomcat-5.5.15 and apache-2.0.54 with jk2.
Whenever i run my test app although it should be doing round-robin loadbalancing it doesn't switch to another instance of tomcat untiltheeighth request and does not appear to have sent the sessioninformation
across as the session ID changes.

Here are my server.xml and workers2.properties files

server.xml

<Server port="8005" shutdown="SHUTDOWN">

  <Listener
className="org.apache.catalina.core.AprLifecycleListener" />
  <Listener
className="org.apache.catalina.mbeans.ServerLifecycleListener" />
  <Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
/>
  <Listener
className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
  
  <GlobalNamingResources>

    
    <Environment name="simpleValue" type="java.lang.Integer"
value="30"/>

    
    <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 name="Catalina">


    



    
    

    
    <Connector port="8009"                enableLookups="false"
redirectPort="8443"
protocol="AJP/1.3" />

    

    


    <Engine name="Standalone" defaultHost="localhost"
jvmRoute="Tomcat5A"> 

      

      

<RealmclassName="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase"/>

      


      

      

      

      
      <Host name="localhost" appBase="webapps"
       unpackWARs="true" autoDeploy="true"
       xmlValidation="false" xmlNamespaceAware="false">

                             
               <Cluster
className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
managerClassName="org.apache.catalina.cluster.session.DeltaManager"
                 expireSessionsOnShutdown="false"
                 useDirtyFlag="true"
                 notifyListenersOnReplication="true">

            <Membership
className="org.apache.catalina.cluster.mcast.McastService"
                mcastAddr="228.0.0.4"
                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="pooled"
                ackTimeout="15000"/>

            <Valve
className="org.apache.catalina.cluster.tcp.ReplicationValve"
filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;"/>
                               <Deployer
className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
                      tempDir="/tmp/war-temp/"
                      deployDir="/tmp/war-deploy/"
                      watchDir="/tmp/war-listen/"
                      watchEnabled="false"/>
                                  <ClusterListener
className="org.apache.catalina.cluster.session.ClusterSessionListener"/>
        </Cluster>

        

        

        

        

      </Host>

    </Engine>

  </Service>

</Server>


workers2.properties

[logger.apache2]
file="/etc/httpd/conf/logs/error.log"
level=INFO
debug=1

# Config settings
[config]
file=/etc/httpd/conf/workers2.properties
debug=0

# Shared memory file settings
[shm]
file=/etc/httpd/conf/jk2.shm
size=100000

# Communcation channel settings for "Tomcat5A"
[channel.socket:localhost:8009]
host=localhost
port=8009
tomcatId=Tomcat5A
group=balanced
lb_factor=1
route=Tomcat5A


# Declare a Tomcat5A worker
[ajp13:localhost:8009]
channel=channel.socket:Tomcat5A


# Communcation channel settings for "Tomcat5B"
[channel.socket:localhost:8010]
host=localhost
port=8010
tomcatId=Tomcat5B
group=balanced
lb_factor=1
route=Tomcat5B


# Declare a Tomcat5B worker
[ajp13:localhost:8010]
channel=channel.socket:Tomcat5B


# Communcation channel settings for "Tomcat5C"
[channel.socket:localhost:8011]
host=localhost
port=8011
tomcatId=Tomcat5C
group=balanced
lb_factor=1
route=Tomcat5C


# Declare a Tomcat5C worker
[ajp13:localhost:8011]
channel=channel.socket:Tomcat5C

# Load balanced Worker
[lb:balanced]
worker=ajp13:localhost:8009
worker=ajp13:localhost:8010
worker=ajp13:localhost:8011
timeout=90
attempts=3
recovery=30
stickySession=0
noWorkerMsg=Server Busy please retry later.
noWorkerCodeMsg=503

# URI mappings for the tomcat worker
# Map the "jsp-examples" web application context to the webserver URI
space
[uri:/jsp-examples/*]
info= Mapping for jsp-examples context for tomcat
context=/jsp-examples
group=balanced

[shm]
file=/etc/httpd/conf/jk2.shm
size=1000000

[uri:/servlets-examples/*]
context=/servlets-examples
group=balanced

# Define a status worker
[status:]

# Status URI mapping
[uri:/jkstatus/*]
group=status
obviously the server.xml files on the other 2 instances oftomcat are
the same except the ports and jvmRoute have been changed.


can anyone see where i am going wrong ?

Thanks
---------------------------------------------------------------------
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 session replication/cluster

Reply via email to