Describe the bug
Programs that use Event Hubs do not exit when disposing the producer or consumer.
Exception or Stack Trace
Program hangs instead of exiting
To Reproduce
Steps to reproduce the behavior:
See code at -- https://github.com/danieljurek/azure-sdk-for-java/blob/smoke-test-jan2020/eng/smoke-tests/src/main/java/com/azure/EventHubs.java
Code Snippet
See code at: https://github.com/danieljurek/azure-sdk-for-java/blob/smoke-test-jan2020/eng/smoke-tests/src/main/java/com/azure/EventHubs.java
Expected behavior
The program exits when producers and consumers are disposed and the reactor doesn't keep the program open.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):
- OS: Windows
- IDE : vscode
- Version of the Library used: 5.0.0-beta.6
Additional context
This issue was discovered using the Smoke Tests. Smoke Tests simulate real world usage of packages (no source dependency or direct dependency on our engineering systems).
@conniey started investigating this and it looks like the scheduler is not being closed properly in this version.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
Describe the bug
Programs that use Event Hubs do not exit when disposing the producer or consumer.
Exception or Stack Trace
Program hangs instead of exiting
To Reproduce
Steps to reproduce the behavior:
See code at -- https://github.com/danieljurek/azure-sdk-for-java/blob/smoke-test-jan2020/eng/smoke-tests/src/main/java/com/azure/EventHubs.java
Code Snippet
See code at: https://github.com/danieljurek/azure-sdk-for-java/blob/smoke-test-jan2020/eng/smoke-tests/src/main/java/com/azure/EventHubs.java
Expected behavior
The program exits when producers and consumers are disposed and the reactor doesn't keep the program open.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):
Additional context
This issue was discovered using the Smoke Tests. Smoke Tests simulate real world usage of packages (no source dependency or direct dependency on our engineering systems).
@conniey started investigating this and it looks like the scheduler is not being closed properly in this version.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report