Currently we are using a manager(CarbonTomcatSessionManager) to handle sessions of webapps, but it is not clusterable. For this purpose[1] tomcat uses two different managers, DeltaManager and BackupManager. DeltaManager replicates sessions to all the nodes in the cluster whereas BackupManager replicates to one backup node(primary-secondary session replication).
I tried with the DeltaManager as an initial approach, by making CarbonTomcatSessionManager to extend DeltaManager, and it works fine. Few things to note, 1. We can use a TomcatValve to initiate the session replication as same as ReplicatonValve[2] of tomcat. 2. For clustering, Tomcat uses Tribes as the underlying communication framework. Since we already use this in Axis2 clustering, we can use the same to send session replication messages(Using Axis2 ClusteringAgent). 3. With Axis2 ClusteringAgent, the sending messages has to extend the ClusteringMessage class. But with tomcat, there is a separate cluster message for session replication called SessionMessage. We have to handle both these and have one which is common to both world. 4. Other configuration details are same as what is mentioned here[1]. Your comments are welcome on this approach. Thanks, Kishanthan. [1] http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html [2] http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/ha/tcp/ReplicationValve.html On Wed, Apr 25, 2012 at 10:04 PM, Kishanthan Thangarajah < [email protected]> wrote: > > > On Tue, Apr 24, 2012 at 7:31 PM, Isuru Suriarachchi <[email protected]>wrote: > >> +1, We've almost completed all the roadmap items for AS 4.5.0. As we've >> not feature freezed yet, we can look into this. >> >> Thanks, >> ~Isuru >> >> >> On Tue, Apr 24, 2012 at 7:15 PM, Afkham Azeez <[email protected]> wrote: >> >>> With the Tomcat OSGification completed, we can finally implement support >>> for HTTP session replication. We could tie into the underlying Tribes >>> framework to do this. I believe we should write a Tomcat >>> HttpSessionReplicationValve which will handle replication of sessions. >>> Kishanthan can you own this? Even though this may look like an AppServer >>> roadmap item, this is something that will get used throughout the platform. >> >> > +1, I will own this. > > Thanks, > Kishanthan. > >> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> >> >> >> -- >> Isuru Suriarachchi >> Technical Lead >> WSO2 Inc. http://wso2.com >> email : [email protected] >> blog : http://isurues.wordpress.com/ >> >> lean . enterprise . middleware >> >> > > > -- > *Kishanthan Thangarajah* > Software Engineer, > Development Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com* > Twitter - *http://twitter.com/kishanthan* > > -- *Kishanthan Thangarajah* Software Engineer, Development Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
