I received an error in airbyte-workload-launcher about Failed to obtain JDBC Connection

[skas-zilo]

I received the following error in the airbyte-workload-launcher. I deployed it in Kubernetes using Helm. I'm using Airbyte 1.5.1. I'm using an external database, RDS Postgres. Temporal can connect to the database without any issues, but the airbyte-workload-launcher keeps restarting with the error below. Please advise. Thank you.

2025-03-20 04:07:24,387 [Thread-2] ERROR i.a.w.l.StartupApplicationEventListener(onApplicationEvent$lambda$1):40 - Failed to retrieve and resume claimed workloads, exiting.io.airbyte.workload.api.client.generated.infrastructure.ClientException: Client error : 400 Bad Request {"message":"Bad Request","logref":null,"path":null,"_links":{"self":{"href":"/api/v1/workload/list","templated":false,"profile":null,"deprecation":null,"title":null,"hreflang":null,"type":null,"name":null}},"_embedded":{"errors":[{"message":"Failed to obtain JDBC Connection","logref":null,"path":null,"_links":{},"_embedded":{}}]}} at io.airbyte.workload.api.client.generated.WorkloadApi.workloadList(WorkloadApi.kt:578) at io.airbyte.workload.launcher.ClaimedProcessor.getWorkloadList$lambda$8(ClaimedProcessor.kt:123) at dev.failsafe.Functions.lambda$toCtxSupplier$11(Functions.java:243) at dev.failsafe.Functions.lambda$get$0(Functions.java:46) at dev.failsafe.internal.RetryPolicyExecutor.lambda$apply$0(RetryPolicyExecutor.java:74) at dev.failsafe.SyncExecutionImpl.executeSync(SyncExecutionImpl.java:187) at dev.failsafe.FailsafeExecutor.call(FailsafeExecutor.java:376) at dev.failsafe.FailsafeExecutor.get(FailsafeExecutor.java:112) at io.airbyte.workload.launcher.ClaimedProcessor.getWorkloadList(ClaimedProcessor.kt:122) at io.airbyte.workload.launcher.ClaimedProcessor.retrieveAndProcess(ClaimedProcessor.kt:64) at io.airbyte.workload.launcher.StartupApplicationEventListener.onApplicationEvent$lambda$1(StartupApplicationEventListener.kt:36) at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30)

[vr]

Hey @skas-zilo , i encounter the same issue, how did you solve this ?