On Tue, Feb 05, 2002 at 09:10:57PM -0500, George Schlossnagle wrote:
Isn't there handling for this in current cvs code? I remember
submitting a patch for this (and assoicated problems) to Thies, and it
being accepted.
there is - but there seem to be some error-codes missing.
From: [EMAIL PROTECTED]
Operating system: RedHat 6.2
PHP version: 4.0.6
PHP Bug Type: OCI8 related
Bug description: Persistent OCI8 Connections Get Poisoned
I have PHP 4.0.6 compiled as an Apache 1.3.20 module with OCI8 and MySQL on
RedHat 6.2. I use persistent connections
We are seeing this problem too. I am thinking of having a standard error
page which executes
posix_kill ( pos_getpid()) ;
On Oracle errors.
From: [EMAIL PROTECTED]
Operating system: RedHat 6.2
PHP version: 4.0.6
PHP Bug Type: OCI8 related
Bug description:
Good idea (for the situation anyway). It works. I have
all custom error handlers anyway, so when I detect a ORA-03313 error, I
kill the current process with a SIGTERM. Since I use header() to
redirect to the error page, sometimes I get a blank page, but atleast when
the database comes back, the
Isn't there handling for this in current cvs code? I remember submitting a patch for this (and assoicated problems) to Thies, and it being accepted.
George
On Tuesday, February 5, 2002, at 04:23 PM, Hans Zaunere wrote:
Good idea (for the situation anyway). It works. I have all custom error
