Hi, So that means Jaggery uses HttpSession in Java Servlet API.
I hope following config also work with API Manager: https://docs.wso2.org/display/AS521/Clustering+and+Http+Session+Replication If the app is storing any non-serializable objects, then it's a problem with app and we should fix it. On Mon, Mar 17, 2014 at 7:20 PM, Ruchira Wageesha <[email protected]> wrote: > Hi Amila, > > Since Jaggery is based on Tomcat, whatever the session replication > mechanism available for Java webapps, should be valid for Jaggery as > well[1]. But, I doubt whether it will work smoothly if there are any > non-serializable objects in the session. > > /Ruchira > > [1] https://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html > > > On Mon, Mar 17, 2014 at 4:59 PM, Amila Maha Arachchi <[email protected]>wrote: > >> Hi, >> >> Assume the scenario of two API Manager instances fronted with WSO2 ELB. >> While user is logged in and working in publisher or store app, all his >> requests are going to the same node where the session is established. >> >> At this moment if we kill one node, requests will start going to the >> other node, but theres no session available in it. >> >> My question is: >> Is session replication valid for jaggery apps? >> >> Regards, >> AmilaM. >> >> -- >> *Amila Maharachchi* >> Senior Technical Lead >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> > > > -- > > *Ruchira Wageesha**Associate Technical Lead* > *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* > > *email: [email protected] <[email protected]>, blog: > ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, > mobile: +94 77 5493444 <%2B94%2077%205493444>* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Isuru Perera Senior Software Engineer | WSO2, Inc. | http://wso2.com/ Lean . Enterprise . Middleware about.me/chrishantha
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
