New Deployment functionality stopped working since the upgrade to zeebe 1.2.1

[mrsateeshp]

zeebe(zeebe-gateway-protocol-impl) 1.2.1 needs 3.18.0 version of com.google.protobuf:protobuf-java but zeebe-hazelcast-connector is brining in 3.15.6 which leads to runtime error when trying to use "New Deployment" functionality(error about GeneratedMessageV3.isStringEmpty method is not found).

i temporarily excluded protobuf-java from zeebe-hazelcast-connector locally to make simple monitor work:

io.zeebe.hazelcast
zeebe-hazelcast-connector
${hazelcast.exporter.version}


com.google.protobuf
protobuf-java

[saig0]

@mrsateeshp thank you for reporting 👍

Please share more details and how to reproduce the issue.

Which version of the simple monitor do you use?

[mrsateeshp]

The issue is not with the released version, but on master branch.

Steps to reproduce:

1. check-out master branch from github
2. build (mvn clean package)
3. run: java -jar target/zeebe-simple-monitor-2.1.1-SNAPSHOT.jar
4. access the portal in browser
5. try deploying a new workflow, will fail.

[saig0]

@mrsateeshp thank you for providing the data 👍 I can confirm the issue ✔️

[Benjoyo]

I am not sure if that is the same issue, but for me the "Processes" tab does not work (does not show anything). Instances are listed under "Instances" but clicking on a Process Definition Id gives
ResponseStatusException 404 NOT_FOUND "No process found with key

And in the instance view there is no process graphic, instead I get "There was no process definition nor BPMN diagram found for this instance."

This is with version 2.3.0 via docker.

[saig0]

@Benjoyo no. This is probably not releated.

There can be different reasons why the process is not imported. For example, the process was deployed before the simple monitor started, or the process record was not available in Hazelcast anymore (i.e. removed because of TTL or reaching the capacity of the ringbuffer).

[Benjoyo]

@saig0 Hm, both are not the case. I start simple monitor and afterwards deploy and start a (single) process. Instance shows up correctly, but not the deployment.

Created an issue: #424

[saig0]

I can't reproduce the issue anymore with version 2.4.0`. I assume that it is fixed (by dumping the dependencies). ✔️

Please reopen the issue if you are facing the problem again in a recent version.