D
dbeavon
Guest
Thanks Laura, I was preparing to wrap a critical section around the first call to the CLR bridge (which happens in my proc trigger: connect-proc) . For whatever reason that first use of the CLR seems to be a fairly predictable place for failure. It behaves in a similar way to a dummy reference to a .Net class. I did a limited amount of work to serialize the connect-proc already and it seems to fix the problem. I had attempted my own serialization using OE database record locks. On the other hand, the remote database interaction also has the effect of simply slowing things down; and we already know that the the problem happens much less frequently when things are running more slowly (eg. it took TS a few tries to reproduce this behavior because of slow VM's, long sleep statements in the reproducible, and because of ABL code that wasn't yet compiled and was being compiled on-the-fly.) Unless someone has another idea, I might start looking into WIN32 library calls that exclusively lock local files or something like that. Its not in-process synchronization, but its probably faster than doing remote database operations.
Continue reading...
Continue reading...