Custom Inbound Connector and Correlate throws Exception when set TenantId

Camunda 8 Topics
,
1

Hi folks!

I am getting the following exception when try to correlate

	at io.camunda.connector.runtime.core.inbound.correlation.InboundCorrelationHandler.triggerStartEvent(InboundCorrelationHandler.java:124)
	at io.camunda.connector.runtime.core.inbound.correlation.InboundCorrelationHandler.correlate(InboundCorrelationHandler.java:64)
	at io.camunda.connector.runtime.core.inbound.correlation.InboundCorrelationHandler.correlate(InboundCorrelationHandler.java:55)
	at io.camunda.connector.runtime.core.inbound.InboundConnectorContextImpl.correlate(InboundConnectorContextImpl.java:66)
	at bpmn.connector.handler.BrokerConnectorHandler.handle(BrokerConnectorHandler.java:38)
	at bpmn.connector.handler.BrokerConnectorHandler.handle(BrokerConnectorHandler.java:19)
	at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:277)
	at io.vertx.core.eventbus.impl.MessageConsumerImpl.dispatch(MessageConsumerImpl.java:177)
	at io.vertx.core.eventbus.impl.HandlerRegistration$InboundDeliveryContext.execute(HandlerRegistration.java:131)
	at io.vertx.core.eventbus.impl.DeliveryContextBase.next(DeliveryContextBase.java:80)
	at io.vertx.core.eventbus.impl.DeliveryContextBase.dispatch(DeliveryContextBase.java:43)
	at io.vertx.core.eventbus.impl.HandlerRegistration.dispatch(HandlerRegistration.java:98)
	at io.vertx.core.eventbus.impl.MessageConsumerImpl.deliver(MessageConsumerImpl.java:183)
	at io.vertx.core.eventbus.impl.MessageConsumerImpl.doReceive(MessageConsumerImpl.java:168)
	at io.vertx.core.eventbus.impl.HandlerRegistration.lambda$receive$0(HandlerRegistration.java:49)
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.NullPointerException
	at io.camunda.zeebe.gateway.protocol.GatewayOuterClass$CreateProcessInstanceRequest$Builder.setTenantId(GatewayOuterClass.java:9993)
	at io.camunda.zeebe.client.impl.command.CreateProcessInstanceCommandImpl.tenantId(CreateProcessInstanceCommandImpl.java:157)
	at io.camunda.zeebe.client.impl.command.CreateProcessInstanceCommandImpl.tenantId(CreateProcessInstanceCommandImpl.java:39)
	at io.camunda.connector.runtime.core.inbound.correlation.InboundCorrelationHandler.triggerStartEvent(InboundCorrelationHandler.java:111)

Scenario:

  • Custom inbound connector using Connector SDK 8.3.0
  • Runtime running with Quarkus 3.4.2 (base code to create the runtime is the connector-runtime-spring project from GitHub - camunda/connectors: Camunda Connectors)
  • Camunda Docker compose running localy

I just want to know how to setup the tenantId, to avoid this error. Its in ZeebeClient? Or i can setup some env variable in the container running Zeebe?

I see the property tenantId coming null in the InboundConnectorDefinition implementation. I need to create my own?

Thanks for any help!!!

2

Hi @hablocher ,

What is the version of Operate you use? If you wish to have multi-tenancy, you should use Operate version 8.3.0+

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.