Modeler causes "unexpected HTTP(1.x) request" in Zeebe-with-hazelcast-exporter 8.2

Hi,

using:

  • Camunda Modeler: 5.17 (on Linux)
  • Zeebe-with-hazelcast-exporter: 8.2.0

When I try to deploy a model from the modeller to the remote Zeebe cluster, I get this:

12:04:46 23.11.2023 GMT+1
io.netty.handler.codec.http2.Http2Exception: Unexpected HTTP/1.x request: POST /gateway_protocol.Gateway/Topology
12:04:46 23.11.2023 GMT+1
at io.netty.handler.codec.http2.Http2Exception.connectionError(Http2Exception.java:109)
12:04:46 23.11.2023 GMT+1
at io.netty.handler.codec.http2.Http2ConnectionHandler$PrefaceDecoder.readClientPrefaceString(Http2ConnectionHandler.java:317)
12:04:46 23.11.2023 GMT+1
at io.netty.handler.codec.http2.Http2ConnectionHandler$PrefaceDecoder.decode(Http2ConnectionHandler.java:247)
12:04:46 23.11.2023 GMT+1
at io.netty.handler.codec.http2.Http2ConnectionHandler.decode(Http2ConnectionHandler.java:453)
12:04:46 23.11.2023 GMT+1
at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:529)
12:04:46 23.11.2023 GMT+1
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:468)
12:04:46 23.11.2023 GMT+1
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:290)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:800)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:499)
12:04:46 23.11.2023 GMT+1
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:397)
12:04:46 23.11.2023 GMT+1
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
12:04:46 23.11.2023 GMT+1
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
12:04:46 23.11.2023 GMT+1
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
12:04:46 23.11.2023 GMT+1
at java.base/java.lang.Thread.run(Unknown Source)
12:04:51 23.11.2023 GMT+1
Nov 23, 2023 11:04:51 AM io.grpc.netty.NettyServerTransport notifyTerminated
12:04:51 23.11.2023 GMT+1
INFO: Transport failed

I also run Zeebe-Simple-Monitor:2.4.1 which is working fine with the Zeebe-with-hazelcast-exporter, which runs within the same application as the broker, though. So it is either the client inside the modeller or something on the network.

First I thought, maybe I have the wrong Camunda-platform defined in my model, but no matter what version I choose in the modeller (Camunda 8.2, 8.3, Zeebe 1.3…) the effect seems the same.