-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Event catching error for intermediate event in spring boot #3363
Comments
As described, multiple channels for springboot is not working as expected. We need to generate different receivers. Working on it |
@fjtirado Thanks for fixing the issue , may i know when would it be available and in which version of kogito/dependency ? |
Tomorrow, you can try updating snapshot, make sure that in your example you are using 999-SNAPSHOT as kogito version |
* [Fix_#3363] Allowing multiple topic for kafka listener * [Fix_#3663] Manual ack and not thread blocking approach
Hi @fjtirado , I was trying to add 999-SNAPSHOT version a for Kogito but was getting straightaway erros in compilation. Did you mean below version or add-on dependency version? Could you please explain in detail, thanks in advance. Adding pom file :
|
All of them |
Ok, probably this is related with the repository you are using, make sure that in your pom.xml you have
|
This worked, thanks a lot @fjtirado. In which Kogito version can we expect this feature to be released in ? |
@sandeepchaudhary1093 |
Describe the bug
Ref: https://blog.kie.org/2021/09/kogito-process-eventing-add-ons.html#comment-357
Regarding : kogito-process-eventing-add-ons
Issue on build tool : spring boot
issue: There is an issue in SpringBoot receiver class, which only listen for topics on default channel and ignore any other one.
For catching intermediate event in workflow with spring boot, i had provided below properties
kogito.addon.cloudevents.kafka.kogito_incoming_stream=start
kogito.addon.cloudevents.kafka.kogito_incoming_stream.intermediate=intermediate
kogito.addon.cloudevents.kafka.kogito_outgoing_stream=end
now after starting the workflow with “start” topic message, when i send a message to “intermediate” topic with the process instance id and type=”intermediate”, the workflow doesn’t recognise it.
However if I send the same message to “start” topic with process inst id and type=”intermediate” then the message gets caught and the workflow continues.
So only incoming and outgoing properties are recognised not the node specific(intermediate).
Expected behavior
For :
kogito.addon.cloudevents.kafka.kogito_incoming_stream=start
kogito.addon.cloudevents.kafka.kogito_incoming_stream.intermediate=intermediate
Event sent to "intermediate" topic with process instance id should be caught by workflow and workflow should progress.
Actual behavior
Only while sending event to "start" topic with "type": "intermediate" and process inst id works.
Events sent to "intermediate" topic are not recognised by workflow.
How to Reproduce?
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: