We've found that some of the cache operations like update and delete take time to replicate. They eventually become consistent. Based on network traffic and other parameters the time it takes to become consistent could vary. Therefore it is recommended that sticky sessions are enabled.
On Wed, Dec 17, 2014 at 3:09 PM, Darshana Gunawardana <[email protected]> wrote: > > Hi folks, > > What is our stand for $subject? > > AFAIK, the new authentication framework doesn't depends on the tomcat > session, so it doesn't required to have sticky session enable in the load > balancer. (May be OpenID have a exception) > > But for management console operations, its required enable sticky > sessions.. > > What are the other concerns, if we disable sticky sessions in the load > balancer? > > Thanks, > Darshana > -- > Regards, > > > *Darshana Gunawardana*Software Engineer > WSO2 Inc.; http://wso2.com > > *E-mail: [email protected] <[email protected]>* > *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware > -- Thanks & Regards, *Johann Dilantha Nallathamby* Associate Technical Lead & Product Lead of WSO2 Identity Server Integration Technologies Team WSO2, Inc. lean.enterprise.middleware Mobile - *+94777776950* Blog - *http://nallaa.wordpress.com <http://nallaa.wordpress.com>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
