Kbase 11917: Proshut -by can hang with multiple db connects & MESSAGE
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Proshut -by can hang with multiple db connects & MESSAGE
If you have 2 servers running and a client running the attached
program, if you try to shutdown the servers, the first one will
shutdown fine, but the second one will hang until the client presses
the space bar.
If you start a 3rd server and connect to it, you
can solve this problem by shutting down the 3rd server in between
shutting down the 2 servers that you are accessing the data on.
There are 3 distinct conditions under which
proshut -by hangs with multiple db connections. The first is if
both message buffers have text, but not any update/set statement.
The second is if there is an update pending in the message buffer of
the unattended client session. The third is if the unattended client
session has escaped out to the operating system and is sitting there
when the proshut attempts to kick it off.
The work-around fixes both text only MESSAGEs and
MESSAGE buffers containing an UPDATE or SET.
The work-around will still not let proshut -by continue
if there is an unattended client session that was escaped out to the
operating system.
Workaround information:
Start another server; have clients connect to it
behind the scenes, but not activate any record
buffers to it.
shut it down in between the proshut for database a
and database b.
if databases a and b are your production database that hang, then
prodb c empty. proserve c (and use the smallest possible startup
parameters). In the client script or .pf file, have a connection to
that database (-db c).
Then change the shutdown script so that it
proshut a -by
proshut c -by
proshut b -by This will allow all three to shut down.
Progress Software Technical Support Note # 11917