Bug #34647 [Com]: mssql.timeout has no affect
Edit report at http://bugs.php.net/bug.php?id=34647edit=1
ID: 34647
Comment by: bsdports at csnstores dot com
Reported by:j dot geusebroek at intellit dot nl
Summary:mssql.timeout has no affect
Status: No Feedback
Type: Bug
Package:MSSQL related
Operating System: Suse 9.3
PHP Version:5.0.5
Assigned To:fmk
Block user comment: N
New Comment:
From what i can tell it's not a bug in php, but in the under lying
freetds library.
For those people on Freebsd or anyone else using freetds .64 and having
problems with the timeout.
Try upgrading your freetds to the latest build.
On Freebsd (until i can get the ports updated):
uninstall php5-mssql and freetds (and/or freetds-msdblib)
then install freetds-devel, and then php5-mssql.
That should get you freetds-devel which in the ports tree is version
0.82 and the mssql.timeout functionality should start working.
Previous Comments:
[2010-02-26 15:46:28] jaysonsantos2003 at yahoo dot com dot br
The only way to it work is setting it to a huge number.
It will ignore -1 and 0.
Edit php.ini and set mssql.timeout = 854358349583 and it will work fine.
[2010-01-05 16:40:17] beoe at komplett dot cc
We are experiencing the same behaviour.
PHP Version 5.2.11
freetds-0.64
CentOS 5.4
If our database queries get queued, the connections will never timeout
and as a result all apache processes lock up. Has anyone found a
workaround?
[2009-05-27 09:58:25] a dot e at inne dot pl
I think i am seeing the same issue on php 5.2.6 on Mac
Im setting timeout 60 in php.ini and 8 at runtime. Im runnig nc -l -p
4000 on localmachine and pointing mssql connection to it.
I can see its connecting and then hangs forever.
If i point mssql connect to non existing ip it fails after
connection_timeout as it should.
Is there any chance for this setting to be fixed? or any way around it?
Thanks
[2009-04-20 21:41:48] vinsonr at gmail dot com
This is still occurring in 5.2.6. It sits there timing out:
write(1, Running query...\n, 17Running query...
) = 17
gettimeofday({1240263244, 234960}, NULL) = 0
gettimeofday({1240263244, 234963}, NULL) = 0
select(4, NULL, [3], NULL, {5, 0}) = 1 (out [3], left {5, 0})
gettimeofday({1240263244, 235613}, NULL) = 0
sendto(3, \1\1...@\0\0\1\0s\0e\0l\0e\0c\0t\0 \0[\0d\0a\0t\0e\0...,
2112, MSG_NOSIGNAL, NULL, 0) = 2112
gettimeofday({1240263244, 235962}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263249, 235390}, NULL) = 0
gettimeofday({1240263249, 235490}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263254, 235491}, NULL) = 0
gettimeofday({1240263254, 235591}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263259, 235422}, NULL) = 0
gettimeofday({1240263259, 235523}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263264, 235536}, NULL) = 0
gettimeofday({1240263264, 235637}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263269, 235253}, NULL) = 0
gettimeofday({1240263269, 235354}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263274, 235997}, NULL) = 0
gettimeofday({1240263274, 236097}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263279, 236311}, NULL) = 0
gettimeofday({1240263279, 236413}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263284, 236515}, NULL) = 0
gettimeofday({1240263284, 236615}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263289, 236319}, NULL) = 0
gettimeofday({1240263289, 236419}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
[2007-06-20 12:19:05] jochem dot blok at fasterforward dot nl
I also have this problem with PHP 5.2.0.
mssql.timeout is set to Local Value 60 and Master Value 60. Php doesn't
time out. I have a query which run over 60 seconds.
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/bug.php?id=34647
--
Edit this bug report at http://bugs.php.net/bug.php?id=34647edit=1
#34647 [Com]: mssql.timeout has no affect
ID: 34647
Comment by: jaysonsantos2003 at yahoo dot com dot br
Reported By: j dot geusebroek at intellit dot nl
Status: No Feedback
Bug Type: MSSQL related
Operating System: Suse 9.3
PHP Version: 5.0.5
Assigned To: fmk
New Comment:
The only way to it work is setting it to a huge number.
It will ignore -1 and 0.
Edit php.ini and set mssql.timeout = 854358349583 and it will work
fine.
Previous Comments:
[2010-01-05 16:40:17] beoe at komplett dot cc
We are experiencing the same behaviour.
PHP Version 5.2.11
freetds-0.64
CentOS 5.4
If our database queries get queued, the connections will never timeout
and as a result all apache processes lock up. Has anyone found a
workaround?
[2009-05-27 09:58:25] a dot e at inne dot pl
I think i am seeing the same issue on php 5.2.6 on Mac
Im setting timeout 60 in php.ini and 8 at runtime. Im runnig nc -l -p
4000 on localmachine and pointing mssql connection to it.
I can see its connecting and then hangs forever.
If i point mssql connect to non existing ip it fails after
connection_timeout as it should.
Is there any chance for this setting to be fixed? or any way around it?
Thanks
[2009-04-20 21:41:48] vinsonr at gmail dot com
This is still occurring in 5.2.6. It sits there timing out:
write(1, Running query...\n, 17Running query...
) = 17
gettimeofday({1240263244, 234960}, NULL) = 0
gettimeofday({1240263244, 234963}, NULL) = 0
select(4, NULL, [3], NULL, {5, 0}) = 1 (out [3], left {5, 0})
gettimeofday({1240263244, 235613}, NULL) = 0
sendto(3, \1\1...@\0\0\1\0s\0e\0l\0e\0c\0t\0 \0[\0d\0a\0t\0e\0...,
2112, MSG_NOSIGNAL, NULL, 0) = 2112
gettimeofday({1240263244, 235962}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263249, 235390}, NULL) = 0
gettimeofday({1240263249, 235490}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263254, 235491}, NULL) = 0
gettimeofday({1240263254, 235591}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263259, 235422}, NULL) = 0
gettimeofday({1240263259, 235523}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263264, 235536}, NULL) = 0
gettimeofday({1240263264, 235637}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263269, 235253}, NULL) = 0
gettimeofday({1240263269, 235354}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263274, 235997}, NULL) = 0
gettimeofday({1240263274, 236097}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263279, 236311}, NULL) = 0
gettimeofday({1240263279, 236413}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263284, 236515}, NULL) = 0
gettimeofday({1240263284, 236615}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263289, 236319}, NULL) = 0
gettimeofday({1240263289, 236419}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
[2007-06-20 12:19:05] jochem dot blok at fasterforward dot nl
I also have this problem with PHP 5.2.0.
mssql.timeout is set to Local Value 60 and Master Value 60. Php doesn't
time out. I have a query which run over 60 seconds.
[2007-06-15 11:36:39] sarstrom at gmail dot com
I'm sorry, but setting the timeouts in php.ini doesn't help either.
phpinfo() confirms that the limit is set to 1 second, but it waits an
infinite amount of time for the query to finish!
Deliberatly making a self-join-query will lock up one php-thread
forever, after all threads are locked up, the webserver won't answer any
further requests.
/hps
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/34647
--
Edit this bug report at http://bugs.php.net/?id=34647edit=1
#34647 [Com]: mssql.timeout has no affect
ID: 34647
Comment by: beoe at komplett dot cc
Reported By: j dot geusebroek at intellit dot nl
Status: No Feedback
Bug Type: MSSQL related
Operating System: Suse 9.3
PHP Version: 5.0.5
Assigned To: fmk
New Comment:
We are experiencing the same behaviour.
PHP Version 5.2.11
freetds-0.64
CentOS 5.4
If our database queries get queued, the connections will never timeout
and as a result all apache processes lock up. Has anyone found a
workaround?
Previous Comments:
[2009-05-27 09:58:25] a dot e at inne dot pl
I think i am seeing the same issue on php 5.2.6 on Mac
Im setting timeout 60 in php.ini and 8 at runtime. Im runnig nc -l -p
4000 on localmachine and pointing mssql connection to it.
I can see its connecting and then hangs forever.
If i point mssql connect to non existing ip it fails after
connection_timeout as it should.
Is there any chance for this setting to be fixed? or any way around it?
Thanks
[2009-04-20 21:41:48] vinsonr at gmail dot com
This is still occurring in 5.2.6. It sits there timing out:
write(1, Running query...\n, 17Running query...
) = 17
gettimeofday({1240263244, 234960}, NULL) = 0
gettimeofday({1240263244, 234963}, NULL) = 0
select(4, NULL, [3], NULL, {5, 0}) = 1 (out [3], left {5, 0})
gettimeofday({1240263244, 235613}, NULL) = 0
sendto(3, \1\1...@\0\0\1\0s\0e\0l\0e\0c\0t\0 \0[\0d\0a\0t\0e\0...,
2112, MSG_NOSIGNAL, NULL, 0) = 2112
gettimeofday({1240263244, 235962}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263249, 235390}, NULL) = 0
gettimeofday({1240263249, 235490}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263254, 235491}, NULL) = 0
gettimeofday({1240263254, 235591}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263259, 235422}, NULL) = 0
gettimeofday({1240263259, 235523}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263264, 235536}, NULL) = 0
gettimeofday({1240263264, 235637}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263269, 235253}, NULL) = 0
gettimeofday({1240263269, 235354}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263274, 235997}, NULL) = 0
gettimeofday({1240263274, 236097}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263279, 236311}, NULL) = 0
gettimeofday({1240263279, 236413}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263284, 236515}, NULL) = 0
gettimeofday({1240263284, 236615}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263289, 236319}, NULL) = 0
gettimeofday({1240263289, 236419}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
[2007-06-20 12:19:05] jochem dot blok at fasterforward dot nl
I also have this problem with PHP 5.2.0.
mssql.timeout is set to Local Value 60 and Master Value 60. Php doesn't
time out. I have a query which run over 60 seconds.
[2007-06-15 11:36:39] sarstrom at gmail dot com
I'm sorry, but setting the timeouts in php.ini doesn't help either.
phpinfo() confirms that the limit is set to 1 second, but it waits an
infinite amount of time for the query to finish!
Deliberatly making a self-join-query will lock up one php-thread
forever, after all threads are locked up, the webserver won't answer any
further requests.
/hps
[2007-06-14 16:47:33] f...@php.net
The two time out parameters is used during request startup and it will
not have any effect to change the value at runtime.
I'll look at a way to move these to the connect/query functions, but
until then you should specify these in your php.ini file.
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/34647
--
Edit this bug report at http://bugs.php.net/?id=34647edit=1
#34647 [Com]: mssql.timeout has no affect
ID: 34647
Comment by: a dot e at inne dot pl
Reported By: j dot geusebroek at intellit dot nl
Status: No Feedback
Bug Type: MSSQL related
Operating System: Suse 9.3
PHP Version: 5.0.5
Assigned To: fmk
New Comment:
I think i am seeing the same issue on php 5.2.6 on Mac
Im setting timeout 60 in php.ini and 8 at runtime. Im runnig nc -l -p
4000 on localmachine and pointing mssql connection to it.
I can see its connecting and then hangs forever.
If i point mssql connect to non existing ip it fails after
connection_timeout as it should.
Is there any chance for this setting to be fixed? or any way around it?
Thanks
Previous Comments:
[2009-04-20 21:41:48] vinsonr at gmail dot com
This is still occurring in 5.2.6. It sits there timing out:
write(1, Running query...\n, 17Running query...
) = 17
gettimeofday({1240263244, 234960}, NULL) = 0
gettimeofday({1240263244, 234963}, NULL) = 0
select(4, NULL, [3], NULL, {5, 0}) = 1 (out [3], left {5, 0})
gettimeofday({1240263244, 235613}, NULL) = 0
sendto(3, \1\1...@\0\0\1\0s\0e\0l\0e\0c\0t\0 \0[\0d\0a\0t\0e\0...,
2112, MSG_NOSIGNAL, NULL, 0) = 2112
gettimeofday({1240263244, 235962}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263249, 235390}, NULL) = 0
gettimeofday({1240263249, 235490}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263254, 235491}, NULL) = 0
gettimeofday({1240263254, 235591}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263259, 235422}, NULL) = 0
gettimeofday({1240263259, 235523}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263264, 235536}, NULL) = 0
gettimeofday({1240263264, 235637}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263269, 235253}, NULL) = 0
gettimeofday({1240263269, 235354}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263274, 235997}, NULL) = 0
gettimeofday({1240263274, 236097}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263279, 236311}, NULL) = 0
gettimeofday({1240263279, 236413}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263284, 236515}, NULL) = 0
gettimeofday({1240263284, 236615}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263289, 236319}, NULL) = 0
gettimeofday({1240263289, 236419}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
[2007-06-20 12:19:05] jochem dot blok at fasterforward dot nl
I also have this problem with PHP 5.2.0.
mssql.timeout is set to Local Value 60 and Master Value 60. Php doesn't
time out. I have a query which run over 60 seconds.
[2007-06-15 11:36:39] sarstrom at gmail dot com
I'm sorry, but setting the timeouts in php.ini doesn't help either.
phpinfo() confirms that the limit is set to 1 second, but it waits an
infinite amount of time for the query to finish!
Deliberatly making a self-join-query will lock up one php-thread
forever, after all threads are locked up, the webserver won't answer any
further requests.
/hps
[2007-06-14 16:47:33] f...@php.net
The two time out parameters is used during request startup and it will
not have any effect to change the value at runtime.
I'll look at a way to move these to the connect/query functions, but
until then you should specify these in your php.ini file.
[2007-06-13 11:30:52] sarstrom at gmail dot com
I can still reproduce this problem as of 2007-06-13.
I've tried with PHP 5.2.1 and 5.2.3, And FreeTDS is at 0.64
on a FreeBSD 6.1 install.
This code always waits the 20 seconds and tells me that everything went
according to plan
$dbLink = mssql_connect('sqldmz','sosuser','123456');
ini_set('mssql.timeout','1');
$query = WAITFOR DELAY '000:00:20' SELECT TOP 1 * FROM
tbl_serviceorder;
$res = mssql_query($query,$dbLink);
if(!$res) {
echo 'No, error, warning, timeout!';
}
else {
$row = mssql_fetch_assoc($res);
echo 'Everything is OK: '.$row['OrderNumber'];
}
/hps
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/34647
--
Edit this bug report at http://bugs.php.net/?id=34647edit=1
#34647 [Com]: mssql.timeout has no affect
ID: 34647
Comment by: vinsonr at gmail dot com
Reported By: j dot geusebroek at intellit dot nl
Status: No Feedback
Bug Type: MSSQL related
Operating System: Suse 9.3
PHP Version: 5.0.5
Assigned To: fmk
New Comment:
This is still occurring in 5.2.6. It sits there timing out:
write(1, Running query...\n, 17Running query...
) = 17
gettimeofday({1240263244, 234960}, NULL) = 0
gettimeofday({1240263244, 234963}, NULL) = 0
select(4, NULL, [3], NULL, {5, 0}) = 1 (out [3], left {5, 0})
gettimeofday({1240263244, 235613}, NULL) = 0
sendto(3, \1\1...@\0\0\1\0s\0e\0l\0e\0c\0t\0 \0[\0d\0a\0t\0e\0...,
2112, MSG_NOSIGNAL, NULL, 0) = 2112
gettimeofday({1240263244, 235962}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263249, 235390}, NULL) = 0
gettimeofday({1240263249, 235490}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263254, 235491}, NULL) = 0
gettimeofday({1240263254, 235591}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263259, 235422}, NULL) = 0
gettimeofday({1240263259, 235523}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263264, 235536}, NULL) = 0
gettimeofday({1240263264, 235637}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263269, 235253}, NULL) = 0
gettimeofday({1240263269, 235354}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263274, 235997}, NULL) = 0
gettimeofday({1240263274, 236097}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263279, 236311}, NULL) = 0
gettimeofday({1240263279, 236413}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263284, 236515}, NULL) = 0
gettimeofday({1240263284, 236615}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
gettimeofday({1240263289, 236319}, NULL) = 0
gettimeofday({1240263289, 236419}, NULL) = 0
select(4, [3], NULL, NULL, {5, 0}) = 0 (Timeout)
Previous Comments:
[2007-06-20 12:19:05] jochem dot blok at fasterforward dot nl
I also have this problem with PHP 5.2.0.
mssql.timeout is set to Local Value 60 and Master Value 60. Php doesn't
time out. I have a query which run over 60 seconds.
[2007-06-15 11:36:39] sarstrom at gmail dot com
I'm sorry, but setting the timeouts in php.ini doesn't help either.
phpinfo() confirms that the limit is set to 1 second, but it waits an
infinite amount of time for the query to finish!
Deliberatly making a self-join-query will lock up one php-thread
forever, after all threads are locked up, the webserver won't answer any
further requests.
/hps
[2007-06-14 16:47:33] f...@php.net
The two time out parameters is used during request startup and it will
not have any effect to change the value at runtime.
I'll look at a way to move these to the connect/query functions, but
until then you should specify these in your php.ini file.
[2007-06-13 11:30:52] sarstrom at gmail dot com
I can still reproduce this problem as of 2007-06-13.
I've tried with PHP 5.2.1 and 5.2.3, And FreeTDS is at 0.64
on a FreeBSD 6.1 install.
This code always waits the 20 seconds and tells me that everything went
according to plan
$dbLink = mssql_connect('sqldmz','sosuser','123456');
ini_set('mssql.timeout','1');
$query = WAITFOR DELAY '000:00:20' SELECT TOP 1 * FROM
tbl_serviceorder;
$res = mssql_query($query,$dbLink);
if(!$res) {
echo 'No, error, warning, timeout!';
}
else {
$row = mssql_fetch_assoc($res);
echo 'Everything is OK: '.$row['OrderNumber'];
}
/hps
[2005-09-26 18:51:57] j dot geusebroek at intellit dot nl
Description:
mssql.timeout has no affect, a query will wait an infinite time and the
scripts hangs.
I'm using the FreeTDS library, version 6.3 but i also tried
latest FreeTDS CVS.
FreeTDS debug file shows that a timeout has occured (i also set the
timeout in the FreeTDS client) but PHP keeps running.
(dblib.c:4010:in dbsqlok()
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
)
Reproduce code:
---
Perform any query that outlasts your mssql.timeout setting.
Expected result:
PHP exiting with a fatal error.
Actual result:
--
Infinite wait.
--
Edit this bug
#34647 [Com]: mssql.timeout has no affect
ID: 34647
Comment by: jochem dot blok at fasterforward dot nl
Reported By: j dot geusebroek at intellit dot nl
Status: No Feedback
Bug Type: MSSQL related
Operating System: Suse 9.3
PHP Version: 5.0.5
Assigned To: fmk
New Comment:
I also have this problem with PHP 5.2.0.
mssql.timeout is set to Local Value 60 and Master Value 60. Php doesn't
time out. I have a query which run over 60 seconds.
Previous Comments:
[2007-06-15 11:36:39] sarstrom at gmail dot com
I'm sorry, but setting the timeouts in php.ini doesn't help either.
phpinfo() confirms that the limit is set to 1 second, but it waits an
infinite amount of time for the query to finish!
Deliberatly making a self-join-query will lock up one php-thread
forever, after all threads are locked up, the webserver won't answer any
further requests.
/hps
[2007-06-14 16:47:33] [EMAIL PROTECTED]
The two time out parameters is used during request startup and it will
not have any effect to change the value at runtime.
I'll look at a way to move these to the connect/query functions, but
until then you should specify these in your php.ini file.
[2007-06-13 11:30:52] sarstrom at gmail dot com
I can still reproduce this problem as of 2007-06-13.
I've tried with PHP 5.2.1 and 5.2.3, And FreeTDS is at 0.64
on a FreeBSD 6.1 install.
This code always waits the 20 seconds and tells me that everything went
according to plan
$dbLink = mssql_connect('sqldmz','sosuser','123456');
ini_set('mssql.timeout','1');
$query = WAITFOR DELAY '000:00:20' SELECT TOP 1 * FROM
tbl_serviceorder;
$res = mssql_query($query,$dbLink);
if(!$res) {
echo 'No, error, warning, timeout!';
}
else {
$row = mssql_fetch_assoc($res);
echo 'Everything is OK: '.$row['OrderNumber'];
}
/hps
[2005-11-14 01:00:03] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to Open.
[2005-11-06 23:19:58] [EMAIL PROTECTED]
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
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/34647
--
Edit this bug report at http://bugs.php.net/?id=34647edit=1
#34647 [Com]: mssql.timeout has no affect
ID: 34647
Comment by: sarstrom at gmail dot com
Reported By: j dot geusebroek at intellit dot nl
Status: No Feedback
Bug Type: MSSQL related
Operating System: Suse 9.3
PHP Version: 5.0.5
Assigned To: fmk
New Comment:
I'm sorry, but setting the timeouts in php.ini doesn't help either.
phpinfo() confirms that the limit is set to 1 second, but it waits an
infinite amount of time for the query to finish!
Deliberatly making a self-join-query will lock up one php-thread
forever, after all threads are locked up, the webserver won't answer any
further requests.
/hps
Previous Comments:
[2007-06-14 16:47:33] [EMAIL PROTECTED]
The two time out parameters is used during request startup and it will
not have any effect to change the value at runtime.
I'll look at a way to move these to the connect/query functions, but
until then you should specify these in your php.ini file.
[2007-06-13 11:30:52] sarstrom at gmail dot com
I can still reproduce this problem as of 2007-06-13.
I've tried with PHP 5.2.1 and 5.2.3, And FreeTDS is at 0.64
on a FreeBSD 6.1 install.
This code always waits the 20 seconds and tells me that everything went
according to plan
$dbLink = mssql_connect('sqldmz','sosuser','123456');
ini_set('mssql.timeout','1');
$query = WAITFOR DELAY '000:00:20' SELECT TOP 1 * FROM
tbl_serviceorder;
$res = mssql_query($query,$dbLink);
if(!$res) {
echo 'No, error, warning, timeout!';
}
else {
$row = mssql_fetch_assoc($res);
echo 'Everything is OK: '.$row['OrderNumber'];
}
/hps
[2005-11-14 01:00:03] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to Open.
[2005-11-06 23:19:58] [EMAIL PROTECTED]
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
[2005-09-26 18:51:57] j dot geusebroek at intellit dot nl
Description:
mssql.timeout has no affect, a query will wait an infinite time and the
scripts hangs.
I'm using the FreeTDS library, version 6.3 but i also tried
latest FreeTDS CVS.
FreeTDS debug file shows that a timeout has occured (i also set the
timeout in the FreeTDS client) but PHP keeps running.
(dblib.c:4010:in dbsqlok()
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
)
Reproduce code:
---
Perform any query that outlasts your mssql.timeout setting.
Expected result:
PHP exiting with a fatal error.
Actual result:
--
Infinite wait.
--
Edit this bug report at http://bugs.php.net/?id=34647edit=1
#34647 [Com]: mssql.timeout has no affect
ID: 34647
Comment by: sarstrom at gmail dot com
Reported By: j dot geusebroek at intellit dot nl
Status: No Feedback
Bug Type: MSSQL related
Operating System: Suse 9.3
PHP Version: 5.0.5
Assigned To: fmk
New Comment:
I can still reproduce this problem as of 2007-06-13.
I've tried with PHP 5.2.1 and 5.2.3, And FreeTDS is at 0.64
on a FreeBSD 6.1 install.
This code always waits the 20 seconds and tells me that everything went
according to plan
$dbLink = mssql_connect('sqldmz','sosuser','123456');
ini_set('mssql.timeout','1');
$query = WAITFOR DELAY '000:00:20' SELECT TOP 1 * FROM
tbl_serviceorder;
$res = mssql_query($query,$dbLink);
if(!$res) {
echo 'No, error, warning, timeout!';
}
else {
$row = mssql_fetch_assoc($res);
echo 'Everything is OK: '.$row['OrderNumber'];
}
/hps
Previous Comments:
[2005-11-14 01:00:03] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to Open.
[2005-11-06 23:19:58] [EMAIL PROTECTED]
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
[2005-09-26 18:51:57] j dot geusebroek at intellit dot nl
Description:
mssql.timeout has no affect, a query will wait an infinite time and the
scripts hangs.
I'm using the FreeTDS library, version 6.3 but i also tried
latest FreeTDS CVS.
FreeTDS debug file shows that a timeout has occured (i also set the
timeout in the FreeTDS client) but PHP keeps running.
(dblib.c:4010:in dbsqlok()
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
net.c:327:exceeded query timeout: 10
)
Reproduce code:
---
Perform any query that outlasts your mssql.timeout setting.
Expected result:
PHP exiting with a fatal error.
Actual result:
--
Infinite wait.
--
Edit this bug report at http://bugs.php.net/?id=34647edit=1
