用的是 vue版本自带 定时任务模块添加的 0 0/2 * * * ? 两分钟执行一次也是会有这样的问题 执行两次 就不动了

定时任务类

package cn.wizzer.app.task.commons.ext.quartz.job;

import cn.wizzer.app.sys.modules.services.SysTaskService;
import cn.wizzer.gr.modules.services.msg.BusMsgService;
import com.alibaba.dubbo.config.annotation.Reference;
import org.nutz.ioc.loader.annotation.Inject;
import org.nutz.ioc.loader.annotation.IocBean;
import org.nutz.log.Log;
import org.nutz.log.Logs;
import org.quartz.Job;
import org.quartz.JobExecutionContext;
import org.quartz.JobExecutionException;

/**
 * 处理消息 任务
 */
@IocBean
public class BusMsgJob implements Job {

    private static final Log log = Logs.get();
    @Inject
    @Reference
    private BusMsgService busMsgService;

    @Inject
    @Reference
    protected SysTaskService sysTaskService;


    public void execute(JobExecutionContext context) throws JobExecutionException {
//        JobDataMap data = context.getJobDetail().getJobDataMap();
//        String taskId = context.getJobDetail().getKey().getName();
//        String hi = data.getString("hi");

        log.info("处理消息 任务开始");
        try{
            //busMsgService.executeBusMsg();
//            sysTaskService.update(Chain.make("exeAt", (int) (System.currentTimeMillis() / 1000)).add("exeResult", "执行成功"), Cnd.where("id", "=", taskId));
            log.info("处理消息 任务结束");
        }catch (Exception e){
            log.error("处理消息 任务出错:",e);
        }
    }

}

是集群 但是我就启动了一个 而且后面 这个实例就一直都没有执行了
集群根据什么唯一呢? 我改改 看看有没有

quartz.jobStore.isClustered = true

好的 我试试 但是我还是想知道 他是根据zookeeper来实现集群的吗? 我同一个 zookeeper只有一个任务实例

3秒一次 22:22开始 差不多 10多钟 也不动了

[INFO ] 2019-02-18 22:34:45.123 cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob.execute(BusMsgJob.java:35) - 处理消息 任务开始
[INFO ] 2019-02-18 22:34:45.123 cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob.execute(BusMsgJob.java:39) - 处理消息 任务结束
[INFO ] 2019-02-18 22:34:45.123 org.quartz.plugins.history.LoggingJobHistoryPlugin.jobWasExecuted(LoggingJobHistoryPlugin.java:513) - Job 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a execution complete at  22:34:45 02/18/2019 and reports: null
[DEBUG] 2019-02-18 22:34:45.124 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:81) - Lock 'TRIGGER_ACCESS' is desired by: defaultScheduler_Worker-1
[DEBUG] 2019-02-18 22:34:45.124 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:88) - Lock 'TRIGGER_ACCESS' is being obtained: defaultScheduler_Worker-1
[DEBUG] 2019-02-18 22:34:45.124 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:105) - Lock 'TRIGGER_ACCESS' given to: defaultScheduler_Worker-1
[DEBUG] 2019-02-18 22:34:45.172 org.quartz.impl.jdbcjobstore.SimpleSemaphore.releaseLock(SimpleSemaphore.java:132) - Lock 'TRIGGER_ACCESS' retuned by: defaultScheduler_Worker-1
[DEBUG] 2019-02-18 22:34:45.229 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 1 triggers
[DEBUG] 2019-02-18 22:34:48.006 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:81) - Lock 'TRIGGER_ACCESS' is desired by: defaultScheduler_QuartzSchedulerThread
[DEBUG] 2019-02-18 22:34:48.007 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:88) - Lock 'TRIGGER_ACCESS' is being obtained: defaultScheduler_QuartzSchedulerThread
[DEBUG] 2019-02-18 22:34:48.007 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:105) - Lock 'TRIGGER_ACCESS' given to: defaultScheduler_QuartzSchedulerThread
[DEBUG] 2019-02-18 22:34:48.121 org.quartz.impl.jdbcjobstore.SimpleSemaphore.releaseLock(SimpleSemaphore.java:132) - Lock 'TRIGGER_ACCESS' retuned by: defaultScheduler_QuartzSchedulerThread
[DEBUG] 2019-02-18 22:34:48.128 org.nutz.ioc.impl.NutIoc.get(NutIoc.java:166) - Get 'busMsgJob'<class cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob>
[INFO ] 2019-02-18 22:34:48.128 org.quartz.plugins.history.LoggingJobHistoryPlugin.jobToBeExecuted(LoggingJobHistoryPlugin.java:469) - Job 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a fired (by trigger 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a) at:  22:34:48 02/18/2019
[DEBUG] 2019-02-18 22:34:48.128 org.quartz.core.JobRunShell.run(JobRunShell.java:201) - Calling execute on job 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a
[INFO ] 2019-02-18 22:34:48.128 cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob.execute(BusMsgJob.java:35) - 处理消息 任务开始
[INFO ] 2019-02-18 22:34:48.128 cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob.execute(BusMsgJob.java:39) - 处理消息 任务结束
[INFO ] 2019-02-18 22:34:48.129 org.quartz.plugins.history.LoggingJobHistoryPlugin.jobWasExecuted(LoggingJobHistoryPlugin.java:513) - Job 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a execution complete at  22:34:48 02/18/2019 and reports: null
[DEBUG] 2019-02-18 22:34:48.129 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:81) - Lock 'TRIGGER_ACCESS' is desired by: defaultScheduler_Worker-2
[DEBUG] 2019-02-18 22:34:48.129 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:88) - Lock 'TRIGGER_ACCESS' is being obtained: defaultScheduler_Worker-2
[DEBUG] 2019-02-18 22:34:48.129 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:105) - Lock 'TRIGGER_ACCESS' given to: defaultScheduler_Worker-2
[DEBUG] 2019-02-18 22:34:48.176 org.quartz.impl.jdbcjobstore.SimpleSemaphore.releaseLock(SimpleSemaphore.java:132) - Lock 'TRIGGER_ACCESS' retuned by: defaultScheduler_Worker-2
[DEBUG] 2019-02-18 22:34:48.365 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:34:53.947 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012b after 1ms
[DEBUG] 2019-02-18 22:35:07.287 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012b after 0ms
[DEBUG] 2019-02-18 22:35:11.864 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:35:20.624 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012b after 1ms
[DEBUG] 2019-02-18 22:35:29.151 com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:74) -  [DUBBO] Received heartbeat from remote channel /192.168.1.3:60271, cause: The channel has no data-transmission exceeds a heartbeat period: 60000ms, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:35:30.016 com.alibaba.dubbo.remoting.exchange.support.header.HeartBeatTask.run(HeartBeatTask.java:66) -  [DUBBO] Send heartbeat to remote channel /192.168.1.3:12153, cause: The channel has no data-transmission exceeds a heartbeat period: 60000ms, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:35:30.017 com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:84) -  [DUBBO] Receive heartbeat response in thread New I/O client worker #1-1, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:35:33.961 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012b after 0ms
[DEBUG] 2019-02-18 22:35:39.639 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:35:47.296 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012b after 1ms
[DEBUG] 2019-02-18 22:36:00.632 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012b after 1ms
[DEBUG] 2019-02-18 22:36:09.509 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:36:13.969 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012b after 1ms
[DEBUG] 

还是这样\\

22:55:45.098 cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob.execute(BusMsgJob.java:35) - 处理消息 任务开始
[INFO ] 2019-02-18 22:55:45.098 cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob.execute(BusMsgJob.java:39) - 处理消息 任务结束
[INFO ] 2019-02-18 22:55:45.098 org.quartz.plugins.history.LoggingJobHistoryPlugin.jobWasExecuted(LoggingJobHistoryPlugin.java:513) - Job 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a execution complete at  22:55:45 02/18/2019 and reports: null
[DEBUG] 2019-02-18 22:55:45.098 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:81) - Lock 'TRIGGER_ACCESS' is desired by: defaultScheduler_Worker-2
[DEBUG] 2019-02-18 22:55:45.098 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:88) - Lock 'TRIGGER_ACCESS' is being obtained: defaultScheduler_Worker-2
[DEBUG] 2019-02-18 22:55:45.099 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:105) - Lock 'TRIGGER_ACCESS' given to: defaultScheduler_Worker-2
[DEBUG] 2019-02-18 22:55:45.138 org.quartz.impl.jdbcjobstore.SimpleSemaphore.releaseLock(SimpleSemaphore.java:132) - Lock 'TRIGGER_ACCESS' retuned by: defaultScheduler_Worker-2
[DEBUG] 2019-02-18 22:55:45.229 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 1 triggers
[DEBUG] 2019-02-18 22:55:48.002 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:81) - Lock 'TRIGGER_ACCESS' is desired by: defaultScheduler_QuartzSchedulerThread
[DEBUG] 2019-02-18 22:55:48.002 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:88) - Lock 'TRIGGER_ACCESS' is being obtained: defaultScheduler_QuartzSchedulerThread
[DEBUG] 2019-02-18 22:55:48.002 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:105) - Lock 'TRIGGER_ACCESS' given to: defaultScheduler_QuartzSchedulerThread
[DEBUG] 2019-02-18 22:55:48.937 org.quartz.impl.jdbcjobstore.SimpleSemaphore.releaseLock(SimpleSemaphore.java:132) - Lock 'TRIGGER_ACCESS' retuned by: defaultScheduler_QuartzSchedulerThread
[DEBUG] 2019-02-18 22:55:50.616 org.nutz.ioc.impl.NutIoc.get(NutIoc.java:166) - Get 'busMsgJob'<class cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob>
[INFO ] 2019-02-18 22:55:50.616 org.quartz.plugins.history.LoggingJobHistoryPlugin.jobToBeExecuted(LoggingJobHistoryPlugin.java:469) - Job 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a fired (by trigger 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a) at:  22:55:50 02/18/2019
[DEBUG] 2019-02-18 22:55:50.616 org.quartz.core.JobRunShell.run(JobRunShell.java:201) - Calling execute on job 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a
[INFO ] 2019-02-18 22:55:50.616 cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob.execute(BusMsgJob.java:35) - 处理消息 任务开始
[INFO ] 2019-02-18 22:55:50.616 cn.wizzer.app.task.commons.ext.quartz.job.BusMsgJob.execute(BusMsgJob.java:39) - 处理消息 任务结束
[INFO ] 2019-02-18 22:55:50.616 org.quartz.plugins.history.LoggingJobHistoryPlugin.jobWasExecuted(LoggingJobHistoryPlugin.java:513) - Job 14c4ffc8d9ab4f1ca6613746f009fe6a.14c4ffc8d9ab4f1ca6613746f009fe6a execution complete at  22:55:50 02/18/2019 and reports: null
[DEBUG] 2019-02-18 22:55:50.616 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:81) - Lock 'TRIGGER_ACCESS' is desired by: defaultScheduler_Worker-1
[DEBUG] 2019-02-18 22:55:50.616 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:88) - Lock 'TRIGGER_ACCESS' is being obtained: defaultScheduler_Worker-1
[DEBUG] 2019-02-18 22:55:50.616 org.quartz.impl.jdbcjobstore.SimpleSemaphore.obtainLock(SimpleSemaphore.java:105) - Lock 'TRIGGER_ACCESS' given to: defaultScheduler_Worker-1
[DEBUG] 2019-02-18 22:55:50.675 org.quartz.impl.jdbcjobstore.SimpleSemaphore.releaseLock(SimpleSemaphore.java:132) - Lock 'TRIGGER_ACCESS' retuned by: defaultScheduler_Worker-1
[DEBUG] 2019-02-18 22:55:50.687 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:55:51.676 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 0ms
[DEBUG] 2019-02-18 22:56:05.011 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 1ms
[DEBUG] 2019-02-18 22:56:18.291 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:56:18.347 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 1ms
[DEBUG] 2019-02-18 22:56:20.817 com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:74) -  [DUBBO] Received heartbeat from remote channel /192.168.1.3:52010, cause: The channel has no data-transmission exceeds a heartbeat period: 60000ms, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:56:21.177 com.alibaba.dubbo.remoting.exchange.support.header.HeartBeatTask.run(HeartBeatTask.java:66) -  [DUBBO] Send heartbeat to remote channel /192.168.1.3:12153, cause: The channel has no data-transmission exceeds a heartbeat period: 60000ms, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:56:21.177 com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:84) -  [DUBBO] Receive heartbeat response in thread New I/O client worker #1-1, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:56:31.123 org.quartz.impl.jdbcjobstore.JobStoreSupport$MisfireHandler.manage(JobStoreSupport.java:3995) - MisfireHandler: scanning for misfires...
[DEBUG] 2019-02-18 22:56:31.684 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 0ms
[DEBUG] 2019-02-18 22:56:32.831 org.quartz.impl.jdbcjobstore.JobStoreSupport.doRecoverMisfires(JobStoreSupport.java:3244) - Found 0 triggers that missed their scheduled fire-time.
[DEBUG] 2019-02-18 22:56:45.020 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 1ms
[DEBUG] 2019-02-18 22:56:46.271 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:56:58.358 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 1ms
[DEBUG] 2019-02-18 22:57:09.368 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:57:11.692 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 0ms
[DEBUG] 2019-02-18 22:57:20.817 com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:74) -  [DUBBO] Received heartbeat from remote channel /192.168.1.3:52010, cause: The channel has no data-transmission exceeds a heartbeat period: 60000ms, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:57:21.178 com.alibaba.dubbo.remoting.exchange.support.header.HeartBeatTask.run(HeartBeatTask.java:66) -  [DUBBO] Send heartbeat to remote channel /192.168.1.3:12153, cause: The channel has no data-transmission exceeds a heartbeat period: 60000ms, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:57:21.179 com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:84) -  [DUBBO] Receive heartbeat response in thread New I/O client worker #1-1, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:57:25.031 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 1ms
[DEBUG] 2019-02-18 22:57:34.765 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:57:38.369 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 0ms
[DEBUG] 2019-02-18 22:57:51.702 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 0ms
[DEBUG] 2019-02-18 22:58:00.370 org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:291) - batch acquisition of 0 triggers
[DEBUG] 2019-02-18 22:58:05.037 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 1ms
[DEBUG] 2019-02-18 22:58:18.371 org.apache.zookeeper.ClientCnxn$SendThread.readResponse(ClientCnxn.java:745) - Got ping response for sessionid: 0x100000e6575012c after 1ms
[DEBUG] 2019-02-18 22:58:20.823 com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:74) -  [DUBBO] Received heartbeat from remote channel /192.168.1.3:52010, cause: The channel has no data-transmission exceeds a heartbeat period: 60000ms, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:58:21.184 com.alibaba.dubbo.remoting.exchange.support.header.HeartBeatTask.run(HeartBeatTask.java:66) -  [DUBBO] Send heartbeat to remote channel /192.168.1.3:12153, cause: The channel has no data-transmission exceeds a heartbeat period: 60000ms, dubbo version: 2.6.5, current host: 192.168.1.3
[DEBUG] 2019-02-18 22:58:21.186 com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:84) -  [DUBBO] Receive heartbeat response in thread New I/O client worker #1-1, dubbo version: 2.6.5, current host: 192.168.1.3

public void execute(JobExecutionContext context) throws JobExecutionException {
//        JobDataMap data = context.getJobDetail().getJobDataMap();
//        String taskId = context.getJobDetail().getKey().getName();
//        String hi = data.getString("hi");

        log.info("处理消息 任务开始");
        try{
            //busMsgService.executeBusMsg();
//            sysTaskService.update(Chain.make("exeAt", (int) (System.currentTimeMillis() / 1000)).add("exeResult", "执行成功"), Cnd.where("id", "=", taskId));
            log.info("处理消息 任务结束");
        }catch (Exception e){
            log.error("处理消息 任务出错:",e);
        }catch (Throwable e){
            log.error("处理消息 任务出错2:",e);
        }
    }

是这样的 我远程有个实例 和我本地的实例看的库是一样的 我把远程的停掉后 就正常了 所以说是以库里的唯一咯

我前面以为他是根据zookeper 来通信唯一的 原来是根据库来的\\