Scenario: 1. ObjectPooling true/enabled or false for ServicedComponent class. 2. Libray activation. 3. JustInTimeActivation true for ServicedComponent class. 4. AutoComplete false for a method. 5. ContextUtil.SetComplete is called just prior to step 5 below. 6. An exception is thrown from the ServicedComponent method out to a non- serviced .net client in a tight loop to the Serviced component method.
Issue: I noticed that if the original exception instance is thrown from the Serviced component method after SetComplete is called the object appears not to Deactivate after the method call/I see assciated Oracle connections staying open. However, strangely? if I catch the orginal exception and create and throw a new exception instance in the same method there appears to be object Deactivation after the method call/I see assciated Oracle connections close. I must be doing something wrong/what's going on here? =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
