Constant messages in connector logs and response error when using connector webhook

Camunda 8 Topics Discussion & Questions
1

Greetings everyone,
Can anyone help me with this, I’m having an authorization error when using the webhook connector.

Log:
2024-05-14 12:07:54 2024-05-14T11:07:54.569Z WARN 1 — [nio-8080-exec-6] ocalVariableTableParameterNameDiscoverer : Using deprecated ‘-debug’ fallback for parameter name resolution. Compile the affected code with ‘-parameters’ instead or avoid its introspection: io.camunda.connector.runtime.inbound.webhook.InboundWebhookRestController
2024-05-14 12:07:55 2024-05-14T11:07:55.154Z INFO 1 — [nio-8080-exec-6] i.c.c.r.c.i.c.InboundCorrelationHandler : Created a process instance with key2251799813711316
2024-05-14 12:07:55 2024-05-14T11:07:55.191Z INFO 1 — [pool-2-thread-2] i.c.c.r.c.outbound.ConnectorJobHandler : Received job: 2251799813711337 for tenant:
2024-05-14 12:11:14 2024-05-14T11:11:14.440Z ERROR 1 — [ scheduling-1] i.camunda.common.http.DefaultHttpClient : Failed POST with responseType class io.camunda.operate.model.SearchResult, parameterType class io.camunda.operate.model.ProcessDefinition, selector io.camunda.operate.model.SearchResult<io.camunda.operate.model.ProcessDefinition>, body io.camunda.operate.search.SearchQuery@71fc1fa2 due to Response not successful: 401
2024-05-14 12:11:14 2024-05-14T11:11:14.442Z ERROR 1 — [ scheduling-1] o.s.s.s.TaskUtils$LoggingErrorHandler : Unexpected error occurred in scheduled task
2024-05-14 12:11:14
2024-05-14 12:11:14 io.camunda.common.exception.SdkException: io.camunda.common.exception.SdkException: Response not successful: 401
2024-05-14 12:11:14 at io.camunda.common.http.DefaultHttpClient.post(DefaultHttpClient.java:146)
2024-05-14 12:11:14 at io.camunda.operate.CamundaOperateClient.searchProcessDefinitionResults(CamundaOperateClient.java:46)
2024-05-14 12:11:14 at io.camunda.connector.runtime.inbound.importer.ProcessDefinitionSearch.query(ProcessDefinitionSearch.java:64)
2024-05-14 12:11:14 at io.camunda.connector.runtime.inbound.importer.ProcessDefinitionImporter.scheduleImport(ProcessDefinitionImporter.java:52)
2024-05-14 12:11:14 at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
2024-05-14 12:11:14 at java.base/java.lang.reflect.Method.invoke(Unknown Source)
2024-05-14 12:11:14 at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84)
2024-05-14 12:11:14 at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
2024-05-14 12:11:14 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
2024-05-14 12:11:14 at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown Source)
2024-05-14 12:11:14 at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
2024-05-14 12:11:14 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
2024-05-14 12:11:14 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
2024-05-14 12:11:14 at java.base/java.lang.Thread.run(Unknown Source)
2024-05-14 12:11:14 Caused by: io.camunda.common.exception.SdkException: Response not successful: 401
2024-05-14 12:11:14 at io.camunda.common.http.DefaultHttpClient.parseAndRetry(DefaultHttpClient.java:257)
2024-05-14 12:11:14 at io.camunda.common.http.DefaultHttpClient.post(DefaultHttpClient.java:143)
2024-05-14 12:11:14 … 13 common frames omitted
2024-05-14 12:11:14

2

@Domingos_Dias Do you see this error right after starting the Connector runtime? It seems like there is an authentication issue when trying to connect to Operate.

3

Not necessarily, the error in the image appears periodically at intervals of constant minutes/seconds, the only error I receive only when I activate the connector is: 2024-05-14 12:07:55 2024-05-14T11:07:55.154Z INFO 1 — [nio-8080-exec-6] i.c.c.r.c.i.c.InboundCorrelationHandler : Created a process instance with key2251799813711316
2024-05-14 12:07:55 2024-05-14T11:07:55.191Z INFO 1 — [pool-2-thread-2] i.c.c.r.c.outbound.ConnectorJobHandler : Received job: 2251799813711337 for tenant:
2024-05-14 12:11:14 2024-05-14T11:11:14.440Z ERROR 1 — [ scheduling-1] i.camunda.common.http.DefaultHttpClient : Failed POST with responseType class io.camunda.operate .model.SearchResult, parameterType class io.camunda.operate.model.ProcessDefinition, selector io.camunda.operate.model.SearchResult<io.camunda.operate.model.ProcessDefinition>, body io.camunda.operate.search.SearchQuery@ 71fc1fa2 due to Response not successful: 401
2024-05-14 12:11:14 2024-05-14T11:11:14.442Z ERROR 1 — [ scheduling-1] o.s.s.s.TaskUtils$LoggingErrorHandler : Unexpected error occurred in scheduled task

image
image1496×425 19.8 KB

4

@Domingos_Dias When did you start the application and when did the error starting to appear? And which version are you one?

5

As soon as I updated camunda to version 8.5.0.

6

Thanks for the answer. There was a bug in one of the components used by the Connectors Runtime [8.5.1] Token not refreshed · Issue #755 · camunda-community-hub/spring-zeebe · GitHub which lead to this issue. Please upgrade to our latest release 8.5.2 and the error should be gone.

7

Good, thanks for your help, at least the problem has been resolved, although I really want to understand why this is happening.

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.