How do I clear the Tomcat cache on my NAC appliance?

Aruba Employee
Aruba Employee

Product and Software: This article applies to all ECS product and software versions earlier than 3.1.8. In NAC appliance versions later than 3.1.8, installing updates automatically clears the Tomcat cache. When you are applying a patch, this applies to all versions.


You will sometimes need to clear the Tomcat cache on your NAC appliance, such as when:

  • Adding a patch
  • Upgrading from 2.x firmware
  • Getting java.lang.NullPointerException
  • Troubleshooting admin GUI connection issues

This solution describes clearing both the tomcat-admin cache and the tomcat-portal cache. For a NAC server such as NS500, both caches are on the same box. Otherwise, the tomcat-admin is located on the Network Control Server (such as NS1200), and the tomcat-portal is on the Network Application Server (such as NS8200).

This procedure assumes you have separate control and application servers. If instead you have an NS500, you can clear both caches before restarting the NAC appliance.

You need to have root access to the CLI.

On the Network Control Server:

1) Access the NAC appliance CLI, and log in as root.

2)  Stop the tomcat-admin service:

/etc/init.d/tomcat-admin stop

3) Clear the tomcat-admin cache:

cd /bsc/services/tomcat-admin/work/Catalina/cm
rm –rf *

4) Restart the tomcat-admin service:

/etc/init.d/tomcat-admin restart

On the Network Application Server:

1) Access the NAC appliance CLI and log in as root.

2) Stop the tomcat-portal service by entering the following command:

/etc/init.d/tomcat-portal stop

3) Clear the tomcat-portal cache:

rm –rf *

4) Restart the tomcat-portal service:

/etc/init.d/tomcat-portal restart


Version history
Revision #:
1 of 1
Last update:
‎06-30-2014 06:06 PM
Updated by:
Search Airheads
Showing results for 
Search instead for 
Did you mean: