Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Tue, 19 Feb 2008 11:45:25 -0500
From: "Mark H. Wood" <mwood@IUPUI.Edu>
To: users@tomcat.apache.org
Subject: Re: Using mod_jk with other Java programs
Message-ID: <20080219164525.GG2279@IUPUI.Edu>
References: <47BA0831.6000801@thinktankmaths.co.uk>
 <47BA0CB4.70507@kippdata.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="dgjlcl3Tl+kb3YDk"
Content-Disposition: inline
In-Reply-To: <47BA0CB4.70507@kippdata.de>
User-Agent: Mutt/1.5.16 (2007-06-09)

--dgjlcl3Tl+kb3YDk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Implementing AJP just to get proxying may be more than you want to do.

However, to address your question, notice in jk-workers.properties
that mod_jk doesn't point to programs; it points to host:port pairs.
Whatever is listening to that port on that host will get the requests
that mod_jk siphons off for that worker.  (The URL/worker mapping is
done with jkMount directives in the main config.)

--=20
Mark H. Wood, Lead System Programmer   mwood@IUPUI.Edu
Typically when a software vendor says that a product is "intuitive" he
means the exact opposite.


--dgjlcl3Tl+kb3YDk
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHuwels/NR4JuTKG8RAiRnAJ4ls4gAHMdqIqntEqdTLb3dengpWgCaAzO5
53Z7b1RuoxzlB9ncUyDgJaw=
=8VGv
-----END PGP SIGNATURE-----

--dgjlcl3Tl+kb3YDk--