Object caching properties define the cache lifetimes of applications, projects and sessions.

Object caching configuration
Property
|
Description
|
Life time of application object [min]
|
Life time of application objects [min]

|
The life time of application objects should be set to the time span between Apache Tomcat restarts. When using default settings (1440 minutes = 24 hours) an Apache Tomcat restart is recommended every day to correctly reinitialize all resources.
|
|
Life time of project objects [min]
|
Life time of project objects [min]

|
This value must be at least twice the session timeout in the web_user.xml and higher than the life time of session objects [min].
A project that no session uses is removed from the cache after half to all of its life time. The session of a user does not keep its project in the cache. If the session timeout is longer than half the life time, a user who returns to a rarely used project after a break can lose the work state (selection, markup, sketches) although the session is still valid: the project is restarted. Projects that other users keep working with are not affected.
Example: if the session timeout is raised to 480 minutes, the life time of project objects must be at least 960 minutes. The life time of application objects must not be lower than the life time of project objects, otherwise the whole object caching configuration is ignored and the default values apply. Longer life times keep more objects in memory - check the memory of Apache Tomcat afterwards.
If the values do not fit, WebOffice writes the warning SESSION_TIMEOUT_EXCEEDS_OBJECT_CACHING to the log once at start, with the configured values and the recommended settings.
|
|
Life time of session objects [min]
|
Life time of session objects [min]
|
Object caching configuration