I am trying to configure a cluster of Jboss servers (7.1.1.Final) with mod_cluster 1.2.I am able to achieve e.g. 600 http requests/second on a single jboss instance (requests sent directly to this instance) but with mod_cluster it never goes better than e.g. 200 req/sec but only for a minute. Then the performance degrades.I have 4 instances of jboss in a cluster. RAM and CPU is no issue.

Hi AJ, I don't find anything obviously wrong with your configuration at first sight, but for the very high max-connections="20000", if you are not running a real many-cores beast, it may actually make the performance worse. I do not have any decent performance-oriented domain configuration on my hand at the moment, nor I have any perf-setup running with advertise-security-key and busyness load metric as it is in your case. Anyhow, I can show you a config that has a pretty decent performance. In order to help you further though, I would need to know what exactly you are testing - e.g. is there session replication going on? I guess so. Does session stickiness work properly (no unnecessary digging session data up from other nodes)? What does your test-servlet (app) look like? What OS do you use?

thank you for those tips. It worked much better this time. I changed the load metric, removed security key, connector="ajp" in mod-cluster-config was not accepted on my version of the server. But those lines in the Apache configuration did the trick for testing:

MaxKeepAliveRequests 0KeepAlive OnKeepAliveTimeout 300

This is a POC application that is exposing rest web services and does some simple EJB/JPA logic behind that, no session replication is needed. 20000 is the target max capacity, but I could reach over 1000 req/sec which is satisfactory for now and this PoC. It looks like this is all about httpd tuning this time.However, sorry to say, I am unable to perform more tests right now as I am expected to 'return' blades tomorrow...