Hanging on close EventStream about azeventhubs HOT 5 CLOSED

Totally understand, I wasn't able to distill a repro so I am sorry about that! This isn't actionable so I am going to go ahead and close this. Especially since simply dropping the connection seems to suffice for me.

from azeventhubs.

Interesting. Let me see if i can recreate this behavior.

from azeventhubs.

My initial guess is that there's something wrong with my state machine implementation. A temporary workaround would be just drop the EventStream. This will still perform the graceful shutdown but just in a non-async manner

from azeventhubs.

Thanks! That's a great work around

from azeventhubs.

Hi @jackgerrits I tried to recreate the bug but haven't been able to. I have added a new example (https://github.com/minghuaw/azeventhubs/blob/main/examples/spawn_multiple_consumer.rs) which essentially does the same thing with the exception that there are 3 partitions instead of 4 (this is simply because of how my test eventhubs instance is set up).

This example has been working fine so far on both my local machine (mac) and my testing Azure VM instance. The underlying AMQP implementation may log an error that says IllegalConnectionState (this would only appear in logs but won't return an error), but this is usually caused by the server side closing the underlying TCP connection before the client side completes the handshake, and this should not lead to client hanging.

from azeventhubs.