pmoneoingen / myschedule

Automatically exported from code.google.com/p/myschedule
0 stars 0 forks source link

My job is pending even if it is finished in 'Jobs currently executing by scheduler' menu #85

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. It seems that My job was pending for 25 hours due to some reason. 
Because my log file is switched every day by using DailyAppender in log4j . But 
I'm not sure it was pending 25hours or 1hours .
I think it try to connect database resource but it neither return or throw 
exception for some hours.
2. Anyway as you see in log file , I saw an exception in another logfile 
(batch.log.2012-04-26),
it printed the stackTrace
3.
This is  code snippet of dao where the code print exception.
        }catch (Exception e){
            log.info(" --> Fail");
            log.error("Exception in UPSERT the records!,e);
            e.printStackTrace();
            return -1;
        }
Anyway, it was finished   because it doesn't throw exception.
But as you see the screenshot, my job is pending and the next job cannot be 
executed.
Why the executed job is not disappeared .
Is there any way to get rid of this instance so that the next job can be 
executed.

Original issue reported on code.google.com by james.yo...@gmail.com on 26 Apr 2012 at 7:53

Attachments:

GoogleCodeExporter commented 9 years ago
I would not able to help you with what you given. If you think it's a Quartz 
issue itself, you can try their forum for support. If you think it's MySchedule 
issue, you can post more information here. In any case, you would want to post 
your quartz.properties content and your full code on how you scheduled the jobs.

Original comment by saltnlight5 on 27 Apr 2012 at 1:37

GoogleCodeExporter commented 9 years ago
Pls provide further info if you cont having problem. Else I will close this.

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

GoogleCodeExporter commented 9 years ago
Not enough info to debug.

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

GoogleCodeExporter commented 9 years ago

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