Hello,
We’re currently facing an issue where camunda client stops listening to any new tasks/instances after a while. Following the document here - Spring Boot Starter for the External Task Client | Camunda, we’ve setup our spring boot app, with ClientProperties bean where we setup the basic auth, lockDuration and etc., as shown in below Bean code.
@Primary
@Bean
public ClientProperties clientProperties() throws IOException {
BasicAuthProperties basicAuthProperties = new BasicAuthProperties();
basicAuthProperties.setUsername(secretsProperties.fetchCamundaUserName());
basicAuthProperties.setPassword(secretsProperties.fetchCamundaUserPassword());
clientProperties.setBasicAuth(basicAuthProperties);
clientProperties.setBaseUrl(databaseProperties.getCamundaDevUrl());
clientProperties.setLockDuration(10000L);
clientProperties.setDisableBackoffStrategy(true);
clientProperties.setWorkerId("dummyWorker");
clientProperties.setSubscriptions(getSubscriptionConfiguration());
return clientProperties;
}
pom dependency
<dependency>
<groupId>org.camunda.bpm.springboot</groupId>
<artifactId>camunda-bpm-spring-boot-starter-external-task-client</artifactId>
<version>7.15.0</version>
</dependency>
log info from pod as below
[org.springframework.boot.actuate.health.SystemHealth@155ccb40]
2021-12-09 19:22:24 Camunda-Demo [http-nio-8080-exec-1] DEBUG o.s.web.servlet.DispatcherServlet - Completed 200 OK
2021-12-09 19:22:25 Camunda-Demo [http-nio-8080-exec-2] DEBUG o.s.web.servlet.DispatcherServlet - GET "/actuator/health", parameters={}
2021-12-09 19:22:25 Camunda-Demo [http-nio-8080-exec-2] DEBUG o.s.b.a.e.w.s.WebMvcEndpointHandlerMapping - Mapped to Actuator web endpoint 'health'
2021-12-09 19:22:25 Camunda-Demo [http-nio-8080-exec-2] DEBUG o.s.jdbc.datasource.DataSourceUtils - Fetching JDBC Connection from DataSource
2021-12-09 19:22:25 Camunda-Demo [http-nio-8080-exec-2] DEBUG o.s.jdbc.datasource.DataSourceUtils - Fetching JDBC Connection from DataSource
2021-12-09 19:22:25 Camunda-Demo [http-nio-8080-exec-2] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Using 'application/vnd.spring-boot.actuator.v3+json', given [*/*] and supported [application/vnd.spring-boot.actuator.v3+json, application/vnd.spring-boot.actuator.v2+json, application/json]
2021-12-09 19:22:25 Camunda-Demo [http-nio-8080-exec-2] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Writing [org.springframework.boot.actuate.health.SystemHealth@64b8228f]
2021-12-09 19:22:25 Camunda-Demo [http-nio-8080-exec-2] DEBUG o.s.web.servlet.DispatcherServlet - Completed 200 OK
2021-12-09 19:22:30 Camunda-Demo [http-nio-8080-exec-10] DEBUG o.s.web.servlet.DispatcherServlet - GET "/actuator/health", parameters={}
2021-12-09 19:22:30 Camunda-Demo [http-nio-8080-exec-10] DEBUG o.s.b.a.e.w.s.WebMvcEndpointHandlerMapping - Mapped to Actuator web endpoint 'health'
2021-12-09 19:22:30 Camunda-Demo [http-nio-8080-exec-10] DEBUG o.s.jdbc.datasource.DataSourceUtils - Fetching JDBC Connection from DataSource
2021-12-09 19:22:30 Camunda-Demo [http-nio-8080-exec-10] DEBUG o.s.jdbc.datasource.DataSourceUtils - Fetching JDBC Connection from DataSource
2021-12-09 19:22:30 Camunda-Demo [http-nio-8080-exec-10] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Using 'application/vnd.spring-boot.actuator.v3+json', given [*/*] and supported [application/vnd.spring-boot.actuator.v3+json, application/vnd.spring-boot.actuator.v2+json, application/json]
2021-12-09 19:22:30 Camunda-Demo [http-nio-8080-exec-10] DEBUG o.s.w.s.m.m.a.HttpEntityMethodProcessor - Writing
The app works fine initially, the problem starts after a while and i can that in my camunda instance the tasks do not have any workers assigned to them, meaning the client is not listening to or fetching any tasks from the above connection. Is this something related to the lockDuration ? I know i can extend the lock during a task’s execution if it is required but how to keep the connection alive and listen to any new tasks ?