bucket4j-spring-boot-starter incompatible with testcontainers

[nie-suva]

Hello

Don't really know where to place this issues, if its related to bucket4j-spring-boot-starter or spring-boot-testcontainers.
When I setup my project with this starter and the testcontainers starter something getting messed up, so that spring boot isn't able any more to connect to postgresql container created by testcontainers.

java.lang.RuntimeException: Driver org.postgresql.Driver claims to not accept jdbcUrl, jdbc:h2:mem:0f0956c1-7e99-4b0c-a65e-5efe370afaae;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE
	at com.zaxxer.hikari.util.DriverDataSource.<init>(DriverDataSource.java:109) ~[HikariCP-5.1.0.jar:na]

I created a mcve to reproduce the issue: https://github.com/[mavarazo/mcve_testcontainers](https://github.com/mavarazo/mcve_testcontainers)
when ch.mav.mcve_testcontainers.LocalApplication from test folder is started.

btw: I used the this guide: https://github.com/testcontainers/java-local-development-workshop/blob/main/step-3-local-development-environment.md

[MarcGiffing]

It seems that there is a problem with your Postgres / H2 configuraiton:

• Driver org.postgresql.Driver claims to not accept
• jdbc:h2:mem:0f0956c1-7e99-4b0c

Driver is postgresql and jdbc url is h2

[nie-suva]

You catchend a point, that was a miss configuration. H2 should be defined as dependency.

So I updated the mcve and removed the h2 dependency. Still isn't bucket4j and testcontainers working together.
Something gets messed up, while evaluating a jdbc url, which works without bucket4j.

org.testcontainers.images.PullPolicy     : Image pull policy will be performed by: DefaultPullPolicy()
o.t.utility.ImageNameSubstitutor         : Image name substitution will be performed by: DefaultImageNameSubstitutor (composite of 'ConfigurationFileImageNameSubstitutor' and 'PrefixingImageNameSubstitutor')
org.testcontainers.DockerClientFactory   : Testcontainers version: 1.20.6
o.t.d.DockerClientProviderStrategy       : Found Docker environment with Environment variables, system properties and defaults. Resolved dockerHost=unix:///run/user/2669/podman/podman.sock
org.testcontainers.DockerClientFactory   : Docker host IP address is localhost
org.testcontainers.DockerClientFactory   : Connected to docker: 
  Server Version: 5.2.2
  API Version: 1.41
  Operating System: rhel
  Total Memory: 31808 MB
org.testcontainers.DockerClientFactory   : Checking the system...
org.testcontainers.DockerClientFactory   : ✔︎ Docker server version should be at least 1.6.0
tc.postgres:16-alpine                    : Creating container for image: postgres:16-alpine
o.t.utility.RegistryAuthLocator          : Failure when attempting to lookup auth config. Please ignore if you don't have images in an authenticated registry. Details: (dockerImageName: postgres:16-alpine, configFile: /home/nie/.docker/config.json, configEnv: DOCKER_AUTH_CONFIG). Falling back to docker-java default behaviour. Exception message: Status 404: No config supplied. Checked in order: /home/nie/.docker/config.json (file not found), DOCKER_AUTH_CONFIG (not set)
tc.postgres:16-alpine                    : Reusing container with ID: b42fed5ac1398d805d1690834fb30c236dff29c724126db1b1e807a34f41d722 and hash: ba818691a4192523c5cab7c58200e97956343c88
tc.postgres:16-alpine                    : Reusing existing container (b42fed5ac1398d805d1690834fb30c236dff29c724126db1b1e807a34f41d722) and not creating a new one
tc.postgres:16-alpine                    : Container postgres:16-alpine started in PT0.178936305S
tc.postgres:16-alpine                    : Container is started (JDBC URL: jdbc:postgresql://localhost:44439/test?loggerLevel=OFF)
ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaConfiguration.class]: Failed to initialize dependency 'liquibase' of LoadTimeWeaverAware bean 'entityManagerFactory': Error creating bean with name 'liquibase' defined in class path resource [org/springframework/boot/autoconfigure/liquibase/LiquibaseAutoConfiguration$LiquibaseConfiguration.class]: Failed to instantiate [liquibase.integration.spring.SpringLiquibase]: Factory method 'liquibase' threw exception with message: Error creating bean with name 'dataSource' defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]: Failed to instantiate [com.zaxxer.hikari.HikariDataSource]: Factory method 'dataSource' threw exception with message: Failed to determine suitable jdbc url
```

[MarcGiffing]

I don't know how I can support you by this issue. There is not hint relating to this project. What are the changes that you make if you add this starter? Without a reproducible project I can't help here.

[nie-suva]

The reproducible ist here https://github.com/%5Bmavarazo/mcve_testcontainers%5D(https://github.com/mavarazo/mcve_testcontainers). The testcontainers starter works when I remove the bucket4j-starter, then will testcontainers work and vise versa.

[MarcGiffing]

OK, I see the problem, but I don't understand the reason.

With the Bucket4j Dependency the registration of the @Serviceconnection source is skipped, because a jdbcConnectionDetails bean is present. I don't understand why.
Skipping registration of @ServiceConnection source for Bean 'postgreSqlContainer' defined in ch.mav.mcve_testcontainers.LocalApplication$LocalPostgreSqlContainerConfig due to existing beans [jdbcConnectionDetails]

With Bucket4j Dep:

2025-06-02T20:45:39.785+02:00 DEBUG 26396 --- [           main] o.s.b.t.s.c.ConnectionDetailsRegistrar   : Registering 'liquibaseContainerConnectionDetailsForPostgreSqlContainer' for @ServiceConnection source for Bean 'postgreSqlContainer' defined in ch.mav.mcve_testcontainers.LocalApplication$LocalPostgreSqlContainerConfig
2025-06-02T20:45:39.786+02:00 DEBUG 26396 --- [           main] o.s.b.t.s.c.ConnectionDetailsRegistrar   : Skipping registration of @ServiceConnection source for Bean 'postgreSqlContainer' defined in ch.mav.mcve_testcontainers.LocalApplication$LocalPostgreSqlContainerConfig due to existing beans [jdbcConnectionDetails]
2025-06-02T20:45:39.786+02:00 DEBUG 26396 --- [           main] o.s.b.t.s.c.ConnectionDetailsRegistrar   : Registering 'flywayContainerConnectionDetailsForPostgreSqlContainer' for @ServiceConnection source for Bean 'postgreSqlContainer' defined in ch.mav.mcve_testcontainers.LocalApplication$LocalPostgreSqlContainerConfig
2

Without:

2025-06-02T20:44:47.278+02:00 DEBUG 23776 --- [           main] o.s.b.t.s.c.ConnectionDetailsRegistrar   : Registering 'flywayContainerConnectionDetailsForPostgreSqlContainer' for @ServiceConnection source for Bean 'postgreSqlContainer' defined in ch.mav.mcve_testcontainers.LocalApplication$LocalPostgreSqlContainerConfig
2025-06-02T20:44:47.279+02:00 DEBUG 23776 --- [           main] o.s.b.t.s.c.ConnectionDetailsRegistrar   : Registering 'liquibaseContainerConnectionDetailsForPostgreSqlContainer' for @ServiceConnection source for Bean 'postgreSqlContainer' defined in ch.mav.mcve_testcontainers.LocalApplication$LocalPostgreSqlContainerConfig
2025-06-02T20:44:47.280+02:00 DEBUG 23776 --- [           main] o.s.b.t.s.c.ConnectionDetailsRegistrar   : Registering 'jdbcContainerConnectionDetailsForPostgreSqlContainer' for @ServiceConnection source for Bean 'postgreSqlContainer' defined in ch.mav.mcve_testcontainers.LocalApplication$LocalPostgreSqlContainerConfig

[MarcGiffing]

Maybe this issue:
AxonFramework/AxonFramework#3022

[gysi]

@nie-suva

Its a strange problem. Somehow the AutoConfigration of Bucket4J changes the order of AutoConfigurations, so that the jdbcConnectionDetails Bean from DataSourceAutoConfiguration gets created earlier, than it would normally.

Therefore the ConnectionDetailsRegistrar doesn't create the container jdbcConnectionDetails Bean because there is already a factory registered.

A solution would be to exclude the DataSourceAutoConfiguration from LocalApplication:

@SpringBootApplication(exclude = {
        DataSourceAutoConfiguration.class,
})

And you also need a jakarta validation implementation for Bucket4J, so you need to add:

implementation ("org.springframework.boot:spring-boot-starter-validation")

@MarcGiffing

I don't really see anything you can do about it. I guess its a problem of the @ServiceConnection Annotation that needs to get fixed.