New discovery. It does not seem to be those that had jobs scheduled for the same second after all. I changed the metadata that controls when the jobs run to prevent same second schedules. I have a total of 51 jobs that are scheduled after a particular job runs. They are staggered about 2 - 5 seconds apart. I get groupings of the time of those that fail as follows:
70 and 77 seconds after. 107 and 125 seconds after 190 and 195 seconds after 275 and 280 seconds after It is always 8 that fail to run. I can probably work around until I can get Turbine 2.2b1 running under debug to see the behaviour first hand. Thanks David -----Original Message----- From: David Wynter [mailto:[EMAIL PROTECTED]] Sent: 23 March 2002 13:08 To: Turbine-User Subject: Scheduler fails if 2 jobs scheduled for the same second I am scheduling many jobs automatically in my Turbine application and on occasion 2 get scheduled for the same second. Strictly speaking it does not fail but one of the jobs scheduled for the same second does not run and thereafter I have 100% CPU utilisation until I kill the Tomcat process. I am on W2K SP2, Sun's JVM 1.3.1 using Turbine 2.1, although I have noted that the Scheduler service class stuff had not changed in 2.2b1 I downloaded about a month ago. Any ideas. David -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
