I haven't done this in a while, but when I did, an article that helped
me a lot was from here:
http://galatea.com/flashguides/home
Good luck,
iksrazal
cji_work@yahoo.com said:
>I am trying to make this "Apache2, mod_jk2, Tomcat4.1" working together
>on linux machine and so far no luck.
mod_jk should be easier to get working than mod_jk2. Also, mod_jk2
development has been abandoned, so you'll be better off switching
to mod_jk.
By the way, are you certain there are no prebuild packages of the
needed components for your Linux distribution? Or do you have some
special needs not catered by the prebuilt packages?

Signature
Wolf a.k.a. Juha Laiho Espoo, Finland
(GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
"...cancel my subscription to the resurrection!" (Jim Morrison)
cji_work@yahoo.com - 10 Jun 2005 19:01 GMT
> cji_work@yahoo.com said:
> >I am trying to make this "Apache2, mod_jk2, Tomcat4.1" working together
[quoted text clipped - 3 lines]
> development has been abandoned, so you'll be better off switching
> to mod_jk.
My original perpose is to build the mose powerful one of the Apahce,
mod_jk, mod_jk2. Than I realized that mod_jk2 was in the maintaince
mode. Since I was in the middle of it, and it also suppose to work, so
I just continued to work on it. Later on I think I will build another
one also.
> By the way, are you certain there are no prebuild packages of the
> needed components for your Linux distribution? Or do you have some
> special needs not catered by the prebuilt packages?
> --
If you are talking about the pre-built package that has both
Apache&Tomcat, I do not know anything that are of the open source. I
have been playing with some of the commercial products. But this time I
have to work something that costs "0" budget.
If you are asking why I am building the mod_jk2 libraries, other than
download the binary one. That is because it makes me easy to tell if
the package was broken during the compiling time or the run time.
-cji
Hi cji,
I did a similar setup for a production migration just a few months
ago. Yes & Yes - you can build & install Apache(2) in any directory you
want. The default install packages are (as I recall) bound to specific
non-user directories such as /usr/local/apache2. Tomcat can be
configured to listen on any port - with the default something like
8080, which does not require root. You can very easily set this up in a
user dir/subdir. In fact, I have three different tomcats running under
my id serving different apache vhosts.
I agree with Juha - use mod_jk, not mod_jk2. Also - why Tomcat4.1?
If you are not specifically required to use 4.1 for some compatability
reason, we've found 5.0.28 to be very stable & 5.5 I hear is also doing
well.
best of luck,
Noah