Edit report at https://bugs.php.net/bug.php?id=81029&edit=1
ID: 81029
Comment by: schamberumarcelo at gmail dot com
Reported by: kdonaldson at staff dot nexigen dot digital
Summary: SOAP HTTP socket not closing on object destruction
Status: Open
Type: Bug
Package: SOAP related
Operating System: macOS and Cent OS 7
PHP Version: 7.4.19
Block user comment: N
Private report: N
New Comment:
This closes the socket, but the web services engine does not recognize this as being closed and
tries to reuse it, resulting in exceptions. The requests module leaves a connection open until it is
garbage. when the response object is dropped, the file would be closed.
(https://www.myccpay.me)github.com
Previous Comments:
------------------------------------------------------------------------
[2022-12-21 08:54:06] jbriss at ebridge dot sk
The problem seems to be discussed here too:
https://github.com/googleads/googleads-php-lib/commit/17bf38ce7ba0a994f317ea78df40539f89a89789
------------------------------------------------------------------------
[2022-12-15 11:06:40] johnsonsellen at gmail dot com
That was unpredicted.
(https://dolgeneraldgme.com/)github.com
------------------------------------------------------------------------
[2022-12-08 06:00:00] kimia dot salamsao9881 at gmail dot com
That was unexpected.
(https://www.mynordstrom.ltd/)github.com
------------------------------------------------------------------------
[2021-05-17 14:43:09] nikic@php.net
@cmb: As it's stored in a property, shouldn't that happen automatically when the object
(and thus also its properties) are destroyed?
------------------------------------------------------------------------
[2021-05-11 11:27:24] cmb@php.net
It seems to me we're missing to undo the refcount increment[1]
when the object is destroyed.
[1] <https://github.com/php/php-src/blob/php-7.4.19/ext/soap/php_http.c#L523>
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=81029
--
Edit this bug report at https://bugs.php.net/bug.php?id=81029&edit=1