You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Mike Mondragon <mi...@yahoo.com> on 2000/08/02 11:07:19 UTC
subscribe TOMCAT-USER
subscribe TOMCAT-USER
=====
Mike Mondragon
__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/
Re: IBM JDK 1.3 w/ TOMCAT - Help?
Posted by Andy Lewis <an...@veritas.com>.
Ah, excellent. The system is running 2.1.2 glibc. I'll look for an update
there.
Thanks!
Chong Yu Meng wrote:
> Greetings, Andy !!
>
> I encountered the same problem with Caldera eServer 2.3. My guess is, it is
> probably the glibc libraries that are causing the problem. I haven't
> actually tried it on the Dell system I'm trying to get IBM's JDK 1.3 on. I
> found that Java works really bad or not at all on certain glibc libraries
> (notoriously 2.1.2). I'm pretty sure the problem doesn't lie in Tomcat or
> Apache. I fixed the problem on my Thinkpad 390X accidentally when one member
> on the Caldera Mailing list posted an updated glibc library (2.1.4 if I
> recall correctly). I'm going to try the fix either today or tomorrow.
>
> Regards,
> Chong Yu Meng
>
> ----- Original Message -----
> From: "Andy Lewis" <an...@veritas.com>
> To: <to...@jakarta.apache.org>
> Sent: Wednesday, August 02, 2000 11:38 PM
> Subject: IBM JDK 1.3 w/ TOMCAT - Help?
>
> >
> > I'm running Tomcat 3.1 on Radhat 6.1 with Apache 1.3.12 and have had
> > some major problems with the IBM 1.3 JDK. Sadly, I've had to go back to
> > the Sun 1.2.2. The two symptoms were that the Tomcat shutdown didn't
> > work right - basically the Java processes would stick around, holding
> > the port, but not responsind to and connection requests for about 3
> > minutes before actually going away. Most of them would go away before
> > that with a simple "kill", but two of them would require a "kill -9" to
> > remove. The second symptom was that Tomcat would simply hang and stop
> > serving requests after 6 or 7 hours. Neither case produced any error
> > messages of relevant log entries. Tomcat is running as a "tomcat" user.
> > The system is a Dual PIII 550.
> >
> > Perhaps something related to the dual processors with the IBM JDK?
> >
> > Has anyone else seen anything like this?
> >
> > Not time critical - I'm up and running fine on Sun 1.2.2, but it does
> > bug me....
> >
> >
> > Thanks!
> >
> >
Re: IBM JDK 1.3 w/ TOMCAT - Help?
Posted by Chong Yu Meng <cy...@cyberway.com.sg>.
Greetings, Andy !!
I encountered the same problem with Caldera eServer 2.3. My guess is, it is
probably the glibc libraries that are causing the problem. I haven't
actually tried it on the Dell system I'm trying to get IBM's JDK 1.3 on. I
found that Java works really bad or not at all on certain glibc libraries
(notoriously 2.1.2). I'm pretty sure the problem doesn't lie in Tomcat or
Apache. I fixed the problem on my Thinkpad 390X accidentally when one member
on the Caldera Mailing list posted an updated glibc library (2.1.4 if I
recall correctly). I'm going to try the fix either today or tomorrow.
Regards,
Chong Yu Meng
----- Original Message -----
From: "Andy Lewis" <an...@veritas.com>
To: <to...@jakarta.apache.org>
Sent: Wednesday, August 02, 2000 11:38 PM
Subject: IBM JDK 1.3 w/ TOMCAT - Help?
>
> I'm running Tomcat 3.1 on Radhat 6.1 with Apache 1.3.12 and have had
> some major problems with the IBM 1.3 JDK. Sadly, I've had to go back to
> the Sun 1.2.2. The two symptoms were that the Tomcat shutdown didn't
> work right - basically the Java processes would stick around, holding
> the port, but not responsind to and connection requests for about 3
> minutes before actually going away. Most of them would go away before
> that with a simple "kill", but two of them would require a "kill -9" to
> remove. The second symptom was that Tomcat would simply hang and stop
> serving requests after 6 or 7 hours. Neither case produced any error
> messages of relevant log entries. Tomcat is running as a "tomcat" user.
> The system is a Dual PIII 550.
>
> Perhaps something related to the dual processors with the IBM JDK?
>
> Has anyone else seen anything like this?
>
> Not time critical - I'm up and running fine on Sun 1.2.2, but it does
> bug me....
>
>
> Thanks!
>
>
Re: IBM JDK 1.3 w/ TOMCAT - Help?
Posted by Chong Yu Meng <cy...@cyberway.com.sg>.
Actually, Punky, the pthread problem existed even in the 1.1.8 version of
the IBM JDK. It was fixed by the respective Linux companies (I think). Well,
at least, Caldera released a set of updates for people trying to use the IBM
JDK for OpenLinux 2.3 and above. See the Caldera Knowledge Base at
http://support.calderasystems.com
Regards,
Chong Yu Meng
----- Original Message -----
From: "Punky Tse" <pu...@yahoo.com>
To: <to...@jakarta.apache.org>
Sent: Thursday, August 03, 2000 7:29 PM
Subject: Re: IBM JDK 1.3 w/ TOMCAT - Help?
> Andy,
> Please check news://ibm.software.java.linux, there are some threads
> about SMP issue.
>
> Seems that SMP is not supported for IBM JDK 1.3. PThread library is
the
> problem....
>
> Hope that help.
>
> - Punky
>
>
> ----- Original Message -----
> From: "Andy Lewis" <an...@veritas.com>
> To: <to...@jakarta.apache.org>
> Sent: Wednesday, August 02, 2000 11:38 PM
> Subject: IBM JDK 1.3 w/ TOMCAT - Help?
>
>
> >
> > I'm running Tomcat 3.1 on Radhat 6.1 with Apache 1.3.12 and have had
> > some major problems with the IBM 1.3 JDK. Sadly, I've had to go back to
> > the Sun 1.2.2. The two symptoms were that the Tomcat shutdown didn't
> > work right - basically the Java processes would stick around, holding
> > the port, but not responsind to and connection requests for about 3
> > minutes before actually going away. Most of them would go away before
> > that with a simple "kill", but two of them would require a "kill -9" to
> > remove. The second symptom was that Tomcat would simply hang and stop
> > serving requests after 6 or 7 hours. Neither case produced any error
> > messages of relevant log entries. Tomcat is running as a "tomcat" user.
> > The system is a Dual PIII 550.
> >
> > Perhaps something related to the dual processors with the IBM JDK?
> >
> > Has anyone else seen anything like this?
> >
> > Not time critical - I'm up and running fine on Sun 1.2.2, but it does
> > bug me....
> >
> >
> > Thanks!
> >
>
Re: IBM JDK 1.3 w/ TOMCAT - Help?
Posted by Punky Tse <pu...@yahoo.com>.
Andy,
Please check news://ibm.software.java.linux, there are some threads
about SMP issue.
Seems that SMP is not supported for IBM JDK 1.3. PThread library is the
problem....
Hope that help.
- Punky
----- Original Message -----
From: "Andy Lewis" <an...@veritas.com>
To: <to...@jakarta.apache.org>
Sent: Wednesday, August 02, 2000 11:38 PM
Subject: IBM JDK 1.3 w/ TOMCAT - Help?
>
> I'm running Tomcat 3.1 on Radhat 6.1 with Apache 1.3.12 and have had
> some major problems with the IBM 1.3 JDK. Sadly, I've had to go back to
> the Sun 1.2.2. The two symptoms were that the Tomcat shutdown didn't
> work right - basically the Java processes would stick around, holding
> the port, but not responsind to and connection requests for about 3
> minutes before actually going away. Most of them would go away before
> that with a simple "kill", but two of them would require a "kill -9" to
> remove. The second symptom was that Tomcat would simply hang and stop
> serving requests after 6 or 7 hours. Neither case produced any error
> messages of relevant log entries. Tomcat is running as a "tomcat" user.
> The system is a Dual PIII 550.
>
> Perhaps something related to the dual processors with the IBM JDK?
>
> Has anyone else seen anything like this?
>
> Not time critical - I'm up and running fine on Sun 1.2.2, but it does
> bug me....
>
>
> Thanks!
>
Re: IBM JDK 1.3 w/ TOMCAT - Help?
Posted by Andy Lewis <an...@veritas.com>.
Ok...that sort of rules out a lot of SMP and Tomcat or RedHat version
specific issues....Do you have an EAPI version of mod_jserv? I'm just
trying to pin down possibilites here...
Thanks!
Yun Sang Jung wrote:
>
>
> [Image]
> I'm running Tomcat 3.2 beta 2 on Radhat 6.0 with Apache 1.3.12 & IBM JDK 1.3 on Single PII 350.
> I met a exact same problem. "Tomcat shutdown didn't work right - basically the Java
> processes would stick around, holding the port"
>
>
> >
> > I'm running Tomcat 3.1 on Radhat 6.1 with Apache 1.3.12 and have had
> > some major problems with the IBM 1.3 JDK. Sadly, I've had to go back to
> > the Sun 1.2.2. The two symptoms were that the Tomcat shutdown didn't
> > work right - basically the Java processes would stick around, holding
> > the port, but not responsind to and connection requests for about 3
> > minutes before actually going away. Most of them would go away before
> > that with a simple "kill", but two of them would require a "kill -9" to
> > remove. The second symptom was that Tomcat would simply hang and stop
> > serving requests after 6 or 7 hours. Neither case produced any error
> > messages of relevant log entries. Tomcat is running as a "tomcat" user.
> > The system is a Dual PIII 550.
> >
> > Perhaps something related to the dual processors with the IBM JDK?
> >
> > Has anyone else seen anything like this?
> >
> > Not time critical - I'm up and running fine on Sun 1.2.2, but it does
> > bug me....
> >
> >
> > Thanks!
> >
> >
>
>
>
>
>
IBM JDK 1.3 w/ TOMCAT - Help?
Posted by Andy Lewis <an...@veritas.com>.
I'm running Tomcat 3.1 on Radhat 6.1 with Apache 1.3.12 and have had
some major problems with the IBM 1.3 JDK. Sadly, I've had to go back to
the Sun 1.2.2. The two symptoms were that the Tomcat shutdown didn't
work right - basically the Java processes would stick around, holding
the port, but not responsind to and connection requests for about 3
minutes before actually going away. Most of them would go away before
that with a simple "kill", but two of them would require a "kill -9" to
remove. The second symptom was that Tomcat would simply hang and stop
serving requests after 6 or 7 hours. Neither case produced any error
messages of relevant log entries. Tomcat is running as a "tomcat" user.
The system is a Dual PIII 550.
Perhaps something related to the dual processors with the IBM JDK?
Has anyone else seen anything like this?
Not time critical - I'm up and running fine on Sun 1.2.2, but it does
bug me....
Thanks!