tomcat_view.log file size issue

Products

• CA Service Catalog
• CA Service Management - Asset Portfolio Management
• CA Service Management - Service Desk Manager

Issue/Introduction

The tomcat_view.log keeps on growing and it doesn't rotate based on the size control configured in log4j.xml at all 

The  tomcat_view.log file under CA\Service Catalog\logs\view is taking more than 1.2GB  ? How can we manage that log.? 

Environment

ITSM Catalog 14.1 , 17.1 and 17.2 

Resolution

It  is the outcome of the following piece of configuration in USMHOME/view/conf/server.xml  file :

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="__USMHOME__/logs/view" prefix="tomcat_view" suffix=".log" pattern="common" resolveHosts="false" rotatable="false"/>

By default ,  the property rotatable is set as "false"   in access valve log configuration above . 

The solution for it :

1.  stop catalog service  on catalog server 

2 .  go to USM_HOME\logs\view\ folder  and delete existing tomcat_view.log .

Note :  it is important step !  if not deleting the existing tomcat_view.log , the configuration change here has no meaning and will not take effect . 

3.  update  server.xml file under USM_HOME\view\conf\ folder 

Change :

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="__USMHOME__/logs/view" prefix="tomcat_view" suffix=".log" pattern="common" resolveHosts="false" rotatable="false"/>

to 

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="__USMHOME__/logs/view" prefix="tomcat_view" suffix=".log" pattern="common" resolveHosts="false" rotatable="true"/>
 
save it .

4.   restart catalog service .

Note :   the first tomcat_view.log is going to 0 size  ( i.e. empty ) .  The logging messages will start to write into tomcat_view_<date>.log  and in rotatable way .