RadUploadProgressHandler causing .net4 website downtime

Thread is closed for posting
3 posts, 0 answers
  1. Derek
    Derek avatar
    2 posts
    Member since:
    May 2013

    Posted 01 Dec 2014 Link to this post

    Our server/website is going down at random times. I now believe this to be related to the RadUploadProgressHandler. A detailed description of the problem as well as server specks can be found here. As I said in the post I have set up a W3C Extended Log File Format log for this site. During downtime there seems be an excessive amount of GET requests for a Telerik.RadUploadProgressHandler.ashx, in fact these are pretty much the only requests which are being logged with a different request, say for a webpage, every couple minutes or so. The machine with which the website resides has one single core CPU, meaning that it can in reality only process one task at any given time. So my questions are, if the server is continuously processing these GET requests for a Telerik.RadUploadProgressHandler.ashx, then will it not process any other requests causing the server/website to appear as if it is down? If so, is this a known issue with this control and are there any ways to fix this issue? The version of telerik controls we are using is 2011.3.1115.40.
  2. Peter Filipov
    Peter Filipov avatar
    1028 posts

    Posted 04 Dec 2014 Link to this post

    Hello Derek,

    How do you use the RadProgressArea control - with a RadUpload control or interdependently measuring a custom process. Keep in mind that if your users start uploading many files at the same time it is possible to push your server.

    Peter Filipov

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

  3. Derek
    Derek avatar
    2 posts
    Member since:
    May 2013

    Posted 04 Dec 2014 in reply to Peter Filipov Link to this post

    It's used with a RadUpload control and a RadProgressManager. This seems to have fixed my issue however.
Back to Top