Kbase 16622: Telnet Session Hangs Server After Abnormal Disconnect
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/10/2006 |
|
Status: Unverified
GOAL:
What to do when an abnormally disconnected telnet user causes the broker to hang.
GOAL:
How to prevent this situation from recurring.
CAUSE:
Typically, when a telnet session disconnects abnormally (example: user
powers off the terminal first disconnecting from the application) the terminal session sends a hangup signal (SIGHUP) to the application. If the hangup signal is not sent, which can happen depending on configuration, the application, namely the PROGRESS broker, will not be notified that the terminal session has gone away. This can prevent the proshut command from executing successfully because Progress will think the user is still connected.
FIX:
In Versions prior to 6.3, if the broker hangs when trying to perform a proshut after a telnet session disconnects abnormally, you would need to kill the shutdown process, remove the user via promon, and use ipcrm to remove the shared memory segment for the database.
With the release of Progress Version 6.3 a force (-F) switch was added
as an option to the proshut command, and can be used in lieu of the
procedures described above.
Proshut <database name> -F
For Version 6.2+ under VMS, the syntax is:
PROGRESS/MULTI_USER=SHUTDOWN/ACCESS=FORCED