ID: 19529
Comment by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Assigned
Bug Type: MySQL related
Operating System: Linux 2.4.18
PHP Version: 4.2.3
Assigned To: georg
New Comment:
i did't get any error with
apache1.3.26
mod php compiled with mysql4.0.2 client lib
connect to mysql4.0.4
but once i rebuild php, with mysql4.0.4 client lib, get the same error
as u
unnable to do mysql_select_db, and unnable to connect from remote,
event use connect do not help(not sure)
hope this info help u guys
Previous Comments:
------------------------------------------------------------------------
[2002-10-24 20:53:27] [EMAIL PROTECTED]
Workarounds:
A) Don't use persistent connections.
B) If you must, you need to edit PHP source,
ext/mysql/php_mysql.c (I think). Look for a callback
function that has ROLLBACK in it. Either disable the
callback or comment out all the lines in it.
PHP 4.3.0 should do (B) over what is in 4.2.1. Better to
still not have transactional garantee than to break all
sites and then still not have transactional garantee.
My $0.02.
------------------------------------------------------------------------
[2002-10-24 02:33:52] [EMAIL PROTECTED]
Upgraded to PHP 4.2.3, using EZ Portal Content Server.
Linux 2.2.15
MySQL client 3.22.32
Apache 1.3.26
Was working before upgrade to PHP 4.2.3, now getting 30%
command sync errors, this is not a heavily loaded site,
just in dev stage.
I have stopped httpd, mysql, and restarted, and problem is
exhibited straight away.
Thus doubtful load or time related.
Turned off persistant connections, problem went away.
Fix soon?
------------------------------------------------------------------------
[2002-10-24 00:38:43] [EMAIL PROTECTED]
A forum I'm helping with also ran into this problem (the site runs
vbulletin). I'm trying to track down exactly when it started
happening. I can say that with apache 1.3.26 and php 4.2.1 and mysql
4.23.49, it didn't happen, nor with apache2.0.43+php4.2.3+mysql4.23.49.
It definately does happen with apache 1.3.27+php4.2.3+mysql4.23.53,
leading me to believe that it's an issue with something that changed in
mysql since last spring, but unless I misread, that contradicts some
other reports here. Disabling vbulletin's persistent connection usage
eliminated the errors, of which there were tons.
------------------------------------------------------------------------
[2002-10-10 19:21:14] [EMAIL PROTECTED]
Interesting stuff. I am heading out on the road for about
a month. I will follow up with this as soon as I get
stable network access again.
------------------------------------------------------------------------
[2002-10-10 15:03:07] [EMAIL PROTECTED]
reassigning
------------------------------------------------------------------------
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
http://bugs.php.net/19529
--
Edit this bug report at http://bugs.php.net/?id=19529&edit=1
