Fork me on GitHub
#immutant
<
2018-06-19
>
a.espolov12:06:02

1. Created Wildfly cluster 2. On master server in host. xml Left one server using full-ha profile 3. Added a couple of changes to Feautre-Demo - singleton-daemon - (sch/schedule # (println "Singleton schedule run ") :id "singleton-runner1 " :every [10 :seconds] :singleton true) but unfortunately singleton-daemon and schedule are run on all nodes On each node, when the application is deployed to the log, I see these messages: - [Server: S1. Master] 12:18:46,353 INFO [org. quartz. Core. Quartzscheduler] (wunderboss-Daemon-thread [runner1]) Scheduler meta-data: Quartz Scheduler (v 2.2.1) ' Simplequartzscheduler:-1011881444 ' with InstanceId ' simple_non_clustered:- 1011881444 ' - [Server: S1. Node1] 12:18:46,379 INFO [org. quartz. Core. Quartzscheduler] (wunderboss-Daemon-thread [runner1]) Scheduler meta-data: Quartz Scheduler (v 2.2.1) ' Simplequartzscheduler:-1011881444 ' with InstanceId ' simple_non_clustered:- 1011881444 ' - [Server: S1. Node2] 12:18:46,364 INFO [org. quartz. Core. Quartzscheduler] (wunderboss-Daemon-thread [runner1]) Scheduler meta-data: Quartz Scheduler (v 2.2.1) ' Simplequartzscheduler:-1011881444 ' with InstanceId ' simple_non_clustered:- 1011881444 ' wildfly-10.1.0 Suspect something is wrong with the cluster, maybe need additional configuration of full-ha profile?

a.espolov13:06:50

@jcrossley3 I understood correctly that I need to configure Quartz to use not RAMjob, and JDBCJobStore