You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just to make sure that we're on the same page, could you please clarify exactly what your question is or what behaviour you're expecting?
Are you surprised that any error message is triggered, or that you're seeing multiple error messages? If the latter - how many times are you running the test in your REPL?
Both. So I am surprised that I get an error message at all, since closing the listener seems like a legitimate usecase. I guess it's not that hard to filter that out in the handler.
But the other thing is just confusing. I am running a single test and I get either 1 or 12 errors. I don't understand the mechanism behind that.
To be more specific, running the test code I pasted above in a fresh JVM usually produces 1 conn-closed error, but sometimes it produces 12 conn-closed errors. That's a single run in freshly started JVM. I am just trying to make sure I am not missing something here.
I'm running this code here:
So this posts a message and closes listener and it awaits for the message to get back from redis.
First thing is that this always produces an error message to the listener:
But if I run this test in REPL a couple of times in a row I get runs that look like this:
It instantly calls the listener handler fn with 11 instances of same error message.
The text was updated successfully, but these errors were encountered: