Skip to content
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

Using MassTransit feature with concurrent processes #6336

Open
krivovs opened this issue Jan 25, 2025 · 0 comments
Open

Using MassTransit feature with concurrent processes #6336

krivovs opened this issue Jan 25, 2025 · 0 comments
Milestone

Comments

@krivovs
Copy link

krivovs commented Jan 25, 2025

Description

I couldn't find a way how to distinguish several instances of one process when it comes to receive message with MassTransit feature.
I have very simple process, which sends UpdateClient message and then waits for arriving ClientUpdated message.
If I start 2 processes at the same time, they all get completed when the first ClientUpdated message arrives.
Using CorrelateId is not working: screenshots shows 2 processes with different CorrelationID (77 and 78), ClientUpdated sent by process with CorrelationID = 77.
UpdateClient and ClientUpdated are activities, created by MassTransit feature from registered messages.

Expected Behavior

Upon receiving ClientUpdated message only one process should be completed. Which one - could depends on CorrelationID (or ClientId).

Screenshots

Image

Image

Image

Environment

  • Elsa Package Version: 3.3.1
  • Operating System: Windows 11
@sfmskywalker sfmskywalker moved this to Triage in ELSA 3 Jan 27, 2025
@sfmskywalker sfmskywalker added this to the Elsa 3.4 milestone Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Triage
Development

No branches or pull requests

2 participants