Load Balancer Configuration Tool

Updated -

This tool is designed to help you create an optimal configuration for apache-based load balancers and JBoss/Tomcat application servers. Input information about your current or planned deployment to generate configurations and advice about how you can increase your servers' performance.

On the presented form fill out the Apache MPM type and Module, then pick the JBoss version and example configuration files will be presented.

You can change all of the form inputs and see instant updates to the configuration examples.

Was this helpful?

We appreciate your feedback. Leave a comment if you would like to provide more detail.
It looks like we have some work to do. Leave a comment to let us know how we could improve.
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Get notified when this content is updated

Follow

3 Comments

Subscriber exclusive content

An active Red Hat subscription is required to participate.

Log In

We are using Apache/2.2.15 with Modcluster connector with Jboss EAP 6.2.1 server, and the options it is giving is not acceptable for example :

connectionTimeout attribute is not valid for connector tag, can any one suggest the correct tool to configure this.

Sorry, I believe the correct configuration in EAP6 is to add the following snippet after the <extentions/> tag.
I have updated this app accordingly. Please let me know if you have any other questions. Thanks for the feedback.

<system-properties>
   <property name="org.apache.tomcat.util.net.MAX_THREADS" value="YOUR_CALCULATED_VALUE"/>
</system-properties>

Thanks for the information, I think this configuration is for the max threads, I would like to add for connection time out for ajp connections, so that over a period of time the connections will be released. The main problem we face is over a period of time the Apache server gives service unavailable error even I could access with http direct url from JBoss. I observe that the ajp connections are full and not released for the new connections. So I was reviewing for the connection time out option for ajp connector.

I think the DEFAULT_CONNECTION_TIMEOUT and DEFAULT_KEEP_ALIVE_TIMEOUT props listed here should give you what you are looking for.

Cool app! My client found what looks like a minor bug though:

https://access.redhat.com/labs/lbconfig/#/?apache_cores=6&apache_instances_per_server=1&apache_servers=1&jboss_cores=4&jboss_jvms=1&jboss_servers=18&long_running=true&long_running_num=10&mpmtype=Worker&modtype=mod_cluster&modcluster_version=12x&modcluster_discovery=mcast&jboss_version=6&same_server=false

This line shows up twice in the httpd.conf output:
Deny from all
Deny from all

Thanks for the feedback! This was a simple error to fix. The issue should be resolved in production now.
Please let me know if you notice any other issues.
Thanks again.

what this mean "that jboss can handle xxxx request" ?

You mean " can handle xxxx request per seconds"?

It should mean the configuration is such that the maximum number of concurrent requests is xxxx.
So if JBoss can handle much more than Apache then Apache is essentially bottlenecking JBoss.

Very helpful page!

Do we have any provision for generating the configuration for mod_mpm_event

MPM type "Prefork" with one server and 4 cores per server should give "MaxClients" value 800 (200*4=800) but I see 1200 value with PREFORK MPM type . It seems a bug in lbconfig tool . Do we have any reported bug for this issue ?

Priyanka, Coty has resolved this issue. Thanks for the report.

May I know can this config be used in RHEL 7? Any update?

Only with mod_proxy. The Apache httpd that comes with RHEL doesn't have mod_cluster and mod_jk.

according to tools...

COMMAND LINE OPTIONS
Since advertise is turned off, thus no multicast, when starting JBoss add the following so that JBoss connects to the Apache proxy
-Djboss.modcluster.proxyList=127.0.0.1:6666

is correct? I think it's not working.