FAQ

The “Login error: Maximum number of sessions for user … has been reached. Please try again later.” occurs when the application or system level limit on the number of simultaneous users is reached. Limits are built in by default as a protection against one single application logging in so many users that it occupies all the resources of the host server and other application users are effectively denied access. Under normal circumstances the limits can be set appropriately for the expected user population and available server resources (see below) so this error should not occur. But in the case of a software problem or some kind of robot targeting the application this is a useful line of protection. Note that Muse allows administrators to set these logon limits at both the application and system levels. These setting are kept in the MAX_USER_CONCURRENT_SESSIONS variable, which can be modified as follows: – system wide level: edit the $MUSE_HOME/use/ice/ICECore.xml file and change the value of the MAX_USER_CONCURRENT_SESSIONS tag. – application level ($APPLICATION_HOME/profile.xml): access the application settings via MCAA console (Application Actions > Edit Configuration Options) and set the “User Concurrent Sessions” value as needed. Changes here affect only the application you’re editing. Note: please be aware that low values can deny access too often while high values can allow unmanageable load on the server. We recommend multiple, small adjustments rather than a single large change.

1) At the application level:

This can be done by changing the value of the “User Concurrent Sessions” field from the application’s properties using the Muse Admin Console.
The file from within the application which contains this setting is $APPLICATION_HOME/profile.xml, field: .
Note that this field sets the maximum number of simultaneous sessions for one user (application). New connections for the same user are rejected if the number of simultaneous sessions reaches maximum.

2) At the system level:

In the $ICE_HOME/ICECore.xml file there are 2 fields that control the maximum sessions:

Maximum number of simultaneous sessions. New clients are rejected if the number of simultaneous sessions reaches maximum.
Maximum number of simultaneous sessions for one user (application). New connections for the same user are rejected if the number of simultaneous sessions reaches maximum.

By default the configured values are:
100
25

This means that no more than 25 simultaneous sessions are allowed for an user/application and no more than 100 simultaneous sessions for all users/applications. The value of the MAX_USER_CONCURRENT_SESSIONS field must be always smaller or equal with the MAX_CONCURRENT_SESSIONS value. Also, when changing the value of MAX_CONCURRENT_SESSIONS one must be aware that the new value must accommodate enough sessions to cover the largest number of MAX_USER_CONCURRENT_SESSIONS set in the applications. It is not necessary nor recommended for this to be the sum of all MAX_USER_CONCURRENT_SESSIONS from applications.

Please Note:

The MAX_USER_CONCURRENT_SESSIONS value set in the $ICE_HOME/ICECore.xml file is the default one and it is being overwritten by the value from the application level. In other words the value from the application level has the highest priority.

1) At the application level:

This can be done by changing the value of the “User Concurrent Sessions” field from the application’s properties using the Muse Admin Console.
The file from within the application which contains this setting is $APPLICATION_HOME/profile.xml, field: .
Note that this field sets the maximum number of simultaneous sessions for one user (application). New connections for the same user are rejected if the number of simultaneous sessions reaches maximum.

2) At the system level:

In the $ICE_HOME/ICECore.xml file there are 2 fields that control the maximum sessions:
Maximum number of simultaneous sessions. New clients are rejected if the number of simultaneous sessions reaches maximum.
Maximum number of simultaneous sessions for one user (application). New connections for the same user are rejected if the number of simultaneous sessions reaches maximum.

By default the configured values are:
100
25

This means that no more than 25 simultaneous sessions are allowed for an user/application and no more than 100 simultaneous sessions for all users/applications. The value of the MAX_USER_CONCURRENT_SESSIONS field must be always smaller or equal with the MAX_CONCURRENT_SESSIONS value. Also, when changing the value of MAX_CONCURRENT_SESSIONS one must be aware that the new value must accommodate enough sessions to cover the largest number of MAX_USER_CONCURRENT_SESSIONS set in the applications. It is not necessary nor recommended for this to be the sum of all MAX_USER_CONCURRENT_SESSIONS from applications.

Please Note:

The MAX_USER_CONCURRENT_SESSIONS value set in the $ICE_HOME/ICECore.xml file is the default one and it is being overwritten by the value from the application level. In other words the value from the application level has the highest priority.