SC6.2 crashed by too many empty user sessions

[youyoufly]

now the system crashed very frequently,(about every 20 hours), please help!

there are a lot of empty user name&device sessions in system status. and meanwhile many system locks by user RCOPERTOR, JETOPERTATOR, HPSX .... all these users are used by integrated system. they all using webservice for integreation with OVSC.

we have inactive timer set to 60 and timeoutlimit in sc.ini set to 3.

screen shot for system status and locks is attached.

I can't find any valuable information in logs. could anyone help on this?

[swhirschfeld]

When you see empty entries in system status this usually means that the session is connected but not yet logged in,  for example a web client just sitting on the login screen.

It could also mean that the login process has started but not yet competed.  Since your locks attachment had several entries for "loginLock" it could be that the login process is stuck waiting for this resource.

The use of the login lock was eliminated in 6.2.8.9 with QCCR1E67022.  You can upgrade the server RTE to obtain this change.  This will reduce contention at login and improve the login performance.

SC should not crash due to too many empty users sessions.   Could you provide more detail around the term 'crash'?  This usually indicates a GPF or signal 11 which should be captured in the log file.

[Carmella_G]

crash means, the loginLock and empty user keep growing, and the performance getting slow and slow, at the end the system won't response to any request and have to restart.

do you have a detail description for QCCR1E67022? I didn't find it in HP web site?

and what the log looks like for signal 11? 

[ramesh9]

Can you please check whether "sessiontimeout" sc.ini parameter is available in SC? If yes apply that and check out whether crashes are continuing...

[Carmella_G]

we have timeoutlimit set to 3.

I think sessiontimeout is a similar parameter for later version.

Thanks