Appian Platform: 16.2 Cloud Implementation
In order to accurately performance test a code change, we took a clone of our production environment in order to use realistic data to test the code change.
Our production environment limits to 3 concurrent sessions per user account. In order to performance test, we run automated scrips which log in as the same user multiple times to perform tasks and simulate system noise. As one would expect, the first attempt failed for all but 3 login attempts. We then disabled the setting in suite/admin.
After disabling the concurrent sessions limit, we were able to log in with our user manually using Chrome, however, Firefox was still showing a validation error on login relating to too many concurrent user sessions. We tried logging in with Firefox from another machine, and it worked, so we cleared the Firefox cache from the original machine, but yet it still failed again.
When we ran our automated script, passing our browser information as both Chrome and Firefox, some logins failed. The number of failures is inconsistent as well, once 16/25 logins succeeded, and then upon rerunning 14/25 succeeded.
Are there any known issues with this setting not fully being disabled? We suspect a server bounce would resolve the issue, but that's not necessary as this is a isolated time-boxed environment for targeted testing, as well as we can work around the issue by attempting more logins so we have a higher number of successes.
We have been able to confirm that it seems to be related to the machine that was logged in to the user before the setting change took place. With a different user (not being used by scripts), we were able to login with that machine. We then logged out, and used a separate machine to login with three sessions (Firefox, IE, Chrome), returning the original machine, we could not login. We were able to open a 4th session on the second machine (Chrome Incognito).
Discussion posts and replies are publicly visible