On Mon, Apr 06, 2009 at 06:08:54PM -0400, Christopher Schultz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > John, > > On 4/6/2009 5:51 PM, John Oliver wrote: > > RHEL 5.2, httpd-2.2.3-11.el5_1.3, tomcat5-5.5.23-0jpp.7.el5_2.1 > > 2.2.3 is pretty old... any chance of upgrading to 2.2.11? You're nearly > 3 years out of sync with the state-of-the-art.
Tell it to Red Hat... > > There is no firewall... Tomcat and httpd are on the same box. > > iptables could be interfering, but not likely. Most people don't bother > protecting localhost from itself :) Even if the app works? Some of these systems have some "default" iptables. Others have something else. Until I understand why which is what, I try to let things be. > > I'm not sure how to check the JVM version... this is the first time I've > > ever had to worry about Tomcat and Java stuff, so I'm doing a lot of > > guessing. > > $ java -version [r...@mda-services ~]# java -version java version "1.6.0_05" Java(TM) SE Runtime Environment (build 1.6.0_05-b13) Java HotSpot(TM) Server VM (build 10.0-b19, mixed mode) > > [r...@mda-services ~]# rpm -qa | grep java > > java-1.4.2-gcj-compat-devel-1.4.2.0-40jpp.115 > > gcc-java-4.1.2-42.el5 > > java-1.4.2-gcj-compat-1.4.2.0-40jpp.115 > > Hmm... it's probably /not/ your problem, here, but a /lot/ of people > have had problems with the gcj version of Java. Fortunately, you're > taking care of SSL through Apache httpd: that's where I've heard of lots > of incompatibilities and simply incorrect (or very surprising) operation > and/or crashes. > > I would recommend using Sun's Java. I'd also recommend a newer version > (they're on 1.6 these days... 1.4 is a dinosaur). I think I am... :-) I'm guessing that version was installed some other way, and the Red Hat packages aren't being used? > > It seems to work, even with all of these error messages, but this > > setup nwas cobbled together by developers. > > So, are you using mod_proxy_ajp? Please post your configuration. I have > had much better luck with mod_jk, but I think that's more due to my > history with it than anything else: I simply have the experience with > mod_jk and not with mod_proxy_ajp. The only config I'm aware of is /etc/httpd/conf.d/proxy_ajp.conf, which consists of lines like: ProxyPass /GmmsL/ ajp://localhost:8009/GmmsL/ I just add another similar line for each app. > > > Also, Tomcat seems to be pretty unstable and needs to be restarted > > every week or so, and I wouldn't be surprised if these errors have > > something to do with that. > > Tomcat itself is super stable. I have never ever had it crash on me. I didn't mean to blame Tomcat itself. I'm sure that whatever problem is because someone hacked at something until it was "good enough", and then walked away and forgot all about it :-) > I've had the JVM crash crash (for different issues) and I've run out of > memory, but Tomcat has never failed me. The most likely reason for > "server instability" is, sadly, your own application. We might be able > to help with that, too. That would rock :-) Thanks, Chris. -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
