Unable to connect to Zeebe cluster

Hi,

I am using spring zeebe client and trying to connect to self managed cluser with below configurations. Can you please help to get this issue resolved.

zeebe.client.broker.gateway-address:443=dev.zeebe.xxx.com
zeebe.client.security.plaintext=true
zeebe.client.connection-mode=ADDRESS

But getting error,

2023-04-01T23:38:54.146+05:30 WARN 35912 — [nio-9080-exec-1] o.g.j.s.ServerRuntime$Responder : An exception mapping did not successfully pro
duce and processed a response. Logging the exception propagated to the default exception mapper.

io.camunda.zeebe.client.api.command.ClientStatusException: http2 exception
at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.transformExecutionException(ZeebeClientFutureImpl.java:93) ~[zeebe-client-java-8.1.9.jar:8
.1.9]
at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:50) ~[zeebe-client-java-8.1.9.jar:8.1.9]
at com.ey.tax.gtpw.camunda.services.CamundaServices.initiateProcess(CamundaServices.java:69) ~[main/:?]
at com.ey.tax.gtpw.controller.CamundaIntegrationController.startProcess(CamundaIntegrationController.java:27) ~[main/:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
at org.glassfish.jersey.server.internal.routing.SubResourceLocatorRouter.lambda$getResource$0(SubResourceLocatorRouter.java:132) ~[jersey-server
-3.1.0.jar:?]
at org.glassfish.jersey.server.internal.routing.SubResourceLocatorRouter.getResource(SubResourceLocatorRouter.java:150) ~[jersey-server-3.1.0.ja
r:?]
at org.glassfish.jersey.server.internal.routing.SubResourceLocatorRouter.apply(SubResourceLocatorRouter.java:86) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:86) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:89) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:89) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:89) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:89) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.server.internal.routing.RoutingStage.apply(RoutingStage.java:69) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.server.internal.routing.RoutingStage.apply(RoutingStage.java:38) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.process.internal.Stages.process(Stages.java:173) ~[jersey-common-3.1.0.jar:?]
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:253) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248) ~[jersey-common-3.1.0.jar:?]
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244) ~[jersey-common-3.1.0.jar:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:292) ~[jersey-common-3.1.0.jar:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:274) ~[jersey-common-3.1.0.jar:?]
at org.glassfish.jersey.internal.Errors.process(Errors.java:244) ~[jersey-common-3.1.0.jar:?]
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:265) ~[jersey-common-3.1.0.jar:?]
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:240) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:697) ~[jersey-server-3.1.0.jar:?]
at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:394) ~[jersey-container-servlet-core-3.1.0.jar:?]
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346) ~[jersey-container-servlet-core-3.1.0.jar:?]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:357) ~[jersey-container-servlet-core-3.1.0.jar:?]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:311) ~[jersey-container-servlet-core-3.1.0.jar:?]
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205) ~[jersey-container-servlet-core-3.1.0.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:223) ~[tomcat-embed-core-10.1.5.jar:10.1.5]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) ~[tomcat-embed-core-10.1.5.jar:10.1.5]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) ~[tomcat-embed-websocket-10.1.5.jar:10.1.5]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185) ~[tomcat-embed-core-10.1.5.jar:10.1.5]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158) ~[tomcat-embed-core-10.1.5.jar:10.1.5]
at org.springframework.boot.actuate.web.exchanges.servlet.HttpExchangesFilter.doFilterInternal(HttpExchangesFilter.java:89) ~[spring-boot-actuat
or-3.0.2.jar:3.0.2]

Hello @syedkp - can you confirm what you have set for the zeebe.client.broker.gateway-address value in your configuration? Your post has zeebe.client.broker.gateway-address:443=dev.zeebe.xxx.com but the :443 should be part of the value not the key (zeebe.client.broker.gateway-address=dev.zeebe.xxx.com:443). I am not sure if that’s a typo or possibly an issue with your client configuration.

Hi @nathan.loding - yeah its typo. I have 443 in the value and not in the key.

@syedkp - that’s what I thought but I had to make sure! Have you ever been able to connect to the self-managed instance before, or is the first time attempting? This error isn’t very explicit (we have an issue open to make it friendlier), but it typically means that there was a networking error (e.g., firewall, proxy, bad address, missing route), the broker isn’t running, or, in some cases, there are missing credentials (see the referenced Github issue).

Thanks @nathan.loding . Let me check and see if this solves my problem.

@nathan.loding - I am getting the above error only if I use the @JobWorker annotation. I am able to create instance and deploy the bpmn file but If I have the job worker enabled I get the error.

@syedkp - it’s really hard to say without more information. Could you share the full startup log? The spring-zeebe client should output a log by default.

Hi @nathan.loding . please check below logs. let me know if you are able to find anything that could help.

2023-04-11T00:30:18.242+05:30  INFO 8512 --- [           main] c.e.t.g.CamundaIntegrationApplication    : Starting CamundaIntegrationApplication using Java 17.0.6 with PID 8512 (C:\OGM-Next\OGM_Next_Camunda8\tax-ogmwf-next-camunda\build\classes\java\main started by BW311MJ in C:\OGM-Next\OGM_Next_Camunda8\tax-ogmwf-next-camunda)
2023-04-11T00:30:18.314+05:30  INFO 8512 --- [           main] c.e.t.g.CamundaIntegrationApplication    : No active profile set, falling back to 1 default profile: "default"
2023-04-11T00:30:21.217+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'io.camunda.zeebe.spring.client.annotation.processor.AnnotationProcessorConfiguration' of type [io.camunda.zeebe.spring.client.annotation.processor.AnnotationProcessorConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.300+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'deploymentPostProcessor' of type [io.camunda.zeebe.spring.client.annotation.processor.ZeebeDeploymentAnnotationProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.304+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'io.camunda.zeebe.spring.client.connector.ConnectorConfiguration' of type [io.camunda.zeebe.spring.client.connector.ConnectorConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.310+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'io.camunda.zeebe.spring.client.ZeebeClientSpringConfiguration' of type [io.camunda.zeebe.spring.client.ZeebeClientSpringConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.345+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'commandExceptionHandlingStrategy' of type [io.camunda.zeebe.spring.client.jobhandling.DefaultCommandExceptionHandlingStrategy] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.376+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'secretProvider' of type [io.camunda.zeebe.spring.client.connector.SpringSecretProvider] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.677+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'zeebe.client-io.camunda.zeebe.spring.client.properties.ZeebeClientConfigurationProperties' of type [io.camunda.zeebe.spring.client.properties.ZeebeClientConfigurationProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.685+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'io.camunda.zeebe.spring.client.config.ZeebeClientStarterAutoConfiguration' of type [io.camunda.zeebe.spring.client.config.ZeebeClientStarterAutoConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.698+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonObjectMapperConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonObjectMapperConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.702+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonObjectMapperBuilderConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonObjectMapperBuilderConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.705+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$Jackson2ObjectMapperBuilderCustomizerConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$Jackson2ObjectMapperBuilderCustomizerConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.727+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.jackson-org.springframework.boot.autoconfigure.jackson.JacksonProperties' of type [org.springframework.boot.autoconfigure.jackson.JacksonProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.741+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'jacksonModuleConfiguration' of type [com.ey.tax.gtpw.config.JacksonModuleConfiguration$$SpringCGLIB$$0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.818+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'javaTimeModule' of type [com.fasterxml.jackson.datatype.jsr310.JavaTimeModule] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.820+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$ParameterNamesModuleConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$ParameterNamesModuleConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.824+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'parameterNamesModule' of type [com.fasterxml.jackson.module.paramnames.ParameterNamesModule] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.826+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonMixinConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$JacksonMixinConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.918+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'jsonMixinModuleEntries' of type [org.springframework.boot.jackson.JsonMixinModuleEntries] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.923+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'jsonMixinModule' of type [org.springframework.boot.jackson.JsonMixinModule] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:21.927+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.006+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'jsonComponentModule' of type [org.springframework.boot.jackson.JsonComponentModule] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.026+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'standardJacksonObjectMapperBuilderCustomizer' of type [org.springframework.boot.autoconfigure.jackson.JacksonAutoConfiguration$Jackson2ObjectMapperBuilderCustomizerConfiguration$StandardJackson2ObjectMapperBuilderCustomizer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.037+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'jacksonObjectMapperBuilder' of type [org.springframework.http.converter.json.Jackson2ObjectMapperBuilder] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.366+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'jacksonObjectMapper' of type [com.fasterxml.jackson.databind.ObjectMapper] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.368+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'zeebeJsonMapper' of type [io.camunda.zeebe.client.impl.ZeebeObjectMapper] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.375+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'jobWorkerManager' of type [io.camunda.zeebe.spring.client.jobhandling.JobWorkerManager] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.462+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'outboundConnectorManager' of type [io.camunda.zeebe.spring.client.connector.OutboundConnectorManager] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.475+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'outboundConnectorAnnotationProcessor' of type [io.camunda.zeebe.spring.client.annotation.processor.OutboundConnectorAnnotationProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.482+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'propertyBasedZeebeWorkerValueCustomizer' of type [io.camunda.zeebe.spring.client.properties.PropertyBasedZeebeWorkerValueCustomizer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:22.488+05:30  INFO 8512 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'zeebeWorkerPostProcessor' of type [io.camunda.zeebe.spring.client.annotation.processor.ZeebeWorkerAnnotationProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-04-11T00:30:24.711+05:30  INFO 8512 --- [           main] o.s.b.w.e.t.TomcatWebServer              : Tomcat initialized with port(s): 9082 (http)
2023-04-11T00:30:24.732+05:30  INFO 8512 --- [           main] o.a.c.c.StandardService                  : Starting service [Tomcat]
2023-04-11T00:30:24.732+05:30  INFO 8512 --- [           main] o.a.c.c.StandardEngine                   : Starting Servlet engine: [Apache Tomcat/10.1.7]
2023-04-11T00:30:25.148+05:30  INFO 8512 --- [           main] o.a.c.c.C.[.[.[/c8i]                     : Initializing Spring embedded WebApplicationContext
2023-04-11T00:30:25.160+05:30  INFO 8512 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 6652 ms
2023-04-11T00:30:25.696+05:30  WARN 8512 --- [           main] ocalVariableTableParameterNameDiscoverer : Using deprecated '-debug' fallback for parameter name resolution. Compile the affected code with '-parameters' instead or avoid its introspection: com.ey.tax.gtpw.Handler.JobWorkerHandler
2023-04-11T00:30:25.708+05:30  INFO 8512 --- [           main] z.s.c.a.p.ZeebeWorkerAnnotationProcessor : Configuring 2 Zeebe worker(s) of bean 'jobWorkerHandler': [ZeebeWorkerValue{type='initialise-variables', name='jobWorkerHandler#initialise', timeout=-1, maxJobsActive=-1, requestTimeout=-1, pollInterval=-1, autoComplete=true, fetchVariables=[], enabled=true, methodInfo=io.camunda.zeebe.spring.client.bean.MethodInfo@2fd72332}, ZeebeWorkerValue{type='io.camunda.zeebe:userTask', name='jobWorkerHandler#handle', timeout=-1, maxJobsActive=-1, requestTimeout=-1, pollInterval=-1, autoComplete=false, fetchVariables=[], enabled=true, methodInfo=io.camunda.zeebe.spring.client.bean.MethodInfo@51f18e31}]
2023-04-11T00:30:25.908+05:30  WARN 8512 --- [           main] c.a.m.s.ServiceBusClientBuilder          : 'enableAutoComplete' is not supported in synchronous client except through callback receive.
2023-04-11T00:30:26.531+05:30  INFO 8512 --- [           main] c.a.m.s.i.ServiceBusConnectionProcessor  : {"az.sdk.message":"Setting next AMQP channel.","entityPath":"N/A"}
2023-04-11T00:30:26.535+05:30  INFO 8512 --- [           main] c.a.m.s.ServiceBusClientBuilder          : # of open clients with shared connection: 1
2023-04-11T00:30:26.595+05:30  INFO 8512 --- [           main] c.a.m.s.i.ServiceBusConnectionProcessor  : {"az.sdk.message":"Setting next AMQP channel.","entityPath":"N/A"}
2023-04-11T00:30:26.595+05:30  INFO 8512 --- [           main] c.a.m.s.ServiceBusClientBuilder          : # of open clients with shared connection: 1
2023-04-11T00:30:26.616+05:30  INFO 8512 --- [           main] s.c.p.ZeebeClientConfigurationProperties : Using connection mode 'ADDRESS' to connect to Zeebe
2023-04-11T00:30:27.494+05:30  INFO 8512 --- [           main] i.c.z.s.c.ZeebeClientSpringConfiguration : Creating ZeebeClient using ZeebeClientBuilder [gatewayAddress: dev.zeebe.gtpw-rules.ey.com:443
jobWorkerMaxJobsActive: 32
numJobWorkerExecutionThreads: 1
defaultJobWorkerName: null
defaultJobTimeout: PT5M
defaultJobPollInterval: PT0.1S
defaultMessageTimeToLive: PT1H
defaultRequestTimeout: PT10S
overrideAuthority: null
]
2023-04-11T00:30:28.411+05:30  INFO 8512 --- [           main] i.c.z.s.c.c.OutboundConnectorManager     : Reading environment variables or parsing SPI to find connectors that are not Spring beans
2023-04-11T00:30:28.415+05:30  INFO 8512 --- [           main] .u.o.OutboundConnectorRegistrationHelper : Parsing SPI to find connectors that are not Spring beans
2023-04-11T00:30:28.417+05:30  WARN 8512 --- [           main] i.c.z.s.c.c.OutboundConnectorManager     : No outbound connectors configured or found in classpath
2023-04-11T00:30:28.464+05:30  INFO 8512 --- [           main] i.c.z.s.c.j.JobWorkerManager             : . Starting Zeebe worker: ZeebeWorkerValue{type='initialise-variables', name='jobWorkerHandler#initialise', timeout=-1, maxJobsActive=-1, requestTimeout=-1, pollInterval=-1, autoComplete=true, fetchVariables=[], enabled=true, methodInfo=io.camunda.zeebe.spring.client.bean.MethodInfo@2fd72332}
2023-04-11T00:30:28.464+05:30  INFO 8512 --- [           main] i.c.z.s.c.j.JobWorkerManager             : . Starting Zeebe worker: ZeebeWorkerValue{type='io.camunda.zeebe:userTask', name='jobWorkerHandler#handle', timeout=-1, maxJobsActive=-1, requestTimeout=-1, pollInterval=-1, autoComplete=false, fetchVariables=[], enabled=true, methodInfo=io.camunda.zeebe.spring.client.bean.MethodInfo@51f18e31}
2023-04-11T00:30:28.531+05:30  INFO 8512 --- [           main] o.s.b.w.e.t.TomcatWebServer              : Tomcat started on port(s): 9082 (http) with context path '/c8i'
2023-04-11T00:30:28.564+05:30  INFO 8512 --- [           main] c.e.t.g.CamundaIntegrationApplication    : Started CamundaIntegrationApplication in 11.683 seconds (process running for 13.919)

Inside createProcessInstance() for bpmnProcessId : TwitterDemoProcess
BPMN Process instance Key - 2251799813687781
BPM Id : TwitterDemoProcess
Completed job: 2251799813687786
Inside JobWorkerHandler
Inside JobWorkerService:startProcessing()
AUTOMATIC PROCESSING HAPPENING
Completed job: 2251799813687793
2023-04-11T00:31:46.942+05:30  WARN 8512 --- [ault-executor-0] .DefaultCommandExceptionHandlingStrategy : Ignoring the error of type 'NOT_FOUND' during {command=class io.camunda.zeebe.client.impl.command.CompleteJobCommandImpl, job={"key":2251799813687786,"type":"initialise-variables","customHeaders":{},"processInstanceKey":2251799813687781,"bpmnProcessId":"TwitterDemoProcess","processDefinitionVersion":1,"processDefinitionKey":2251799813686542,"elementId":"Initialise_Variables","elementInstanceKey":2251799813687785,"worker":"jobWorkerHandler#initialise","retries":3,"deadline":1681153606405,"variables":"{}","variablesAsMap":{}}, currentRetryDelay=50}. Job might have been canceled or already completed.
2023-04-11T00:35:34.260+05:30  WARN 8512 --- [ault-executor-0] i.c.z.c.j.poller                         : Failed to activate jobs for worker jobWorkerHandler#handle and job type io.camunda.zeebe:userTask

io.grpc.StatusRuntimeException: UNKNOWN: HTTP status code 302
invalid content-type: text/html
headers: Metadata(:status=302,date=Mon, 10 Apr 2023 19:05:34 GMT,content-type=text/html,location=https://dev.gtpw-rules.ey.com/oauth2/start?rd=%2Fgateway_protocol.Gateway%2FActivateJobs,content-length=138)
DATA-----------------------------
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>

	at io.grpc.Status.asRuntimeException(Status.java:535) ~[grpc-api-1.49.2.jar:1.49.2]
	at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:487) ~[grpc-stub-1.49.2.jar:1.49.2]
	at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:563) ~[grpc-core-1.49.2.jar:1.49.2]
	at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70) ~[grpc-core-1.49.2.jar:1.49.2]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:744) ~[grpc-core-1.49.2.jar:1.49.2]
	at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:723) ~[grpc-core-1.49.2.jar:1.49.2]
	at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) ~[grpc-core-1.49.2.jar:1.49.2]
	at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133) ~[grpc-core-1.49.2.jar:1.49.2]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
	at java.lang.Thread.run(Thread.java:833) ~[?:?]

2023-04-11T00:35:34.273+05:30  WARN 8512 --- [ault-executor-7] i.c.z.c.j.poller                         : Failed to activate jobs for worker jobWorkerHandler#initialise and job type initialise-variables

@syedkp - I took a look through the logs, and it appears to me that Nginx is returning a 302 response instead of starting the job worker.

2023-04-11T00:35:34.260+05:30  WARN 8512 --- [ault-executor-0] i.c.z.c.j.poller                         : Failed to activate jobs for worker jobWorkerHandler#handle and job type io.camunda.zeebe:userTask

io.grpc.StatusRuntimeException: UNKNOWN: HTTP status code 302
invalid content-type: text/html
headers: Metadata(:status=302,date=Mon, 10 Apr 2023 19:05:34 GMT,content-type=text/html,location=https://dev.gtpw-rules.ey.com/oauth2/start?rd=%2Fgateway_protocol.Gateway%2FActivateJobs,content-length=138)
DATA-----------------------------
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>nginx</center>
</body>
</html>

I cannot say exactly what is wrong with the job worker configuration, but that appears to be what is happening. Zeebe is getting to your task and the response it is getting is HTTP 302 Found. To be more specific, I think I would need to see the code for the job worker, including variable values (leave out the keys and sensitive data of course!), and perhaps see how you have that task configured in your process model.