Underlying connection was closed.

Underlying connection was closed.

Old forum URL: forums.lhotka.net/forums/t/9273.aspx

jwhook posted on Monday, July 26, 2010

Hello All.

We have a user who comes in through the web who about once a day errors out with:

System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.

The stack details vary slightly depending on what they were doing at the time. Typically, it's after they've initiated a search in our application.

I've looked through the threads here where something similar has happened, but they are all on later versions of CSLA than ours. We're way back at 1.5x, with a rebuild to .Net 2.0. While we will get to later versions of CSLA, it probably won't be until the end of the year.

I'm at a loss to even know where to start, so any advice would be helpful. All of our users startup from the same place, although only this one user connects via the web to get to the startup location. None of our other users are experiencing this problem.


- jim

RockfordLhotka replied on Monday, July 26, 2010

It sounds like a timeout issue. When you say "connects via the web" are you referring to the data portal running over the web, or something else?

Either way though, if it is a timeout issue, the solution is almost certainly to up the timeout limits on your network technology (Remoting, asmx, etc), probably on both client and server. That's typically done through configuration - though with the Remoting channel of the data portal it might mean creating a custom client-side proxy subclass (I honestly don't remember how that worked in 1.5 off the top of my head).

jwhook replied on Monday, July 26, 2010

I mis-stated the connectivity. They come in through our firewall, which redirects them to the appropriate location, which is the same application server everyone else is running from. They do have their own folder with their own copy of netrun.exe, but it's an exact copy of what our people inside the firewall use.

We'll see if we can make some adjustments to the network and see what happens.


Kevin Fairclough replied on Monday, July 26, 2010

This exception is probably not the real fault.  I would enable logging on the web server.

I had similar errors and it was a class that was not marked [Serializable].  It might have been an inner class, can't remember.

jwhook replied on Monday, July 26, 2010

Would having a class unmarked result in intermittant behavior? That doesn't sound right, but ... It's also the case that they can be running different parts of our application when this occurs, but I suppose that would point to a problem in code that is used by lots of the application.

Kevin Fairclough replied on Tuesday, July 27, 2010

No it wouldn't be intermittent, only if the class was used intermittently.

I thought your classes were going through the data portal.  Any class that goes through the data portal must be marked.

Copyright (c) Marimer LLC