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

[Guest]

I have a .aspx page on my web site that intermittently fails to load with the
following error: Cannot access a disposed object named
"System.Net.Sockets.NetworkStream.

My hosting company says this is due to the fact that multiple ASP.NET
applications are sharing the same server. the only remedy they can offer is
for me to pay for a dedicated server (obviously for more hosting $$).
Is the hosting company being lazy and not getting to the root of a solvable
problem?
Can the problem be in my code?
Can somebody suggest a solid but reasonable web hosting company that
supports .NET?
Thanks,

 

[Guest]

What is your page trying to do, load a grid from databse, take over the
world?.....need to give additonal info.

 

[Guest]

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.

 

[Guest]

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

 

[Guest]

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???

 

[Guest]

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?

 

[Guest]

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

 

[Guest]

Keep me posted.

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