It cannot be fixed because this is the way that the framework is designed. Explanation : When a portlet window is maximized, it goes on a new page and the region of the portlet changes temporarily, from its region to the "maxmized" region. In order to avoid this to be done on a shared page the window navigational state (region/position) is cached in the http session of every user. So any update to the window region will be taken in account by users when they have a new portal session (expiration or logout). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962104#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...