Kommentare zu: Quartz integration in JEE https://sterl.org/2019/09/quartz-scheduler-integration-in-java-jee/ Mon, 04 Jul 2022 08:57:04 +0000 hourly 1 https://wordpress.org/?v=6.8.3 Von: Quartz triggers, jobs, groups and more | Pauls Blog https://sterl.org/2019/09/quartz-scheduler-integration-in-java-jee/#comment-2040 Sun, 03 Jul 2022 12:38:55 +0000 http://sterl.org/?p=378#comment-2040 […] Setup Quartz in JEE […]

]]> Von: Quartz integration in Spring | Pauls Blog https://sterl.org/2019/09/quartz-scheduler-integration-in-java-jee/#comment-2039 Fri, 01 Jul 2022 19:51:05 +0000 http://sterl.org/?p=378#comment-2039 […] We will use the CMT Store here, for more details because of the why please read the following tutorial. […]

]]> Von: Vladimir Schöner https://sterl.org/2019/09/quartz-scheduler-integration-in-java-jee/#comment-1883 Mon, 13 Jan 2020 16:23:49 +0000 http://sterl.org/?p=378#comment-1883 Als Antwort auf Vladimir Schöner.

For the payara version 4.1.2.191 it works fine.

]]> Von: Vladimir Schöner https://sterl.org/2019/09/quartz-scheduler-integration-in-java-jee/#comment-1882 Sun, 12 Jan 2020 19:58:29 +0000 http://sterl.org/?p=378#comment-1882 The test succeeds with payara 5.194 which is good! I have still the issue with the version 4.1.2.174. Let’s see how we solve the issue or find a workaround, since we cannot upgrade the server version in production environment.

One thing I have discovered, you use the „name“ attribute for resource annotation for the executor service. Is that what you want? Actually in this case the default executor service will be injected not the quartz executor. Please check https://github.com/payara/Payara/issues/1914

]]> Von: Paul Sterl https://sterl.org/2019/09/quartz-scheduler-integration-in-java-jee/#comment-1881 Sat, 11 Jan 2020 11:35:10 +0000 http://sterl.org/?p=378#comment-1881 Als Antwort auf Vladimir.

Interesting I would need to test it with a payara 4 // could you please give it a try with a payara 5? I added the domain.xml to git: https://github.com/sterlp/jee-quartz-integration/blob/master/src/test/resources/example-domain-payara-5.xml

]]> Von: Vladimir https://sterl.org/2019/09/quartz-scheduler-integration-in-java-jee/#comment-1880 Fri, 10 Jan 2020 18:03:20 +0000 http://sterl.org/?p=378#comment-1880 Great article, thanks!
I tried to configure payara with your quartz-jee integration example, but the thing is the executor service seems not to work properly (or my Payara configuration was wrong). Would you provide the server configuration (probably it is like in my case, payara too) ?

Actually I created the default Managed Executor Service with default values.

If you are interested in here are two Exceptions I’m getting:

[2020-01-10T17:34:04.473+0100] [Payara 4.1] [WARNING] [] [quartz.SimpleQuartzJeeThreadPool] [tid: _ThreadID=117 _ThreadName=JEE-QUARTZ_QuartzSchedulerThread] [timeMillis: 1578674044473] [levelValue: 900] [[
  blockForAvailableThreads failed to pruge queue!
java.util.concurrent.RejectedExecutionException: Task org.glassfish.enterprise.concurrent.internal.ManagedFutureTask@29a98c6c rejected from org.glassfish.enterprise.concurrent.internal.ManagedThreadPoolExecutor@20502db2[Shutting down, pool size = 2, active threads = 2, queued tasks = 0, completed tasks = 6]
	at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
	at org.glassfish.enterprise.concurrent.AbstractManagedExecutorService.executeManagedFutureTask(AbstractManagedExecutorService.java:405)
	at org.glassfish.enterprise.concurrent.AbstractManagedExecutorService.submit(AbstractManagedExecutorService.java:389)
	at org.glassfish.enterprise.concurrent.ManagedExecutorServiceAdapter.submit(ManagedExecutorServiceAdapter.java:62)
	at quartz.SimpleQuartzJeeThreadPool.blockForAvailableThreads(SimpleQuartzJeeThreadPool.java:59)
	at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:278)
]]

or

[2020-01-10T17:26:33.824+0100] [Payara 4.1] [WARNING] [] [quartz.SimpleQuartzJeeThreadPool] [tid: _ThreadID=117 _ThreadName=JEE-QUARTZ_QuartzSchedulerThread] [timeMillis: 1578673593824] [levelValue: 900] [[
  blockForAvailableThreads failed to pruge queue!
java.util.concurrent.ExecutionException: javax.enterprise.concurrent.AbortedException: Module null is disabled
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:192)
	at quartz.SimpleQuartzJeeThreadPool.blockForAvailableThreads(SimpleQuartzJeeThreadPool.java:59)
	at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:278)
Caused by: javax.enterprise.concurrent.AbortedException: Module null is disabled
	at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:146)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
	at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
]]
]]>