[PHP-DEV] Bug #10597 Updated: RE #5684: PHP Intermittently reports Unable to allocate connection record
ID: 10597 Updated by: lobbin Reported By: [EMAIL PROTECTED] Old Status: Feedback Status: Closed Bug Type: Sybase-ct (ctlib) related Operating System: RedHat 6.2 PHP Version: 4.0.5 New Comment: No feedback. Closing. Previous Comments: [2001-12-18 13:36:16] [EMAIL PROTECTED] Does this still happen with PHP 4.1.0? R. [2001-05-02 02:40:02] [EMAIL PROTECTED] RE #5684, You asked for any other cases: I get this error when I use a custom error handler to catch sybase errors. For example, if I try to delete a record with children in other tables, it raises a FK constraint violation error...everything normal. But after that error, where I try to do database reads and writes in my error handler function, I get really wierd problems. The main problem is that ctlib start reporting level 10 errors, instead of level 11, eg: DB ERROR: Changed database context to 'xxx'. After this, I get cannot allocate connection record. This only happens after I catch the error. If I turn off my error handling function, everything is fine. This says to me that the ctlib (or PHP) can't carry on after an error. But then I know little about either :) Edit this bug report at http://bugs.php.net/?id=10597edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
[PHP-DEV] Bug #10597 Updated: RE #5684: PHP Intermittently reports Unable to allocate connection record
ID: 10597 Updated by: lobbin Reported By: [EMAIL PROTECTED] Old Status: Open Status: Feedback Bug Type: Sybase-ct (ctlib) related Operating System: RedHat 6.2 PHP Version: 4.0.5 New Comment: Does this still happen with PHP 4.1.0? R. Previous Comments: [2001-05-02 02:40:02] [EMAIL PROTECTED] RE #5684, You asked for any other cases: I get this error when I use a custom error handler to catch sybase errors. For example, if I try to delete a record with children in other tables, it raises a FK constraint violation error...everything normal. But after that error, where I try to do database reads and writes in my error handler function, I get really wierd problems. The main problem is that ctlib start reporting level 10 errors, instead of level 11, eg: DB ERROR: Changed database context to 'xxx'. After this, I get cannot allocate connection record. This only happens after I catch the error. If I turn off my error handling function, everything is fine. This says to me that the ctlib (or PHP) can't carry on after an error. But then I know little about either :) Edit this bug report at http://bugs.php.net/?id=10597edit=1 -- PHP Development Mailing List http://www.php.net/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
