ID: 20298 User updated by: phpbug at tab1 dot clara dot co dot uk Reported By: phpbug at tab1 dot clara dot co dot uk -Status: Feedback +Status: Open Bug Type: ODBC related Operating System: Windows 2000 Server SP4 -PHP Version: 4.3.2 +PHP Version: 4.3.3RC4-dev New Comment:
The same problem is still present in that snapshot, tested both FastCGI and ISAPI. Warning: odbc_exec(): SQL error: [Informix][Informix ODBC Driver]Communication link failure., SQL state 08S01 in SQLExecDirect in C:\InetPub\wwwroot\test.php on line 5 Warning: odbc_fetch_row(): supplied argument is not a valid ODBC result resource in C:\InetPub\wwwroot\test.php on line 7 Previous Comments: ------------------------------------------------------------------------ [2003-08-15 08:18:28] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip ------------------------------------------------------------------------ [2003-07-18 06:28:51] phpbug at tab1 dot clara dot co dot uk Yes the problem still exists in PHP 4.3.2. I discovered FastCGI mode the other day and the same problem is exists running PHP like that. ------------------------------------------------------------------------ [2003-02-20 04:58:12] t_o_m_ at yahoo dot com Having reread all of this I see that nowhere have I mentioned I'm using IIS (ISAPI) not Apache, if that makes a difference? I thought when I put Windows in the OS box whoever read it would assume IIS. In answer to your question "no", the behaviour is the same if odbc.check_persistent is on or off. The point is when it is off I would expect it to be my responsibility to check the connection and would expect the error if I did not. I would expect that when odbc.check_persistent was on odbc_pconnect was supposed to check the connection for me if the connection it is about to return from its pool is dead then it should discard it and create a new one as when the pool is empty. Which is clearly not happening. ------------------------------------------------------------------------ [2003-02-18 12:01:03] [EMAIL PROTECTED] Well the nature of CGI doesn't really lend itself to supporting persistant connections. It's run when requested and then exited after that. So no data can really presist between pages that exists solely in the CGI. So this behavior only exists when odbc.check_persistent is turned on? ------------------------------------------------------------------------ [2003-02-17 10:08:22] t_o_m_ at yahoo dot com Yes still a problem under 4.3.0 I am using the ISAPI module. I don't believe that persistent connections are supported at all under CGI. So odbc_pconnect == odbc_connect which would give the illusion of working, although the connection would not actually be persisting. The first time you reload the page after killing the database connection you get: Warning: SQL error: No response from the backend; Subsequent reloads give: Warning: SQL error: Could not send Query(connection dead); ------------------------------------------------------------------------ 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/20298 -- Edit this bug report at http://bugs.php.net/?id=20298&edit=1
