Page 1 of 1
All users (including Admin) cannot open client session.
Posted: Sat Mar 24, 2018 8:09 pm
by rkashyap
Attempts to open Client session for all users including Admin are failing with message:
Code: Select all
<Status xmlns="http://iis.ibm.com">
<httpStatus>503</httpStatus>
<msgId>CDISF0001E</msgId>
<msgSeverity>Error</msgSeverity>
<msgText>The maximum number of sessions has been reached.</msgText>
</Status>
Manintenance mode is not ON. Can you please share your thoughts?
Posted: Sun Mar 25, 2018 9:26 am
by chulett
Sounds like time for a reboot / restart, although that won't help you figure out what caused this in the first place. Guessing you have a large number of zombie sessions.
Unfamiliar with "maintenance mode", is that related to having the deadlock daemon running?
Posted: Sun Mar 25, 2018 8:01 pm
by PaulVL
Maintenance mode is a feature I requested awhile back. It prevents users from logging in while you are patching. One of the big advantages of having been at Wal-Mart... you get features installed.
Posted: Mon Mar 26, 2018 7:04 am
by chulett
Ah... gotcha. So basically a "single user" mode.
Posted: Mon Mar 26, 2018 12:34 pm
by rkashyap
Thank you. Apparently, lots of zombie DataStage connections were being created from a rogue DataStage session on a desktop and maximum no of sessions was exhausted, thus no new session could be opened to diagnose/resolve the issue.
Solution was to bounce the box, restart DataStage and logon to IIS Console (before maximum no of sessions was exhausted). Subsequently (using the ip address from Session management -> Active Sessions) the desktop was identified and restarted.
Please note that only (one) Designer session was open on this desktop, which was not listed on IIS Console, but thousands of sessions with type "Unknown" were!
Posted: Tue Jul 17, 2018 7:55 am
by skathaitrooney
Apparently i ran into the same situation.
I was making IGC rest-api calls to the services tier. What i did not realize is that if i do not make proper use of cookies and sessions, each rest call would initiate a new session which shows as UNKNOWN in the admin console.
I made 1000 rest api calls and ultimately exhausted my session limits.
Had to modify my python code to make use of sessions and cookies so that only 1 session is created and re-used in subsequent calls...
Posted: Wed Jul 18, 2018 7:30 pm
by ray.wurlod
chulett wrote:Ah... gotcha. So basically a "single user" mode.
Not quite. Maintenance mode prevents users who do not have the suite administrator role from logging in.
Other than the setting in Global Properties, there is no limit on the number of administrators who can log in while maintenance mode is asserted.
Posted: Wed Jul 18, 2018 8:56 pm
by chulett
Ah... gotcha.
Posted: Sat Jul 21, 2018 4:36 am
by ray.wurlod
The maximum number of sessions is set in Global Properties in the web console for Information Server.
If none of your Information Server users can log in to this console, try the WebSphere Application Server administrator ID, which is set as the default IIS administrator when switching to LDAP realm, and (in my experience) never uses that privilege.
Otherwise use the command line option SessionAdmin.sh to kill all user sessions, then start again.