Simple Monitor error on publishing the message

Camunda 8 Topics Discussion & Questions
1

Hi Team,

I got error while i was pulishing the message.

zeebe version : camunda/zeebe:0.23.1
monitor version : camunda/zeebe-simple-monitor:0.18.0
OS: windows

Please find the below log.

zeebe_monitor | 2020-08-09 17:40:41.756 ERROR 1 — [pool-1-thread-1] o.h.engine.jdbc.spi.SqlExceptionHelper : Value too long for column “PAYLOAD_ VARCHAR(255)”: "STRINGDECODE('fields {\n key: ““womId””\n value {\n string_value: ““02"”\n }\n}\nfields {\n key: ““userMail””\n value {… (291)”; SQL statement:
zeebe_monitor | insert into message (correlation_key_, message_id_, name_, payload_, state_, timestamp_, key_) values (?, ?, ?, ?, ?, ?, ?) [22001-200]
zeebe_broker | 2020-08-09 17:44:41.883 [Broker-0-SnapshotDirector-1] [Broker-0-zb-fs-workers-0] INFO io.zeebe.logstreams.snapshot - Finished taking snapshot, need to wait until last written event position 21475137216 is committed, current commit position is 21475137216. After that snapshot can be marked as valid.
zeebe_broker | 2020-08-09 17:44:41.884 [Broker-0-SnapshotDirector-1] [Broker-0-zb-fs-workers-0] INFO io.zeebe.logstreams.snapshot - Current commit position 21475137216 is greater then 21475137216, snapshot is valid.

2

Hi @Tauqeer,

this bug is already fixed (https://github.com/zeebe-io/zeebe-simple-monitor/issues/138).

Please use the latest version of the simple monitor 0.19.0.

Best regards,
Philipp

3

Hi @philipp.ossler,

Thank you so much, i will try the simple monitor 0.19.0

4

Hi @philipp.ossler,

After updating zeebe-docker-compopse, im getting error in my spring zeebe worker.

Zeebe Details

camunda/zeebe:0.24.1
camunda/zeebe-simple-monitor:0.19.0

Error Log

10-08-2020 22:35:57.880 [grpc-default-executor-43] WARN io.zeebe.client.job.poller.onError - Failed to activated jobs for worker WOM-Worker and job type solution-design-escalation-process
io.grpc.StatusRuntimeException: UNKNOWN
at io.grpc.Status.asRuntimeException(Status.java:533)
at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:449)
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:426)
at io.grpc.internal.ClientCallImpl.access$500(ClientCallImpl.java:66)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:689)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$900(ClientCallImpl.java:577)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:751)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:740)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

5

Hi @Tauqeer,

this warning doesn’t seem related to the simple monitor application. It says that something went wrong while activating jobs for the job worker.

If you see any negative effect then please open a new thread.

6