httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject AW: [users@httpd] Any Comparisons? -- mod_wl vs mod_proxy vs mod_jk
Date Mon, 09 Feb 2015 07:42:40 GMT

mod_wl has some advantages, mod_proxy does not support i.e. mod_proxy does normally only a
ping to check if a backend server is available, which normally works in 99% even if the web-application
behind is not available, so it is possible that mod_proxy routes the request to /backend even
if /backend is not yet available, because the application server has not loaded the application

This means mod_wl does a little bit more then just checking if the backend server is available
via ping, it even checks if the backend url gives a working response. Also mod_wl gets information
about the all current cluster members within the session cookie, so if a server is not available
anymore he directly knows, which cluster members the plugin can forward the request. Also
to simulate the load balancing with mod_proxy in front of a weblogic, this must be done via
a ROUTE_ID within the Apache and can not be done via the sessionid like it is done with Glassfish
or Tomcat.

But it also has currently some disadvantages i.e. certificate handling via oracle wallets.

Currently all our instances are running with mod_proxy and we have normally no problems, only
in the case an application on ONE cluster member breaks, so that the application server is
still available but not the application, so in this case the only feature I’m currently
missing within mod_proxy is an check URL feature.


Von: Daniel []
Gesendet: Montag, 9. Februar 2015 08:13
An: <>
Betreff: Re: [users@httpd] Any Comparisons? -- mod_wl vs mod_proxy vs mod_jk

2015-02-09 2:22 GMT+01:00 Todd Simons <<>>:
Hello All
We've been using the generic mod_proxy for years.   We utilize Apache to layer in HTTPS from
the world into our DMZ, then utilize proxypass/proxypassreverse to our internal servers. 
Our internal servers vary between iis, weblogic, tomcat, and a few others.

mod_proxy has been working great for us.

Recently I've been asked why not mod_wl and mod_jk.   I really have no answer and I haven't
been able to find much online with regards to advantages of one vs another.

Has anyone seen, or have, any links that can help outline the difference?


I can tell you about a bit the weblogic plugin.

Latest versions include WLSRequest directive that, according to its documentation:
* Lower web server processing overhead in general
* Resolves substantial performance degradation when the web server DocumentRoot is on a slow
* Resolves 403 errors for URIs which cannot be mapped to the filesystem due to the filesystem
length restrictions

Among the interesting things it offers weblogic plugin dinamically updates the weblogic cluster
members on first connection, no matter if you didn't specify all members of the cluster.

For all related info I would suggest you to check the documentation page which describes everything
it can do:

In any case, if you are happy with your actual solution, why change?

Daniel Ferradal
IT Specialist

View raw message