Added dependency on play.db.DBApi to play.db.jpa.DefaultJPAApi.JPAApiProvider to ensure that data sources are initialised and bound to JNDI before they are accessed #6799
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
Helpful things
Fixes
Fixes #6792
Purpose
Adds dependency on play.db.DBApi to play.db.jpa.DefaultJPAApi.JPAApiProvider to ensure that data sources are initialised and bound to JNDI before they are accessed.
Background Context
The implementations of JPAApi and DBApi do not have any dependencies that would ensure the order in which they are both created, so there is no guarantee that the data source is bound to JNDI by HikariCPConnectionPool before it is accessed by DefaultJPAApi. By adding a dependency on play.db.DBApi to play.db.jpa.DefaultJPAApi.JPAApiProvider data sources are always initialised and bound to JNDI before they are accessed.
References