Using Camuda SAAS (30 days Evaluation) , Failed to start bean ‘zeebeClientLifecycle’; nested exception is io.camunda.zeebe.client.api.command.ClientStatusException

I tried using spring-zeebe-starter (8.1.13) Java 11 with Camunda SAAS cloud (30 days evaluation) But I still get exception when I execute my springboot application from InteliijIDE -

My cluster details - [ptcommprocessor-dev1-cluster] US Central Zeebe 8.1.8 Trial Cluster Healthy

2023-02-23 18:49:06.255 INFO 18008 — [ 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-02-23 18:49:06.257 INFO 18008 — [ 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-02-23 18:49:06.261 INFO 18008 — [ 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-02-23 18:49:06.270 INFO 18008 — [ 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-02-23 18:49:06.273 INFO 18008 — [ 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-02-23 18:49:06.341 INFO 18008 — [ 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-02-23 18:49:06.346 INFO 18008 — [ main] trationDelegate$BeanPostProcessorChecker : Bean ‘io.camunda.zeebe.spring.client.config.ZeebeClientStarterAutoConfiguration’ of type [io.camunda.zeebe.spring.client.config.ZeebeClientStarterAutoConfiguration$$EnhancerBySpringCGLIB$$beb0928f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-02-23 18:49:06.351 INFO 18008 — [ 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-02-23 18:49:06.352 INFO 18008 — [ 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-02-23 18:49:06.357 INFO 18008 — [ 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-02-23 18:49:06.366 INFO 18008 — [ 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-02-23 18:49:06.370 INFO 18008 — [ 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-02-23 18:49:06.376 INFO 18008 — [ 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-02-23 18:49:06.385 INFO 18008 — [ 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-02-23 18:49:06.389 INFO 18008 — [ 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-02-23 18:49:06.412 INFO 18008 — [ 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-02-23 18:49:06.425 INFO 18008 — [ 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-02-23 18:49:06.430 INFO 18008 — [ 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-02-23 18:49:06.510 INFO 18008 — [ 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-02-23 18:49:06.553 INFO 18008 — [ 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-02-23 18:49:06.557 INFO 18008 — [ 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-02-23 18:49:06.558 INFO 18008 — [ 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-02-23 18:49:06.559 INFO 18008 — [ 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-02-23 18:49:06.563 INFO 18008 — [ 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-02-23 18:49:06.565 INFO 18008 — [ 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-02-23 18:49:07.035 INFO 18008 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2023-02-23 18:49:07.050 INFO 18008 — [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2023-02-23 18:49:07.051 INFO 18008 — [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.71]
2023-02-23 18:49:07.770 INFO 18008 — [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2023-02-23 18:49:07.771 INFO 18008 — [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 2801 ms
2023-02-23 18:49:07.900 INFO 18008 — [ main] c.a.p.ZeebeDeploymentAnnotationProcessor : Configuring deployment: ZeebeDeploymentValue{resources=[classpath*:/models/.], beanInfo=io.camunda.zeebe.spring.client.bean.ClassInfo@138aa3cc}
2023-02-23 18:49:07.911 INFO 18008 — [ main] s.c.p.ZeebeClientConfigurationProperties : Using connection mode ‘CLOUD’ to connect to Zeebe
2023-02-23 18:49:08.406 INFO 18008 — [ main] z.s.c.a.p.ZeebeWorkerAnnotationProcessor : Configuring 1 Zeebe worker(s) of bean ‘myWorker’: [ZeebeWorkerValue{type=‘invokeMyService’, name=‘myWorker#invokeMyService’, timeout=-1, maxJobsActive=-1, requestTimeout=-1, pollInterval=-1, autoComplete=true, fetchVariables=[], enabled=true, methodInfo=io.camunda.zeebe.spring.client.bean.MethodInfo@158ae284}]
2023-02-23 18:49:14.097 INFO 18008 — [ main] i.c.z.s.c.ZeebeClientSpringConfiguration : Creating ZeebeClient using ZeebeClientBuilder [gatewayAddress: 75dd65b6-753e-4d77-a147-91a93e10fdca.dsm-1.zeebe.camunda.io:443
jobWorkerMaxJobsActive: 32
numJobWorkerExecutionThreads: 1
defaultJobWorkerName: null
defaultJobTimeout: PT5M
defaultJobPollInterval: PT0.1S
defaultMessageTimeToLive: PT1H
defaultRequestTimeout: PT10S
overrideAuthority: null
]
2023-02-23 18:49:15.786 WARN 18008 — [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Failed to start bean ‘zeebeClientLifecycle’; nested exception is io.camunda.zeebe.client.api.command.ClientStatusException: io exception
Channel Pipeline: [SslHandler#0, ProtocolNegotiators$ClientTlsHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
2023-02-23 18:49:15.791 INFO 18008 — [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
2023-02-23 18:49:15.818 INFO 18008 — [ main] ConditionEvaluationReportLoggingListener :

Error starting ApplicationContext. To display the conditions report re-run your application with ‘debug’ enabled.
2023-02-23 18:49:15.863 ERROR 18008 — [ main] o.s.boot.SpringApplication : Application run failed

org.springframework.context.ApplicationContextException: Failed to start bean ‘zeebeClientLifecycle’; nested exception is io.camunda.zeebe.client.api.command.ClientStatusException: io exception
Channel Pipeline: [SslHandler#0, ProtocolNegotiators$ClientTlsHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]

aused by: java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: UNAVAILABLE: io exception
Channel Pipeline: [SslHandler#0, ProtocolNegotiators$ClientTlsHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395) ~[na:na]
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1999) ~[na:na]
at io.camunda.zeebe.client.impl.ZeebeClientFutureImpl.join(ZeebeClientFutureImpl.java:48) ~[zeebe-client-java-8.1.5.jar:8.1.5]
… 22 common frames omitted
Caused by: io.grpc.StatusRuntimeException: UNAVAILABLE: io exception
Channel Pipeline: [SslHandler#0, ProtocolNegotiators$ClientTlsHandler#0, WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
at io.grpc.Status.asRuntimeException(Status.java:535) ~[grpc-api-1.49.1.jar:1.49.1]
at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:487) ~[grpc-stub-1.49.1.jar:1.49.1]
at io.grpc.internal.DelayedClientCall$DelayedListener$3.run(DelayedClientCall.java:470) ~[grpc-core-1.49.1.jar:1.49.1]
at io.grpc.internal.DelayedClientCall$DelayedListener.delayOrExecute(DelayedClientCall.java:434) ~[grpc-core-1.49.1.jar:1.49.1]
at io.grpc.internal.DelayedClientCall$DelayedListener.onClose(DelayedClientCall.java:467) ~[grpc-core-1.49.1.jar:1.49.1]
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:563) ~[grpc-core-1.49.1.jar:1.49.1]
at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:70) ~[grpc-core-1.49.1.jar:1.49.1]
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:744) ~[grpc-core-1.49.1.jar:1.49.1]
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:723) ~[grpc-core-1.49.1.jar:1.49.1]
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) ~[grpc-core-1.49.1.jar:1.49.1]
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133) ~[grpc-core-1.49.1.jar:1.49.1]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host
at java.base/sun.nio.ch.SocketDispatcher.read0(Native Method) ~[na:na]
at java.base/sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43) ~[na:na]
at java.base/sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:276) ~[na:na]
at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:233) ~[na:na]
at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:223) ~[na:na]
at java.base/sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:358) ~[na:na]
at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:259) ~[netty-buffer-4.1.87.Final.jar:4.1.87.Final]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1132) ~[netty-buffer-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:357) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:151) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) ~[netty-transport-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.87.Final.jar:4.1.87.Final]
… 1 common frames omitted

Please help.

regards.
Shilpa