Hi,
I'm struggling here with a multi-threaded test application (around 25
concurrent threads).
Each thread opens, does the same collection of commands, and closes.
the connection, command, transaction etc are all being created on the
calling thread.
and disposed of properly before the thread ends.
this is then all in a very large ongoing loop (I'm searching for memory
leaks in my business object layer)
however i am experiencing "Reading from the stream has failed."
exceptions randomly if I am connected via
pipes, I don't experience these issues when connected TCP/IP.
So I am assuming there's a threading/locking issue with communication
over named pipes.
the exception is really vague (#-2147467259, no innerException) and is
occurring when i am doing myConnection.Open();
Is this a known bug? Anything i can do to stop it?
I'm using "pooling=false;" in my connection string.
Thanks,
Chris.