Upgrading to hibernate 6: Encountered deprecated setting [javax.persistence.lock.timeout], use [jakarta.persistence.lock.timeout] instead

user_243203 0
Viewed 214

I am trying to upgrade to Hibernate 6, but this causes a huge amount of log spam. For every query with my database I get a warning in my console logs:

 WARN deprecation:44 - HHH90000021: 
 Encountered deprecated setting [javax.persistence.lock.timeout], use [jakarta.persistence.lock.timeout] instead

Our code base does not reference javax.persistence.lock.timeout and setting the jakarta property into the peristence.xml file does nothing.

This issue doesn't seem to be documented on the internet, I could only find a single reference to this in a hibernate bug report team, but there are no details.

If its relevant, we are connecting to Postgres on AWS RDS, via the C3P0 connection pool.

This warning continues to appear after removing C3P0 from the server so I don't think this default is coming from there.

Should I just suppress this log source in my log properties file or are there alternatives others are following?

hibernate java
1 Answers

I also experienced the same issue. And it seems not to be fixed yet(in 6.0.1).

At least I see in https://github.com/hibernate/hibernate-orm/blob/c18e611ed6786fd62a6bf2d17c39589c2452fe35/hibernate-core/src/main/java/org/hibernate/internal/FastSessionServices.java that old (and deprecated) javax.* properties are still set and then logged by LegacySpecHelper:

p.putIfAbsent( AvailableSettings.FLUSH_MODE, FlushMode.AUTO.name() );
p.putIfAbsent( JPA_LOCK_SCOPE, PessimisticLockScope.EXTENDED.name() );
p.putIfAbsent( JAKARTA_LOCK_SCOPE, PessimisticLockScope.EXTENDED.name() );
p.putIfAbsent( JPA_LOCK_TIMEOUT, LockOptions.WAIT_FOREVER );
user_32494970
Related