I'm creating an executor using:
executor = Executors.newScheduledThreadPool(0, (r) -> new Thread(r, "Scheduler"));
I'm scheduling 2 tasks, each running once then once on a daily interval
long seconds = Duration.between(now, s.scheduledRunTime).getSeconds();
if (seconds <= 0) {
seconds += TimeUnit.DAYS.toSeconds(1);
}
LOG.info("Scheduling " + s.target + " to run immediately and then every day at " + s.scheduledRunTime + " (first " + seconds + " seconds from now)");
executor.execute(() -> execute(s));
executor.scheduleAtFixedRate(() -> execute(s), seconds, TimeUnit.DAYS.toSeconds(1), TimeUnit.SECONDS);
The tasks perform their initial run correctly, I can see in the logs that they've started and completed in a reasonable timeframe. (One takes 39 seconds, one 16 seconds if it matters).
The tasks also perform their scheduled run correctly if I wait for the time.
Everything works fine on my Windows development environment (JavaSE-1.8 (jdk1.8.0_45) from Eclipse), however once deployed to Linux running on Java 1.8.0_40 I see the thread called Scheduler spinning on 100% CPU permanently.
I've not tried to shutdown the scheduler (research showed that during shutdown this sometimes happened but that isn't the case here).
The stack trace is:
Thread[Scheduler,5,app] RUNNABLE
CPU (msecs) = 15020099
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.poll(ScheduledThreadPoolExecutor.java:809)
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
java.lang.Thread.run(Thread.java:745)
Does anyone know what is causing this thread to spin using 100% CPU?
I've tried refreshing many times and the stack trace never shows anything other than the above.
