[
http://jira.jboss.com/jira/browse/JBPORTAL-2025?page=comments#action_1241... ]
Boleslaw Dawidowicz commented on JBPORTAL-2025:
-----------------------------------------------
This is happening because session timeout of portlet web application doesn't match the
portal one. Username remains in jsf session beans that are not invalidated together with
portal servlet session.
As a workaround in portal-identity.sar/portal-identity.war/WEB-INF/web.xml add:
<session-config>
<session-timeout>XX</session-timeout>
</session-config>
with the same XX value as in portal-server.war/WEB-INF/web.xml
Portlet cache doesn't expires with http session
-----------------------------------------------
Key: JBPORTAL-2025
URL:
http://jira.jboss.com/jira/browse/JBPORTAL-2025
Project: JBoss Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.6.4 Final, 2.6.5 Final
Reporter: Boleslaw Dawidowicz
Assigned To: Boleslaw Dawidowicz
Fix For: 2.6.6 Final
With <expiration-cache>-1</expiration-cache> set UserIdentityPortlet
- login as user 1
- wait until http session expire
- refresh page and put credentials of user 2
The UserIdentityPortlet still shows user 1 related data.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira