Updating to org.testcontainers:db2:1.20.4 makes our builds fail

[auloin]

Hi! Thanks for making testing easier than ever!

We are in the process of upgrading all the dependencies of our own open source software github.com/jobrunr/jobrunr. Unfortunately, updating to org.testcontainers:db2:1.20.4 (from org.testcontainers:db2:1.20.1) makes our build fail with the below exception. This may be related to a recent change to the Db2Container which removes privileged mode: #9460.

Are we missing extra configuration steps that comes with org.testcontainers:db2:1.20.4?

@rdehuyss can give extra details on the CI environment if needed.

Container setup

new Db2Container("ibmcom/db2:11.5.5.0").acceptLicense()

Relevant logs

com.zaxxer.hikari.pool.HikariPool$PoolInitializationException: Failed to initialize pool: [jcc][t4][2030][11211][4.33.31] A communication error occurred during operations on the connection's underlying socket, socket input stream, 
    or socket output stream.  Error location: Reply.fill() - insufficient data (-1).  Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001
        at com.zaxxer.hikari.pool.HikariPool.throwPoolInitializationException(HikariPool.java:606)
        at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:593)
        at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:101)
        at com.zaxxer.hikari.HikariDataSource.<init>(HikariDataSource.java:80)
        at org.jobrunr.storage.sql.SqlTestUtils.toHikariDataSource(SqlTestUtils.java:40)
        at org.jobrunr.storage.sql.SqlTestUtils.toHikariDataSource(SqlTestUtils.java:31)
        at org.jobrunr.storage.sql.SqlTestUtils.toHikariDataSource(SqlTestUtils.java:23)
        at org.jobrunr.storage.sql.db2.DB2StorageProviderTest.getDataSource(DB2StorageProviderTest.java:17)

        Caused by:
        com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException: [jcc][t4][2030][11211][4.33.31] A communication error occurred during operations on the connection's underlying socket, socket input stream, 
        or socket output stream.  Error location: Reply.fill() - insufficient data (-1).  Message: Insufficient data. ERRORCODE=-4499, SQLSTATE=08001
            at app//com.ibm.db2.jcc.am.b4.a(b4.java:338)
            at app//com.ibm.db2.jcc.t4.a.a(a.java:580)
            at app//com.ibm.db2.jcc.t4.a.a(a.java:564)
            at app//com.ibm.db2.jcc.t4.a.a(a.java:559)
            at app//com.ibm.db2.jcc.t4.x.b(x.java:315)
            at app//com.ibm.db2.jcc.t4.x.c(x.java:342)
            at app//com.ibm.db2.jcc.t4.x.c(x.java:455)
            at app//com.ibm.db2.jcc.t4.x.v(x.java:1230)
            at app//com.ibm.db2.jcc.t4.y.a(y.java:53)
            at app//com.ibm.db2.jcc.t4.b.c(b.java:1523)
            at app//com.ibm.db2.jcc.t4.b.b(b.java:1391)
            at app//com.ibm.db2.jcc.t4.b.b(b.java:938)
            at app//com.ibm.db2.jcc.t4.b.a(b.java:890)
            at app//com.ibm.db2.jcc.t4.b.a(b.java:458)
            at app//com.ibm.db2.jcc.t4.b.a(b.java:431)
            at app//com.ibm.db2.jcc.t4.b.<init>(b.java:369)
            at app//com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:259)
            at app//com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:215)
            at app//com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:491)
            at app//com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:117)
            at app//com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:139)
            at app//com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:367)
            at app//com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:205)
            at app//com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:484)
            at app//com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:572)
            ... 6 more

[eddumelendez]

Hi, are you running on GHA? We ran tests on GHA and all was green. Can you declare withPrivilegedMode(true)? I think the change only affects specific DB2 versions

[rdehuyss]

Hi @eddumelendez! Long time no see! Thanks for your swift feedback. We added the withPrivilegedMode(true) and that worked.

Thanks again for your help!