Bug #74223 [Fbk->NoF]: db2 table locks during commit after hitting max_execution_time

Edit report at https://bugs.php.net/bug.php?id=74223&edit=1 ID: 74223 Updated by: php-bugs@lists.php.net Reported by: giacomo dot fontanella at carige dot it Summary: db2 table locks during commit after hitting max_execution_time -Status: Feedback +Status: No Feedback Type: Bug Package: ODBC related Operating System: windows server 2008 R2 PHP Version: 5.6.30 Assigned To: cmb Private report: N New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Re-Opened". Thank you. Previous Comments: ------------------------------------------------------------------------ [2020-09-29 15:17:46] cmb@php.net Can anyone still reproduce this problem with any of the actively supported PHP versions[1]? [1] <https://www.php.net/supported-versions.php> ------------------------------------------------------------------------ [2018-01-05 13:05:32] nikic@php.net I'd also be interested in knowing if this issue still reproduces on PHP 7.1. I have no familiarity with ODBC or DB2, but depending on the specific reasons of why this happens, the timeout handling changes in PHP 7.1 may have fixed this already. Timeouts will no longer interrupt internal function calls -- either it will wait until the call is finished, or it will kill the process entirely. ------------------------------------------------------------------------ [2018-01-05 13:00:28] spam2 at rhsoft dot net > with different versions of PHP from 5.3 to 5.6 but in Linux server what about try and report back with some *supported* version of PHP (7.1.x/7.2.x) especially for a niche like db2 stuff not that widely used combined with PHP ------------------------------------------------------------------------ [2018-01-05 12:53:57] j_a_v_i at hotmail dot com Same problem here. We have been facing this issue during years with different versions of PHP from 5.3 to 5.6 but in Linux server. The only solution we found is killing the server each time it happens and to create scripts to kill process when they detect that happening. Any chance this be solved? ------------------------------------------------------------------------ [2017-03-08 10:14:41] spam2 at rhsoft dot net > PHP: 5.6.30 > Seems similar to bug #63576, reported for php 5.3.16 PHP 5.6 is as you should know EOL and won't get any updates except high critial security patches ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=74223 -- Edit this bug report at https://bugs.php.net/bug.php?id=74223&edit=1