Thanks, Christian! I tested the newest version, and the only issue is that
without a specific check for a socket_recv() result of 0, the infinite loop
will still happen on an unexpected socket closure. There won't be a socket
error, but the "buffer" property will be NULL, so the while loop in
Hi Tamara,
Thanks for introducing error handling in the PHP client in your pull
request. I took this as an opportunity to revise some more lines of
code.
The updated client raises an exception whenever something unexpected
happens in any of the socket function calls, and it returns the error
Follow up 6 months later: The same pattern happened again yesterday. The
error log blew up to 6 GB with the repeated PHP notice, and the production
server stopped responding.
This time I could see in the logs that what triggered the event was a heap
error, which caused BaseX to stop when it was
Hi Tamara,
Sorry for the late reply. It’s mainly because I have no definitive
solution on how to resolve the issue.
My knowledge of PHP is limited, but I assume that the socket_recv
function raises an error and returns false instead of the buffer size
[1,2]. You could try to check the return
4 matches
Mail list logo
