This now accomplishes what we wanted with a very low cpu usage (below 1%) when the server is quiet.
![commons daemon service runner ansys licensing tomcat commons daemon service runner ansys licensing tomcat](https://s1.manualzz.com/store/data/009368468_1-e83654557fb261ec8850a829cd696f90.png)
In order to point the tomcat to this other directory (where we compile our dspace code), we just used the Host entry in conf/server.xml, and changed the appBase setting to our dspace directory: Suddenly we had a normal, well-behaved tomcat again. To test, we removed the xml files from the conf/Catalina/localhost directory, and restarted tomcat. However, we had this problem with continually spiking cpu usage. Excluding 'bin/Tomcat9.exe' from the 'Path to executable' property of the above located service will be the path of Tomcat installation. Open the properties of the searched services. Search 'Dell WMS: Tomcat Service' service from the service panel.
Commons daemon service runner ansys licensing tomcat code#
The xml files in this directory look like this: Īnd this worked, tomcat ran with the code in these directories rather than its own webapps directory. Open the window service panel using 'services.msc' command in command prompt.
![commons daemon service runner ansys licensing tomcat commons daemon service runner ansys licensing tomcat](https://i.ytimg.com/vi/nofuLnng5Ek/hqdefault.jpg)
We had used the configuration option in the tomcat/conf/Catalina/localhost directory, in which we pointed tomcat to another directory, other than its own webapps directory.
![commons daemon service runner ansys licensing tomcat commons daemon service runner ansys licensing tomcat](https://i.ytimg.com/vi/CvNxydziIUk/mqdefault.jpg)
We did not find our solution in a web search, so I am posting it here in the hopes of helping someone else. This occurred all day long and all night long, whether the server was performing any work or not. We just solved a problem with our tomcat instance running with very high cpu usage, swinging up to 100% and more every few seconds and then briefly down again. Out.println("" + t.getThreadName() + " " + percent + " (" + prev + ", " + current + ")") Īfter that you can get a thread dump and analyze the code in this thread to fix excessive CPU usage. First of all (this applies to all java applications) you must pin down which thread is using CPU.