ID: 3910
Comment by: david dot gaia dot kano at dartmouth dot edu
Reported By: guage at usa dot net
Status: Closed
Bug Type: Oracle related
Operating System: Linux - Redhat 6.1
PHP Version: 4.0.01pl2
New Comment:
This is happening on our server using PHP 4.3.4
Should this be reopened?
Previous Comments:
------------------------------------------------------------------------
[2003-08-08 04:46:26] [EMAIL PROTECTED]
wrong version -> bug got lost, but is propably fixed in later versions
of PHP anyway.
------------------------------------------------------------------------
[2000-08-21 12:26:06] guage at usa dot net
OciLogoff seems to do something now but does not clear a connection
that has been killed on the oracle server (at least when ociplogon is
used). The only way to recover from this situation is to restart the
httpd server. I have tried to create a new connection via ociplogon
but it continues to try to use the old connection which was killed.
OCIPlogon returns a success but ociexecute returns an error.
connecting to oracle Connected successfully
^- does a ociplogon
Warning: OCIStmtExecute: ORA-00028: your session has been killed in
orabugtest.php on line 12
^--- this is from a ociexecute
killing session !!!!! <--- this does a ocilogoff
Warning: failed to rollback outstanding transactions!: ORA-01012: not
logged on in
orabugtest.php on line 16
Warning: OCIFetchStatement: OCI_INVALID_HANDLE in
orabugtest.php on line 18
------------------------------------------------------------------------
[2000-08-21 12:19:48] guage at usa dot net
Bug still exists. I have verified for php 4.0.1pl2
Thanks...
------------------------------------------------------------------------
[2000-08-20 01:54:04] [EMAIL PROTECTED]
No feedback from user.
--Jani
------------------------------------------------------------------------
[2000-08-01 23:30:25] [EMAIL PROTECTED]
Please verify that it�s still happening using the latest version of PHP
(release 4.0.1pl2 or CVS).
------------------------------------------------------------------------
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/3910
--
Edit this bug report at http://bugs.php.net/?id=3910&edit=1
