You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by bu...@apache.org on 2003/02/07 10:29:45 UTC
DO NOT REPLY [Bug 16869] New: -
cactus RunServerTestsTask timeout parameter
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=16869>.
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=16869
cactus RunServerTestsTask timeout parameter
Summary: cactus RunServerTestsTask timeout parameter
Product: Cactus
Version: 1.4.1
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Client Side
AssignedTo: cactus-dev@jakarta.apache.org
ReportedBy: mpichler@hyperwave.com
Hello,
a small suggestion for enhancement of the ant task runservertests.
We run cactus tests as part of a nightly build process.
If deployment done by the startTarget of runservertests fails,
the build process hangs and must be killed.
It would be nice if the ant task runservertests had an additional
parameter that limits the time that StartServerHelper attempts to
start the server. If the server URL is not callable within the timeout,
a build exception should be raised. The same should be done when the
startTarget (invoked in a separate thread) throws a BuildException.
The parameter might be called startTimeout, integer, unit seconds.
The default could be -1 to wait "forever".
regards,
mpi.
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org