ARC application log file grow larger sizes and is unable to open.

ARC application log file grow larger sizes and is unable to open.

It is always recommended to have a regular, scheduled restart of the Tomcat/HSQL service for uninterruptible and normal functioning of the ARC application. The log file records the details of various activities performed in the ARC application. Therefore, when ARC usage is more and frequent non-restarting of the Tomcat services enables the log file to grow larger sizes.

    • Related Articles

    • ARC application log file grows large and cannot be opened. Why?

      It is always recommended to have a regular, scheduled restart of Tomcat/HSQL Service, for the smooth functioning of the application. The log file records the details of various activities performed in the application. When ARC usage is more, and ...

    • Unable to login to ARC Instance.

      Restart the HSQL DB to resolve the Issue. Also to avoid this problem in future, it is recommended to have a scheduled re-start of tomcat at least twice a week and HSQL instances once a week. Apart from these scheduled re-starts clean-up of the usage ...

    • Unable to Login to ARC. Why?

      Check for the following as a first step: a) The last ETL date key from the application log is displaying as 'null' and hence unable to login to Analyst. b) Check for the connections to Admin DB and the Warehouse c) Look for any exceptions thrown in ...

    • Error in the Log file while rendering Login Page

      We have added a column 'CHARSET_TYPE' in the table 'ADMIN_LANGUAGE' and updated the column with value 'ISO-8859-'

    • Unable to open .pdf attachment from report bursts scheduled After ETL. It is a BCM KPI. Why?

      One of the reasons is because of the non-availability of sub-reports (BCM) in the Batch Process folder (which is responsible for After ETL reports). We have to synchronize all the sub reports (.bcm, .jasper and .jrxml) available within ARC App folder ...