Yes, that's true. I finally found the old email thread. I don't remember how it started ..probably related to a support case:

Steps to reproduce:
1) Start two instances of EPP5 in cluster
2) Start Apache with mod_jk as loadbalancer with sticky session enabled
3) Login as root in loadbalancer and going to
http://loadbalancer/portal/private/FailoverPortal/organization/management.
Actually I am seeing list of users in User management
4) Click to Group management
5) Failover active node which served requests from loadbalancer
6) Click to group "Platform" in group list menu. Now I expected to see
the "Platform" group details and it's subgroups. But I am redirected
back to "User management" and I am seeing list of users. So Organization
portlet is in default state and his actual UI state is lost.

And when <distributable /> in exoadmin.war is enabled, then behaviour is
correct and I am seeing details of "Platform" group in group management
menu. And I am not redirected to "User management".

I think there is more similar scenarios with <distributable /> in
exoadmin.war disabled. Problem is that state of WebUI administration
portlets, changed by ajax requests, is lost after failover and so these
admin portlets are always in default state after doing failover.


----- "Julien Viet" <julien@julienviet.com> wrote:
> but exoadmin is always accessed through the portal context, right ?

>

>

>
On Nov 24, 2010, at 10:53 PM, Prabhat Jha wrote:

>
> By default, distributable for exoadmin.war and other compressed .war files is not set but it is set for 02portal.war.  For portal admin UI to work properly in cluster, it had to be enabled for exoadmin.war
>
> ----- "Julien Viet" <julien@julienviet.com> wrote: 
> > can you clarify :-) ?

> >
On Nov 24, 2010, at 10:25 PM, Prabhat Jha wrote:

> > While we are on this topic, I think we should also clarify on  <distributable/> configuration . I would have to dig previous mail threads but I think it needed changing in three .war for everything to work well in cluster.
> > 
> > 
> > ----- "Thomas Heute" <theute@redhat.com> wrote: 
> > > I also agree
> > > 
> > > On 11/24/2010 04:16 PM, Nicolas Filotto wrote:
Fully agree with you
> > > 
> > >
> > > On Wed, Nov 24, 2010 at 3:05 PM, Julien Viet <julien@julienviet.com> wrote:
> > >
Hi,
> > > 
> > > I've been looking a bit at the Tomcat default configuration (the context.xml) and improved id : https://jira.jboss.org/browse/GTNPORTAL-1688
> > > 
> > > I was looking also at web.xml and a few war files have a session timeout value that is 30 minutes (portal.war and a 2 others).
> > > 
> > > This value matches the default tomcat and jboss value declared in the default.xml.
> > > 
> > > I would like to remove the value in web.xml because
> > > 
> > > 1/ the change has no effect on the current configuration
> > > 2/ it simplifies the timeout configuration of those when touching the value that is set in the default web.xml
> > > 
> > > When one portal access is done, not only the portal war file has sessions created by usually also the portlets that the portal access: an anonymous hit on the default page creates 3 sessions in 3 war files. This change would per 2/ allow to have change it by changing the default value.
> > > 
> > > Also having a web.xml timeout different than the portal one does not make much sense as the war files are accessed by a request dispatch from the portal war. So any war file accessed this way will have its session bound to the portal one. A greater value does not have sense, a lower value can have sense but usually one would do that by specifying that value directly in the web.xml of the portlet application war file, so his configuration would not be much affected.
> > > 
> > > Then is a setting for a particular war file is needed, one can still make the setup in any web.xml he wants.
> > > 
> > > let me know if that makes sense to you
> > > 
> > > Julien
> > > _______________________________________________
> > > gatein-dev mailing list
> > > gatein-dev@lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/gatein-dev
> > >

> > > 

> > > -- 
> > > Nicolas Filotto
> > > Project Leader JCR
> > > eXo Platform SAS
> > > nicolas.filotto@exoplatform.com
> > > +33 (0)6 31 32 92 19  
> > >

_______________________________________________
gatein-dev mailing list
gatein-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev

> > > 
> > > _______________________________________________ gatein-dev mailing list gatein-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/gatein-dev
_______________________________________________
> > gatein-dev mailing list
> > gatein-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/gatein-dev
> >

> >

>