(in series of
tests).
..
- [EMAIL PROTECTED]
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: 24. júní 2002 09:47
To: Tomcat Users List
Subject: Re: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Reynir Hübner wrote:
hi Remy
Reynir Hübner wrote:
Hi guys,
this is just a follow up on the case,
I've tried serveral combinations to get rid of the memory bug :
tc4.1.5 with jasper1 from tc.4.0.3.
tc4.1.3 with jasper1 from tc.4.0.3.
tc4.1.5 with HTTPConnector from tc.4.0.3
tc4.1.3 with HTTPConnector from
more clearly that there are no problems with coyote.
-reynir
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: 25. júní 2002 10:07
To: Tomcat Users List
Subject: Re: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Reynir Hübner wrote:
Hi
Subject: Re: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Reynir Hübner wrote:
Victor the others..
I've tested tc 4.1.5 and I get very similar problems as I
did with tc. 4.1.3.
if I stress/load my application with 10*10 threads I get
messages like this on the stdout log
Reynir Hübner wrote:
no not really.
but for the reference of what the jsp-pages are doing in this application (that I
tested), we are using OSCache from www.opensymphony.com, that seems to crack up when
being run in 4.1.5 (really weird... I dont know what is happening). We are using few
hi Remy,
I don't see how opensymphony would create problems, but 4.1.5
introduces
tag instance pooling. If those are tags which keep a lot of
stuff in
memory, then I suppose it could hurt.
That's what it is. both in memory and on disk.
Or it is, as I stated before, an
Jacob Hookom wrote:
I have found performance problems with the new Coyote connector, it runs
fine initially, but after about 2 hours of simple operation, it hangs on
page requests at 4-6 seconds while at the same time, I can hit the
standard HTTP connector on a different port, and requests
Reynir Hübner wrote:
hi Remy,
I don't see how opensymphony would create problems, but 4.1.5
introduces
tag instance pooling. If those are tags which keep a lot of
stuff in
memory, then I suppose it could hurt.
That's what it is. both in memory and on disk.
Or it is, as I
Title: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Has anyone tried running stress tests using the new JDK 1.4.1 Beta??
Apparently it fixes the Javac memory leak bug. This may not make a difference here ( I believe there might be instance pooling issues), but would
Reynir Hübner wrote:
Victor the others..
I've tested tc 4.1.5 and I get very similar problems as I did with tc. 4.1.3.
if I stress/load my application with 10*10 threads I get messages like this on the
stdout log :
ThreadPool: Caught exception executing
(ms level).
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Sunday, June 23, 2002 3:04 PM
To: Tomcat Users List
Subject: Re: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Reynir Hübner wrote:
Victor the others..
I've tested tc 4.1.5 and I get very
, at least
I would not use tc4.1.5 for production as it is right now.
-reynir
-Original Message-
From: Victor Popiol [mailto:[EMAIL PROTECTED]]
Sent: 21. júní 2002 15:57
To: Tomcat Users List
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
It also helped us
, 2002 11:44 AM
To: Tomcat Users List
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
More details:
Server
Compaq Single Processor 512 MB RAM
Windows 2K
Tomcat
- Tomcat 4.1.3 Beta, binary distribution running as a service and using
Tomcat 4.0's isapi_redirector.dll to interface
the same stress and tests.
Regards
Victor
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 10:47 AM
To: Tomcat Users List
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Howdy,
You're getting that because you need more
.
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Victor Popiol [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 20, 2002 4:24 AM
To: Tomcat Users List
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Hi. I installed Tomcat 4.1.3 and deployed my
Victor Popiol wrote:
I installed Tomcat 4.1.3 beta. Took a while to configure because the hidden issue
with the user vs username parameter in the datasource definition.
After it has been running for a day, it died. Looking at the logs I found the
following:
java.lang.OutOfMemoryError
Orders of magnitude better.
-Original Message-
From: William Au [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 9:38 AM
To: Tomcat Users List
Subject: Re: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
So how is the performance of Tomcat 4.1.3 comparing to 4.0?
Bill
Millennium ChemInformatics
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 9:46 AM
To: Tomcat Users List
Subject: Re: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Victor Popiol wrote:
I installed Tomcat 4.1.3 beta. Took a while
: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Victor Popiol wrote:
I installed Tomcat 4.1.3 beta. Took a while to configure because the hidden issue
with the user vs username parameter in the datasource definition.
After it has been running for a day, it died. Looking at the logs I
Users List
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
More details:
Server
Compaq Single Processor 512 MB RAM
Windows 2K
Tomcat
- Tomcat 4.1.3 Beta, binary distribution running as a service and using
Tomcat 4.0's isapi_redirector.dll to interface with IIS
- Using
2002 15:44
To: Tomcat Users List
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
More details:
Server
Compaq Single Processor 512 MB RAM
Windows 2K
Tomcat
- Tomcat 4.1.3 Beta, binary distribution running as a service
and using Tomcat 4.0's isapi_redirector.dll
, June 21, 2002 11:43 AM
To: Tomcat Users List
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
I had the same problem, increased memory up to 512 and got rid of it.
But it seemd kind of obvious to me that tomcat 4.1.3 was taking way more memory than
4.0.3, for example
Victor Popiol wrote:
It also helped us when we increased the memory. Right now, we have scheduled a daily
service restart (this is in production :-( ).
I'll be looking forward to your feedback regarding 4.1.5
Since apparently you are not using many static pages, this would seem to
rule out
of memory yet.
Thanks
Victor
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 21, 2002 12:09 PM
To: Tomcat Users List
Subject: Re: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Victor Popiol wrote:
It also helped us when we increased
Victor Popiol wrote:
My initial suspition was Jasper. But there have been less and less JSP compilations
after the site was deployed.
One thing I wanted to try, to rule out Jasper, was to precompile all the JSP's. But
I can't figure out how to do that. I guess I'll have to write an ant
-
From: Victor Popiol [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 20, 2002 4:24 AM
To: Tomcat Users List
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Hi. I installed Tomcat 4.1.3 and deployed my application. But I
consistently get en error trying to connect to our
:[EMAIL PROTECTED]]
Sent: Thursday, June 20, 2002 10:08 AM
To: Tomcat Users List
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
Howdy,
I know you already solved the problem (was userid).
As an aside, it's a bad idea to unpack 3rd party jars. You probably
want to rename classes12
!
- Original Message -
From: Victor Popiol [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, June 20, 2002 5:19 PM
Subject: RE: Tomcat 4 performance issues - Trying Tomcat 4.1.3 Beta
I installed Tomcat 4.1.3 beta. Took a while to configure because the hidden
issue
28 matches
Mail list logo
