, 2012 1:33 PM
Subject: Re: upgraded fedora and mod_jk will not work
Ray Holme wrote:
I have recently upgraded from Fedora 14 to Fedora 16. I am testing 4 tomcat
applications on the local web (and one plain apache app.) on one box (no
other tricks like multiple servers ...). The below should
PS - the answer to my original question about which linux ports had to be
enabled is: 80
(if you want another machine to get at the port) - the other four ports are
internal and do not need firewall access
(8005, 8009, 8080, 8443)
over and out on this one.
I have recently upgraded from Fedora 14 to Fedora 16. I am testing 4 tomcat
applications on the local web (and one plain apache app.) on one box (no other
tricks like multiple servers ...). The below should pretty well describe
everything I think matters.
I was running Tomcat 6.0.29 and then
From: Ray Holme [mailto:rayho...@yahoo.com]
Subject: upgraded fedora and mod_jk will not work
I downloaded and built the newest mod_jk.so (tomcat-connectors-1.2.33)
Oops - please read the headline in the docs:
The Apache Tomcat team wishes to draw your attention to stability issues
2012/3/23 Ray Holme rayho...@yahoo.com:
I downloaded and built the newest mod_jk.so (tomcat-connectors-1.2.33) from
src (had to strip final binary to make it work at all - not mentioned). I
still have the old one if need be and yes I tried it too.
1.2.33 is known to be broken and causes core
Ray Holme wrote:
I have recently upgraded from Fedora 14 to Fedora 16. I am testing 4 tomcat
applications on the local web (and one plain apache app.) on one box (no other
tricks like multiple servers ...). The below should pretty well describe
everything I think matters.
I was running
Note : you /do/ get bonus points for providing the versions of what you're
using.
Not everyone does that.
And you also got an immediate reward, in the form of Chuck's and Konstantin's warnings
about your mod_jk version (which could have caused you severe problems later, had you not
mentioned
(had to strip final binary to make it work at all - not mentioned)
What do you mean?
I mean that the built binary was NOT stripped and would not work (apache
complained about loading it - sorry I forgot the message).
I simply did strip mod_jk.so and the size went down by a factor of 4 and
Andre - good information. Thanks but still in the weeds here.
Depends how long Tomcat and your applications need to start up and be ready
to answer requests.
makes sense. since httpd is NOT coming up on boot as it should, I will make it
second
with a preceding sleep and background the
