We use a commercially available application written in Progress 9.1D and running on a Windows platform. Something in the application is failing to release user sessions when users logout. The result is that our available Progress license count is reached and we are locked out until we restart the database and broker. This occurs at least once everyday. I am aware of the method of killing user sessions with the ProShut command. However, I am looking for something I can do from code to release the user sessions without restarting the database and broker. Other database engines like Oracle and SQL Server provide a way to kill user processes from within the database. How can this be done in Progress?
Hung Database and Broker Sessions
- Thread starter BCM
- Start date
If I understand correctly,
These are 4GL clients ?
I'm guessing GUI application and Workgroup database ?
Is the application still open on the user desktop after logging out ? or even still running in the background ?
And you want or expect that after logging out and regardless if the client is still running that the application releases the connection, right ?
Maybe if you want I can put together and post a small watch dog process that kicks off users that have been idle for x period of time ?
Other then any other possible license, code or arch changes I think this maybe the most unintrusive to do.
These are 4GL clients ?
I'm guessing GUI application and Workgroup database ?
Is the application still open on the user desktop after logging out ? or even still running in the background ?
And you want or expect that after logging out and regardless if the client is still running that the application releases the connection, right ?
Maybe if you want I can put together and post a small watch dog process that kicks off users that have been idle for x period of time ?
Other then any other possible license, code or arch changes I think this maybe the most unintrusive to do.
TomBascom
Curmudgeon
There is no way to disconnect a user from "within the database" or by using pure 4GL commands.
However... you seem to be under the impression that using proshut results in a complete database shutdown. It does not have to. There are options to disconnect specific users rather than shutting down the whole database.
If you can identify the users that you want to disconnect it is common to script an interface to proshut (or promon, they're the same executable under the covers) to take care of this problem.
However... you seem to be under the impression that using proshut results in a complete database shutdown. It does not have to. There are options to disconnect specific users rather than shutting down the whole database.
If you can identify the users that you want to disconnect it is common to script an interface to proshut (or promon, they're the same executable under the covers) to take care of this problem.
TomBascom
Curmudgeon
BTW -- how does this licensing difficulty justify the thread title of "hung database"? Is there more to the story?
I hope that you aren't confusing the value of -n with "licensed users". They are not the same thing except in the fevered imaginations of a few exceptionally greedy sales weasels.
I hope that you aren't confusing the value of -n with "licensed users". They are not the same thing except in the fevered imaginations of a few exceptionally greedy sales weasels.