DataGrip Connection Pool Timeout Missing in Production

Connection Pool Timeout

The goal is to ensure that the production database connection pool applies the same 30‑second timeout that works locally. In the production project the JDBC URL overrides the default timeout, and the project’s connection‑pool settings do not contain a timeout property, so DataGrip inherits the server’s default and connections hang until the server times out.

Constraints

Production uses a custom JDBC URL that hides the timeout, and the project file is shared across multiple users. Network latency or firewall rules can further delay the connection, making the missing timeout more pronounced.

Unresolved Questions

• What specific setting should be added to the production project file to enforce the desired timeout?
• How can the timeout value DataGrip uses for the production connection be verified in the logs?
• Is there a way to apply a global timeout across all projects without editing each project file individually?