Failed to remove session for user because actions are still running. Client access disabled

0
When first starting the app, I am able to login fine with a variety of logins. After time, I am unable to log in with any of those same logins and see the messages below in the logfile. Can anyone help me identify what is going wrong? Thanks, Tracy    Client access has been disabled. Session will be attempted to be removed again in 300 seconds. 2017-08-16 12:55:51.835 WARNING - Core: Failed to remove session '10839c6b-0f41-440e-94ee-b394f6731b3a' for user 'tadmin' because actions are still running for this session. Client access has been disabled. Session will be attempted to be removed again in 300 seconds. 2017-08-16 12:55:51.835 WARNING - Core: Failed to remove session '15d449e6-5e4c-43ee-9d88-a34ff562b9a1' for user 'madmin' because actions are still running for this session. Client access has been disabled. Session will be attempted to be removed again in 300 seconds. 2017-08-16 12:55:51.835 WARNING - Core: Failed to remove session '88fc13cd-f61b-4f53-bd0e-63a7baf08cb8' for user 'mchampagne' because actions are still running for this session. Client access has been disabled. Session will be attempted to be removed again in 300 seconds. 2017-08-16 12:55:51.835 WARNING - Core: Failed to remove session 'cd0a3483-ac28-47c6-9cb4-92216ab87c91' for user 'ltest' because actions are still running for this session. Client access has been disabled. Session will be attempted to be removed again in 300 seconds. 2017-08-16 12:55:51.835 WARNING - Core: Failed to remove session '31dd2d13-46fb-4888-9e07-c8740c432bb2' for user 'mchampagne' because actions are still running for this session. Client access has been disabled. Session will be attempted to be removed again in 300 seconds.
asked
1 answers
0

Hi Tracy,

  This occurs when there is a microflow running in the background that was kicked off by the user mchampagne when they were in the application.   Even though the user closes the browser, the session will still stay active if there is something going on in the background.  If your application has some long running import or calculation microflows, then this could explain it, but from your description it sounds like something could be hung up.  The first thing I would check is the list of running processes in the home.mendix.com portal to see if there is some microflow that may be hung up.

answered