cancel
Showing results for 
Search instead for 
Did you mean: 

Why is the flexnetls (LLS) consuming CPU when doing nothing?

No ratings

Why is the flexnetls (LLS) consuming CPU when doing nothing?

Summary

Why is the flexnetls (LLS) consuming CPU when doing nothing?

Question

When looking at the FlexNet Embedded (FNE) 2017 R3 local license server (LLS) running as a Windows service inside Apache Commons Daemon Service Runner, it consumes between 3 and 20% of the CPU even though its not actually doing anything (no application is calling it). Why?

Answer

This is likely due to the option you're using for Tomcat services. When you downloaded Tomcat, instead of the Apache Commons Daemon Service Runner option, please test this using the default option. Normally, when using the generic non-daemon service option, the local license server (LLS) doesn't have any background processes running utilizing CPU other than when there's some activity going on (acquiring a license or configuration, etc).

Additional Information

In a production environment, you'd likely use prunserv.exe on Windows, as you'll want your LLS restarting automatically with a system restart. In this case, the CPU usage is expected, as the service has functionality happening beyond just the LLS-specific activities.

From the Apache webpage:
"Tomcat can be run as a daemon using the jsvc tool from the commons-daemon project. Source tarballs for jsvc are included with the Tomcat binaries, and need to be compiled. Building jsvc requires a C ANSI compiler (such as GCC), GNU Autoconf, and a JDK. "

The common solution is to have Tomcat installed and run as a windows service.
For Unix systems, Tomcat can be run as a daemon using the commons daemon.

Please note, since FNE 2017.08, we started using the service wrapper (flexnetlsw.exe) rather than prunsrv.exe.
Was this article helpful? Yes No