We are using zeebe 8.5 and have upgraded maven dependency from zeebe-client-java
to spring-boot-starter-camunda-sdk
(8.5.0). Assuming this setup is correct, our application fails to configure new workers. The below code that worked earlier now fails with null pointer exception
zeebeClient.newWorker().jobType("http").handler(HTTPJobHandler).name(
"zeebehttpworker").maxJobsActive(maxJobsActive).streamEnabled(true).open();
The stacktrace indicates that the code is trying to set the default worker name which is turning out to be null
Caused by: java.lang.NullPointerException: null
at io.camunda.zeebe.gateway.protocol.GatewayOuterClass$StreamActivatedJobsRequest$Builder.setWorker(GatewayOuterClass.java:1026)
at io.camunda.zeebe.client.impl.command.StreamJobsCommandImpl.workerName(StreamJobsCommandImpl.java:136)
at io.camunda.zeebe.client.impl.command.StreamJobsCommandImpl.<init>(StreamJobsCommandImpl.java:71)
at io.camunda.zeebe.client.impl.worker.JobClientImpl.newStreamJobsCommand(JobClientImpl.java:94)
at io.camunda.zeebe.client.impl.worker.JobStreamerImpl.buildCommand(JobStreamerImpl.java:157)
at io.camunda.zeebe.client.impl.worker.JobStreamerImpl.openStreamer(JobStreamerImpl.java:112)
at io.camunda.zeebe.client.impl.worker.JobWorkerImpl.openStream(JobWorkerImpl.java:115)
at io.camunda.zeebe.client.impl.worker.JobWorkerImpl.<init>(JobWorkerImpl.java:110)
at io.camunda.zeebe.client.impl.worker.JobWorkerBuilderImpl.open(JobWorkerBuilderImpl.java:211)
I tried setting the default worker name through this property camunda.client.zeebe.defaults.name="defaultWN"
in the application.properties file but it didn’t work.
Kindly share your inputs on the root cause and the fix for this.
Thanks