if you use a more recent JDK, then the OutOfMemoryError should have an
additional message, depending on what this message is, you'll need to
apply different tuning parameters.
so if you share the message with us, we can maybe help you,
if your OOME doesn't have a message, upgrade your JDK and try again
Filip
mopont wrote:
Hello everyone!
I use tomcat since version 4, and in all of this time I always used to work
with small number of contexts in the webapps.
Nowadays I'm in working with a e-learning application, so we customize the
same version of our application to our clients. The fact is that the
increasing number of clients requests for the product made the number of
contexts in our tomcat raise to a limit, at this moment we have around 38
contexts (6.000 files each).
While we were using 4...5 contexts everything was fine, but now all that we
go is a bunch of "OutofMemory" errors even with a single .class deployment.
We use IIS as the front end + ISAPI FILTER + Tomcat. In a first moment we
tought that a version upgrade would give us a solution, and afted doing that
unhapply the same occurs again and again....
we gave to tomcat -Xms 512m -Xmx1024m of memory, but we have a "OutofMemory"
even before reaching that limit.
We setted the configuration for the JK connector for 450 connections and
even before that the same occurs!! Now we are thinking about clustering
tomcat, but we fear that even a cluster won't give us a solution.
Has anyone here experienced a similar problem before? We already thinking in
moving to SunAppServer...
can someone here help me with this ?
thanks in advance!!!
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 270.2.0/1495 - Release Date: 6/10/2008 5:11 PM
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
