Hi, I looked in the issue. we do few things in our session replication code..
- set our own simpleTCPCluster implementaiton (to set the sessionManager) - We have extended the default tomcat sessionManager. - There we are making use of CarbonClusteringAgent to send messages , instead of using tcpCluster by tomcat default session manager. AFAIU, the code should work, even with new clusteringManager. However functionality seems to be broken. :) As per my current understanding, we dont need a rewrite.... Kishanthan, please add if my understanding is wrong.. thanks, --Pradeep On Thu, Aug 1, 2013 at 8:26 PM, Afkham Azeez <[email protected]> wrote: > Looks like the old implementation directly uses Tomcat+Tribes. Looks like > we would need to rewrite it. > > -- > *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* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Pradeep Fernando* Associate Technical Lead;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
