Bug #74290 [Fbk->NoF]: [mysqlnd] Annoying "mysqli::close(): Couldn't fetch mysqli" warning

From: Date: Sun, 23 Apr 2017 04:22:50 +0000
Subject: Bug #74290 [Fbk->NoF]: [mysqlnd] Annoying "mysqli::close(): Couldn't fetch mysqli" warning
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-208722@lists.php.net to get a copy of this message 
Edit report at https://bugs.php.net/bug.php?id=74290&edit=1

 ID:               74290
 Updated by:       php-bugs@lists.php.net
 Reported by:      vedad at kajtaz dot net
 Summary:          [mysqlnd] Annoying "mysqli::close(): Couldn't fetch
                   mysqli" warning
-Status:           Feedback
+Status:           No Feedback
 Type:             Bug
 Package:          MySQLi related
 Operating System: FreeBSD 10.1
 PHP Version:      7.0.17
 Private report:   N

 New Comment:

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.


Previous Comments:
------------------------------------------------------------------------
[2017-04-12 12:51:21] vedad at kajtaz dot net

I'm not using a MySQL server, but a closed source MySQL proxy. I can provide a test access if
necessary?

------------------------------------------------------------------------
[2017-04-10 08:29:36] fjanisze@php.net

Can you provide some details on what server version you're using?

------------------------------------------------------------------------
[2017-03-22 13:22:49] vedad at kajtaz dot net

Description:
------------
The following warning is generated by mysqlnd on mysqli::close() call when the server, upon
receiving COM_QUIT, closes the connection instead of sending an OK_Packet:

PHP Warning:  mysqli::close(): Couldn't fetch mysqli in ...

According to the MySQL spec, simply closing the connection is perfectly valid:

https://dev.mysql.com/doc/internals/en/com-quit.html

    "response: either a connection close or a OK_Packet"

Therefore, I believe this warning should be removed, as it does not report any unexpected behavior.

One may overcome the issue using the @ operator, or disabling the error reporting for this specific
call, but both the warning itself and the workarounds are a waste of CPU resources IMHO.






------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=74290&edit=1

Thread (9 messages)

« previous php.bugs (#208722) next »