Closed Tinche closed 8 years ago
@Tinche - could you please comment out the call to shutdown
within the Python client code in your environment to see if that resolves the issue? The BadResource
exception should cause the operation to re-try.
Will do, I'll play around with it.
Thank you, I appreciate it. I'm going to try and reproduce here as well.
I've left work for the day, but something just occurred to me worth mentioning: I've been testing out this code all morning on our Linux servers without this issue popping up, but when I started the application in question locally on my work Mac it manifested very quickly. Maybe it's a platform-specific thing?
It could be. I'm planning on addressing it by catching EnvironmentError
and logging it.
Commenting out the shutdown removes the exceptions on my OS X workstation. I'll try catching EnvironmentError instead and see what happens.
Hi,
I'm the original author of #399. I'm trying out the newest version (2.5.1) to see if we can drop our internal workaround. When the issue from #399 occurs, the client will leak an exception to the surrounding code:
I'm guessing it's an error to shutdown a socket in this state (half-closed). In any case, the expectation is for these errors to not propagate, but to be handled by the pools transparently.