Bug #75171 [Opn]: Killing long running query breaks PHP connection to MSSQL database
| From: | ron at healthendeavors dot com | Date: | Fri, 08 Sep 2017 00:53:04 +0000 |
| Subject: | Bug #75171 [Opn]: Killing long running query breaks PHP connection to MSSQL database | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-211003@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=75171&edit=1
ID: 75171
User updated by: ron at healthendeavors dot com
Reported by: ron at healthendeavors dot com
Summary: Killing long running query breaks PHP connection to
MSSQL database
Status: Open
Type: Bug
Package: MSSQL related
Operating System: Windows
PHP Version: 7.0.23
Block user comment: N
Private report: N
New Comment:
point 2: the long running query needs to be run by the PHP application.
Previous Comments:
------------------------------------------------------------------------
[2017-09-08 00:51:21] ron at healthendeavors dot com
Description:
------------
1. Have you PHP application up and running and connected to database
2. create a long running query that can be seen in SMSS.
3. Query can be seen doing a whois: execute sp_whoisactive
4. Do a Kill command on the long running query: kill (spid)
5. go back to your PHP application and you will get a '[Microsoft][ODBC Driver 13 for SQL
Server]Communication link failure'
6. If you go to windows event viewer and look in administrative events you will see 'Session
recovery feature data used in login record to open or recover a connection is structurally or
semantically invalid; the connection has been closed. Please contact the vendor of the client
library. [CLIENT: <local machine>]'
Expected result:
----------------
I would expect that a problematic query could be killed without interruption to the application as a
whole.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=75171&edit=1