-
Notifications
You must be signed in to change notification settings - Fork 321
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
reactor-kafka activation/deactivation is not consistent #3837
Labels
Comments
Managed to reproduce using the following code: Code
The problem seems to rather lie within our kafka instrumentation than reactor:
That code first deactives and then ends the kafka transaction. It seems to be invoked twice (deactivating again and ending again), which in turn causes the activation stack to be broken. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
See https://discuss.elastic.co/t/reactor-parallel-streams-causes-apm-log-spam-and-possibly-missed-spans/366890 - basically when used with parallel() there is an inconsistency
Steps to reproduce
See https://discuss.elastic.co/t/reactor-parallel-streams-causes-apm-log-spam-and-possibly-missed-spans/366890
Expected behavior
No related errors or warnings
Note that #3830 prevents the error stack trace, but the related warnings show the issue elsewhere
The text was updated successfully, but these errors were encountered: