In some instances, the Apache Tomcat server's cache needs to be cleared for the QRadar® environment to function correctly. For example, IBM QRadar support might suggest an administrator clears the cache if the graphical user interface is slow or specific components of the user interface does not load as expected. This article provides the steps required to clear the Tomcat cache.
- Before attempting to clear the Tomcat cache check if the issue is limited to certain users. If it is, have them attempt to access the graphical user interface using their browser's incognito mode or a private tab. If that method resolves the issue, have the users clear their browser caches and attempt to access the user interface again.
- Administrators with strict outage policies are advised to complete this procedure during a scheduled maintenance window for their organization.
- Restarting Tomcat ends all active user sessions and logs out all users. When the Tomcat service is stopped or restarting, the QRadar user interface is not available.
- Performance or user interface issues are not necessarily related to the Tomcat cache. If IBM QRadar support did not suggest clearing the cache, check with them for a more in-depth analysis before you complete the procedure in this article.
- Use SSH to log in to the Console as root user.
- To create a backup directory for files, type the following command:
- Type the following command to stop the Tomcat service:
systemctl stop tomcat
- To backup of the /opt/tomcat/work/Catalina/localhost directory, type:
cp -pr /opt/tomcat/work/Catalina/localhost/console/org/apache/jsp /store/ibm_support/
- To clear cached files from the /opt/tomcat/work/Catalina/localhost/console directory, type:
rm -rfv /opt/tomcat/work/Catalina/localhost/console/org/apache/jsp
- Type the following command to start the Tomcat service:
systemctl start tomcat
10 February 2021