User Behavior Profiling printing logs in Tomcat logs


Article ID: 211592


Updated On:


CA Risk Authentication


We have noticed that the User Behavior Profiling is printing the logs in Tomcat standard output files, these are normally not managed so it is filling up the space and concerns it may consume all the space.


ubp-logging.xml file present at ARCOT_HOME/conf had configurations enabled by default to redirect the logs to Tomcat standard output logs.


Release : 9.0

Component : RiskMinder(Arcot RiskFort)


There is ubp-logging.xml file present at ARCOT_HOME/conf directory and that file should be modified, the ubp-logging.xml file from TOMCAT location will only be used if there is none present at ARCOT_HOME/conf directory.

Please make the changes as below at ARCOT_HOME/conf directory and this will require the application server restart to make the changes into effect.

<?xml version="1.0" encoding="UTF-8"?>
  <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
      <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">

      <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
      <pattern>%date{YYYY-MM-dd HH:mm:ss} %level [%thread] %logger{10} [%file:%line] %msg%n</pattern>

  <logger name="" level="ERROR" additivity="false">
   <appender-ref ref="FILE" />
  <logger name="java.sql" additivity="false">
    <level value="ERROR" />
    <appender-ref ref="FILE" /> 
  <logger name="com.ibatis" additivity="false">
    <level value="ERROR"/>
    <appender-ref ref="FILE"/>