OK - I found the problem.
I had a bad scheduled job in the turbine scheduled job table. Once I
cleared that table things started working again.
-jeff
----- Original Message -----
From: "Jeff Owens" <[EMAIL PROTECTED]>
To: "Turbine Torque Users List" <[EMAIL PROTECTED]>
Sent: Monday, October 21, 2002 1:58 PM
Subject: Odd problem
I've been working with the scheduler service and it works fine except for 1
oddity.
I've got a screen that displays the vector of the job entries in the
scheduler. It has corresponding java screen code that gets called first.
Basically the code does this:
Vector slist = null;
try
{
ScheduleService ss =
(ScheduleService)TurbineServices.getInstance().getService(ScheduleService.SE
RVICE_NAME);
slist = ss.listJobs();
}
...
context.put("entries", slist);
...
Which works fine as long as I don't shut down. If I shutdown and restart
tomcat and my app, then - EVEN THOUGH the scheduled object runs at the
appropriate time - I don't get any list with my jobentry objects. They
still exist in the database, the schedule service just doesn't return them
in the listJobs method.
For example, I create a job and set it to run in 30 seconds. If I go in and
view the job list, I see the job. I kill my app and tomcat and restart
them. I go back in and view the job list - I don't see my job in the
joblist!! - even though its in the database - but it DOES run on time.
So how come the scheduler service isn't giving me any jobs in the joblist
but its still running them (after a shutdown and restart)?
Thanks for any help!
-jeff
--
To unsubscribe, e-mail: <mailto:turbine-torque-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:turbine-torque-user-help@;jakarta.apache.org>
