Hibernate ORM tries to connect to the database on startup even with schema validation disabled

[yrodiere]

Apparently it tries to connect to the database to retrieve metadata. This might be a bug: I think we disable that metadata collection on startup, because that cannot work with native images, so I don't know why that collection happens anyway...

See #29846, quoting:

I think is connecting to database. With not option to delay the connection.

no validate the scheme = false.

Originally posted by @sirlordt in #29846 (comment)

[quarkus-bot]

/cc @Sanne(hibernate-orm), @gsmet(hibernate-orm)

[yrodiere]

@sirlordt you're using the configuration property javax.persistence.validation.mode, which is not expected to work in application.properties. You should use the Quarkus-specific property quarkus.hibernate-orm.database.generation.

That being said, even taking that mistake into account, the stacktraces still look suspicious. We need to have a closer look.

[yrodiere]

See also #34309. It seems Hibernate ORM does try to connect to the DB on startup to retrieve metadata, here's the stack trace:

handlerFromSharedCache:288, ConnectionPool (io.agroal.pool)
getConnection:249, ConnectionPool (io.agroal.pool)
getConnection:86, DataSource (io.agroal.pool)
getConnection:23, QuarkusConnectionProvider (io.quarkus.hibernate.orm.runtime.customized)
obtainConnection:316, JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess (org.hibernate.engine.jdbc.env.internal)
initiateService:152, JdbcEnvironmentInitiator (org.hibernate.engine.jdbc.env.internal)
initiateService:34, JdbcEnvironmentInitiator (org.hibernate.engine.jdbc.env.internal)
initiateService:119, StandardServiceRegistryImpl (org.hibernate.boot.registry.internal)
createService:264, AbstractServiceRegistryImpl (org.hibernate.service.internal)
initializeService:239, AbstractServiceRegistryImpl (org.hibernate.service.internal)
getService:216, AbstractServiceRegistryImpl (org.hibernate.service.internal)
configure:45, JdbcServicesImpl (org.hibernate.engine.jdbc.internal)
configureService:125, StandardServiceRegistryImpl (org.hibernate.boot.registry.internal)
initializeService:248, AbstractServiceRegistryImpl (org.hibernate.service.internal)
getService:216, AbstractServiceRegistryImpl (org.hibernate.service.internal)
<init>:274, SessionFactoryOptionsBuilder (org.hibernate.boot.internal)
buildSessionFactoryOptionsBuilder:70, PrevalidatedQuarkusMetadata (io.quarkus.hibernate.orm.runtime.recording)
build:81, FastBootEntityManagerFactoryBuilder (io.quarkus.hibernate.orm.runtime.boot)
createEntityManagerFactory:74, FastBootHibernatePersistenceProvider (io.quarkus.hibernate.orm.runtime)
createEntityManagerFactory:80, Persistence (jakarta.persistence)
createEntityManagerFactory:55, Persistence (jakarta.persistence)
get:156, JPAConfig$LazyPersistenceUnit (io.quarkus.hibernate.orm.runtime)
run:64, JPAConfig$1 (io.quarkus.hibernate.orm.runtime)
run:833, Thread (java.lang)

And it seems to be on purpose; we disable this metadata retrieval during static init but re-enable it during runtime init (application startup):

quarkus/extensions/hibernate-orm/runtime/src/main/java/io/quarkus/hibernate/orm/runtime/FastBootHibernatePersistenceProvider.java

Lines 230 to 231 in 143a61b

	// Allow detection of driver/database capabilities on runtime init (was disabled during static init)
	runtimeSettingsBuilder.put("hibernate.temp.use_jdbc_metadata_defaults", "true");

I believe the only way to prevent this metadata retrieval would be #13522, which involves a fair amount of work, in particular upstream, and may require explicit configuration from users since some metadata just cannot be inferred without connecting to the DB (e.g. sometimes Hibernate ORM needs to know about some DB settings).

[yrodiere]

FWIW we'll need to address at least #13522 and this upstream issue before we can work on this, and maybe more: https://hibernate.atlassian.net/browse/HHH-17425

[AB-xdev]

Hey we're having the same problem that Quarkus tries to connect to the database during boot (which does not exist at that time).

This can usually be solved easily (like in Spring Boot) by providing the following properties:

• hibernate.boot.allow_jdbc_metadata_access=false
• jakarta.persistence.database-product-name=...
• jakarta.persistence.database-major-version=...
• jakarta.persistence.database-minor-version=...

I supplied these using quarkus.hibernate-orm.unsupported-properties."full-property-key" however some are ignored:

Persistence-unit [<default>] sets property 'hibernate.boot.allow_jdbc_metadata_access' to a custom value through 'quarkus.hibernate-orm.unsupported-properties."hibernate.boot.allow_jdbc_metadata_access"', but Quarkus already set that property independently. The custom value will be ignored.
Persistence-unit [<default>] sets property 'jakarta.persistence.database-product-name' to a custom value through 'quarkus.hibernate-orm.unsupported-properties."jakarta.persistence.database-product-name"', but Quarkus already set that property independently. The custom value will be ignored.

Is it somehow possible to enforce setting these values during runtime? Or is there some other way to do that?

Fun Fact:
Manually overwriting FastBootHibernatePersistenceProvider and removing this continue makes it work.