Critical Description
The problem is evident when more than one thread starts using the database during startup. For example, when there are jobs that run concurrently with main startup sequence.
Two different JPA connections are started, and one of the two reports errors during initialization.
A concurrent lock should be present to pause other threads waiting for a database connection until the first one is correctly initialized.