Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NoSuchMethodError with v2.2.0 #346

Closed
sebakerckhof opened this issue Dec 23, 2021 · 3 comments
Closed

NoSuchMethodError with v2.2.0 #346

sebakerckhof opened this issue Dec 23, 2021 · 3 comments
Assignees

Comments

@sebakerckhof
Copy link

I try to connect the monitor to my zeebe instance (zeebe 1.2.8 and hazelcast exporter 1.0.1).
This works with simple-monitor v 2.0.0 and 2.1.0, but fails with 2.2.0, where every action I take in the monitor (e.g. deploying diagram, sending a message, ...) results in the following error:

zeebe-monitor_1  | Exception in thread "grpc-default-executor-0" java.lang.NoSuchMethodError: 'boolean com.google.protobuf.GeneratedMessageV3.isStringEmpty(java.lang.Object)'
zeebe-monitor_1  | 	at io.camunda.zeebe.gateway.protocol.GatewayOuterClass$ProcessRequestObject.getSerializedSize(GatewayOuterClass.java:11683)
zeebe-monitor_1  | 	at com.google.protobuf.CodedOutputStream.computeMessageSizeNoTag(CodedOutputStream.java:877)
zeebe-monitor_1  | 	at com.google.protobuf.CodedOutputStream.computeMessageSize(CodedOutputStream.java:661)
zeebe-monitor_1  | 	at io.camunda.zeebe.gateway.protocol.GatewayOuterClass$DeployProcessRequest.getSerializedSize(GatewayOuterClass.java:10791)
zeebe-monitor_1  | 	at io.grpc.protobuf.lite.ProtoInputStream.available(ProtoInputStream.java:108)
zeebe-monitor_1  | 	at io.grpc.internal.MessageFramer.getKnownLength(MessageFramer.java:205)
zeebe-monitor_1  | 	at io.grpc.internal.MessageFramer.writePayload(MessageFramer.java:137)
zeebe-monitor_1  | 	at io.grpc.internal.AbstractStream.writeMessage(AbstractStream.java:65)
zeebe-monitor_1  | 	at io.grpc.internal.ForwardingClientStream.writeMessage(ForwardingClientStream.java:37)
zeebe-monitor_1  | 	at io.grpc.internal.DelayedStream$6.run(DelayedStream.java:283)
zeebe-monitor_1  | 	at io.grpc.internal.DelayedStream.drainPendingCalls(DelayedStream.java:182)
zeebe-monitor_1  | 	at io.grpc.internal.DelayedStream.access$100(DelayedStream.java:44)
zeebe-monitor_1  | 	at io.grpc.internal.DelayedStream$4.run(DelayedStream.java:148)
zeebe-monitor_1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
zeebe-monitor_1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
zeebe-monitor_1  | 	at java.base/java.lang.Thread.run(Unknown Source)
@saig0 saig0 self-assigned this Dec 30, 2021
@saig0
Copy link
Contributor

saig0 commented Dec 30, 2021

@sebakerckhof thank you for reporting 👍
I can reproduce the issue. I will check why it is failing in version 1.2.0 🤔

@saig0
Copy link
Contributor

saig0 commented Dec 30, 2021

There is a dependency conflict with com.google.protobuf:protobuf-java.

+- io.camunda:spring-zeebe-starter:jar:1.2.8:compile
|  \- io.camunda:spring-zeebe:jar:1.2.8:compile
|     +- io.camunda:zeebe-client-java:jar:1.2.9:compile
|     |  +- com.google.protobuf:protobuf-java:jar:3.18.0:compile

+- io.zeebe.hazelcast:zeebe-hazelcast-connector:jar:1.0.1:compile
|  \- io.zeebe:zeebe-exporter-protobuf:jar:1.0.0:compile
|     \- com.google.protobuf:protobuf-java:jar:3.15.6:compile

I need to release a new version of zeebe-exporter-protobuf and zeebe-hazelcast-connector to fix the dependency issue.

@saig0
Copy link
Contributor

saig0 commented Jan 10, 2022

Fixed by #350 🚀

@saig0 saig0 closed this as completed Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants