From: Nicolas R. <nic...@gm...> - 2013-06-14 06:04:19
|
Hi, The recommended way is to not use sessions if you can : - use discardCookies and forwardCookies directives to ensure no cookies are stored in esigate. With this, esigate will not create sessions at all (stateless) - use several instances with any loadbalancer - You can share the cache between instances using memcached or a replicated ehcache (cacheStorage directive) for better hit ratio, but this is not required. - Session replication can be set in backend servers (your applications) if necessary If you really need cookie storage in esigate, the session replication can be set up in your servlet container using standard documentation. You can also implement a shared cookieManager. Please tell us if this solves your issue :-) Nicolas http://www.esigate.org/reference.html#Configuration_file Le 14 juin 2013 à 07:44, 謝福明 <aug...@ch...> a écrit : > Hi > > How to setup ESIGate cluster with session replication?? > Have any documentation describes this? > > Thanks. > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev_______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users |