Question
Bankers Life
US
Last activity: 11 Feb 2020 14:59 EST
OSCR crashed and refuses to let me in
I was on Firefox using OSCR and the page crashed. When I hit refresh I was required to reenter my credentials. Upon logging in I got an error message that reads "The current session is blocked, as the maximum number of active sessions for the current operator has been reached."
Along with this error message I am given a "node" that is comprised of 33 letters/numbers and seems to be randomized. I attempted clearing my browser history and cookies, I restarted my computer, and I attempted logging on in Chrome and Internet Explorer. I am given this same error message every time. The only thing I can think of is this is an issue on the other end, because nothing I do seems to help. Is there something I can do to log back onto OSCR? Or do I just have to wait until the system refreshes on the other end?
Updated: 11 Feb 2020 14:59 EST
Pegasystems Inc.
US
Hi Zachary,
It looks like your system is configured to prevent concurrent operator sessions. System uses presence records in Hazelcast distributed structure to determine if an operator is already logged in or not.
I have seen issues where the presence records not getting removed upon browser crash scenarios and Admin need to manually remove the presence record by passing the OperatorID
Below are the options you got: -
1. Request HFix-57715 for Pega 7.4 to get the Presence API exposed to remove the presence record for the OperatorID.
After installing the Hotfix. Restart the server.
To clear the presence record when the issue occurs, You may follow the below steps:
a.Write an activity
b. Step-1:Select method as Java and paste the below code:
pega.getSystemOperationsProvider().getPresenceSessionManagementAPI().clearPresenceSessions(operatorId);
c.Replace parameter operatorId with the actual operatorId whose presence record should be cleared.
d.Run the activity.
2. You can also disable the concurrent sessions setting in your Data-Admin-System instance. If you don't need this feature.
3. If you are a developer and want to whitelist yourself from this feature, you can do so by adding the below setting.
Hi Zachary,
It looks like your system is configured to prevent concurrent operator sessions. System uses presence records in Hazelcast distributed structure to determine if an operator is already logged in or not.
I have seen issues where the presence records not getting removed upon browser crash scenarios and Admin need to manually remove the presence record by passing the OperatorID
Below are the options you got: -
1. Request HFix-57715 for Pega 7.4 to get the Presence API exposed to remove the presence record for the OperatorID.
After installing the Hotfix. Restart the server.
To clear the presence record when the issue occurs, You may follow the below steps:
a.Write an activity
b. Step-1:Select method as Java and paste the below code:
pega.getSystemOperationsProvider().getPresenceSessionManagementAPI().clearPresenceSessions(operatorId);
c.Replace parameter operatorId with the actual operatorId whose presence record should be cleared.
d.Run the activity.
2. You can also disable the concurrent sessions setting in your Data-Admin-System instance. If you don't need this feature.
3. If you are a developer and want to whitelist yourself from this feature, you can do so by adding the below setting.
4. Also, doing an entire cluster restart should help in clearing the presence records. Unlike rolling restarts.
Let me know if it helps!