M
Mike Fechner
Guest
I think it’s safe to assume, that a developer working on Windows in Progress Developer Studio does not have shared memory access to a production database … I’m killing (DELETE key in Windows Task Manager) runaway prowin.exe’s since years. And my DB’s have never become inconsistent. Von: dbeavon Gesendet: Freitag, 24. August 2018 19:42 An: TU.OE.Development@community.progress.com Betreff: RE: [Technical Users - OE Development] How to break out of program running in infinite loop in PDSOE Update from Progress Community dbeavon The OE-dba in me thinks you might want to be very careful. Is this a "shared memory" client application? Aren't those always risky to kill (IE. by killing them, it risks an OE database crashing, or worse)? It seems like you should take into consideration whether it is a "shared memory" app, vs a remote "client-server" app (which is connected by TCP.) You might want to try to use disconnect the related user from the database *before* killing the application, right? proshut -C disconnect I don't mean to cause alarm, but there are KB's that talk about the dangers of killing processes that share memory with the database, eg. knowledgebase.progress.com/.../P14679 View online You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here . Flag this post as spam/abuse.
Continue reading...
Continue reading...