How to handle exception occurred in MVC onexception method

Question

0.00/5 (No votes)

See more:

.NET4.6

Hi,

I have override OnException Method in my MVC BaseController.
protected override void OnException(ExceptionContext filterContext)

Do we need to handle exception in this method? What will happen if some error occurred in this method?
What is the best practice to handle this scenario.

Regards,
Saurabh

What I have tried:

I tried to look at different approach like using try catch inside OnException but nothing seems correct to me till now.

Posted 13-Feb-20 1:58am

saurabh.15in

Updated 13-Feb-20 5:32am

v2

Add a Solution

Comments

jimmson 13-Feb-20 8:10am

You seem to misunderstand what "protected" means in this case. Question would be much more clear if you can include your code.

saurabh.15in 13-Feb-20 9:05am

Thanks Jimmson for reply.
I am not referring to protected access specifier.
My doubt is, what we can do if some exception occurred in OnException Method itsself. I have implemented my own logging here.
Example : Some error occurred in Application-> It comes to OnException and try to log the exception in DB using some logger-> some exception occurred in logger itsself(lets say DB connection is lost) again there will be exception inside Onexception. Now what we can do to handle this situation.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2020-02-13T05:33:00

You normally keep your exception handling code simple and very robust so it can't throw its own exceptions. That means not taking anything for granted. If you're doing database work, you NEVER assume the connection works and the table you're writing to exists.

On top of that, you also have to think about logging your errors in an alternate place, guaranteed to work if the database fails.