Return-Path: 
 <user-return-40065-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 29120 invoked from network); 14 Jan 2004 21:57:31 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 14 Jan 2004 21:57:31 -0000
Received: (qmail 33409 invoked by uid 500); 14 Jan 2004 21:57:11 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 33369 invoked by uid 500); 14 Jan 2004 21:57:10 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:user-subscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 33355 invoked from network); 14 Jan 2004 21:57:10 -0000
Received: from unknown (HELO barrierb241.nike.com) (146.197.27.11)
  by daedalus.apache.org with SMTP; 14 Jan 2004 21:57:10 -0000
Received: from barrierb241.nike.com (root@localhost)
	by barrierb241.nike.com with ESMTP id i0ELvGC17443
	for <user@ant.apache.org>; Wed, 14 Jan 2004 13:57:16 -0800 (PST)
Received: from beavertn-svr-r9.nike.com (beavertn-svr-r9.nike.com
 [146.197.20.109])
	by barrierb241.nike.com with ESMTP id i0ELvEV17382
	for <user@ant.apache.org>; Wed, 14 Jan 2004 13:57:15 -0800 (PST)
Received: from 146.197.1.183 by beavertn-svr-n9.nike.com with SMTP (
 Tumbleweed MMS SMTP Relay (MMS v5.0)); Wed, 14 Jan 2004 13:57:11 -0800
X-Server-Uuid: F122D6CD-24F0-4253-8986-549FB7942DF9
Received: from beavertn-svr-a0.nike.com (beavertn-svr-a0.nike.com
 [146.197.251.36]) by cammail1.nike.com (8.11.7p1+Sun/8.11.6) with ESMTP
 id i0ELvA912701 for <user@ant.apache.org>; Wed, 14 Jan 2004 13:57:10
 -0800 (PST)
Received: from beavertn-svr-b4.nike.com ([146.197.251.242]) by
 beavertn-svr-a0.nike.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 14
 Jan 2004 13:57:09 -0800
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: problem with exec & rsh
Date: Wed, 14 Jan 2004 13:57:09 -0800
Message-ID: 
 <C72E822C38A44D40938D36E473884BD4027B9A3E@beavertn-svr-b4.nike.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: problem with exec & rsh
Thread-Index: AcPa5xdR+mdy1sk6ShCvK5YnNAz3nwAAUU2Q
From: "Anderson, Rob (Global Trade)" <Rob.Anderson2@nike.com>
To: "Ant Users List" <user@ant.apache.org>
X-OriginalArrivalTime: 14 Jan 2004 21:57:09.0332 (UTC)
 FILETIME=[5B77D140:01C3DAE9]
X-WSS-ID: 6C1B64BD707262-01-01
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Does the rsync command you are trying to run behave the same way if you =
run it from the command line? I think I have seen this behavior from =
rsync before. I think you might be better off trying a different =
strategy than calling rsync from the <exec> task. I have automated a =
deployment similar to the one you describe, where an ear is build on one =
machine and then deployed to another. I would do the following:

1. Build the ear/war.
2. Tar is up with <tar>
3. Scp it to the remote server with <scp>
4. Use <sshexec> to connect to the remote server and do the following:
	a. stop the appserver
	b. backup the existing ear/war (delete the previous backup first)
	c. untar the new ear/war
	d. move the new ear/war into place
	e. start the appserver

This strategy provides you with the ability to quickly and easily =
backout the changes if necessary.

I hope this helps,

-Rob Anderson

-----Original Message-----
From: Basel Ahmed [mailto:B06BSA@FDS.com]
Sent: Wednesday, January 14, 2004 1:39 PM
To: user@ant.apache.org
Subject: problem with exec & rsh


Hello,

I have a problem with rsh called through the ant exec directive not=20
terminating properly.

Synopsis:

I have an ant script that handles building the application ear file on a =

build server.  Upon
successfully completing the build tasks, it then calls a deploy task =
which=20
attempts to install
the ear to a remote server using ant's <exec> directive and the Unix rsh =

command.

Problem:

>From all indications, the scripts are called properly and the remote=20
deploy does in fact=20
complete successfully, however the rsh process does not terminate.=20
Furthermore, it looks
like a second rsh process is being spawned by the first one as indicated =

by the process id
(the process id for rsh process #2 has a parent process number of rsh=20
process #1).

My Questions:

1 -  Has anyone else experienced this and if so, is there a known=20
resolution?

2 -  What could be resulting in the second rsh process being spawn and=20
does anyone have
any suggestions on how I can further debug this issue?

3 - Can anyone offer some insight into a better way of doing the same=20
thing and possibly
in a more robust manner?

Below is the specific task responsible for the remote deploy:

<!--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -->
<!-- Target Name: remotedeploy  -->
<!--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -->
<target name=3D"remotedeploy"
        description=3D"Deploy EAR package"
        depends=3D"transfer" >

  <echo message=3D"Deploying fedad${build.name}.ear copied to:=20
${deploy.to.server} " />
  <exec executable=3D"/usr/bin/rsh">
     <arg line=3D"${deploy.to.server} -l fsgapp &quot;scripts/deploy.sh=20
fedad${build.name}.ear&quot;" />
  </exec>

  <exec executable=3D"bin/deploy_notify.sh">
     <arg line=3D"fedad${build.name}.ear ${deploy.to.server}" />
  </exec>

</target>


Thanks in advance!


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