fix: rename async executor bean to avoid clash with DeploymentExecutor
All checks were successful
CI / build (push) Successful in 49s
CI / docker (push) Successful in 36s

The @Bean named 'deploymentExecutor' (ThreadPoolTaskExecutor) collided
with the @Service class DeploymentExecutor. Rename the bean to
'deploymentTaskExecutor'.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
hsiegeln
2026-04-07 18:06:10 +02:00
parent dade9cefe2
commit d6f488199c
2 changed files with 3 additions and 3 deletions

View File

@@ -18,8 +18,8 @@ public class AsyncConfig {
this.runtimeConfig = runtimeConfig;
}
@Bean(name = "deploymentExecutor")
public Executor deploymentExecutor() {
@Bean(name = "deploymentTaskExecutor")
public Executor deploymentTaskExecutor() {
var executor = new ThreadPoolTaskExecutor();
// Core == max: no burst threads. Deployments beyond pool size queue (up to 25).
executor.setCorePoolSize(runtimeConfig.getDeploymentThreadPoolSize());

View File

@@ -47,7 +47,7 @@ public class DeploymentExecutor {
this.runtimeConfig = runtimeConfig;
}
@Async("deploymentExecutor")
@Async("deploymentTaskExecutor")
public void executeAsync(DeploymentEntity deployment, AppEntity app, EnvironmentEntity env) {
try {
var jarPath = appService.resolveJarPath(app.getJarStoragePath());