You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@jakarta.apache.org by Craig Day <cr...@alderaan.com.au> on 2000/10/27 03:07:18 UTC
bad time with tomcat
Hi All,
We are having a horrible time with tomcat in out production
environment. We are running 3.1 on multiple Ultra-250s each
with 1gig of memory running Solaris26 and Sun JDK1.2.2_005.
The application is a relatively simple JSP-based app producing
XML out of Oracle 8.1.6. We do simple load balancing via DNS.
We are using Stronghold, but not the jserv connector, we ProxyPass
the requests instead.
At this point, tomcat is the least stable component in our
environment. Tomcat will die on us regularly without giving any
hint as to why, and also occasionally decides to chew all the
CPU for no apparent reason (no hits even being made). Id love to
hear from anyone who is having more success with Tomcat and
any suggestions anyone may have for improving its stability and or
diagnosing what the problem may be.
regards
craig
Re: bad time with tomcat && Maybe Unicode
Posted by Alex Sanderson <al...@duke-interactive.com>.
I run an Identical version of apache1.3.14/tomcat3.2b6/jsdk1.3/postgres7 .... on Linux and Solaris machines. With JSDK 1.3 on Solaris I have the problem with ?'s for any accented characters however returning to JSDK 1.2.2 fixes the problem. This problem does not exist with the Linux JSDK 1.3. I haven't had any success finding help on the Sun's bug or support site but all of the tests I have tried suggested that it was a problem with the JSDK and perhaps with codepages on Solaris. Anyway at the moment I don't recommend running JSDK 1.3 on Solaris if you are wanting foreign language support.
Alex
----- Original Message -----
From: Brett Morgan
To: general@jakarta.apache.org
Sent: Friday, October 27, 2000 4:28 AM
Subject: Re: bad time with tomcat
Do yoursel a favour and run jdk1.3 and tomcat3.2beta5. Both solve
serious numbers of bugs.
On Fri, Oct 27, 2000 at 09:07:18AM +0800, Craig Day didst scribe:
> Hi All,
> We are having a horrible time with tomcat in out production
> environment. We are running 3.1 on multiple Ultra-250s each
> with 1gig of memory running Solaris26 and Sun JDK1.2.2_005.
> The application is a relatively simple JSP-based app producing
> XML out of Oracle 8.1.6. We do simple load balancing via DNS.
> We are using Stronghold, but not the jserv connector, we ProxyPass
> the requests instead.
> At this point, tomcat is the least stable component in our
> environment. Tomcat will die on us regularly without giving any
> hint as to why, and also occasionally decides to chew all the
> CPU for no apparent reason (no hits even being made). Id love to
> hear from anyone who is having more success with Tomcat and
> any suggestions anyone may have for improving its stability and or
> diagnosing what the problem may be.
>
> regards
> craig
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
--
Brett Morgan
Phone: +61-2-9004-5588
Email: morganb@news.com.au
And, now for something completely different:
Help! I'm trapped in a Chinese computer factory!
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: bad time with tomcat
Posted by Brett Morgan <mo...@news.com.au>.
Do yoursel a favour and run jdk1.3 and tomcat3.2beta5. Both solve
serious numbers of bugs.
On Fri, Oct 27, 2000 at 09:07:18AM +0800, Craig Day didst scribe:
> Hi All,
> We are having a horrible time with tomcat in out production
> environment. We are running 3.1 on multiple Ultra-250s each
> with 1gig of memory running Solaris26 and Sun JDK1.2.2_005.
> The application is a relatively simple JSP-based app producing
> XML out of Oracle 8.1.6. We do simple load balancing via DNS.
> We are using Stronghold, but not the jserv connector, we ProxyPass
> the requests instead.
> At this point, tomcat is the least stable component in our
> environment. Tomcat will die on us regularly without giving any
> hint as to why, and also occasionally decides to chew all the
> CPU for no apparent reason (no hits even being made). Id love to
> hear from anyone who is having more success with Tomcat and
> any suggestions anyone may have for improving its stability and or
> diagnosing what the problem may be.
>
> regards
> craig
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
--
Brett Morgan
Phone: +61-2-9004-5588
Email: morganb@news.com.au
And, now for something completely different:
Help! I'm trapped in a Chinese computer factory!
Re: bad time with tomcat
Posted by Cedric Berger <ce...@wireless-networks.com>.
Phil Evans wrote:
>> environment. Tomcat will die on us regularly without giving any
>> hint as to why, and also occasionally decides to chew all the
>> CPU for no apparent reason (no hits even being made). Id love to
>> hear from anyone who is having more success with Tomcat and
>> any suggestions anyone may have for improving its stability and or
>> diagnosing what the problem may be.
>>
>
> Are you certain that it is Tomcat - not Stronghold - that takes over your
> processor?
Tomcat *does* take over the processor. I see that very often with Tomcat
3.2b6/jdk1.3/Win2K
For example, any slight configuration error and BANG, 100% CPU used, no
errors reported.
Cedric
Re: bad time with tomcat
Posted by Phil Evans <ph...@solnet.co.nz>.
> environment. Tomcat will die on us regularly without giving any
> hint as to why, and also occasionally decides to chew all the
> CPU for no apparent reason (no hits even being made). Id love to
> hear from anyone who is having more success with Tomcat and
> any suggestions anyone may have for improving its stability and or
> diagnosing what the problem may be.
>
Are you certain that it is Tomcat - not Stronghold - that takes over your
processor?
Can't remember the version details, but there was a version of Stronghold
which ate all your resources without telling you it was doing so - I was
able to get a patch from the site to fix it.
It might at least be worth trying to run your app on Apache rather than
Stronghold ... as a test ...
RE: bad time with tomcat
Posted by John Bateman <jo...@cyberworldgroup.com>.
Hi
I've also had issues with Tomcat, but maybe along different lines.
I'm using a P2-400mhz with 256 meg Ram Linux (6.2) box running Tomcat as
Stand alone.
I use JMeter to pound the heck out of some servlets on the machine like
SnoopServlet, Cookie25 and a couple of other basic servlets. The most
complex of them connects to a Sybase DB using the Sybase Type 4 driver
JConnect 5.2 (it does a Select 1 and spits out the value returned.).
So, here's the 'issue'. When we configure Jmeter to use Thread Groups of 20
threads each to beat up the machine, occasionally, okay I'm being generous,
frequently the Tomcat process dies at around an average of 50 threads or 50
concurrent requests.
My next step is to integrate with Apache, using mod_jk and see if I can get
this number higher. I know if I can hit about 100 or so my boss would feel
satisfied that it can be used in our production environment (load balanced
with all the bells and whistles). This would also mean he would be willing
to classify Servlet Engines as High end solutions and not low to mid level
like he does now.
Another reason I am using the 100 thread/connects as a 'highbar' is because
PHP, which is out current web language of choice, handles this load amount
easily, albeit it's not as strong a language as Java, but it does what it
has to to get our job done.
I'll keep you all posted with my tests.
Please feel free to let me know if I am barking up the wrong tree with these
tests.
Thanks a lot. (I'm very impressed with the participation of this list).
> -----Original Message-----
> From: Craig Day [mailto:craig@alderaan.com.au]
> Sent: Thursday, October 26, 2000 9:07 PM
> To: tomcat-user@jakarta.apache.org; general@jakarta.apache.org
> Subject: bad time with tomcat
>
>
> Hi All,
> We are having a horrible time with tomcat in out production
> environment. We are running 3.1 on multiple Ultra-250s each
> with 1gig of memory running Solaris26 and Sun JDK1.2.2_005.
> The application is a relatively simple JSP-based app producing
> XML out of Oracle 8.1.6. We do simple load balancing via DNS.
> We are using Stronghold, but not the jserv connector, we ProxyPass
> the requests instead.
> At this point, tomcat is the least stable component in our
> environment. Tomcat will die on us regularly without giving any
> hint as to why, and also occasionally decides to chew all the
> CPU for no apparent reason (no hits even being made). Id love to
> hear from anyone who is having more success with Tomcat and
> any suggestions anyone may have for improving its stability and or
> diagnosing what the problem may be.
>
> regards
> craig
>