[ https://issues.jboss.org/browse/GTNPORTAL-3137?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3137: ---------------------------------------------------- Radoslav Husar <rhusar(a)redhat.com&gt; made a comment on [bug 974549|https://bugzilla.redhat.com/show_bug.cgi?id=974549] Unfortunately, this is to be expected with such scenario in default configurations, because in 6.1 added support for session persistence has been added to non-HA profile. The sessions now survive app upgrades, restarts, crashes, etc. The cache is *write-through*; compared to 6.0 where there has been no session persistence at all. So in the end, its apple-to-oranges comparison. To revert to original 6.0 behaviour, simply remove the 'local-web' cache store. * Option to investigate to keep the functionality but configure the cache store as write-behind, see https://docs.jboss.org/author/display/ISPN/Write-Through+And+Write-Behind... * Note that standalone-full-ha.xml is intended as the production profile IIRC, whereas standalone.xml is mroe or less the developer profile. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira