Forrest/Jetty hangs in dynamic mode

For the last week or two weeks, forrest no longer
initializes in the 
background in dynamic mode. I use Java 1.4.2 on Linux and OS
X and I 
usually update from svn several times a week.

After "Note: Use Ctrl-C to stop the Jetty
server" the process waits for 
tty input. If I bring the process to the foreground,
initialization 
completes and then forrest runs fine even in the background.
Has anyone 
else experienced this?

Brian

Brian M Dube wrote:
> For the last week or two weeks, forrest no longer
initializes in the 
> background in dynamic mode. I use Java 1.4.2 on Linux
and OS X and I 
> usually update from svn several times a week.
> 
> After "Note: Use Ctrl-C to stop the Jetty
server" the process waits for 
> tty input. If I bring the process to the foreground,
initialization 
> completes and then forrest runs fine even in the
background. Has anyone 
> else experienced this?

I have no such problems. Tested on Windoes + Cygwin and Suse
9

Ross

Ross Gardler wrote:
> Brian M Dube wrote:
> >For the last week or two weeks, forrest no longer
initializes in the 
> >background in dynamic mode. I use Java 1.4.2 on
Linux and OS X and I 
> >usually update from svn several times a week.
> >
> >After "Note: Use Ctrl-C to stop the Jetty
server" the process waits for 
> >tty input. If I bring the process to the
foreground, initialization 
> >completes and then forrest runs fine even in the
background. Has anyone 
> >else experienced this?
> 
> I have no such problems. Tested on Windoes + Cygwin and
Suse 9

I *do* have that problem on Mac OS X on my local desktop.
In the past i have not tried to run forrest in the
background.
When doing that today, i get the same as Brian.

Also, i have been experimenting on forrest.zones.apache.org
with a 'forrest run'. The shell script that starts it
puts forrest into the background. That still works with
today's trunk. That is on Solaris 10.

The only thing that i can suggest is going back to an
old svn revision to find one that works, then updating
forwards until it breaks. For example, lets assume that
the recent Ant upgrade is the culprit ...

Look at the svn mailing list to see where the upgrade
happened: 
Date: Tue May 16 00:20:06 2006                              
                                                
New Revision: 406862

Update backwards to just before the upgrade:
svn update -r 406861
... do 'build clean; build'

Go back further if it still doesn't work.
After sucess, start upgrading forward.

Looking at the svn mailing list shows that
could jump forward past minor changes such as doc edits.
e.g. just after the upgrade:
svn update -r 406863
... do 'build clean; build'

If it still works, move a bit further on:
svn update -r 407260
... do 'build clean; build'

After finding the break, move back to head of trunk
svn update -r HEAD.

-David

David Crossley wrote:
> Ross Gardler wrote:
> 
>>Brian M Dube wrote:
>>
>>>For the last week or two weeks, forrest no
longer initializes in the 
>>>background in dynamic mode. I use Java 1.4.2 on
Linux and OS X and I 
>>>usually update from svn several times a week.
>>>
>>>After "Note: Use Ctrl-C to stop the Jetty
server" the process waits for 
>>>tty input. If I bring the process to the
foreground, initialization 
>>>completes and then forrest runs fine even in the
background. Has anyone 
>>>else experienced this?
>>
>>I have no such problems. Tested on Windoes + Cygwin
and Suse 9
> 
> 
> I *do* have that problem on Mac OS X on my local
desktop.
> In the past i have not tried to run forrest in the
background.
> When doing that today, i get the same as Brian.
> 
> Also, i have been experimenting on
forrest.zones.apache.org
> with a 'forrest run'. The shell script that starts it
> puts forrest into the background. That still works with
> today's trunk. That is on Solaris 10.

Thanks, this gave me an idea. Invoking forrest as a
background process 
in a script works for me too. Strange.

> The only thing that i can suggest is going back to an
> old svn revision to find one that works, then updating
> forwards until it breaks. For example, lets assume that
> the recent Ant upgrade is the culprit ...

I may or may not chase this issue. It will be next week if I
do.

Brian

Brian M Dube wrote:
> David Crossley wrote:
>> I *do* have that problem on Mac OS X on my local
desktop.
>> In the past i have not tried to run forrest in the
background.
>> When doing that today, i get the same as Brian.
>>
>> Also, i have been experimenting on
forrest.zones.apache.org
>> with a 'forrest run'. The shell script that
starts it
>> puts forrest into the background. That still works
with
>> today's trunk. That is on Solaris 10.
> 
> 
> Thanks, this gave me an idea. Invoking forrest as a
background process 
> in a script works for me too. Strange.
> 
>> The only thing that i can suggest is going back to
an
>> old svn revision to find one that works, then
updating
>> forwards until it breaks. For example, lets assume
that
>> the recent Ant upgrade is the culprit ...
> 
> 
> I may or may not chase this issue. It will be next week
if I do.

Rev 406861 works, rev 406863 does not.

Date: Tue May 16 00:20:06 2006
New Revision: 406862

URL: http://svn.apache.org/viewcvs?rev=406862&view=rev
Log:
Updated to Apache-Ant-1.6.5 release, jsch-0.1.28, 
apache-jakarta-commons-net-1.4.1

Brian