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 19:38:56 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 19:38 -------
There still seems to be a misunderstanding here. 
(Sorry for giving you headaches, if I do. I'm not a native english speaker and 
maybe I'm expressing s.th wrong. So let me try once again...)

I am NOT having any network problem. This is not about DNS, ports, firewalls or 
anything. My problem is NOT that I'd be trying to connect to a host that I 
assume to be up and ant would report to me that it is not, or any such kind of 
problem.

It is simply like this: The waitfor task can be instructed to return from its 
execution after lets say 5 seconds. This I can specify within the maxwait 
attribute. This is my understanding of this attribute. I tell the waitfor task 
to return after 5 seconds. No matter what. Please return after five seconds. 
Dear waitfor task, if I gave you too hard a test to execute within your body 
and after five seconds it should still be executing, then tear it down and 
return. That is my undertanding of the maxwait attribute. And my point is that 
the waitfor task is not behaving like this. The socket test is just meant to be 
a testcase for this wrong behaviour.

This is the kind of bug that I want to report. An appropriately set up socket 
test that is deliberately configured in a way so that it would probably need a 
minute or two to complete is merely the testcase that I wanted to provide to 
prove my point.

If you look at the code snippet then you will agree that the waitfor task 
should in any case return after 5 seconds, right? Whatever condition is 
executing in its 'body'. My understanding is that if the body of the waitfor 
task is executing a test that takes 60 seconds to return, but the waitfor task 
has a 5 seconds timeout, then it has to interrupt the test after 5 seconds. 
If you run my example, the waitfor task will NOT return after its allotted 5 
seconds but waits for as long as the socket test takes to complete.

--
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