D
dbeavon
Guest
>> I have a repro now, and I'll submit to tech support. Tech support was able to recreate this as well. The case number is 00508141. We are eager for a fix, despite the fact that it is rare. When it comes up, it causes an outage and involves manual intervention (to restart the app or appdomain). Our openclient processes won't auto-recover (ie. after the exception, the static member fields within the API become corrupted and don't repair themselves until things are restarted).
Continue reading...
Continue reading...