System.Net.Sockets.NetworkStream object disposed in shared ser

System.Net.Sockets.NetworkStream object disposed in shared ser

Post by am9obm55dH » Sun, 06 Nov 2005 02:23:02


It reads from a database and populates labels within a user control with
information about a band's next gig -- venue name, date, time, etc.
 
 
 

System.Net.Sockets.NetworkStream object disposed in shared ser

Post by Q2hyaX » Wed, 09 Nov 2005 00:02:07

Hi,
Are you using MYSql? If so then are you setting connection pooling in
connection string? If yes the set the pool;ing to false. Let me know.

Thanks

 
 
 

System.Net.Sockets.NetworkStream object disposed in shared ser

Post by am9obm55dH » Wed, 09 Nov 2005 00:31:32

I am using MySQL. I'm not explicitly using connection pooling but I belive
my web hosting company pools its connections. My understanding of this is a
little fuzzy so bear with me. Isn't connection pooling a good thing... a la
reuse of scarce resources???
 
 
 

System.Net.Sockets.NetworkStream object disposed in shared ser

Post by Q2hyaX » Wed, 09 Nov 2005 07:03:06

Pooling is good. But only effective if the request is always the same. In
your case, since given a hard time by the providers, don't persist the pool.
It doesn't matter if they pool connections. It's up to you to specify, in
connection string, if pooling is enabled.

Did you setting pooling to false?
 
 
 

System.Net.Sockets.NetworkStream object disposed in shared ser

Post by am9obm55dH » Wed, 09 Nov 2005 23:25:06

I set pooling=false. I'll monitor site & see how it behaves. Thanks for the
suggestion.
 
 
 

System.Net.Sockets.NetworkStream object disposed in shared ser

Post by Q2hyaX » Thu, 10 Nov 2005 00:43:01

Keep me posted.