Getting Error While Starting Zeebe Broker

Camunda 8 Topics Discussion & Questions
1

Hi Please find the error details below.

Recreating zeebe_broker … done
Recreating zeebe_monitor … done
Attaching to zeebe_broker, zeebe_monitor
zeebe_broker | ++ hostname -i
zeebe_broker | + export ZEEBE_HOST=172.22.0.2
zeebe_broker | + ZEEBE_HOST=172.22.0.2
zeebe_broker | + ‘[’ false = true ‘]’
zeebe_broker | + export ZEEBE_BROKER_NETWORK_HOST=172.22.0.2
zeebe_broker | + ZEEBE_BROKER_NETWORK_HOST=172.22.0.2
zeebe_broker | + export ZEEBE_BROKER_GATEWAY_CLUSTER_HOST=172.22.0.2
zeebe_broker | + ZEEBE_BROKER_GATEWAY_CLUSTER_HOST=172.22.0.2
zeebe_broker | + exec /usr/local/zeebe/bin/broker
zeebe_monitor |
zeebe_monitor | ___ __
zeebe_monitor | / _ _ | _ (_ . _ _ | _ |/| _ _ . |_ _ _
zeebe_monitor | /__ (- (- |) (- __) | ||| |) | (- | | () | ) | | () |
zeebe_monitor | |
zeebe_monitor |
zeebe_monitor | ================================================================
zeebe_monitor |
zeebe_monitor |
zeebe_broker | ______ ______ ______ ____ ______ ____ _____ ____ _ __ ______ _____
zeebe_broker | |__ / | | | | | _ \ | | | _ \ | __ \ / __ \ | |/ / | | | __
zeebe_broker | / / | | | | | |) | | | | |) | | |) | | | | | | ’ / | | | |__) |
zeebe_broker | / / | | | | | _ < | | | _ < | _ / | | | | | < | | | _ /
zeebe_broker | / / | | | | | |) | | | | |) | | | \ \ | || | | . \ | |____ | | \
zeebe_broker | /| || || |/ || |/ || _\ _/ ||_\ |___| || _
zeebe_broker |
zeebe_monitor | 2020-07-15 18:06:18.309 INFO 1 — [ restartedMain] io.zeebe.monitor.ZeebeSimpleMonitorApp : Starting ZeebeSimpleMonitorApp on 1b0fcb16bb13 with PID 1 (/app/classes started by root in /)
zeebe_monitor | 2020-07-15 18:06:18.314 DEBUG 1 — [ restartedMain] io.zeebe.monitor.ZeebeSimpleMonitorApp : Running with Spring Boot v2.2.6.RELEASE, Spring v5.2.5.RELEASE
zeebe_monitor | 2020-07-15 18:06:18.314 INFO 1 — [ restartedMain] io.zeebe.monitor.ZeebeSimpleMonitorApp : No active profile set, falling back to default profiles: default
zeebe_broker | 2020-07-15 18:06:18.348 [] [main] INFO io.zeebe.broker.StandaloneBroker - Starting StandaloneBroker v0.23.1 on e8b6bdb3bcf3 with PID 7 (/usr/local/zeebe/lib/zeebe-distribution-0.23.1.jar started by root in /usr/local/zeebe)
zeebe_broker | 2020-07-15 18:06:18.354 [] [main] INFO io.zeebe.broker.StandaloneBroker - No active profile set, falling back to default profiles: default
zeebe_broker | 2020-07-15 18:06:21.048 [] [main] INFO io.zeebe.broker.StandaloneBroker - Started StandaloneBroker in 3.733 seconds (JVM running for 8.468)
zeebe_broker | 2020-07-15 18:06:21.213 [] [main] INFO io.zeebe.broker.system - Version: 0.23.1
zeebe_broker | 2020-07-15 18:06:21.373 [] [main] INFO io.zeebe.broker.system - Starting broker 0 with configuration {
zeebe_broker | “network” : {
zeebe_broker | “host” : “172.22.0.2”,
zeebe_broker | “portOffset” : 0,
zeebe_broker | “maxMessageSize” : “4MB”,
zeebe_broker | “advertisedHost” : “172.22.0.2”,
zeebe_broker | “commandApi” : {
zeebe_broker | “host” : “172.22.0.2”,
zeebe_broker | “port” : 26501,
zeebe_broker | “advertisedHost” : “172.22.0.2”,
zeebe_broker | “advertisedPort” : 26501,
zeebe_broker | “advertisedAddress” : “172.22.0.2:26501”,
zeebe_broker | “address” : “172.22.0.2:26501”
zeebe_broker | },
zeebe_broker | “internalApi” : {
zeebe_broker | “host” : “172.22.0.2”,
zeebe_broker | “port” : 26502,
zeebe_broker | “advertisedHost” : “172.22.0.2”,
zeebe_broker | “advertisedPort” : 26502,
zeebe_broker | “advertisedAddress” : “172.22.0.2:26502”,
zeebe_broker | “address” : “172.22.0.2:26502”
zeebe_broker | },
zeebe_broker | “monitoringApi” : {
zeebe_broker | “host” : “172.22.0.2”,
zeebe_broker | “port” : 9600,
zeebe_broker | “advertisedHost” : “172.22.0.2”,
zeebe_broker | “advertisedPort” : 9600,
zeebe_broker | “advertisedAddress” : “172.22.0.2:9600”,
zeebe_broker | “address” : “172.22.0.2:9600”
zeebe_broker | },
zeebe_broker | “maxMessageSizeInBytes” : 4194304
zeebe_broker | },
zeebe_broker | “cluster” : {
zeebe_broker | “initialContactPoints” : [ ],
zeebe_broker | “partitionIds” : [ 1 ],
zeebe_broker | “nodeId” : 0,
zeebe_broker | “partitionsCount” : 1,
zeebe_broker | “replicationFactor” : 1,
zeebe_broker | “clusterSize” : 1,
zeebe_broker | “clusterName” : “zeebe-cluster”,
zeebe_broker | “gossipFailureTimeout” : 10000,
zeebe_broker | “gossipInterval” : 250,
zeebe_broker | “gossipProbeInterval” : 1000
zeebe_broker | },
zeebe_broker | “threads” : {
zeebe_broker | “cpuThreadCount” : 2,
zeebe_broker | “ioThreadCount” : 2
zeebe_broker | },
zeebe_broker | “data” : {
zeebe_broker | “directories” : [ “/usr/local/zeebe/data” ],
zeebe_broker | “logSegmentSize” : “512MB”,
zeebe_broker | “snapshotPeriod” : “PT15M”,
zeebe_broker | “logIndexDensity” : 100,
zeebe_broker | “logSegmentSizeInBytes” : 536870912
zeebe_broker | },
zeebe_broker | “exporters” : {
zeebe_broker | “hazelcast” : {
zeebe_broker | “jarPath” : “/usr/local/zeebe/exporters/zeebe-hazelcast-exporter.jar”,
zeebe_broker | “className” : “io.zeebe.hazelcast.exporter.HazelcastExporter”,
zeebe_broker | “args” : null,
zeebe_broker | “external” : true
zeebe_broker | }
zeebe_broker | },
zeebe_broker | “gateway” : {
zeebe_broker | “network” : {
zeebe_broker | “host” : “0.0.0.0”,
zeebe_broker | “port” : 26500,
zeebe_broker | “minKeepAliveInterval” : “PT30S”
zeebe_broker | },
zeebe_broker | “cluster” : {
zeebe_broker | “contactPoint” : “172.22.0.2:26502”,
zeebe_broker | “requestTimeout” : “PT15S”,
zeebe_broker | “clusterName” : “zeebe-cluster”,
zeebe_broker | “memberId” : “gateway”,
zeebe_broker | “host” : “172.22.0.2”,
zeebe_broker | “port” : 26502
zeebe_broker | },
zeebe_broker | “threads” : {
zeebe_broker | “managementThreads” : 1
zeebe_broker | },
zeebe_broker | “monitoring” : {
zeebe_broker | “enabled” : false,
zeebe_broker | “host” : “172.22.0.2”,
zeebe_broker | “port” : 9600
zeebe_broker | },
zeebe_broker | “security” : {
zeebe_broker | “enabled” : false,
zeebe_broker | “certificateChainPath” : null,
zeebe_broker | “privateKeyPath” : null
zeebe_broker | },
zeebe_broker | “enable” : true
zeebe_broker | },
zeebe_broker | “backpressure” : {
zeebe_broker | “enabled” : true,
zeebe_broker | “algorithm” : “VEGAS”
zeebe_broker | },
zeebe_broker | “stepTimeout” : “PT5M”
zeebe_broker | }
zeebe_broker | 2020-07-15 18:06:21.414 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [1/11]: actor scheduler
zeebe_broker | 2020-07-15 18:06:21.418 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [2/11]: membership and replication protocol
zeebe_broker | 2020-07-15 18:06:26.694 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [3/11]: command api transport
zeebe_broker | 2020-07-15 18:06:27.075 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [4/11]: command api handler
zeebe_broker | 2020-07-15 18:06:27.137 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [5/11]: subscription api
zeebe_broker | 2020-07-15 18:06:27.191 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [6/11]: embedded gateway
zeebe_broker | 2020-07-15 18:06:27.204 [] [main] INFO io.zeebe.gateway - Version: 0.23.1
zeebe_broker | 2020-07-15 18:06:27.205 [] [main] INFO io.zeebe.gateway - Starting gateway with configuration {
zeebe_broker | “network” : {
zeebe_broker | “host” : “0.0.0.0”,
zeebe_broker | “port” : 26500,
zeebe_broker | “minKeepAliveInterval” : “PT30S”
zeebe_broker | },
zeebe_broker | “cluster” : {
zeebe_broker | “contactPoint” : “172.22.0.2:26502”,
zeebe_broker | “requestTimeout” : “PT15S”,
zeebe_broker | “clusterName” : “zeebe-cluster”,
zeebe_broker | “memberId” : “gateway”,
zeebe_broker | “host” : “172.22.0.2”,
zeebe_broker | “port” : 26502
zeebe_broker | },
zeebe_broker | “threads” : {
zeebe_broker | “managementThreads” : 1
zeebe_broker | },
zeebe_broker | “monitoring” : {
zeebe_broker | “enabled” : false,
zeebe_broker | “host” : “172.22.0.2”,
zeebe_broker | “port” : 9600
zeebe_broker | },
zeebe_broker | “security” : {
zeebe_broker | “enabled” : false,
zeebe_broker | “certificateChainPath” : null,
zeebe_broker | “privateKeyPath” : null
zeebe_broker | },
zeebe_broker | “enable” : true
zeebe_broker | }
zeebe_broker | 2020-07-15 18:06:27.399 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [7/11]: cluster services
zeebe_broker | 2020-07-15 18:06:28.476 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [8/11]: topology manager
zeebe_broker | 2020-07-15 18:06:28.479 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [9/11]: metric’s server
zeebe_broker | 2020-07-15 18:06:28.502 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [10/11]: leader management request handler
zeebe_broker | 2020-07-15 18:06:28.505 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 [11/11]: zeebe partitions
zeebe_broker | 2020-07-15 18:06:28.509 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 partitions [1/1]: partition 1
zeebe_broker | 2020-07-15 18:06:30.284 [Broker-0-StreamProcessor-1] [Broker-0-zb-actors-1] INFO org.camunda.feel.FeelEngine - Engine created. [value-mapper: CompositeValueMapper(List(io.zeebe.el.impl.feel.MessagePackValueMapper@59dfda0b)), function-provider: io.zeebe.el.impl.feel.FeelFunctionProvider@21ca4ff2, configuration: Configuration(false)]
zeebe_broker | 2020-07-15 18:06:30.510 [Broker-0-StreamProcessor-1] [Broker-0-zb-actors-1] INFO io.zeebe.logstreams - Recovered state of partition 1 from snapshot at position -1
zeebe_broker | 2020-07-15 18:06:30.673 [Broker-0-StreamProcessor-1] [Broker-0-zb-actors-1] INFO org.camunda.feel.FeelEngine - Engine created. [value-mapper: CompositeValueMapper(List(io.zeebe.el.impl.feel.MessagePackValueMapper@3c9c6bdf)), function-provider: io.zeebe.el.impl.feel.FeelFunctionProvider@18291eee, configuration: Configuration(false)]
zeebe_broker | 2020-07-15 18:06:30.696 [Broker-0-StreamProcessor-1] [Broker-0-zb-actors-1] INFO org.camunda.feel.FeelEngine - Engine created. [value-mapper: CompositeValueMapper(List(io.zeebe.el.impl.feel.MessagePackValueMapper@6382215b)), function-provider: io.zeebe.el.impl.feel.FeelFunctionProvider@abebe77, configuration: Configuration(false)]
zeebe_broker | 2020-07-15 18:06:30.931 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 partitions succeeded. Started 1 steps in 2422 ms.
zeebe_broker | 2020-07-15 18:06:30.932 [] [main] INFO io.zeebe.broker.system - Bootstrap Broker-0 succeeded. Started 11 steps in 9518 ms.
zeebe_broker | Jul 15, 2020 6:06:31 PM com.hazelcast.instance.HazelcastInstanceFactory
zeebe_broker | WARNING: Hazelcast is starting in a Java modular environment (Java 9 and newer) but without proper access to required Java packages. Use additional Java arguments to provide Hazelcast access to Java internal API. The internal API access is used to get the best performance results. Arguments to be used:
zeebe_broker | --add-modules java.se --add-exports java.base/jdk.internal.ref=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.management/sun.management=ALL-UNNAMED --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED
zeebe_broker | 2020-07-15 18:06:31.295 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.instance.AddressPicker - [LOCAL] [dev] [3.12.6] Prefer IPv4 stack is true, prefer IPv6 addresses is false
zeebe_broker | 2020-07-15 18:06:31.303 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.instance.AddressPicker - [LOCAL] [dev] [3.12.6] Picked [172.22.0.2]:5701, using socket ServerSocket[addr=/0.0.0.0,localport=5701], bind any local is true
zeebe_monitor | 2020-07-15 18:06:31.316 INFO 1 — [ restartedMain] i.z.monitor.zeebe.ZeebeHazelcastService : Connecting to Hazelcast ‘zeebe:5000’
zeebe_broker | 2020-07-15 18:06:31.358 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.system - [172.22.0.2]:5701 [dev] [3.12.6] Hazelcast 3.12.6 (20200130 - be02cc5) starting at [172.22.0.2]:5701
zeebe_broker | 2020-07-15 18:06:31.359 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.system - [172.22.0.2]:5701 [dev] [3.12.6] Copyright © 2008-2020, Hazelcast, Inc. All Rights Reserved.
zeebe_broker | 2020-07-15 18:06:31.769 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.spi.impl.operationservice.impl.BackpressureRegulator - [172.22.0.2]:5701 [dev] [3.12.6] Backpressure is disabled
zeebe_monitor | WARNING: An illegal reflective access operation has occurred
zeebe_monitor | WARNING: Illegal reflective access by com.hazelcast.internal.networking.nio.SelectorOptimizer (file:/app/libs/hazelcast-3.12.6.jar) to field sun.nio.ch.SelectorImpl.selectedKeys
zeebe_monitor | WARNING: Please consider reporting this to the maintainers of com.hazelcast.internal.networking.nio.SelectorOptimizer
zeebe_monitor | WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
zeebe_monitor | WARNING: All illegal access operations will be denied in a future release
zeebe_monitor | 2020-07-15 18:06:32.569 WARN 1 — [ient_1.cluster-] c.h.c.c.nio.ClusterConnectorService : hz.client_1 [dev] [3.12.6] Exception during initial connection to [zeebe]:5000: com.hazelcast.core.HazelcastException: java.net.SocketException: Connection refused to address zeebe/172.22.0.2:5000
zeebe_monitor | 2020-07-15 18:06:32.570 WARN 1 — [ient_1.cluster-] c.h.c.c.nio.ClusterConnectorService : hz.client_1 [dev] [3.12.6] Unable to get live cluster connection, retry in 3000 ms, attempt 1 of 2.
zeebe_broker | 2020-07-15 18:06:32.688 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.instance.Node - [172.22.0.2]:5701 [dev] [3.12.6] Creating MulticastJoiner
zeebe_broker | 2020-07-15 18:06:33.201 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.spi.impl.operationexecutor.impl.OperationExecutorImpl - [172.22.0.2]:5701 [dev] [3.12.6] Starting 4 partition threads and 3 generic threads (1 dedicated for priority tasks)
zeebe_broker | 2020-07-15 18:06:33.206 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.internal.diagnostics.Diagnostics - [172.22.0.2]:5701 [dev] [3.12.6] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
zeebe_broker | 2020-07-15 18:06:33.234 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.core.LifecycleService - [172.22.0.2]:5701 [dev] [3.12.6] [172.22.0.2]:5701 is STARTING
zeebe_monitor | 2020-07-15 18:06:35.573 WARN 1 — [ient_1.cluster-] c.h.c.c.nio.ClusterConnectorService : hz.client_1 [dev] [3.12.6] Exception during initial connection to [zeebe]:5000: com.hazelcast.core.HazelcastException: java.net.SocketException: Connection refused to address zeebe/172.22.0.2:5000
zeebe_monitor | 2020-07-15 18:06:35.574 WARN 1 — [ient_1.cluster-] c.h.c.c.nio.ClusterConnectorService : hz.client_1 [dev] [3.12.6] Unable to get live cluster connection, attempt 2 of 2.
zeebe_monitor | 2020-07-15 18:06:35.574 WARN 1 — [ient_1.cluster-] c.h.c.c.nio.ClusterConnectorService : hz.client_1 [dev] [3.12.6] Unable to connect to any address for cluster: dev. The following addresses were tried: [[zeebe]:5000]
zeebe_monitor | 2020-07-15 18:06:35.574 WARN 1 — [ient_1.cluster-] c.h.c.c.nio.ClusterConnectorService : hz.client_1 [dev] [3.12.6] Could not connect to any cluster, shutting down the client: Unable to connect to any cluster.
zeebe_monitor | 2020-07-15 18:06:35.884 ERROR 1 — [ restartedMain] o.s.boot.SpringApplication : Application run failed
zeebe_monitor |
zeebe_monitor | org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘zeebeHazelcastService’: Invocation of init method failed; nested exception is java.lang.IllegalStateException: Unable to connect to any cluster.
zeebe_monitor | at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:160) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:416) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1788) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:595) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:882) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:878) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:550) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]
zeebe_monitor | at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
zeebe_monitor | at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
zeebe_monitor | at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
zeebe_monitor | at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
zeebe_monitor | at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
zeebe_monitor | at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE]
zeebe_monitor | at io.zeebe.monitor.ZeebeSimpleMonitorApp.main(ZeebeSimpleMonitorApp.java:39) ~[classes/:na]
zeebe_monitor | at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
zeebe_monitor | at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na]
zeebe_monitor | at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
zeebe_monitor | at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
zeebe_monitor | at org.springframework.boot.devtools.restart.RestartLauncher.run(RestartLauncher.java:49) ~[spring-boot-devtools-2.2.6.RELEASE.jar:2.2.6.RELEASE]
zeebe_monitor | Caused by: java.lang.IllegalStateException: Unable to connect to any cluster.
zeebe_monitor | at com.hazelcast.client.connection.nio.ClusterConnectorServiceImpl.connectToClusterInternal(ClusterConnectorServiceImpl.java:214) ~[hazelcast-client-3.12.6.jar:3.12.6]
zeebe_monitor | at com.hazelcast.client.connection.nio.ClusterConnectorServiceImpl.access$000(ClusterConnectorServiceImpl.java:62) ~[hazelcast-client-3.12.6.jar:3.12.6]
zeebe_monitor | at com.hazelcast.client.connection.nio.ClusterConnectorServiceImpl$1.call(ClusterConnectorServiceImpl.java:279) ~[hazelcast-client-3.12.6.jar:3.12.6]
zeebe_monitor | at com.hazelcast.client.connection.nio.ClusterConnectorServiceImpl$1.call(ClusterConnectorServiceImpl.java:275) ~[hazelcast-client-3.12.6.jar:3.12.6]
zeebe_monitor | at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[na:na]
zeebe_monitor | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na]
zeebe_monitor | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na]
zeebe_monitor | at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]
zeebe_monitor | at com.hazelcast.util.executor.HazelcastManagedThread.executeRun(HazelcastManagedThread.java:64) ~[hazelcast-3.12.6.jar:3.12.6]
zeebe_monitor | at com.hazelcast.util.executor.HazelcastManagedThread.run(HazelcastManagedThread.java:80) ~[hazelcast-3.12.6.jar:3.12.6]
zeebe_monitor |
zeebe_broker | 2020-07-15 18:06:36.003 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.internal.cluster.ClusterService - [172.22.0.2]:5701 [dev] [3.12.6]
zeebe_broker |
zeebe_broker | Members {size:1, ver:1} [
zeebe_broker | Member [172.22.0.2]:5701 - 2a375746-90ce-48b7-a2fe-841f65a2254f this
zeebe_broker | ]
zeebe_broker |
zeebe_broker | 2020-07-15 18:06:36.072 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.core.LifecycleService - [172.22.0.2]:5701 [dev] [3.12.6] [172.22.0.2]:5701 is STARTED
zeebe_broker | 2020-07-15 18:06:36.092 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO com.hazelcast.internal.partition.impl.PartitionStateManager - [172.22.0.2]:5701 [dev] [3.12.6] Initializing cluster partition table arrangement…
zeebe_broker | 2020-07-15 18:06:36.123 [Broker-0-Exporter-1] [Broker-0-zb-fs-workers-0] INFO io.zeebe.broker.exporter.hazelcast - Export records to ringbuffer with name ‘zeebe’ [head: 0, tail: -1, size: 0, capacity: 10000]
zeebe_monitor exited with code 0

2

Hi @Tauqeer,

Thanks for sharing this error. Which version of the hazelcast exporter are you using?

1 Like
3

Hi @korthout,
Thank you for your immediate response, as you can see from logs its Hazelcast 3.12.6.
And i did nothing much, i just pulled the image of zeebe broker and simple monitor and tried to run these application and got the error.

4

Hazelcast is part of the zeebe-hazelcast-exporter you use. In version 0.9.0 of the zeebe-hazelcast-exporter the version of hazelcast is updated from 3.12.6 to 4.0.1. I am not entirely sure that the zeebe version you are using (0.23.1) works together with the older version of the zeebe-hazelcast-exporter you are using. I can not see which version of the zeebe-hazelcast-exporter you use in the logs, only that it is defined in /usr/local/zeebe/exporters/zeebe-hazelcast-exporter.jar.

I would recommend to try and replace your /usr/local/zeebe/exporters/zeebe-hazelcast-exporter.jar (as defined in your config in exporters.hazelcast.jarPath) withthe newer version https://github.com/zeebe-io/zeebe-hazelcast-exporter/releases/tag/0.9.0

I also would like to note that 0.23.1 is not the latest stable release. You can find 0.23.4 here: https://github.com/zeebe-io/zeebe/releases/tag/0.23.4

Please let me know if this helped.

1 Like
5

Hi @korthout,

Thank you so much for your guidance and i want to learn more about zeebe and i have gone through the documentattion also, is there any source from where i can learn more about zeebe.

https://github.com/zeebe-io/zeebe-docker-compose this is the link from where i downloaded zeebe-docker-compose

1 Like
6

Great to hear you’re eager to learn. I generally recommend our docs at https://docs.zeebe.io/ to learn more about using zeebe. There’s a lot of info there.

I’m surprised to see that zeebe-docker-compose is so behind in its supported versions. I don’t have time right now, but I’ll take a look later to try and reproduce your situation. You may have just ran into an actual bug instead of a configuration mistake. I’ll come back on that later. Hope that’s okay with you.

For now, it might be useful to run a broker without docker compose. Perhaps have a look at the quick start guide to get on your way with Zeebe: https://docs.zeebe.io/introduction/quickstart.html and connect a https://github.com/zeebe-io/zeebe-simple-monitor. If you need any help with that, don’t hesitate to reach out.

Best,
Nico

1 Like
7

Hi @Tauqeer,

I’ve tried to reproduce your problem, but so far I have been unable to. Please find my steps below and let me know if I did something different from what you tried.

git clone https://github.com/zeebe-io/zeebe-docker-compose
cd zeebe-docker-compose
cd simple-monitor
docker-compose up

Logs contained:

zeebe_broker | 2020-07-20 14:39:35.553 [] [main] INFO  io.zeebe.broker.system - Bootstrap Broker-0 succeeded. Started 11 steps in 4640 ms.
...
zeebe_monitor | 2020-07-20 14:39:41.892  INFO 1 --- [  restartedMain] io.zeebe.monitor.ZeebeSimpleMonitorApp   : Started ZeebeSimpleMonitorApp in 13.515 seconds (JVM running for 14.291)

I hope this helps and don’t hesitate to reach out.

Best,

Nico

1 Like
8

Hi @korthout
Thank you so much for your help, i actually tried in a VM and got such error. I previsouly had installed zeebe-docker-compose and i just copied my zeebe-docker-compose from local to VM and it worked fine. So i thought the current version might be unstable, but i will try once again in my local and on VM with the newer vesion and if i face any such issue i will report back to you.

Thank you,
Tauqeer.

9

Hi @Tauqeer,

Awesome. Good luck. And I’m curious to your results.

Best,

Nico

10

Hi @korthout

I have one question, Can we pass event subprocess Process ID dynamically.

Thank You,
Tauqeer

11

Hi @Tauqeer,

I’m sorry, but I don’t fully understand your question.

An event subprocess is started by the occurrence of an event (i.e. timer, message or error). Being a subprocess, the event subprocess is part of another process and does have a Process ID on its own. Only a process can have this. You can read more about event subprocesses here: https://docs.zeebe.io/bpmn-workflows/event-subprocesses/event-subprocesses.html. If this does not answer your question, please provide a bit more detail.

Best,

Nico

1 Like
12

Hi @Korthout

I’m extremely sorry i had explained you wrongly. For Call activities can we pass the Process Id Dynamically, Lets assume when we are creating the instance of workflow we are getting the value of process id or workflow Id which should be called. Please give me one example.

image
image1647×461 30.6 KB

13

Hi @Tauqeer,

No problem whatsoever. You can define the Process Id of a call activity dynamically. You can read more about that here: Zeebe | Camunda 8 Docs, but this is the important part for you:

Usually, the processId is defined as a static value (e.g. shipping-process ) but it can also be defined as expression (e.g. = "shipping-" + tenantId ). The expression is evaluated on activating the call activity and must result in a string .

So you can use any FEEL expression here that results in a string. You can find more about such expressions here: Zeebe | Camunda 8 Docs.

Hope this helps.

Best,

Nico

2 Likes
14

@korthout Thank You so much.

15

Happy to help :slight_smile:

16

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

18