D
dbeavon
Guest
>> There is an unfortunately strong correlation between people who use "kill -9" and people who take those other steps. That sometimes leads to the false impression that killing the shared memory connection corrupts data. Tom, I can understand this point of view because I have a long experience with Progress too, and after a while you learn how to avoid some of the more severe pitfalls. But I can see the other side too. We are talking about the crashing of the *entire* OE database server because a *single* connected client was misbehaving and needed to be terminated. It isn't reasonable for a system admin to face these high stakes whenever they must terminate a runaway (or hung) client application. Nor does it seem right that we should "blame the victim" when the OpenEdge database goes into a panic mode and decides to crash itself, and it results (directly or indirecly) in subsequent database corruption. On a personal note, I recently opened a bug (KB 000089700) where one of the workarounds for the problem, once encountered, is to terminate a remote server with promon (see article P39432 for those instructions). This is analogous to killing a shared memory client. If we ever face any subsequent data corruption as a result of that bug, or the recommended workaround, then it is definitely the OE database that will be getting the blame.
Continue reading...
Continue reading...