-
Notifications
You must be signed in to change notification settings - Fork 38.4k
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
Only one connection receive subscriber allowed #26699
Comments
I believe this is a result of an attempt to read the body while wrapping an exception concurrently with a cancellation from a closed server response. I'll have look to see if we can do something better and avoid this. |
Any updates on this issue, if its a spring issue or a usage issue? |
Hi, any update on this? @rstoyanchev |
I have this issue too - any updates @rstoyanchev ? Would be good to know if a) it can be safely ignored or b) a workaround. Thanks |
Hi, stack trace here @rstoyanchev
|
Hey guys, having the same problem here using |
We are also experiencing this issue. Is there a workaround? |
I am encountering this issue as well. Any update please? Good day! |
Hi, guys, don't forget to vote with a thumbs up if you still have this issue |
Hello team, I am encountering this even 2 years after the original post. I am using the latest 3.2.0-M2 and able to reproduce it consistently.
I have some more debug logs enabled, but do not know what can be usefull. May I ask what is the root cause of this technical issue, and how to solve this please? Thank you |
Any update on this? I am experiencing this issue in spring boot 2.5.8, spring 5.3.14 |
Any updates in 2024? thank you |
Hello, any updates on this issue? I also seem to have this error with |
Hi guys the same issue was occured. Any updates? Thanks |
Hi, Have we found anything about this? I am also encountering the same issue. |
originally opened spring-cloud/spring-cloud-sleuth#1854 however it can reproduced without Spring Cloud Sleuth. Below you can find the original description by @violetagg
Describe the bug
The exception below is observed when using
spring-cloud-sleuth
the double subscription happens with
onError
:and
onNext
The issue
Only one connection receive subscriber allowed.
is reported as part of the memory leak issue reactor/reactor-netty#1513. However this exception is not related to the memory leak issue.Sample
In the example https://github.com/shj95/webflux-leak-test that is provided with reactor/reactor-netty#1513, add a dependency
implementation 'org.springframework.cloud:spring-cloud-starter-sleuth:3.0.1'
, then use the providedjmeter
script to reproduce it.The text was updated successfully, but these errors were encountered: