Does Red Hat / JBoss offer support for Apache, mod_jk, mod_proxy, or mod_cluster?
- Red Hat Enterprise Linux (RHEL)
- Red Hat JBoss Enterprise Application Platform (EAP)
- Red Hat JBoss Web Server (JWS)
- Does Red Hat provide any products or entitlements that include full support for the following?
- Apache httpd
- What load balancing, proxy, or web server solutions are supported for JBoss EAP?
- Is my load balancer incompatible with JBoss?
- If so, which hardware load balancers should I use?
- Are the following third-party load balancers supported?
- BIG-IP (F5)
- ACE (Cisco)
- AppDirector (radware)
- Is the use of mod_jk with Apache httpd-2.2.15 RHEL6 supported for JBoss EAP 4.3.0?
- Is mod_jk supported on a server running "Red Hat Enterprise Linux Server release 6.4" or we have to buy a different license?
- What is the latest version of mod_jk. Is there will be future developments of mod_jk or its deprecated?
- Is the use of mod_jk with Apache httpd-2.2.15 for Tomcat 6.0.24 supported under RHEL subscription?
- Is the use of mod_jk with IBM HTTP Webserver for JBoss EAP supported?
Red Hat does not provide support for third-party hardware load balancers
- If you have queries on third party load balancers, we recommend contacting the hardware vendor
In regards to what is supported for each product please see the resources section and the associated links for each url below:
We only officially support running the Apache httpd version shipped with RHEL or JBoss Core Services (JBCS). Prior httpd distributions through JBoss EWS or JWS or the EAP 6 Apache Web Server are now retired and end of life.
- Note that using custom builds of Apache httpd or the community versions of Apache httpd is out of our support scope and we do not provide any support for such Apache httpd.
You can use Red Hat's load balancer configuration app to generate an optimize configuration for mod_jk, mod_proxy, or mod_cluster.
A few notes pertaining to
- mod_proxy is generally available/builtin with each Apache related product we ship
- mod_jk and mod_cluster are only provided and supported within JBCS, which is only currently supported on RHEL 7 and 8.
- A JBCS httpd zip distribution for RHEL 9 is forthcoming
- In RHEL 9,
mod_proxy_clusterhave been added as RHEL packages. See RHEL9 release note for details.
- httpd, mod_jk, and mod_cluster were previously included under JWS 3.0 and earlier, but this is now retired and end of life
- An Apache HTTPD bundle (equivalent to JWS's httpd offering and tested and supported for loadbalancing EAP 6 servers through mod_proxy/jk/cluster) was included as a separate download with JBoss EAP 6 but is now end of life.
- You can see the supported configurations of each version at following urls:
You can refer to the table below for a reference of what Apache httpd loadbalancer modules are supported for a given EAP and httpd combination.
|EAP 4||EAP 5||EAP 6||EAP 7|
|RHEL 5's 2.2.3||mod_proxy||mod_proxy||mod_proxy||mod_proxy|
|RHEL 6's 2.2.15||mod_proxy||mod_proxy||mod_proxy +mod_cluster+mod_jk||mod_proxy|
|EWS/JWS||Use JBCS instead||Use JBCS instead||Use JBCS instead||Use JBCS instead|
|EAP 6 HTTP Server||Use JBCS instead||Use JBCS instead||Use JBCS instead||Use JBCS instead|
If you have further questions that aren't answered here or in the above links please don't hesitate to contact sales or support
- Red Hat JBoss Web Server
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
I wonder why you describe such a important thing here, not on public web pages.
This must be described on public space and read before buying its subscription.
I couldn't recognize this by reading the note:" Red Hat only certifies and supports the connectors provided with JBoss Enterprise Web Server (EWS), JBoss Enterprise Application Platform (EAP) and JBoss Enterprise Web Platform (EWP) " on http://www.jboss.com/products/platforms/application/supportedconfigurations/ page with my English reading ability...
The information is contained at that URL:
The following Web Servers / Connectors were validated and certified with JBoss Enterprise Application Platform 5.
(Apache Web Server)
Red Hat Enterprise Linux 4 (x86, x86_64)
Solaris 10 (x86, x86_64, SPARC 64 bit)
Solaris 9 (x86, SPARC 32 & 64 bit)
Windows Server 2008 R2 (x86, x86_64)
Windows Server 2003 (x86, x86_64)
Is this page still accurate?
According to http://www.jboss.com/products/platforms/application/components mod_cluster is also supported on RHEL 6.1 regardless if you have EWS or not.
That link doesn't make clear the fact that mod_cluster is only tested and certified on EWS. So although it's a component shipped with EAP, it needs to be run in a EWS httpd server with relevant entitlements for full support.
I think rhn-sa-tqvarnst meant to refer to  instead of . Indeed, the last row of the last table there does indicate that mod_cluster 1.0.10.GA_CP01 (and mod_jk 1.2.31) are tested and supported on Apache Web Server 2.2.15 delivered in RHEL 6. Note from  that these versions ov mod_cluster and mod_jk are in EAP 5.1.1. So, to enjoy support of mod_cluster without an EWS subscription requires the specific combination of EAP 5.1.1 and RHEL 6, with subscriptions to both, of course.
Actually I meant to refer to  but thanks for spotting that. This page states "The following Web Servers / Connectors were validated and certified with JBoss Enterprise Application Platform 5." so either this article is wrong or that page is wrong. Since potential customers and RH Sales use the external link to make decisions regarding what products are need and apperently this article is references by support these shouldn't differ.
What is the validated and certified of Web Servers / Connectors with JBoss Enterprise Application Platform 4?
JBoss Enterprise Application Platform 4 has reached end of life. See https://access.redhat.com/support/policy/updates/jboss_notes/ for more details.
Consider using EAP 5 or EAP 6 instead. More details about supported configuration can be found at https://access.redhat.com/site/support/configurations/jboss
In the above talbe,only mod_proxy is supported in RHEL5+EAP5.
But,according to https://access.redhat.com/site/articles/112673,mod_cluster and mod_jk are listed as well,they(mod_jk and mod_cluster) are also supported(include RHEL5 and RHEL6).Is that right?
I would suggest opening a support ticket to address your query
How about the RHEL7?
See the supported configuration pages :https://access.redhat.com/support/configurations/jboss/
For additional information, please log a support ticket.
I've read on the link from red hat portal
Inside this page, there is an information about the location of mod_jk .
The page says :
" If you are using Apache HTTPD, download the JBoss Enterprise Application Platform Native Components package for Red Hat Enterprise Linux from the Red Hat Customer Service Portal at https://access.redhat.com. This package contains both the mod_jk and mod_cluster binaries precompiled for Red Hat Enterprise Linux. If you are using JBoss Enterprise Web Server, it already includes the binary for mod_jk. ",
When i download the package jboss-eap-native-XX-RHEL6 from the link suggested , but inside this I did not found the mod_jk and mod_cluster modules .
I' ve found the mod_jk and mod_cluster modules on zip file jboss-eap-native-webserver-connectors .
I hope this help
Thanks for bringing this to our attention. A bugzilla has been filed to fix the document https://bugzilla.redhat.com/show_bug.cgi?id=1274207
How about RHEL7's 2.4.6 + EAP6 now ?
One question, in the table, in the EWS + EAP7 combination, is it possible that the output is "mod_proxy + mod_jk + mod_cluster"? And in the EAP 6 HTTP Server + EAP7 combination, is it possible that the output is "Use JBCS instead"?
Moving forward, for users requiring just httpd, JBCS is the way to go. Reference https://access.redhat.com/support/configurations/jboss to verify which version of httpd is supported with a specific EAP release. For any other queries, please open a support ticket.