[
http://www.jahia.org/jira/browse/DOCU-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stéphanie Rouaud resolved DOCU-9.
---------------------------------
Resolution: Fixed
added to performance guide
> ESI - Expiration mode how to
> ----------------------------
>
> Key: DOCU-9
> URL: http://www.jahia.org/jira/browse/DOCU-9
> Project: Jahia Documentation
> Issue Type: Assistance
> Environment: All
> Reporter: Cédric Mailleux
> Assignee: Cédric Mailleux
> Priority: Critical
>
> Changes to ESI behaviour
> You must run ESI without aspectwerkz so be sure to start with jahia.sh or
> jahia.bat ESI_MODE must not be equals to ON
> The Jboss cache instance for ESI is now configured in esi-local-cache.xml
> even if you are in cluster this will not cause any problem as there is no
> more invalidation messages send because of track back parts in cache being
> empty from the non activation of aspectwerkz (the esi-cluster-cache.xml will
> be used later when we will find a solution to make it worked)
> In ESI server the data.xml is now back to not caching edit/preview/compare
> mode (defined in pass through rules)
> So now the expiration of content will only happen from expiration time by
> default I put the expiration to 300s (5 minutes) this could be easily changed
> in jahia.properties or jahia.skeleton
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
