By: Tomas Liljebergh user 20 Feb 2023 at 6:44 a.m. CST

After adding support for a second identity provider (OP) using iodc and passport we are experiencing problems with the passport process getting non responsive. If we restart the passport process, (service passport restart) everything starts to work again as expected for a short amount of time (20-30-minutes) and users can start logging in as expected using any of the 2 configured providers. During this we have tried to monitor processes, cpu and memory but none of them indicates any problems. None of the loggfiles indicates any problems during the time the process is stuck. Only thing we can find that could be a problem is --max-old-space-size that is set to 541 MB on the passport process: /opt/node/bin/node --max-old-space-size=541 /opt/gluu/node/passport/server/app.js Can that be a problem? Is it too low and what number do you recommend to use? Are there any other recommended settings we should use? Regards Tomas