Misleading exception message for using JPA with custom IsolationLevels [SPR-8325]

[spring-projects-issues]

Oliver Drotbohm opened SPR-8325 and commented

When trying to use JPA with custom transaction isolation levels and no specfic JPA dialect configured one will get an exception saying:

Standard JPA does not support custom isolation levels - use a special JpaDialect for your JPA implementation

Unfortunately all our provided implementations do not support custom isolation levels at all. So even configuring a HibernateJpaDialect for example ends up with the same exception. This is not that of a big deal but might lead to quite some time spending on tracing an asssumed bug in the configuration where there actually is none.

---

Affects: 3.0.5, 3.1 M1

Issue Links:

• Isolation support for JPA with Hibernate EntityManager 4 [SPR-11942] #16559 Isolation support for JPA with Hibernate EntityManager 4

Backported to: 3.2.10

2 votes, 4 watchers

[spring-projects-issues]

Joris Kuipers commented

In addition to adding a better message that explains that we don't support this, it would be preferable to actually support this in the various dialects obviously. I'm assuming this issue can be used to track that: if not, then please say so and I'll create a separate issue for that.