MID Server wrapper logs contain INFO message "Wrapper Process has not received any CPU time. Extending timeouts."DescriptionIn the MID Server wrapper.log files you may find INFO messages logged similar to below informing that the Wrapper Process and JVM Process have not received any CPU time for x amount of seconds: INFO | wrapper | Wrapper Process has not received any CPU time for 27 seconds. Extending timeouts.INFO | jvm 1 | JVM Process has not received any CPU time for 27 seconds. Extending timeouts.Release or EnvironmentAll Releases The MID Server installer includes the Tanuki Software Java Service Wrapper which is used for the MID. Orlando, Paris, and Quebec include version 3.5.40 New York- includes version 3.5.36 https://docs.servicenow.com/bundle/quebec-servicenow-platform/page/product/mid-server/reference/r_MIDServerSystemRequirements.htmlCauseThese messages are warnings that, in this case, both the Wrapper and its JVM process were denied access to the CPU for a period of 27 seconds. Depending on the current state of the Wrapper, either the startup, ping, or shutdown timeout is extended to avoid a FALSE timeout caused by the lack of processing power. There are two cases where either the Wrapper or its controlled JVM could be denied access to the CPU for an extended period of time. Either could lead to the Wrapper thinking that the JVM was hung, causing it to be restarted or shutdown because one or more of the timeouts expired. The first way that this can happen is when the Wrapper is competing for system resources with another process that has the habit of consuming 100% of the CPU for extended periods of time without yielding to other processes. Most modern operating systems are fairly good about managing multitasking. But there are still cases where it can fail. One example of this on Windows is when the machine is very low on memory, leading to lots of disk swapping. If the total memory is not large enough, the entire system can freeze up for as long as a minute before any applications are again given any CPU cycles. A second way is if the system is suspended and then resumed. This is a common thing to do on notebooks. When the system comes back up, it will appear to have suddenly been set ahead by potentially several hours. By default, warning messages will be displayed after 10 seconds, which is actually quite a while. CPU timeout being triggered will not have any adverse effects on an application other than the message being displayed in the logs. To avoid this message being logged, the timeout can be set to a larger value or disabled completely. ResolutionIn most cases, when you are having problems with CPU timeouts, you should really look at finding a way to resolve the problem of the Wrapper not getting any CPU rather than extending any timeouts in the wrapper-override.conf file. If the application being run by the Wrapper is not getting any CPU then it will not be able to reliably service requests from clients. Contact your MID Server host's server team to check the logs to find out why the Wrapper or it's controlled JVM would be denied access to the CPU at the time of the logged message.Additional InformationAdditional Information can be found in Tanuki Softwares documentation in the below link. https://wrapper.tanukisoftware.com/doc/english/prop-cpu-timeout.html