Hi there
I know a few of you are using asp.net with uo.net and perhaps connection pooling b I want to ask a question b I have this scenario where my connection pools are on occasion fully utilised due to a combination of a spike in system usage, very busy backend systems, and probably some bad backend code, and so my asp.net app is grinding to a halt (causing me major grief). I would like the app to try a pooled connection, with a timeout, and if it times out to try and connect again using a non pooled connection. b just placing this in a try catch in my connector class seems to break the pooling completely (i.e. when it tries to connect without pooling, the existing pools disappear and donbt want to reconnect) b So I wondered if any one else has done something similar or has any suggestions Thanks Symeon. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
