RunDeck 3.4.1 TomCat Java Memory issue

[Aaron Sheppard]

How can we manage our memory better with RunDeck and TomCat on Windows?

We have a Windows Server 2016 vm with 8192 MB ram with six cores and running RunDeck 3.4.1 with TomCat 9 from the rundeck.war file.  Lately we've been seeing a couple issues crop up. First, RunDeck keeps user login sessions open well past the 30 minute idle limit in TomCat and Second, RunDeck does not respond or is extremely sluggish when the StandBy Memory leaves less than 400 MB of 'free memory' as if it never gets access to the StandBy Cache or queue or the priority is so low it can't get access to it. When a job fails, this problem gets even worse; but it also happens on successful jobs.  This is causing our server to become unresponsive multiple times a day and the only way so far to free it is to manually release sessions in TomCat and/or to reboot the server completely.  In the RunDeck Profile I have set the JVM to export RDECK_JVM="$RDECK_JVM -Xmx2048m -Xms512m -XX:MaxMetaspaceSize=512m -server".  

[rac...@rundeck.com]

Hi Aaron,

Those memory parameters are defined in the setenv.bat file? take a look at this.

In addition, could you post the catalina.out errors at the moment of failure?

Regards.

​

[Aaron Sheppard]

Hi Racuna,

Thank you for your quick response-

We don't have a setenv.bat file, instead we had been setting the memory parameters manually with the server setup; as we have been using RunDeck since before 3.3 our procedures didn't have the setenv.bat as part of the build- our parameters were defined as this:  JAVA_OPTS=-XX:MaxPermSize=512m -Xmx2048m -Xms512m -server

I couldn't find any catalina.out files or errors.