Return-Path: 
 <ant-user-return-19184-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 44485 invoked from network); 5 Apr 2002 00:54:04 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 5 Apr 2002 00:54:04 -0000
Received: (qmail 21251 invoked by uid 97); 5 Apr 2002 00:54:04 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 21235 invoked by uid 97); 5 Apr 2002 00:54:04 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Id: "Ant Users List" <ant-user.jakarta.apache.org>
Reply-To: "Ant Users List" <ant-user@jakarta.apache.org>
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 21224 invoked from network); 5 Apr 2002 00:54:03 -0000
Message-ID: <05ac01c1dc3c$c44ccac0$1219570f@ranier>
From: "Steve Loughran" <steve_l@iseran.com>
To: "Ant Users List" <ant-user@jakarta.apache.org>
References: <200204041644.RAA18119@high-wycombe.beasys.com>
Subject: Re: pingURL: A better way to start and stop application servers?
Date: Thu, 4 Apr 2002 16:56:49 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


----- Original Message -----
From: "Philip Aston" <paston@bea.com>
To: <ant-user-digest@jakarta.apache.org>
Sent: Thursday, April 04, 2002 8:43 AM
Subject: pingURL: A better way to start and stop application servers?


>
> Hi,
>
> I thought folks might be interested in the attached task, pingURL. It
> was inspired by the cactus runservertests task, which I've tweaked in
> the past. IMHO, its syntactically neater though.

You can use <waitfor> to probe a url with controlled sleep time and timeout
interval, sets a property on success, etc.

All pingurl does is add a container wrapper, but it only allows url 2XX
conditions to be evaluated (presumably); <waitfor> can probe any port for
being openable, plus all the other conditions that are possible

>
> Here's how I use it to start with WLS 6.1:
>
>     <pingURL testURL="http://localhost:7001/" waitUntil="alive">
>         <java classname="weblogic.Server" fork="yes" dir="${wls.dir}"
>               maxmemory="64m" output="${wls.dir}/stdout.log">
>           <sysproperty key="bea.home" path="${bea.home}"/>
>           <sysproperty key="java.library.path" path="${wls.libpath}"/>
>           <classpath path="${wls.classpath}"/>
>         </java>
>     </pingURL>
>
>
> and to stop WLS 6.1:
>
>     <pingURL testURL="http://localhost:7001/" waitUntil="dead">
>        <java classname="weblogic.Admin" fork="yes"> <!-- Fork or die
:-( -->
>          <classpath path="${wls.classpath}"/>
>          <arg line="-url t3://localhost:7001 -username system -password
password SHUTDOWN"/>
>        </java>
>     </pingURL>
>
>
> What's it do?
>
> When started with waitUntil="alive":
>
>      1. Pings the testURL, and returns immediately if it can connect.
>
>      2. Otherwise, it runs all its nested tasks in a separate thread
>      and then..
>
>      3. .. pings the testURL every half a second and doesn't return
>      until a response is received.
>
>
> When started with waitUntil="dead":
>
>      1. Pings the testURL, and returns immediately if it cannot connect.
>
>      2. Otherwise, it runs all its nested tasks in a separate thread
>      and then..
>
>      3. .. pings the testURL every half a second and doesn't return
>      until a response is not received.
>
>
> The functionality of pingURL is actually orthogonal to that of wlrun
> and wlstop. If they work for you, you can of course say things like:
>
>   <pingURL testURL="http://localhost:7001/" waitUntil="alive">
>     <wlrun...>
>   </pingURL>
>
>
> [For the interested, here's why I avoid wlrun and wlstop:
>
> Problems with the standard wlrun target:
>        1. It is synchronous, doesn't allow you to do anything
>           until WLS exits unless you use <parallel>
>        2. No way of setting shared library path in OS independent way.
>        3. It makes bogus assumptions about the relation of WLS
>           run time directory and WLS installation.
>
> Problems with the standard wlstop target:
>        1. It doesn't wait until the server is dead.
>        2. It doens't work with WLS 6.1
>
> and both of them require you to obtain new versions of the task
> whenever the server start/stop protocol changes.]
>
> I'm quite willing to submit pingURL as an optional package if people
> think its generally useful. It may need a more meaningful name, anyone
> got a better than suggestion?
>
>
> - Phil
>
>


----------------------------------------------------------------------------
----


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


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