#1573 closed Bug (Fixed)
TCPConnect TCPTimeout
| Reported by: | s.c.a.r.y@… | 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 Changed 14 years ago by Jpm
- Owner set to Jpm
- Status changed from new to assigned
comment:2 Changed 14 years ago by Jpm
- Milestone set to 3.3.7.0
- Resolution set to Fixed
- Status changed from assigned to closed
comment:3 Changed 13 years ago by Jon
- Resolution Fixed deleted
- Status changed from closed to reopened
comment:5 Changed 12 years ago by anonymous
Is this ever going to get fixed?
comment:6 Changed 11 years ago by anonymous
Bump?
comment:7 Changed 11 years ago by guinness
This isn't a Forum, please do not post 'bump' or pointless messages in Trac.
comment:8 Changed 11 years ago by anonymous
Bumpy Bump
comment:9 Changed 11 years ago by Jpm
I have submitted the fix to Jon,
I hope he will have sometime to commit it
Cheers
JP
comment:10 Changed 10 years ago by Jpm
- Summary changed from TCPTimeout to TCPConnect TCPTimeout
comment:11 Changed 10 years ago by Jon
- Milestone set to 3.3.13.2
- Owner changed from Jpm to Jon
- Resolution set to Fixed
- Status changed from reopened to closed
Fixed by revision [10302] in version: 3.3.13.2
comment:12 Changed 10 years ago by anonymous
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 Changed 10 years ago by anonymous
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.
comment:14 follow-up: ↓ 15 Changed 8 years ago by anonymous
did they fix that ?
comment:15 in reply to: ↑ 14 Changed 8 years ago by TheDcoder
Guidelines for posting comments:
- You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
- In-depth discussions should take place on the forum.
For more information see the full version of the ticket guidelines here.
Fixed by revision [5826] in version: 3.3.7.0