HikariCP | 光 HikariCP・A solid , high-performance , JDBC connection | DB Client library

You should be passing the .env variables to backend container as you did for db:

Luis Miguel Mejía Suárez's comment worked perfectly and was the easier approach.

In the context of this project, all I had to do was:

1. Append -SNAPSHOT to the version in /version.sbt (should not be needed normally but for this project I had to do this)
2. Run sbt publishLocal in the parent project.

After this, the example project (which already targets the -SNAPSHOT version) is able to pick up the locally built package.

you can set under db config:

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

The problem here is that determining the hashCode of the data class instance is leading to a stackoverflow error due to the bidirectional association (mutual references).

To avoid this you need to exclude the @ManyToMany properties from the hashCode method (e.g. by explicitly declaring hashCode on your own).

Property include/exclude on Kotlin data classes

It seems the issue lies in the fact with how you try to access your DB in gitlab.

When you add the mysql service

I found a solution to my problem in adding

I've tried your example:

The reason for this is that Jaybird currently doesn't support a timeout for Connection.isValid(int) and ignores it, and thus - if the specified timeout is non-zero - it registers a SQLWarning on the connection (instead of throwing an exception). Although registering a warning here isn't specified in the JDBC specification, this is similar to what JDBC requires a driver to do when it replaces/ignores user-specified values when configuring the result set type, concurrency and holdability.

When Hibernate notices there is a warning registered on the connection, it will log that warning in org.hibernate.engine.jdbc.spi.SqlExceptionHelper. This logging of warnings can be disabled by setting the property hibernate.jdbc.log.warnings=false (see Query Settings in the Hibernate documentation). In case of Spring Boot, I guess you can set this as property spring.jpa.properties.hibernate.jdbc.log.warnings (but I haven't verified this).

The timeout is configurable through the HikariCP property validationTimeout, but - by default - this doesn't accept a value lower than 250 milliseconds (you can change that with system property com.zaxxer.hikari.timeoutMs.floor). Alternatively, you can configure HikariCP property connectionTestQuery with - for example - select 1 from rdb$database, so HikariCP uses the test query instead of Connection.isValid(int). Be aware that a test query has more overhead.

The warning code printed is the SQLWarning.getErrorCode() (technically, SQLException.getErrorCode(), a.k.a the vendor code). And given this warning doesn't have an error/warning code, its value is 0, which simply means "there is no specific vendor code associated with this warning".

I have created this issue to see if actual timeout support can be added in Jaybird 4.0.6 or Jaybird 5.

Disclosure: I am one of the maintainers of Jaybird.