Session being reset by server

Discussion in 'ASP.NET / ASP.NET Core' started by jibbercan, May 2, 2008.

  1. In our web application we are allowing users to download files from a database. Some of them are large (i.e. > 25 Mb) and we're seeing that with the larger ones, the user's session is being reset during the file download process so they have to re-login to the website.

    We thought maybe there was a memory limit we were exceeding when streaming the file to the response so we slowed down the feed to try to allow the client to keep up with the stream. This seemed to make matters worse so that even during the download the user is getting the "The connection with the server was reset" error message and the download was not even completing.

    We're wondering if there's a response time-out or deadlocksetting which is killing the client's session when the user is downloading one of these large files and if so can we raise the bar so that these files can be downloaded.

    This is rather urgent please advise.

    Best Regards and thanks for all your great help previously.

    James Sutton
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    Can't really tell based on the error message but it looks like the process was killed.


    Have you opened a support ticket?


    Bruce

    DiscountASP.NET
    www.DiscountASP.NET
     
  3. Does anyone have any suggestions for reducing ASP.NET 3.5 web application RAM usage?

    I am also continually hitting the 100MB limit on my discountasp.net server (according to support) and I am getting recycled at least several times per day, but I haven't had much luck tracking down where all the RAM is going. On my local machine, I can't seem to get the RAM indicator in Task Manager for the web server to go much above 50MB, so I don't know what might be going on.

    I removed all of my session variables and IIS server caches, but this doesn't seem to have helped - if anything RAM usage might be a bit higher now without the server cache (I was caching several small 'type' tables in IIS 6.0 server memory to reduce joins). I am using LINQ to SQL for all my data access and I went through and made sure all of the LINQ DataContext objects were manually cleaned up with calls to Dispose().

    Any suggestions or links to articles or better diagnostic/testing tools would be greatly appreciated. Also, would there be any benefit to upgrading to IIS 7.0?
     

Share This Page