tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Using mod_jk in cluster environment responds HTTP 500
Date Tue, 16 Nov 2010 21:28:48 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rikslovein,

On 11/15/2010 12:47 AM, rikslovein wrote:
> Server.xml
> <Connector port="8009" address="localhost" 
> enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />

Is redirectPort="8443" correct for your environment? This has nothing to
do with your HTTP 500 problems, but it's worth having a clean config.

> workers.properties:
> workers.tomcat_home=/opt/webhost/DWH-Tomcat-Inst/tomcat5.5.23
> workers.java_home=/usr/lib/jvm/java-1.5.0
> ps=/

Remove the previous 3 properties: they have no effect and clutter your
configuration.

> worker.list=loadbal_hub_prod,jkstatus,hub0,hub1

I don't believe you have to mention hub0 and hub1 directly, here, but it
doesn't hurt.

> worker.hub0.port=8009
> worker.hub0.host=localhost
> worker.hub0.type=ajp13
> worker.hub0.lbfactor=1
> worker.hub0.redirect=hub1
> 
> worker.hub1.port=9009
> worker.hub1.host=localhost
> worker.hub1.type=ajp13
> worker.hub1.lbfactor=1
> worker.hub1.redirect=hub0

Check out the "worker.XXX.reference" property: it will save you some
typing and help maintain consistency across lb workers.

What version of mod_jk are you currently using? Actually... what
versions of /everything/ are you using?

> worker.jkstatus.type=status
> 
> worker.loadbal_hub_prod.type=lb
> worker.loadbal_hub_prod.balanced_workers=hub0,hub1
> worker.loadbal_hub_prod.sticky_session=false

I notice that you don't have any strategy for determining availability
of workers configured (ping_mode). You might want to look at those
options to determine what is appropriate for your environment.

I see that the sticky_session_force directive can result in a 500 error
being returned to a user who is trying to access a balanced worker in an
error state. I also see that you have sticky_session=false and the
sticky_session_force setting should be irrelevant. Is it possible that
your configuration file isn't actually being used? Try introducing a
syntax error into workers.properties and seeing if mod_jk complains
about it on startup.

Can you show us what the status worker says when you find that 500
responses are being returned?

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzi948ACgkQ9CaO5/Lv0PAzVACeJ86i2QDwkljprTrSEJ7Axlz9
63MAn2YBHgUfBpEqqi1Tz0dtk73A4n+r
=ORgo
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message