Hello Steve/Sanne, While upgrading to hibernate 4.1.9 from 3.6.0 I am facing an blocking issue for which I would appreciate if you can provide your inputs. The issue was logged on jira forum but it didn't get much attention. I will paste it here once. Kindly let me know your thoughts. Description I upgraded my project with hibernate 4.1.9 and spring 3.2.1 and noticed that hibernate throws RuntimeExceptions instead of checked exception in the earlier version (3.6.0 final was the one we used earlier). The code use case is as below. We use spring jdbc template for executing jdbc queries and the application is configured to use JPA (JPATransactionManager and JPADialect) for mapped entities. When executing a query which could throw a exception for e.g. a select query on a table that does not exist, hibernate now proxies the jdbc statements and throws a SQLGrammerException (extends RuntimeException) instead of a checked exception - SQLException. Since spring catch's SQLException, the code no longer executes the catch block and fails with an exception. Attached a sample java program to reproduce the issue. Please execute the main method of the ExceptionHandlingTask class. It starts a spring transaction and executes a query on a non existing table. Spring and hibernate jars must be included in the classpath. Thank you, Amit.