Configuring the Collaborative Review Web application
Optimize Collaborative Review Web application performance by setting Java's initial and maximum heap size and by overriding session timeouts.
Procedure
- Based on the amount of RAM available on your target machine, check and set the initial and maximum memory pool (heap size) used by Java in your Web application server. For example:
- If your Web application server is Apache Tomcat running on a Windows machine, run the tomcatVERSIONw.exe tool, where VERSION is the Tomcat version (say 8), select the Java tab and set Initial memory pool and Maximum memory pool to your preferred size (Thread stack size can be
null). -
If your Web application server is Apache Tomcat running on a Linux machine, access the bin/ subdirectory of your Apache Tomcat home directory and edit the file setenv.sh. In this file, include a value for
JAVA_OPTSby including a line like the following:export JAVA_OPTS="-XmsINITPOOL -XmxMAXPOOLwhere INITPOOL is your initial pool size, and MAXPOOL is your maximum pool size.
If your Tomcat server has at least 8 GB of RAM, your initial pool size can be set to 2048, and your maximum pool size to 6144.
- If your Web application server is Apache Tomcat running on a Windows machine, run the tomcatVERSIONw.exe tool, where VERSION is the Tomcat version (say 8), select the Java tab and set Initial memory pool and Maximum memory pool to your preferred size (Thread stack size can be
- Specify the Tomcat session timeout override for Collaborative Review sessions created by Content Manager publish tasks.
The Tomcat web application server has a timeout setting for each Collaborative Review session. When user inactivity is detected in Collaborative Review , a publish process may be terminated based on Tomcat's session timeout. Tomcat's session timeout can be overridden for publishing by adding the
pub.session.timeoutconfiguration item, so a long publish will not be interrupted.Note: By default,pub.session.timeoutis set to 600 (minutes). When working with publications including several thousands of topics or more, it is suggested to at least double this number.- From the landing page, click Manage Application > Global Config.
- In the right pane, under Customized Config, click Add Item.
- In the Name field, enter
pub.session.timeout. - In the Value field, enter a timeout value in minutes.
- Click Save.
- Specify the Tomcat session timeout override for all Collaborative Review sessions.
Tomcat has a default session timeout of 30 minutes that is imposed on every web application that the Tomcat instance serves. In the case of the Collaborative Review application, that timeout means that you will have to log in again after 30 minutes of inactivity. You can override the Tomcat session timeout defined in the
$tomcatdir\conf\web.xmlfile by editing theContentDelivery_home\WEB-INF\LiveContentSecurity.xmlfile to include asession-timeoutsetting.For example, to set the timeout to 1 hour (60 minutes):<session-config> <session-timeout>60</session-timeout> </session-config>Note: To avoid many dead sessions that may linger, and possibly degrade performance of Tomcat and/or Collaborative Review , do not specify a session timeout greater than 2 hours (120 minutes).