S
slacroixak
Guest
Hi Stefan, thanks you for your input. I just gave it a try. This method sound amazing but cause two problems: 1) it inserts about 1500 lines in the agent log file to show the terrible offending callstack . 2) It raises Progress.Lang.SysError on the client side saying "Server Terminated Unexpectedly". Perhaps I could manage to catch it an decide to ignore it, but if I get this kind of unexpected error for another reason, then I will miss it 
doing a hara-kiri with an OS-COMMAND kill leads to about the same result, but without the issue in the log I wish there would be a way to achieve a nice exit quit, an move the agent outside of the pool so it cannot process any other request. Any opinion from PSC people?
Continue reading...
doing a hara-kiri with an OS-COMMAND kill leads to about the same result, but without the issue in the log I wish there would be a way to achieve a nice exit quit, an move the agent outside of the pool so it cannot process any other request. Any opinion from PSC people?Continue reading...