Darn, this is happening much more frequently than I realized:
2006-01-21 10:56:31,895 INFO [FileTxrCollectorTimetra]
FileTxrCollectorTimetra.getStats(): elapsed time in seconds => 6986.0
2006-01-21 15:23:34,992 INFO [RodentBean] beginning date Fri Jan 20 00:00:00
GMT 2006, end date Sat Jan 21 00:00:00 GMT 2006
2006-01-21 17:24:16,975 INFO [SNMPCollectorSummit] polled all devices
The job above that finished at 15:23:34 was started at 2006-01-21 10:25:10,306,
even though the schedule for it looks like this:
1/21/2005 3:00 AM
86400000
-1
Is this because the "next" iteration starts 86400000 milliseconds after the
previous iteration terminates? Should I rearrange the logic so that the MBean
method just starts up a thread and returns immediately? I think this is what
you were suggesting. I'm gathering that having an MBean method take 5 hrs to
complete is not a good thing.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3918893#3918893
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3918893
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
