Thanks to visit codestin.com
Credit goes to news-web.php.net

Doc #64549 [Com]: mysqlnd persistent connection handling are not properly pooling

From: Date: Wed, 22 May 2024 05:25:18 +0000
Subject: Doc #64549 [Com]: mysqlnd persistent connection handling are not properly pooling
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to [email protected] to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=64549&edit=1

 ID:                 64549
 Comment by:         sonia0992alvarez at outlook dot com
 Reported by:        rgagnon24 at gmail dot com
 Summary:            mysqlnd persistent connection handling are not
                     properly pooling
 Status:             Verified
 Type:               Documentation Problem
 Package:            PDO MySQL
 Operating System:   CentOS 5.9
 PHP Version:        5.3.23
 Block user comment: N
 Private report:     N

 New Comment:

Hello @rgagnon24 at gmail dot com (https://github.com)(https://www-costcoess.com)

Certainly! When encountering a bug, it’s essential to provide relevant information to help the
development team identify and address the issue. Here are some steps you can take:

Detailed Bug Report:
If you encounter a bug, create a detailed bug report. Include information such as:
Steps to reproduce the issue.
Expected behavior.
Actual behavior (what went wrong).
Any error messages or logs.
The platform or environment where you encountered the bug (e.g., operating system, browser, etc.).
Simpler Test Case:
Simplify the test case as much as possible. Remove any unnecessary complexity to isolate the issue.
If you can reproduce the bug with a minimal example, it will be easier for others to understand and
fix.
Cross-Platform Testing:
Test the bug on different platforms (e.g., different operating systems, browsers, devices).
Sometimes bugs are specific to certain environments, so cross-platform testing helps identify such
cases.
Avoid Cluttering the Database:
Instead of just saying “Me too!” in the bug report, focus on providing additional
information.
Upvote the bug if it affects you, but avoid adding noise to the discussion.


Previous Comments:
------------------------------------------------------------------------
[2021-06-21 13:29:20] rgagnon24 at gmail dot com

Ok, so that sort of makes sense that there is a connection pool per worker in apache, but the bug
noted in the comment from "[2013-04-02 16:47 UTC]" still exists that emits an error about
the connection being dead even though one is returned after being reconnected.

------------------------------------------------------------------------
[2021-06-21 09:34:38] [email protected]

Indeed, the persistent connections and the stats are stored
separately for each worker process (or thread), so in a typical
scenario with multiple workers, pooling may not work as expected.
The respective documentation[1] should clarify that; the note
about ODBC connection pooling already hints at this, but is not
general enough.

[1] <https://www.php.net/manual/en/pdo.connections.php>

------------------------------------------------------------------------
[2021-06-20 08:30:25] wf3f2g dot wf2f3f at egrg dot dd

maybe you don't understand that each worker process has it's own persistent connection and
that every client connection to the Webserver may be handled by a different worker

so in the reality you have sooner or later the number of max worker processes mysql connections and
hence the concept of persistent database connections is idiotic

------------------------------------------------------------------------
[2021-06-20 06:07:36] rgagnon24 at gmail dot com

Changing Summary

------------------------------------------------------------------------
[2021-06-20 06:06:34] rgagnon24 at gmail dot com

Why is it I received an email that said I could re-open the case if the problem still exists, yet
when I do (which the correct password), it says "you are not allowed to change a ticket to that
state" (or something like that

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


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=64549


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


Thread (3 messages)

« previous php.doc.bugs (#19716) next »