#18347 [Csd->Bgs]: ibase_pconnect() spawn connections to InterBase

ID: 18347 Updated by: abies@php.net Reported By: michael at mediacom dot ru -Status: Closed +Status: Bogus Bug Type: InterBase related Operating System: nt4 sp6a PHP Version: 4.2.1 Previous Comments: ------------------------------------------------------------------------ [2002-07-16 02:04:03] michael at mediacom dot ru Yes! You almost right. I have looked in httpd.conf and understood that reason in settings of KeepAlive (KeepAliveTimeout & ThreadsPerChild) of my Apache server. Thank for support. ------------------------------------------------------------------------ [2002-07-15 20:23:10] sniper@php.net The persistent connection does not mean that you have ONE single connection to the database, but you have one connection from each httpd child. Are you sure this is not what is happening? ie. if the child you hit does not have the connection established yet, it will be created. ------------------------------------------------------------------------ [2002-07-15 08:15:44] michael at mediacom dot ru Settings for interbase in php.ini? Noting. I didn't found description for those in PHP Manual. Interbase is not closing connection - thay are not closing. PHP spawned new connections in ibase_pconnect() function, when there are available persistent connections. ------------------------------------------------------------------------ [2002-07-15 06:27:22] sniper@php.net What settings you have for interbase in php.ini? Are you sure it's not interbase closing the connection? Check it's settings too.. ------------------------------------------------------------------------ [2002-07-15 04:43:13] michael at mediacom dot ru My script calls ibase_pconnect("127.0.0.1:/Database/test.gdb", "SYSDBA", "masterkey"). I expected that php reuse persistent connection to InterBase. But if time from last script executing is over 15 seconds - php spawn new InterBase connection. ------------------------------------------------------------------------ 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/18347 -- Edit this bug report at http://bugs.php.net/?id=18347&edit=1