#1573 closed Bug (Fixed)
TCPConnect TCPTimeout
| Reported by: | Owned by: | Jon | |
|---|---|---|---|
| Milestone: | 3.3.13.2 | Component: | AutoIt |
| Version: | 3.3.6.0 | Severity: | None |
| Keywords: | Cc: |
Description
Hello,
i don´t really know, if this is a bug or maybe wrong/ unclear in the helpfile.
There is an option (Opt("TCPTimeout",100)), which should timeout the tcp-functions when there is no communication.
But this timeout seems to do nothing, if you maybe try to connect via TCPConnect to an IP+Port which is not reachable. It tooks about 20 sec. after the script continues working (and there is no possibility to stop this, because adblibregister does also not catch).
Attachments (0)
Change History (15)
comment:1 by , 16 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 16 years ago
| Milestone: | → 3.3.7.0 |
|---|---|
| Resolution: | → Fixed |
| Status: | assigned → closed |
comment:3 by , 15 years ago
| Resolution: | Fixed |
|---|---|
| Status: | closed → reopened |
comment:7 by , 13 years ago
This isn't a Forum, please do not post 'bump' or pointless messages in Trac.
comment:9 by , 12 years ago
I have submitted the fix to Jon,
I hope he will have sometime to commit it
Cheers
JP
comment:10 by , 12 years ago
| Summary: | TCPTimeout → TCPConnect TCPTimeout |
|---|
comment:11 by , 12 years ago
| Milestone: | → 3.3.13.2 |
|---|---|
| Owner: | changed from to |
| Resolution: | → Fixed |
| Status: | reopened → closed |
Fixed by revision [10302] in version: 3.3.13.2
comment:12 by , 12 years ago
This ticket has been closed but the problem still persists. If I use TCPConnect to connect to a port that is not active, it takes 20 seconds before TCPConnect times out.
comment:13 by , 12 years ago
Never mind. I did not notice the "Milestone set to 3.3.13.2" part in the previous comment. Downloaded the beta and it works fine in the beta. Thanks.
Fixed by revision [5826] in version: 3.3.7.0