QuartzInitializationHelper: TODO about potential conn pool size setting

Evolveum · Oct 8, 2021 · 371fa05 · 371fa05
1 parent a7db70a
commit 371fa05
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/...rc/main/java/com/evolveum/midpoint/task/quartzimpl/quartz/QuartzInitializationHelper.java b/...rc/main/java/com/evolveum/midpoint/task/quartzimpl/quartz/QuartzInitializationHelper.java
@@ -86,6 +86,9 @@ public void initializeScheduler() throws TaskManagerInitializationException {
                 quartzProperties.put("org.quartz.dataSource." + myDs + ".URL", configuration.getJdbcUrl());
                 quartzProperties.put("org.quartz.dataSource." + myDs + ".user", configuration.getJdbcUser());
                 quartzProperties.put("org.quartz.dataSource." + myDs + ".password", configuration.getJdbcPassword());
+                // TODO if we want to manage connections? find out whether we really need connection pool size of thread pool + 3
+                //  as documented: http://www.quartz-scheduler.org/documentation/quartz-2.3.0/configuration/ConfigDataSources.html
+//                quartzProperties.put("org.quartz.dataSource." + myDs + ".maxConnections", configuration.getThreads() + CONNECTIONS_THREAD_OFFSET);
             }
 
             quartzProperties.put("org.quartz.jobStore.isClustered", configuration.isClustered() ? "true" : "false");