Skip to content

fix: quick fix handling invoke message #47

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

Merged
merged 2 commits into from
May 3, 2024

Conversation

dorotaphanSiili
Copy link
Collaborator

@dorotaphanSiili dorotaphanSiili commented Apr 25, 2024

adds thread safety.
With a lot of threads, the id was generated in not thread safe manner the id generation was moved under the mutex - it is the only place where it is generated. This way it is unique now.

Closes apigear-io/performance-checks#24 for cpp

📑 Description

✅ Checks

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • All the tests have passed

ℹ Additional Information

adds thread safety.
With a lot of threads, the id was generated in not thread safe manner
the id generation was moved under the mutex - it is the only place where
it is generated. This way it is unique now.
@dorotaphanSiili dorotaphanSiili changed the title fix: quick handling invoke message fix: quick fix handling invoke message Apr 26, 2024
@dorotaphanSiili dorotaphanSiili force-pushed the dphan/thread-safety-invoke-message branch 4 times, most recently from 6a6fffb to 8e902e0 Compare April 26, 2024 13:16
the unsigned type suites better the request id type, id should not be
negative.
Fixes the overflow issue, as unsigned int behavior is defined.
@dorotaphanSiili dorotaphanSiili merged commit 127325c into main May 3, 2024
3 checks passed
@dorotaphanSiili dorotaphanSiili deleted the dphan/thread-safety-invoke-message branch May 3, 2024 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEAT]: method invocation test with high load
2 participants