io.grpc.netty.NettyServerTransport notifyTerminated

Camunda Platform 8 Topics Zeebe Broker
1

Hi,

I have started broker.bat from windows with Java8
then i tried to add order-zeebe.bpmn from https://github.com/berndruecker/flowing-retail/blob/master/zeebe project and i have following error message
C:\Users\zeebe\binaires\windows\zeebe-distribution-0.17.0\zeebe-broker-0.17.0\bin\zbctl deploy C:\Users\IdeaProjects\zeebejava\order\src\main\resources\order-zeebe.bpmn

An idea ?

Blockquote

15:40:33.721 [io.zeebe.gateway.impl.broker.cluster.BrokerTopologyManagerImpl] [gateway-zb-actors-0] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘0’ with address ‘0.0.0.0:26501’ on transport ‘broker-client-internal’
juin 07, 2019 3:40:57 PM io.grpc.netty.NettyServerTransport notifyTerminated
INFOS: Transport failed
java.io.IOException: Une connexion existante a dÂč Ûtre fermÚe par lÆh¶te distant
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(Unknown Source)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
at sun.nio.ch.IOUtil.read(Unknown Source)
at sun.nio.ch.SocketChannelImpl.read(Unknown Source)
at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1125)
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:347)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:677)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:612)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:529)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:491)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:905)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Unknown Source)

strong text

2

Hi @pcouas, I recommend using Docker: https://github.com/zeebe-io/zeebe-docker-compose.

Josh

3

Hi

Currently i have just tested simple docker run and i dont" kwow how to deploy
I must seeing how make docker compose

Regards

4

Hi

I have opened an other ticket, compose failed ! regards
So i could not use Windows distribution to deploy my bpmn file with zbtl deploy ??
Error is predent but bpmn seems deployed zbctl list workflows
Ok now i think i need to zbctl activate ??

5

1 it’s an Alienware intel coreI7 with 12Go Ram with JAVA 8.162

a for Windows Zeebe
i connect to Zeebe github and i make donwload .
I, chose “zeebe-distribution-0.17.0” in Zip format

b sample
i connect to camunda Github

i download and in repository flowing-retail-master\zeebe\java\order\src\main\resources i get order-zeebe.bpmn
c i launch from batch bin/brocker.bat
d i launch bin.zbctl deploy order-zeebe.bpmn
there is an error but that’ seems deployed

6

The error message you are seeing suggests that the embedded gRPC gateway cannot speak to the broker.

  1. Can you please paste the entire start up log of the broker in Pastebin and put a link here?
  2. Which JVM is it?
7

JAVA_HOME=C:\java\jdk1.8.0_162

8

Blockquote
18:21:27.733 [] [main] INFO io.zeebe.util.config - Reading configuration for class class io.zeebe.broker.system.configuration.BrokerCfg from file D:\zpoubelle\xxcamunda\zeebe\zeebe-distribution-0.17.0\zeebe-broker-0.17.0\conf\zeebe.cfg.toml 18:21:27.851 [] [main] INFO io.zeebe.broker.system - Scheduler configuration: Threads{cpu-bound: 2, io-bound: 2}. 18:21:27.888 [] [main] INFO io.zeebe.broker.system - Version: 0.17.0 18:21:27.892 [] [main] INFO io.zeebe.broker.system - Starting broker with configuration { “network”: { “host”: “0.0.0.0”, “defaultSendBufferSize”: “16M”, “portOffset”: 0, “client”: { “controlMessageBufferSize”: “8M”, “host”: “0.0.0.0”, “port”: 26501, “sendBufferSize”: “16M” }, “management”: { “receiveBufferSize”: “8M”, “host”: “0.0.0.0”, “port”: 26502, “sendBufferSize”: “16M” }, “replication”: { “host”: “0.0.0.0”, “port”: 26503, “sendBufferSize”: “16M” }, “subscription”: { “receiveBufferSize”: “8M”, “host”: “0.0.0.0”, “port”: 26504, “sendBufferSize”: “16M” } }, “cluster”: { “initialContactPoints”: [], “partitionIds”: [ 0 ], “nodeId”: 0, “partitionsCount”: 1, “replicationFactor”: 1, “clusterSize”: 1 }, “threads”: { “cpuThreadCount”: 2, “ioThreadCount”: 2 }, “metrics”: { “reportingInterval”: “5s”, “file”: “D:\zpoubelle\xxcamunda\zeebe\zeebe-distribution-0.17.0\zeebe-broker-0.17.0\bin\
\metrics\zeebe.prom”, “enableHttpServer”: false, “host”: “0.0.0.0”, “port”: 9600 }, “data”: { “directories”: [ “D:\zpoubelle\xxcamunda\zeebe\zeebe-distribution-0.17.0\zeebe-broker-0.17.0\bin\
\data” ], “defaultLogSegmentSize”: “512M”, “snapshotPeriod”: “15m”, “snapshotReplicationPeriod”: “5m” }, “gossip”: { “retransmissionMultiplier”: 3, “probeInterval”: “1s”, “probeTimeout”: “500ms”, “probeIndirectNodes”: 3, “probeIndirectTimeout”: “1s”, “suspicionMultiplier”: 5, “syncTimeout”: “3s”, “syncInterval”: “15s”, “joinTimeout”: “1s”, “joinInterval”: “1s”, “leaveTimeout”: “1s”, “maxMembershipEventsPerMessage”: 32, “maxCustomEventsPerMessage”: 8 }, “raft”: { “heartbeatInterval”: “250ms”, “electionInterval”: “1s”, “leaveTimeout”: “1s” }, “exporters”: [], “gateway”: { “enable”: true, “network”: { “host”: “0.0.0.0”, “port”: 26500 }, “cluster”: { “contactPoint”: “0.0.0.0:26501”, “transportBuffer”: “128M”, “requestTimeout”: “15s” }, “threads”: { “managementThreads”: 1 } } } 18:21:27.962 [] [main] INFO io.zeebe.gateway - Version: 0.17.0 18:21:27.962 [] [main] INFO io.zeebe.gateway - Starting gateway with configuration { “enable”: true, “network”: { “host”: “0.0.0.0”, “port”: 26500 }, “cluster”: { “contactPoint”: “0.0.0.0:26501”, “transportBuffer”: “128M”, “requestTimeout”: “15s” }, “threads”: { “managementThreads”: 1 } } 18:21:28.464 [service-controller] [0.0.0.0:26501-zb-actors-1] INFO io.zeebe.broker.transport - Bound managementApi.server to /0.0.0.0:26502 18:21:28.466 [service-controller] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘0’ with address ‘0.0.0.0:26504’ on transport ‘subscriptionApi.client’ 18:21:28.467 [service-controller] [0.0.0.0:26501-zb-actors-1] INFO io.zeebe.broker.transport - Bound subscriptionApi.server to /0.0.0.0:26504 18:21:28.484 [] [main] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘-1’ with address ‘0.0.0.0:26501’ on transport ‘broker-client’ 18:21:28.484 [] [main] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘-1’ with address ‘0.0.0.0:26501’ on transport ‘broker-client-internal’ 18:21:28.790 [service-controller] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘0’ with address ‘0.0.0.0:26502’ on transport ‘managementApi.client’ 18:21:33.014 [service-controller] [0.0.0.0:26501-zb-actors-1] INFO io.zeebe.transport - Bound clientApi.server to /0.0.0.0:26501 18:21:33.017 [service-controller] [0.0.0.0:26501-zb-actors-1] INFO io.zeebe.transport - Bound replicationApi.server to /0.0.0.0:26503 18:21:33.032 [service-controller] [0.0.0.0:26501-zb-actors-1] INFO io.zeebe.raft - Created raft partition-0 with configuration RaftConfiguration{heartbeatInterval=‘250ms’, electionInterval=‘1s’, leaveTimeout=‘1s’} 18:21:33.343 [topology] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘0’ with address ‘0.0.0.0:26502’ on transport ‘managementApi.client’ 18:21:33.344 [topology] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘0’ with address ‘0.0.0.0:26503’ on transport ‘replicationApi.client’ 18:21:33.344 [topology] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘0’ with address ‘0.0.0.0:26504’ on transport ‘subscriptionApi.client’ 18:21:37.928 [partition-0] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.raft - Joined raft in term 0 18:21:37.971 [zb-stream-processor] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.logstreams - Recovering state of partition 0 from snapshot 18:21:41.474 [zb-stream-processor] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.logstreams - Recovered state of partition 0 from snapshot at position -1 18:21:41.619 [zb-stream-processor] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.processor - Start scanning the log for error events. 18:21:41.620 [zb-stream-processor] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.processor - Finished scanning the log for error events. 18:21:42.632 [io.zeebe.gateway.impl.broker.cluster.BrokerTopologyManagerImpl] [gateway-zb-actors-0] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘0’ with address ‘0.0.0.0:26501’ on transport ‘broker-client’ 18:21:42.633 [io.zeebe.gateway.impl.broker.cluster.BrokerTopologyManagerImpl] [gateway-zb-actors-0] INFO io.zeebe.transport.endpoint - Registering endpoint for node ‘0’ with address ‘0.0.0.0:26501’ on transport ‘broker-client-internal’ juin 10, 2019 6:21:43 PM io.grpc.netty.NettyServerTransport notifyTerminated INFOS: Transport failed java.io.IOException: Une connexion existante a dÂč Ûtre fermÚe par lÆh¶te distant at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:192) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288) at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1125) at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:347) at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148) at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:677) at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:612) at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:529) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:491) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:905) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748)

Blockquote

error is not visible in zeebe.log file

9

What happens if you run zbtcl status?

10

zbctl status command
Cluster size: 1
Partitions count: 1
Replication factor: 1
Brokers:
Broker 0 - 0.0.0.0:26501
Partition 0 : Leader

D:\zpoubelle\xxcamunda\zeebe>pause
Appuyez sur une touche pour continuer


11

logs from brocker batch windows at same time
port.endpoint - Registering endpoint for node ‘0’ with address ‘0.0.0.0:26501’ on transport ‘broker-client-internal’
06:37:52.564 [zb-stream-processor] [0.0.0.0:26501-zb-actors-1] INFO io.zeebe.logstreams - Recovered state of partition 0 from snapshot at position -1
juin 11, 2019 6:37:52 AM io.grpc.netty.NettyServerTransport notifyTerminated
INFOS: Transport failed
java.io.IOException: Une connexion existante a dÂč Ûtre fermÚe par lÆh¶te distant
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at io.netty.buffer.PooledUnsafeDirectByteBuf.setBytes(PooledUnsafeDirectByteBuf.java:288)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1125)
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:347)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:677)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:612)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:529)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:491)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:905)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)

06:37:52.709 [zb-stream-processor] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.processor - Start scanning the log for error events.
06:37:52.710 [zb-stream-processor] [0.0.0.0:26501-zb-actors-0] INFO io.zeebe.processor - Finished scanning the log for error events.
06:37:52.711 [z

12

zbctl list

D:\zpoubelle\xxcamunda\zeebe>D:\zpoubelle\xxcamunda\zeebe\zeebe-distribution-0.17.0\zeebe-broker-0.17.0\bin\zbctl list workflows
[
{
“bpmnProcessId”: “order-zeebe”,
“version”: 1,
“workflowKey”: 1,
“resourceName”: “D:\zpoubelle\xxcamunda\zeebe\zeebeflowing\java\order\src\main\resources\order-zeebe.bpmn”
}
]

13

OK, so it looks like it is working even though you have the error message
 you might be able to ignore the error message and just continue on (not ideal, I know - but being pragmatic). The newer version of Zeebe 0.18 (coming soon!) might address this.

14

I have deployed on another computer at Work and exactly same problem
(but docker toolbox docker-compose up is ok on this other computer with broker only !)

1 Like
15

Yay Docker!

So you can use it with Docker then?

16

Now i search how deploy my bpmn to docker with zbctl ?

17

This video demonstrates it: https://youtu.be/xjzwUq-tHXE

18

Ok but in order-zeebe.bpmn, first service task “Save order” callinf with save-order-z an java MicroService Spring Boot.
Where are stored theses micro-service ? it’s ans external jar application listening port 26500.
Zeebe no store Micro service ?

19

Parlez-vous français? Nous n’avons pas encore de documentation en français.

Mais regarde ici pour l’instant: https://translate.google.com/translate?hl=en&sl=en&tl=fr&u=http%3A%2F%2Fdocs.zeebe.io%2Fbasics%2Fclient-server.html&sandbox=1

Auto-translated from https://docs.zeebe.io/basics/client-server.html

20

YES i am french
I have an meeting today with “Product owner” and chief and we must decide if we choose “Zeebe” or not.
Currently we use Camunda in another project and we have too an other project with KAFKA

Regards
Philippe