ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10401] - waitfor task doesn't shut off socket conditions in every case
Date Tue, 02 Jul 2002 17:46:03 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10401>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10401

waitfor task doesn't shut off socket conditions in every case





------- Additional Comments From wtff@freenet.de  2002-07-02 17:46 -------
It happens when I try to connect to a plain IP adress that does not exist, 
regardless of the port. 
It seems as if the waitfor task is not tearing down client-socket connections 
that are in a waiting-state.

The idea for this "testcase" is to create a client-socket that would wait for a 
full socket-timeout period for some server-socket answer and then to test 
whether the waitfor task tears this waiting client-socket down as soon as the 
waitfor-tasks's timeout appears.

When you connect to an *existing* host but to an unused port on it, then the 
client socket will not run into a long lasting waitstate because the host would 
actively respond that this port is not used and then close the connection. That 
was the only reason for why I mentioned my explicit scenario.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message