/cc @gsmet (hibernate-orm)

Partial resolution of #44124.

This is failing at the moment, because of the following error:

2025-11-18T16:04:55.6629145Z     "details": "Error id 4a3b7664-f6d2-41d2-bbe0-c11f33a36e3c-2, org.jboss.resteasy.spi.UnhandledException: io.vertx.db2client.DB2Exception: The database 'ADDITIONAL' provided was not found, SQLCODE=-1001  SQLSTATE=2E000",
2025-11-18T16:04:55.6645349Z     "stack": "org.jboss.resteasy.spi.UnhandledException: io.vertx.db2client.DB2Exception: The database 'ADDITIONAL' provided was not found, SQLCODE=-1001  SQLSTATE=2E000\n\tat org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:357)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:205)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:452)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.lambda$invokePropagateNotFound$6(SynchronousDispatcher.java:275)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:154)\n\tat org.jboss.resteasy.core.interception.jaxrs.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:321)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:157)\n\tat org.jboss.resteasy.core.SynchronousDispatcher.invokePropagateNotFound(SynchronousDispatcher.java:260)\n\tat io.quarkus.resteasy.runtime.standalone.RequestDispatcher.service(RequestDispatcher.java:86)\n\tat io.quarkus.resteasy.runtime.standalone.VertxRequestHandler.dispatch(VertxRequestHandler.java:151)\n\tat io.quarkus.resteasy.runtime.standalone.VertxRequestHandler$1.run(VertxRequestHandler.java:97)\n\tat io.quarkus.vertx.core.runtime.VertxCoreRecorder$15.runWith(VertxCoreRecorder.java:645)\n\tat org.jboss.threads.EnhancedQueueExecutor$Task.doRunWith(EnhancedQueueExecutor.java:2651)\n\tat org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2630)\n\tat org.jboss.threads.EnhancedQueueExecutor.runThreadBody(EnhancedQueueExecutor.java:1622)\n\tat org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1589)\n\tat org.jboss.threads.DelegatingRunnable.run(DelegatingRunnable.java:11)\n\tat org.jboss.threads.ThreadLocalResettingRunnable.run(ThreadLocalResettingRunnable.java:11)\n\tat io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat java.base/java.lang.Thread.run(Thread.java:840)\nCaused by: io.vertx.db2client.DB2Exception: The database 'ADDITIONAL' provided was not found, SQLCODE=-1001  SQLSTATE=2E000"
2025-11-18T16:04:55.6660958Z }

Looking at the difference between the passing code and the failing code, it seems like the named reactive datasources don't work with DB2? I can't debug locally because DB2 also doesn't start on my mac (#51084). I have no idea if this is a test problem or an application problem. I assume a test problem, but the modified test looks pretty innocuous. Any ideas, @lucamolteni or @yrodiere?

Named reactive datasources are not DB dependant, so they should work regardless, I wonder what path is triggering

@holly-cummins I learned the hard way that something in DB2 (the "instance name"? not sure if it's the same thing as the DB name) is... wait for it... limited to 8 characters.

Was that perhaps your problem? :)

@holly-cummins I learned the hard way that something in DB2 (the "instance name"? not sure if it's the same thing as the DB name) is... wait for it... limited to 8 characters.

Was that perhaps your problem? :)

Gosh. In principle it shouldn't affect this, because these are existing tests that are just running on a dev service instead of an independent container. But along with all the optimisations I've been throwing out, there could have been some flag in the container configuration or container image that eased that restriction. I'll try a shorter name and report back!

@holly-cummins I learned the hard way that something in DB2 (the "instance name"? not sure if it's the same thing as the DB name) is... wait for it... limited to 8 characters.

Was that perhaps your problem? :)

Shortening the datasource name doesn't make CI pass, but it does improve it. Five test failures without (https://github.com/holly-cummins/quarkus/actions/runs/19517834498), two failures with (https://github.com/holly-cummins/quarkus/actions/runs/19577145253). The health check test reckons the database is up now, which is encouraging. The error now is

025-11-21T17:04:40.9972583Z 2025-11-21 17:04:40,962 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (vert.x-eventloop-thread-0) RESTEASY002020: Unhandled asynchronous exception, sending back 500: io.vertx.db2client.DB2Exception: The object 'QUARKUS.LEGUMES' provided is not defined, SQLCODE=-204  SQLSTATE=42704

So the error is still on the named datasource, but it's got further. What's also interesting is that the external DB2 doesn't seem to suffer from the name-length restriction, so there may be something we can do to make the dev service work, but I'll raise a separate issue for that once we get to the bottom of it.