Kommentare für Pauls Blog https://sterl.org Tue, 26 Aug 2025 13:57:19 +0000 hourly 1 https://wordpress.org/?v=6.8.3 Kommentar zu Azure DevOps Function App Deployment „No package found“ von Musfirah https://sterl.org/2023/03/azure-devops-function-app-deployment-no-package-found/#comment-7290 Tue, 26 Aug 2025 13:57:19 +0000 https://sterl.org/?p=863#comment-7290 Really well explained! I appreciate the detailed walkthrough of resolving the “No package found” error in Azure DevOps Function App deployments. The step-by-step guidance on including the DownloadBuildArtifacts task and correctly structuring the YAML pipeline makes it much clearer how to manage build artifacts effectively.

]]> Kommentar zu Azure DevOps Function App Deployment „No package found“ von Musfirah https://sterl.org/2023/03/azure-devops-function-app-deployment-no-package-found/#comment-7289 Tue, 26 Aug 2025 13:55:43 +0000 https://sterl.org/?p=863#comment-7289 Great Post!

]]> Kommentar zu Useful links for Event Driven Architectures von Microservices Event- | Command- | Data-Bus | Event Driven | Pauls Blog https://sterl.org/2023/10/useful-links-for-event-driven-architectures/#comment-2644 Fri, 13 Oct 2023 08:03:18 +0000 https://sterl.org/?p=965#comment-2644 […] Useful links for Event Driven Architectures This entry was posted in   Pattern & Best Practice, Tutorials, YouTube and tagged   Command Bus, Data Bus, Event Bus, Event Driven, Microservices, software architektur, training. Bookmark the   permalink. […]

]]> Kommentar zu Quartz integration in Spring von Quartz triggers, jobs, groups and more | Pauls Blog https://sterl.org/2022/07/quartz-integration-in-spring/#comment-2041 Sun, 03 Jul 2022 12:58:22 +0000 https://sterl.org/?p=802#comment-2041 […] Setup Quartz in Spring […]

]]> Kommentar zu Quartz integration in JEE 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 […]

]]> Kommentar zu Quartz integration 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. […]

]]> Kommentar zu Quartz integration in JEE 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.

]]> Kommentar zu Quartz integration in JEE 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

]]> Kommentar zu Quartz integration in JEE 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

]]> Kommentar zu Quartz integration in JEE 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)
]]
]]>