mirror of
https://github.com/xcat2/confluent.git
synced 2026-09-05 04:27:56 +00:00
Markus Hilger
bda403766e
Activation started an event thread whichever way the base handler had just answered, so a refusal started one anyway and an already active console got a second. activated alone cannot tell the two refusals apart, being true already on the already active path, so the value from before the call decides. Deactivation joined that thread on the event loop, where it could stall every other session and its own response. The wait moves off the loop and is bounded, and the thread is a daemon.