|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #494 Interaction between persistent connections and timeouts
Submitted: 1998-06-30 01:49 UTC Modified: 1998-09-21 03:46 UTC
From: cclarke at inconceivable dot com Assigned:
Status: Closed Package: ODBC related
PHP Version: 3.0 Final Release OS: Solaris
Private report: No CVE-ID: None
 [1998-06-30 01:49 UTC] cclarke at inconceivable dot com
(This is really generic to any database interface that supports
persistent connections)
I have some development scripts that I use to initialize a reasonably
large database.  Depending on the runtime platform and load, some of these
scripts may or may not complete in the 30 second (default) timeout.
The scripts are built for that, so I generally just hit Reload.

When I moved to Persistent Connections, and ran one of these scripts on
a slow machine, I found that the Reload generates database

Thinking about this a minute I realized that because the connection
is persistent, the transaction from the timed-out execution is still
open in the database and is holding database locks.

One could easily argue that the bug is writing a script that cannot
live within the tunable timeout, but I thought I'd report it since the result
is a state that can only really be resolved by stopping the web server.

Would it be an appropriate mod to close any/all persistent connections
in the event of an execution timeout?


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [1998-09-21 03:46 UTC] kara
Statement execution is implemented as blocking function call.
I don't know if it is possible at all to interrupt this.
How about execution timeouts for statements? 
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Sat Jan 25 23:01:24 2020 UTC