D
dbeavon
Guest
>> start your client sessions with -q , The -q isn't a guarantee ... any newly started session still has to read r-code before it can run, and this has the potential to crash if the code compilation is actively underway. Funny enough, the bug came up on a build server that does nothing more than compile our source code. So we are avoiding the issue in production, but our build server is a mess as a result of COMPILE statements that are crashing the processes in an unpredictable and unavoidable way. Is there a way to tell a client session NOT to use the preexisting r-code, even if present? I had a long support case with Progress and didn't pose that particular question but it might be a potential workaround, if such a feature existed. I got the impression that they didn't want to make changes on their end, and were OK with occasional/unpredictable crashing of the AVM.
Continue reading...
Continue reading...