Merge pull request #2139 from bosch-io/bugfix/http-dispatcher-config

fix http-push-connection-dispatcher config overrides

Author: alstanchev

connectivity/service/src/main/resources/connectivity.conf

@@ -1329,11 +1329,31 @@ http-push-connection-dispatcher {
   # This executor is meant to be allowed to grow quite big as its limited by the max parallelism of each http connection client.
   # Limit this parallelism here additionally could lead to confusing results regarding througput of some http connections.
   # The core-pool-size-min remains unchanged so its quite small (8). Unused threads will expire after 60s.
-  core-pool-size-factor = 2147483647
-  core-pool-size-factor = ${?HTTP_PUSH_CORE_POOL_SIZE_FACTOR}
 
-  core-pool-size-max = 2147483647
-  core-pool-size-max = ${?HTTP_PUSH_CORE_POOL_SIZE_MAX}
+  thread-pool-executor {
+    # The core-pool-size-factor is used to determine corePoolSize of the
+    # ThreadPoolExecutor using the following formula:
+    # ceil(available processors * factor).
+    # Resulting size is then bounded by the core-pool-size-min and
+    # core-pool-size-max values.
+    # Increasing can help aleviate errors of type "Dropped message as result of backpressure strategy!" during high load.
+    core-pool-size-factor = 4
+    core-pool-size-factor = ${?HTTP_PUSH_CORE_POOL_SIZE_FACTOR}
+    # Max number of threads to cap factor-based corePoolSize number to
+    core-pool-size-max = 64
+    core-pool-size-max = ${?HTTP_PUSH_CORE_POOL_SIZE_MAX}
+    # Minimum number of threads to cap factor-based maximumPoolSize number to
+    max-pool-size-min= 64
+    max-pool-size-min= ${?HTTP_PUSH_POOL_SIZE_MAX}
+    # Max number of threads to cap factor-based maximumPoolSize number to
+    max-pool-size-max = 512
+    max-pool-size-max= ${?HTTP_PUSH_POOL_SIZE_MAX}
+
+    # Allow core threads to time out
+    allow-core-timeout = on
+    # Keep alive time for threads
+    keep-alive-time = 60s
+  }
 }
 
 kafka-consumer-dispatcher {