10-01-2015 09:56 AM
We are facing issues when Business users login to the ECM portal and have mutiple sessions opened in IE and Chrome .SAS Version is 9.2. Looks like some ghost sessions are being created and as a result we face hung sessions and a server restart has to be done.
Is there anyway this can be mitigated without a server restart.Any advise on this issue would be of great help.
Thanks in advance.
10-02-2015 05:40 AM
It woudl be helpfull not to focus on ECM as solution but as SAS_BI as seen by those requiements http://support.sas.com/documentation/installcenter/en/ikcasemgmtofrsr/65196/HTML/default/index.html.
By that you are in a more common platform usage. Mentioing sas 9.2 as base your on that road.
As you are only having web-clients and a midtier and mentioning ghostprocesses you are likely on a Unix system (just guessing).
Ghostprocesses can be cleaned up by killing those or restarting services. Normally there is NI need to restart the whole machine.
By ghostprocesses I am understanding run-away processes on the OS that where started on behalf on user (user personal key WS).
When using shared accounts by ease of installation or as intended by isolated functionality (SP PWS OLAP) There is a difficulty to pinpoint those. Using a SP service is sharing that between users. One faulty userproces can block the next one causing a hangup.
Timeouts with session can become nausty as almost enverywhere somebody is implementing a timer to break something with unpredcitable results (browser router firewall server). This is continously changed and adjusted. http://support.sas.com/documentation/cdl/en/bimtag/68217/HTML/default/viewer.htm#p0n3toyj2v9j4tn0z4y...
10-02-2015 09:44 AM
Thanks for the reply. The Ghost sessions created by individual users are causing the server to hang. Isolating one by one and killing is not feasible.
Are you aware of any fix in SAS which can stop creating such Ghost sessions.
10-02-2015 12:27 PM
Killing one by one is not necessary when you have root access and are abel to build a script to do that.
ps -ef and grep commands to select the ghost processes and the xargs kill to end those. When needed a kill -9 for the repetition after a sleep of ca 10 seconds. Can be planned to run reguakr by cron. That is the bypass.
The permanent fix should come from finding the root-cause(s) most likely some co,bination of an user action some programming/code and those timers. The session-keep alive setting is recognized by SAS and implemented in 9.4. You need an upgrad for that.
When users do not logoff, but disconnect on a rude way that is another one. Find those and ask what/how they are doing the things.
A programming error is evaluating the logs when you have isoalted some evnet (user/action).