Too many open files issues #705
Labels
Comments
|
Could you please provide more info? (Like the wsdl?) |
|
any update on this ? |
CharString
added a commit
to CharString/python-zeep
that referenced
this issue
Sep 15, 2023
I bumped into this when opening several wsdl which in turn opened lots of xsd, with 'file://' scheme. The issue was that the `resp.raw.close` nor `resp.raw.release_conn` set in the `FileAdapter` were ever called. It's unclear to me whether this should be fixed in requests. It doesn't do that great a job at resource management for the naive user aka Human™. It makes sense to me that exhaustively reading `Response.raw` should close it unless the caller explicitly set `stream` on the request. Probably by using this `closing` pattern in the generator in `Response.iter_content`. Workarounds without this fix: - using a scheme-less url as zeep will assume it's a local path and open the file as a context manager. - use one of the caches from `zeep.cache` to hide duplicate open resources.
Kuv
added a commit
to Kuv/python-zeep
that referenced
this issue
Apr 21, 2024
🐛[mvantellingen#705] Properly close 'file://' resources
|
I am running into this issue as well when I am load testing. It looks like any newly created sockets are never closed by the application. They sit in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm using zeep for accessing a SOAP service. However, for some reason it seems that there is an issue with zeep closing sockets or some temporary files as after some period of time I always get the same error:
Is there any workaround this?
The text was updated successfully, but these errors were encountered: