Using v3.1 Beta2. I have a situation where I'm storing a persisted object in a web session variable that is using a timestamp for optimistic locking. It is possible for that persisted object to change during the course of a session. So if I make a change to the object stored in the session and attempt to save it, I may get a StaleObjectStateException error. For this scenario, I am expecting this and I'm doing a try/catch. If I do get the error then I reload the persisted object, remake my change and then save again.

The problem is that even though I'm catching the StaleObjectStateException exception, it's still getting logged as a SEVERE error. I don't want this since in my situation I am expecting and handling it. So how could I prevent the exception from getting logged?

I understand a more graceful solution would be to check to see if the object has changed before attempting to save, but that would require doing extra SQL calls which may be unecessary. Only in rare circumstances in my scenario would the persisted object change during a session, so I don't want to have to check every time.

Thanks.

You could try turning off logging for the class that produces that specific error output.

On the other hand, does it matter if it gets logged? The fact that you handle it doesn't mean its not an exceptional case deserving of logging. Perhaps the level is what bothers you.


JOe

I figured out a soltuion, although not ideal. I've decided to turn off all logging for org.hibernate. This way the exceptions will bubble up and can be handled in my code. If they aren't handled then they will cause a runtime exception and will get logged.

I wish there was a way to handle this on a case by case basis rather than turning off logging globally. I don't want SEVERE exceptions showing up in my logs if they are expected and handled in the code.

Thanks.

Just to share my thoughts on this...

I think you're viewing log output in a manner that is making this more difficult than it has to be.

Log output is just that....a snapshot in time status report of what happened in your system. SEVERE doesn't mean your application can't function.

From Javadocs on Sun:



That doesn't mean your application was poorly written or will fail. It just means that what happened at that snapshot in time is a SEVERE problem. Again, the fact that your application handles this situation means you're fine.

I'm not I've put enough into this to convince you that it is ok.

That said, you should be able to suppress Log messages just from the individual class that produced them, not all of org.hibernate.

joe

"a snapshot in time status report of what happened in your system"

So why does the logging system allow you to choose severity levels? The answer is because there are some things you may not want to see in your log. Does that mean they didn't happen? Of course not. They happened, but they may not be worth logging.

In my opinion a "StaleObjectStateException" is a severe error if you weren't expecting it. But it is completely reasonable that you would catch this error and handle it, in which case it is no longer a severe error and should not show up as such in the log file. This applies to other Hibernate errors as well, such as those relating to constraint violations, etc. They should only show up in the log (in my opinion) if you aren't catching and handling them.

I understand that I could supress logging from just the Hibernate classes that produce just these specific exceptions that I'm handling. But even then there may be other exceptions thrown from those classes that I do want to get logged, or non-severe informational items. Ideally exceptions would not get logged by Hibernate if they were being caught.

Yes, I agree with jim5359 . If you are catching and handling the StaleObjectStateException, Hibernate should not still print the stack trace.

I am having the same problem. I am catching and handling it, but I still get the stack trace on my console and in my log.

How do you disable this just for this class?
Is there an entry I can put in my log4j.properties file somewhere? p..57 and 58 discuss logging briefly, but I guess I need to look at the log4j documentation.

Thanks for any hints.

This may otherwise have adverse consequences, but it seems to work to take care of my problem for now. I just put a line down at the bottom of my log4j.properties file like this:

log4j.logger.org.hibernate.event.def.AbstractFlushingEventListener=fatal

If anyone has a better idea as to how to handle this. please let me know. Thanks.
--Bob