Absolutely correct,
I think that problem may be caused by the JBoss GC (stop the world)
activity.
When it occurs on HA Singleton MASTER node it makes the
web-applications not availables, and the node is considered "off-line"
for 1 minute by the apache.
No problem arises for "standard cluster applications running on all
nodes" because another node can responde.
I've seen that "retry=0" parameters using ProxyPass should avoid the 1
minute "black out" that generates the 503 errors.
I'm not able to find the same behavior using mod_cluster.
Federico
Il 03/07/2014 16:48, Jeff Trawick ha scritto:
On Thu, Jul 3, 2014 at 9:57 AM, Federico Calì <f.c...@tdnet.it
<mailto:f.c...@tdnet.it>> wrote:
Hi Roman,
the mod_cluster is what we have actually in production.
I want to change it, because the communication
between Jboss and front-end sometimes fails with error 503.
I would like to use ProxyPass in order to investigate if these
kinds of errors will remain.
It is very likely that you'll have the same problem, which is an
issue, perhaps intermittent, with the backend server or application.
Maybe one proxy implementation reacts a little better in your
circumstance and/or can be configured to react better (e.g., recover
more quickly), but you'll probably end up needing to diagnose the root
cause either way.
Federico
--
.: Federico Calì
.: TD Group S.p.A.
.: Via del Fischione 19
.: [Via Traversagna -Ingresso Zona C ]
.: 56010 Migliarino Pisano (PI)
.: 050-897406
.: 348-2886628
