When I call criteria.list(), Hibernate now appears to throw a NumberFormatException. I have a logging statement before the offending line which executes correctly, and one after which is never executed. I catch a NumberFormatException in this block, not a Hibernate exception, and my log doesn't show any errors from Hibernate.

Any thoughts on how to look for the problem? The log is pretty long, and I don't know what part of it is relevant, so I doubt posting it is useful to anyone, and my java code hasn't changed from when it worked, so I'm guessing I have a mismatch between the database schema and the mapping file, but don't know how to do debug this.

Do you think anyone has idea how to debug this if you do not? :)

Unlike us you can see
1. exception stack trace
2. SQL statement being executed
3. your mapping file
4. your table column data types
3. your class sources

Hint: if you paste at least SOMETHING of it, it would be much easier :)

Actually, I suspect that yes, someone would have figured this out shortly. I had neglected to put type="yes_no" on one of my boolean fields, and Hibernate tried to convert a 'Y' in the database to a 1. I think Hibernate should be able to trap this and throw an exception, but oh well.

In response to your note, there was no stack trace. My mapping file is a couple thousand lines long, and it was unclear where it was executing without looking at the log output, which was also several thousand lines long. I don't expect others to do this level of debugging for me. I was just hoping someone would have an idea why Hibernate would throw such an exception, or where I should turn. Thanks for the quick response though.

Hey, hey! If you have and exception, you can always make a stack trace :)



Never mind. I'm glad you solved the issue.

Don't worry, dimas. It's never bad to enforce commen sense. :)