Not every exceptions are caught in MVC or WebAPI about exceptionless.net HOT 14 CLOSED

@SKOUB we recently disconnected the global mvc error handler as we were getting duplicate exceptions, upon review it looked like we wouldn't need to wire up to it anymore. Can you try wiring back up to this and see if this fixes this behavior.

6943b0c

For Web API 2.1 can you create a new exception filter with the following content and see if this resolves your web api errors: https://github.com/exceptionless/Exceptionless.Net/blob/master/Source/Platforms/WebApi/ExceptionlessExceptionLogger.cs

If you could update our sample applications with reproduction steps. I'd be more than happy to take a close look under the debugger and get these fixed.

from exceptionless.net.

I will give it a try next week and give you news. Thank you for your help!

from exceptionless.net.

@SKOUB were you able to verify if these changes worked?

from exceptionless.net.

I haven't had time to play with it. But if you had duplicate error with the global mvc error handler, it will come back if it plug it back for sure. So we will have to search why we have duplication.

from exceptionless.net.

i have tested the mvc fix and it seems to solve the problem. I haven't tested the Api fix yet.

from exceptionless.net.

Look at the screenshot, is it possible that this is the problem of the duplicate inserts that you have?

from exceptionless.net.

Yeah looks like it I also see the debugger display is pouting to a property that doesn't exist either

from exceptionless.net.

Those two errors would be the same but the stack trace will change a bit between the handlers

from exceptionless.net.

I think I may have an ideal on how to fix that

from exceptionless.net.

@ejsmith I saw that a few different services clients store a @flag in the exceptions Data property. I think we could also do the same and then we just check for this in the duplicate checker plugin... What are your thoughts.

from exceptionless.net.

I saw the same thing myself. Using a flag to tell that the exception is already grabbed by your client. The logic to remove the duplicate entry will be on the client side or server side?

from exceptionless.net.

This would all be on the client.

from exceptionless.net.

Sounds good to me.

from exceptionless.net.

This should be fixed by this commit: 564d6eb

We will deploy this when we release the next client build (hopefully) in the next week. The work around is to call our extension methods as described above until we fix this. Please let me know if you have any questions.

from exceptionless.net.