We would like to be able to control the number of concurrent threads in HTTP based bindings (at least SOAP and REST) in the same way as they can be controlled in JMS bindings through the consumer limits.
The business requirement is that we need to be able to protect our own application from overload, but also to be able to control the number of connections we open towards external systems. We can of course do this already now, but then we have to apply the same limit for all our services including those that don't need to connect to any external system.
Would this be possible?
Red Hat JBoss Fuse Service Works 6.0.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.