Huge delay when an exception occurs
Hi,
I am having an issue, we tested it on another server and locally and it only happens on appharbor. When an unhandled exception occurs, it takes a huge delay before showing up, and if we try to access the webpage again, it just doesn't respond. But other users can access the website without any problems.
I don't know if there's a setting in the web.config that can causes that or if this is a known issue, I've looked through the support forum and did not find anything about this.
Maybe that's in our code, but we don't manage to find anything and like I said earlier it does not do that on our other server, neither locally.
Thanks,
Charles
Discussions are closed to public comments.
If you need help with AppHarbor please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by friism on 21 Apr, 2011 04:13 PM
We're aware of this problem (it has to do with logging the exceptions) and will be fixing it shortly. I'll post an update here.
2 Posted by couellet on 22 Apr, 2011 12:16 PM
Thanks, I would like to add that I found a kind of workaround for the moment, it might be useful for other people
In my Application_Error in Global.asax I added
Server.ClearError() after logging it and doing the stuff I needed to
Then it seems to not propagate to the apphb logging things
3 Posted by alalbers77 on 25 Apr, 2011 09:10 PM
I too have noticed the huge response delay when an unhandled exception occurs.
The Server.ClearError() workaround fixed the issue and now my custom error page shows up without delay.
Thanks for the tip.
Support Staff 4 Posted by rune on 25 Apr, 2011 09:47 PM
This issue is now resolved so you shouldn't experience the delay anymore and you should be able to see stack traces for your unhandled exceptions by following the "Errors" link from your application page.
Let us know if this problem persists for you.
Best,
Rune
rune closed this discussion on 25 Apr, 2011 09:47 PM.
alalbers77 re-opened this discussion on 26 Apr, 2011 01:11 AM
5 Posted by alalbers77 on 26 Apr, 2011 01:11 AM
Thank you very much! Works great now.
Al
On Mon, Apr 25, 2011 at 4:47 PM, Rune Sørensen <
[email blocked]> wrote:
friism closed this discussion on 26 Apr, 2011 01:27 AM.