Camunda external task client gets stuck on a request when there's any interruption/error happens over the connection

Hello,

Currently we have camunda server and a client (external task client) deployed on a domain. Initially the client and server connection works fine, but because of some maintenance or network disconnection happening on the domain side, the client gets stuck on a particular request and will not handle the issue. Is there any handler/configuration that we can set to handle such http timeout errors ?

What i’m thinking is to handle such http session issue with some defined time, for example 5 minutes, and kill the session, so that client keep calling the server as usual. Below is how we’re setting up the client connection bean using ClientProperties.

    @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.setAsyncResponseTimeout(120000L);
		clientProperties.setWorkerId("dummyWorker");
		clientProperties.setSubscriptions(getSubscriptionConfiguration());
		return clientProperties;
	}

I know we can use ClientRequestInterceptor to intercept any request and add any oauth setting there but is there any intercepter/receiver that should handle the http session timeout and thereby killing the current active session and proceed with the next request is what i’m looking for.

Hi,

Any solution to this issue. I am stuck with similar behaviour. Looking for a handler to proceed on such situations.

Regards,
Anshul Asthana