Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <49DA7D76.2010109@christopherschultz.net>
Date: Mon, 06 Apr 2009 18:08:54 -0400
From: Christopher Schultz <chris@christopherschultz.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US;
 rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: ajp_read_header: ajp_ilink_receive failed
References: <20090406211500.GA28624@ns.sdsitehosting.net>
 <49DA773D.30400@christopherschultz.net>
 <20090406215123.GA29411@ns.sdsitehosting.net>
In-Reply-To: <20090406215123.GA29411@ns.sdsitehosting.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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

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

> 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

> [root@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).

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

> I always figure that error messages are there for a reason, and I'm
> better off fixing them.

+1

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

> I just have no idea how to troubleshoot and tweak this stuff to, 
> hopefully, wind up with a smoothly-running system.

Well, let's get the ajp thing fixed first, then move on to the other
problems. It's midnight in Germany and Croatia. Give Rainer and Mladen a
chance to read this thread and give you some thoughts on the ajp stuff.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAknafXYACgkQ9CaO5/Lv0PD0cQCgi/clnmHKHM4bFYvvCQII6sZ4
kf8An1rdABN28J87EJwmgr6tEJVZAu3y
=B58x
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org