my trigger shows misfired sometimes and never trigger again.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run my job with  db jobstorage and trigger every hour
2. it is  working for a few hours   but  suddenly only get misfired event every 
one minute and never run my job again.
3.

What is the expected output? What do you see instead?
My job should be run every hours.

Please use labels and text to provide additional information.
use oracle and weblogic. myschedule 2.4.2

This is the log of my job history which are recored by JdbcJobHistoryPlugin
50   
    DatabaseClusteredScheduler_$_NON_CLUSTERED  TriggerListener triggerMisfired 03/2
9/12 14:07:35   trigger.mycron  
51   
    DatabaseClusteredScheduler_$_NON_CLUSTERED  TriggerListener triggerMisfired 03/2
9/12 14:07:34   trigger.mycron  
52   
    DatabaseClusteredScheduler_$_NON_CLUSTERED  TriggerListener triggerMisfired 03/2
9/12 14:06:34   trigger.mycron  
53   
    DatabaseClusteredScheduler_$_NON_CLUSTERED  TriggerListener triggerMisfired 03/2
9/12 14:05:35   trigger.mycron  
54   
    DatabaseClusteredScheduler_$_NON_CLUSTERED  TriggerListener triggerMisfired 03/2
9/12 14:04:34   trigger.mycron  
55   
    DatabaseClusteredScheduler_$_NON_CLUSTERED  TriggerListener triggerMisfired 03/2
9/12 14:02:35   trigger.mycron  
56   
    DatabaseClusteredScheduler_$_NON_CLUSTERED  TriggerListener triggerMisfired 03/2
9/12 14:01:34   trigger.mycron  

Original issue reported on code.google.com by james.yo...@gmail.com on 29 Mar 2012 at 12:53

[GoogleCodeExporter]

I loaded my job with xml and I coulnd't find how to set misfire policy for my 
trigger.

Original comment by james.yo...@gmail.com on 29 Mar 2012 at 12:54

[GoogleCodeExporter]

Hum.. it's hard to tell what you have given. You would need to show your quartz 
config. Can you turn on logging and show that as well? Both quartz and 
myschedule has log level you may adjust.

Original comment by saltnlight5 on 6 Apr 2012 at 1:17

[GoogleCodeExporter]

Hi do you still having issue with this?

Original comment by saltnlight5 on 1 Jun 2012 at 2:41

[GoogleCodeExporter]

I couldn't  find the reason this misfired trigger happens and now I just switch 
back to my previous way of scheduling. Because this scheduler should be very 
stable and there shouldn't be any misfired job.
I'm using the way below and it's working well even though there's no front end 
for manage this scheduler.

import org.springframework.context.support.ClassPathXmlApplicationContext;
public class QuartzMain {
        public static void main( String[] args ) throws Exception
    {
        new ClassPathXmlApplicationContext("myJob.xml ");
    }
}

Original comment by james.yo...@gmail.com on 1 Jun 2012 at 7:16

[GoogleCodeExporter]

Hi, sorry to hear that you having trouble with myschedule. Let me know when you 
have time to troubleshoot again then.

I will close with not enough info to reproduce.

Original comment by saltnlight5 on 1 Jun 2012 at 5:07

• Changed state: WontFix

[GoogleCodeExporter]

Original comment by saltnlight5 on 3 Jun 2012 at 1:34

• Added labels: Release-2.4.3