Error in citrix session(due to user locking the table)

chakkucit

New Member
Hi ,
I am getting the below error in the citrix session.

rsn_ref in use by stpbsl03 ,514 on hlnetwork2. Wait or press CTRL-BREAK to stop.

it may be due to the user abnormal session.

I have checked the user in windows server and the user is not found.

After killing the user through promon in unix server .the issue is resolved.

But i want to know the idle session for the citrix server (if the user logged out abnormally, the session ends in windows but in unix server the user was not released) to resolve the issue. please help.

Regards
Chakkaravarthy
 

Attachments

Maybe this does not help, but, for the record: Progress 9.1d is more than 10 years old software, it has long been retired by Progress and therefore I would strongly recommend you to upgrade to a recent version of OpenEdge 10 as soon as possible.

The database uses the TCP keep alive mechanism to detect "disappeared" clients. The default on most operating systems I know is 30 minutes. Therefore I can take up to 30 minutes until the database detects that a client has disappeared. You could set the TCP keep alive on your Unix to a lower value but that may have negative side effects on other applications that run on that machine.

The other problem of yours seem to be that the application uses a pessimistic locking strategy - which might have been perfectly okay in a world 10 to 15 years in the past (when the application was developed) but does not support the concurrency needs for a modern business application anymore. Here I have to say, IMHO of course, that a pessimistic locking strategy never was a good strategy no matter what. But that you can only change when you change the software ...


Heavy Regards, RealHeavyDude.
 
Please suggest..is there anything for monitoring the idle process(process running in windows and then disconnects but still the session alive in unix) in unix server.
 
AFAIK, the TCP keep alive is exactly that monitoring you're asking for - although it may not do what you require in the way you require it. Apart from that I am not aware of a tool you could use and I doubt there is.

The root of all evil is the client/server architecture in conjunction with the pessimistic locking strategy. But that could only be changed when you change the application ...

Heavy Regards, RealHeavyDude.
 
Back
Top