RE: Re: [daemon] High CPU load after update from 1.3.2 to 1.3.3

Hello,

I experience the same symptoms as Andreas (both on Procrun(AMD64)  1.3.4 
and 1.4.0). I am also running a SpringBoot application.

1: If I install the windows service with --StopTimeout=15,  then the 
process will use around 7-9% of CPU in Task Manager on my Lenovo P15 laptop.

2: If I install without --StopTimeout=15 then the process will use 
around 0-1% of CPU

In both cases no one is using the application.


br

Christoffer


On 2023/05/16 08:29:01 Andreas Kuhtz wrote:
 > Hello,
 >
 > I know that the statement "high CPU load" ist pretty vague, but the CPU
 > load in Windows task manager was the only visible thing I saw. No 
different
 > logs even with LogLevel=DEBUG.
 >
 > But I found out that removing the StopTimeout parameter (in my case
 > --StopTimeout=15) solves the issue. So I think it might be related to 
this
 > change:
 > 
https://github.com/apache/commons-daemon/commit/243a8521f780b98247820ae187e395597f6c9b51#diff-b4e825062840bfdafb7eeed624d22a66257983305ca7e21470b679bff4ef1ffeR1840-R1850
 >
 >
 >
 > Am Mo., 15. Mai 2023 um 21:08 Uhr schrieb
 > <[email protected]>:
 >
 > > Andreas,
 > >
 > > Use the java flight recorder to take a recording of a minute or 
two. Open
 > > it in Java Mission Control and look at the method samples. That 
will give
 > > you a good idea where the CPU usage is coming from. If that doesn't 
seem
 > > helpful, maybe enable -XX+DebugNonSafepoints and try again.
 > >
 > >
 > > > -----Original Message-----
 > > > From: Andreas Kuhtz <[email protected]>
 > > > Sent: Monday, May 15, 2023 11:25 AM
 > > > To: [email protected]
 > > > Subject: [daemon] High CPU load after update from 1.3.2 to 1.3.3
 > > >
 > > > Hi there,
 > > >
 > > > I see a high CPU load after updating commons-daemon from 1.3.2 to 
1.3.3
 > > > (and 1.3.4) on my system.
 > > > The application is a simple SpringBoot application that is 
started with
 > > service-
 > > > user LocalSystem (no difference if started with default value).
 > > >
 > > > How can I find the cause for this?
 > > >
 > > > Many thanks,
 > > > Andreas
 > >
 > > ---------------------------------------------------------------------
 > > To unsubscribe, e-mail: [email protected]
 > > For additional commands, e-mail: [email protected]
 > >
 >