F
frank.meulblok
Guest
Well, if the .NET code is only used in the sessionConnectProc, setting up a set of session-managed clients that do nothing more than connect and disconnect as fast as they can should work to put the stress on that code. And that should increase the odds of triggering the issue if it's tied to number or frequency of invocations of the procedure.
Continue reading...
Continue reading...