On Mon, Apr 06, 2009 at 05:30:49PM -0500, Caldarale, Charles R wrote:
> > From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> > Subject: Re: ajp_read_header: ajp_ilink_receive failed
> > 
> > > [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
> 
> Actually, if Tomcat is crashing, it likely *is* the problem.  gcj has never 
> really made it beyond the toy stage, so that's the first thing to replace.

It is very possible that this gcj stuff is just installed, and is
otherwise collecting dust.

> > 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).

[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)

> Definitely.  Make sure when moving up to a real JVM that you remove the 
> Tomcat compatibility package that's used only with 1.4 JVMs.  Since you're 
> using a 3rd-party repackaged Tomcat, that may be difficult to find; on a real 
> Tomcat, the compatibility files are stored in the follow locations:
> 
> $CATALINA_HOME/bin/jmx.jar
> $CATALINA_HOME/common/endorsed/xercesImpl.jar
> $CATALINA_HOME/xml-apis.jar

I don't have any of those files in /var/lib/tomcat5/ which is, I
believe, $CATALINA_HOME (it's referred to as $TOMCAT_HOME, and I suppose
that might be something different, but... )

> While you're upgrading to proper levels of httpd and the JVM, consider 
> installing a real Tomcat from tomcat.apache.org; the 3rd-party ones have 
> files scattered all over, and sometimes change the configuration to the point 
> where behavior is quite different from the standard version.

Using the most recent versions of those would break our support from Red
Hat.  I don't really care about that... I've said we should stop paying
them and use CentOS.  If using more recent versions winds up being the
answer, that would be more ammo for my argument.  But if we can make
things work properly with the supported versions, at least I can always
say, "Blame Red Hat..." :-)

-- 
***********************************************************************
* 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

Reply via email to