We need to increase the “setMaxConnPerRoute” of the “http-connector” Camunda connector. We have read through the “HTTP Connector”, “Extending Connect”, and “Camunda Connector Reference” documents as well as examining the Camunda connect code on Github.
We cannot figure out how you actually use the custom configurator such that when processes are executing and more than five (5) of them are connected to the same route (URL) the processes don’t lock up. This “condition” renders the Camunda server unusable until the underlying JVM is restarted.
We have tried putting the custom configurator jar file into a process deployment war file We have tried putting the jar down in the WildFly modules directories.
We need step-by-step instructions on how this is done for a SHARED Camunda engine, please.
We are using Camunda 7.6.2-ee and WildFly 10.1.