I like it too but if the sticky session is configured at the Hazelcast
level, you need to have a loadbalancer configured to support sticky session
in front of the webserver . If there is no loadbalancer or no sticky
session configured and two webserver are configured, the user that will
log-out from a webserver will not be log-out from the second websever
because the expired session generated by a log-out will not be
propagated by Hazelcast.

So in other term - set the sticky-session parameter to true if a
loadbalancer is configured to support sticky session, if not set the
sticky-session parameter to false


2013/12/14 Julien Dubois <notifications@github.com>

> In app/templates/src/main/java/package/conf/_WebConfigurer.java:
>
> > @@ -91,7 +91,7 @@ private void initClusteredHttpSessionFilter(ServletContext servletContext, EnumS
> >          // on a node, entry for this session on all other nodes is invalidated.
> >          // You have to know how your load -balancer is configured before
> >          // setting this parameter. Default is true.
> > -        parameters.put("sticky-session", "true");
> > +        parameters.put("sticky-session", "false");
>
> still, I like the sticky sessions...
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jhipster/generator-jhipster/pull/57/files#r8352146>
> .
>