We have a large application that is completely schedule driven. We use the varia scheduler to run the schedules. We do very verbose logging; at the bottom of this note is a snippet from yesterday. Notice that it took a 4 1/2 hr break starting at 16:25. This most certainly is not appropriate. We have schedules that go off every 5 minutes and others that go off every 15 minutes. The line at 20:00:17 is actually the termination of a method that started 3 hrs earlier, so really the shedulers didn't start working again until 21:09.
Are there known issues with the varia scheduler not running schedules for long periods of time? Would it be better for me to switch to Quartz? 2006-01-17 16:25:27,024 INFO [FileGroupLockMonitor] readDirectory Thread 106107: Thread[Timer-1939,5,jboss] Directory: /data/java/rodent/alcatelFiles/unprocessed pattern: act.*\.xml\.gz 2006-01-17 16:25:27,026 INFO [FileTxrCollectorTimetra] FileTxrCollectorTimetra.getStats(): elapsed time in seconds => 524.0 2006-01-17 20:00:17,304 INFO [RodentBean] beginning date Mon Jan 16 00:00:00 GMT 2006, end date Tue Jan 17 00:00:00 GMT 2006 2006-01-17 21:09:45,029 INFO [SNMPCollectorSummit] polled all devices 2006-01-17 21:09:45,034 INFO [FileGroupLockMonitor] readDirectory Thread 36: Thread[Timer-3,5,jboss] Directory: /data/java/rodent/alcatelFiles/unprocessed pattern: act.*\.xml\.gz View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918197#3918197 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918197 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
