fix http-push-connection-dispatcher config overrides

properties were not in the right place and the config was defaulting to https://github.com/apache/pekko/blob/2469f729f7503acf814bcbd042b4bb0863103c9d/actor/src/main/resources/reference.conf#L506

Signed-off-by: Aleksandar Stanchev <aleksandar.stanchev@bosch.com>

Author: alstanchev

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

@@ -1329,11 +1329,18 @@ 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 {
+    core-pool-size-factor = 4
+    core-pool-size-factor = ${?HTTP_PUSH_CORE_POOL_SIZE_FACTOR}
+    core-pool-size-max = 64,
+    core-pool-size-max = ${?HTTP_PUSH_CORE_POOL_SIZE_MAX}
+    max-pool-size-min= 64,
+    max-pool-size-min= ${?HTTP_PUSH_CORE_POOL_SIZE_MAX}    # Overriding with the value of HTTP_PUSH_CORE_POOL_SIZE_MAX as if threads are a reason for http problems the pool normaly doesn't grow on its own so
+    # it is better to set the core upper limit manualy and this config will forse the core pool size to this value.
+    max-pool-size-max = 2147483647,
+    allow-core-timeout = on  # Enables timeout of core threads
+  }
 }
 
 kafka-consumer-dispatcher {