Replies: 1 comment
-
KAFKA.KOGITO.INCOMING-STREAM.TOPIC and KAFKA.KOGITO.OUTGOING-STREAM.TOPIC have the same value. So both point to the same topic |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I hope someone can help me.
I have two process
Log shows me the following message when the first process consumes event throws by the second process.
No matches found for trigger raccolta_dati in process cra_edit. Skipping consumed message CloudEventWrapDataEvent [cloudEvent=CloudEvent{id='c91d80dc-aaa9-43b4-83ae-dc6ce55f5424', source=/process/raccolta_dati, type='raccolta_dati', time=2024-01-30T17:56:57.096033500+01:00, data=JsonCloudEventData{node="string"}, extensions={kogitoproctype=BPMN, kogitoprocinstanceid=d48b1e4e-bc15-4ee7-8456-7b5a3adcc577, kogitoprocist=Active, kogitoprocversion=1.0, kogitoprocid=raccolta_dati}}]
For kafka i would use the same topic for all node events and my configuration is:
mp.messaging.incoming.kogito_incoming_stream.connector=${KOGITO.KAFKA.CONNECTOR}
mp.messaging.incoming.kogito_incoming_stream.topic=${KAFKA.KOGITO.INCOMING-STREAM.TOPIC}
mp.messaging.incoming.kogito_incoming_stream.value.deserializer=org.apache.kafka.common.serialization.StringDeserializer
mp.messaging.incoming.kogito_incoming_stream.auto.offset.reset=earliest
mp.messaging.incoming.kogito_incoming_stream.group.id=node-events-consumer
mp.messaging.outgoing.kogito_outgoing_stream.connector=${KOGITO.KAFKA.CONNECTOR}
mp.messaging.outgoing.kogito_outgoing_stream.topic=${KAFKA.KOGITO.OUTGOING-STREAM.TOPIC}
mp.messaging.outgoing.kogito_outgoing_stream.value.serializer=org.apache.kafka.common.serialization.StringSerializer
Maybe i need to set the correlations but I do not understand where insert this configuration.
Thanks
@cristianonicolai Please do you can help me?
Beta Was this translation helpful? Give feedback.
All reactions