TeslaCN opened a new issue #1052:
URL: https://github.com/apache/shardingsphere-elasticjob-lite/issues/1052


   ## Bug Report
   
   **For English only**, other languages will not accept.
   
   Before report a bug, make sure you have:
   
   - Searched open and closed [GitHub 
issues](https://github.com/apache/shardingsphere-elastic-job-lite/issues).
   - Read documentation: [ElasticJob 
Doc](http://shardingsphere.apache.org/elasticjob/docs/elastic-job-lite/00-overview/).
   
   Please pay attention on issues you submitted, because we maybe need more 
details. 
   If no response anymore and we cannot reproduce it on current information, we 
will **close it**.
   
   Please answer these questions before submitting your issue. Thanks!
   
   ### Which version of ElasticJob did you use?
   Branch - master
   
   ### Which project did you use? ElasticJob-Lite or ElasticJob-Cloud?
   ElasticJob-Lite
   
   ### Expected behavior
   
   ### Actual behavior
   ```
   [ERROR] 2020-07-14 08:31:00,033 --simpleJob_Worker-1-- 
[org.apache.shardingsphere.elasticjob.infra.handler.error.impl.LogJobErrorHandler]
 Job 'simpleJob' exception occur in job processing 
   
org.apache.shardingsphere.elasticjob.infra.exception.JobExecutionEnvironmentException:
 Time different between job server and register center exceed '0' seconds, max 
time different is '0' seconds.
        at 
org.apache.shardingsphere.elasticjob.lite.internal.config.ConfigurationService.checkMaxTimeDiffSecondsTolerable(ConfigurationService.java:103)
 ~[classes/:na]
        at 
org.apache.shardingsphere.elasticjob.lite.internal.schedule.LiteJobFacade.checkJobExecutionEnvironment(LiteJobFacade.java:81)
 ~[classes/:na]
        at 
org.apache.shardingsphere.elasticjob.executor.ElasticJobExecutor.execute(ElasticJobExecutor.java:85)
 ~[classes/:na]
        at 
org.apache.shardingsphere.elasticjob.lite.internal.schedule.LiteJob.execute(LiteJob.java:52)
 [classes/:na]
        at org.quartz.core.JobRunShell.run(JobRunShell.java:202) 
[quartz-2.3.2.jar:na]
        at 
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) 
[quartz-2.3.2.jar:na]
   [ERROR] 2020-07-14 08:31:00,043 --scriptJob_Worker-1-- 
[org.apache.shardingsphere.elasticjob.infra.handler.error.impl.LogJobErrorHandler]
 Job 'scriptJob' exception occur in job processing 
   
org.apache.shardingsphere.elasticjob.infra.exception.JobExecutionEnvironmentException:
 Time different between job server and register center exceed '0' seconds, max 
time different is '0' seconds.
        at 
org.apache.shardingsphere.elasticjob.lite.internal.config.ConfigurationService.checkMaxTimeDiffSecondsTolerable(ConfigurationService.java:103)
 ~[classes/:na]
        at 
org.apache.shardingsphere.elasticjob.lite.internal.schedule.LiteJobFacade.checkJobExecutionEnvironment(LiteJobFacade.java:81)
 ~[classes/:na]
        at 
org.apache.shardingsphere.elasticjob.executor.ElasticJobExecutor.execute(ElasticJobExecutor.java:85)
 ~[classes/:na]
        at 
org.apache.shardingsphere.elasticjob.lite.internal.schedule.LiteJob.execute(LiteJob.java:52)
 [classes/:na]
        at org.quartz.core.JobRunShell.run(JobRunShell.java:202) 
[quartz-2.3.2.jar:na]
        at 
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) 
[quartz-2.3.2.jar:na]
   
   ```
   
   ### Reason analyze (If you can)
   The default value of `maxTimeDiffSeconds` is `-1` in 
`JobConfiguration.Builder`. If `JobConfigurationPojo` missing default value, it 
would be set to `0` and ERROR occurred.
   
   ### Steps to reproduce the behavior.
   Using `JobConfigurationPOJO.toJobConfiguration()` to create a instance of 
`JobConfiguration`. Then create a instance of `ScheduleJobBootstrap` and start 
scheduling.
   
   ### Example codes for reproduce this issue (such as a github link).
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to