-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[BUG] Reactor IllegalStateException thrown when using StreamBridge with Spring Cloud Azure Stream Binder #35215
Comments
Closed by mistake, reopened it now. |
Thank you for the detailed issue, @itsmariodias! @conniey @Azure/azsdk-sb-java can you please take a look? |
@yiliuTo I was thinking something like this https://gist.github.com/anuchandy/9b46fb005e783f16fad38e04c1f7ed4a . I didn't test it but maybe useful as a reference or there exists a better way to do it. |
Is there any activity on this? The Additional Context provided should be useful in debugging and provide the correct fix for the same. |
Hi, this seems to still exist in v5.5.0, any timeline on when this would be fixed? @joshfree @anuchandy @conniey @yiliuTo |
@yiliuTo Please feel free to redirect this if you do not own the event hubs spring binder. |
This seems like the same issue as #31358. Is there a known workaround for this? |
Fixed, closing it now. |
Describe the bug
When using StreamBridge to publish messages to Azure Eventhubs in a reactive chain (.map, .flatMap, .doOnSuccess, etc.), an IllegalStateException is thrown by Reactor indicating that .block() call is used in the chain. The offending area is at line 106 in the com.azure.spring.messaging.eventhubs.core.EventHubsTemplate.doSend method.
Exception or Stack Trace
To Reproduce
Steps to reproduce the behavior:
Code Snippet
RestController.java
application.yaml
Expected behavior
The message should be published to eventhub without any errors.
Screenshots
N/A
Setup (please complete the following information):
Additional context
This seems to be identical to the #12500. When adding .publishOn(Schedulers.boundedElastic()) in the reactive chain before the streamBridge call the issue is resolved, however this ought to be done in the library itself.
Information Checklist
The text was updated successfully, but these errors were encountered: