RE: Schedule not working? - Follow-up

This is a follow-up to the list on my variation of this problem.

Being a paranoid type of person, I researched tomcat more thoroughly on
the problem system. It was tomcat 5.0.28 using a jdk of 1.4.2_07 as
installed by the SuSE SLES-9 install program. I had installed jdk
1.5.0_07 and modified the tomcat conf files to launch webapps using it
instead of the default 1.4.2. Everything worked as desired except that
the scheduler did not actually start any builds when it timed down to
zero.

I installed a second instance of tomcat, 5.5.17 - designed to work with
jdk 1.5.x, set it to be started with the java 1.5.0_07 and also
configured it to start webapps using the 1.5.0_07 jdk. Everything came
up properly. I added the anthill.war file to the webapps directory and
bounced tomcat. To my surprise, both tomcats bounced! I had not
configured the new instance to use different ports. I did that along
with fixing the tomcat account to not directly include the JAVA_BINDIR
in its path, then bounced both tomcats again. Both pointed to the same
physical anthill installation, but obviously has different contexts.

The new instance worked fine. I went back to the "old" anthill instance
intending to purge its queue and let it wind down before shutting it
down forever when, much to my surprise the scheduler was behaving as
expected! I removed anthill from the new instance of tomcat, bounced
both, and the scheduler remained working properly. I do not know why
this sequence of events fixed the problem. I would not recommend it to
anyone else. But for now, I can live with the results.

-Ben

-----Original Message-----
From: Ben Weatherall 
Sent: Friday, July 28, 2006 5:59 PM
To: 'Anthill user list'
Subject: RE: [Anthill] Schedule not working?

This is a fresh install of Anthill under SLES-9 SP2 specifically to
support Java 1.5 development. Our previous install was under Windows XP
Server and used Java 1.4.2. The schedules are new and have not been
renamed. The projects were created by first creating them with only
their name and a default schedule selection, doing an update to save,
and then iteratively editing them to set all of the rest of the
parameters. The projects were never renamed during this process.

I am wondering if there is a tomcat release level dependency here
(and/or the java version tomcat uses). Any thoughts along those lines?

-Ben

-----Original Message-----
From: anthill-bounces-IWHQxnLZ/[email protected]
[mailto:anthill-bounces-IWHQxnLZ/[email protected]] On Behalf Of Eric Minick
Sent: Friday, July 28, 2006 4:36 PM
To: Anthill user list
Subject: Re: [Anthill] Schedule not working?

The fix was referring to was the subversion specific fix in looking at
revision files that are retrieved. That fix (as I look at the stamping
history) is present in 1.8.0.297 and greater. A later patch would help
if revision history was retrieved but spaces in user names where the
problem (307 and greater).

But if the schedule is operating properly, but just not firing off the
projects associated with it, I'm just not sure what's going on. My first
guess would be that the schedule is managed largely by its name and
perhaps if its name was changed it would fail to act properly (I'd hope
that wasn't the case but I'm taking guesses).

Perhaps recreating the schedule would be helpful.

-- Eric