>I'd give your .oProcess object a GUID as well and log both GUIDs all the time - not just when there's an error. If you find a case of the same connection GUID being used by two or more different processes you'll at least know that the source of the problem is indeed the sharing of a connection. Logging the method as well might help to narrow down the code where this is happening. It's also worth checking the log even when there's no error - it could be that the connection is often shared without having side effects which actually cause a problem....

Yes, this is what I had in mind.

But, since this afternoon, I have applied three changes in the application. Those changes were related to instantiating objects from the framework by passing oApp instead of oProcess. Since this afternoon, I didn't get the situations. But, I will wait longer and we will see how it goes.

Thanks