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 (asf.osuosl.org: 66.249.82.206 is neither permitted nor
 denied by domain of anna.seekamp@googlemail.com)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=googlemail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=hut7EyOrNxNbrN25Z8N1J/m5gb7fEzSl0KC4644XMv8hUnXUBoPGhaCHlqHy/adzgAuRdTyOFO//9U8V0rZGR+vptDrMheQeF9Ww67jmN9uf/kR3w+oOWkFUQ95DOqbyTCb0Fyn7E1RRutYthFRTCPf+mG5MekwLI3/LGpcGhVI=
Message-ID: <f1809b850511020632obf804b2t@mail.gmail.com>
Date: Wed, 2 Nov 2005 15:32:34 +0100
From: Anna Seekamp <anna.seekamp@googlemail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: tomcat - OutOfMemoryError
In-Reply-To: <DDBBD1E00935D144AB9563D57EF98D622F76CF@raccoon.melandra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <DDBBD1E00935D144AB9563D57EF98D622F76CF@raccoon.melandra.net>

Thanks Peter,

We will run the tomcat with:
  -XX:+PrintGCDetails
in order to see the PermGen-Size

-- anna

2005/11/2, Peter Crowther <Peter.Crowther@melandra.com>:
> > > From: Anna Seekamp [mailto:anna.seekamp@googlemail.com]
> > > The jvm (1.4.2 Suse-Linux) starts with:
> > >  -server -Xmx1500m -Xms1500ms
> > >
> > > We have 9 webapps.
> > > One webapp has 50% load.
> > > The other share the rest.
> > > If we put 7 webapps online, we
> > > ran into problems. After a few hours we get OutOfMemoryErrors. The
> > > tomcat crashes an we get no response. But there isn't a
> > heavy load (<
> > > 1). There isn't OutOfMemory (the last Runtime.freeMemory():
> > 1,3 GB) The
> > > Thread-Dump of the crashed server is unspecific. Most threads are
> > > waiting on findBundle in CoyoteConnector.createRequest().
> > >
> > > Are there any suggestions. Everything is welcome!
> > > I don't know where to look. Threads, Sockets, Memory (is
> > there a problem
> > > with Runtime.freeMemory)
>
> 1. Check the PermGen usage - are you slowly loading more classes in
> until the default (64M I think) PermGen is exhausted?
> Runtime.freeMemory doesn't take into account the separation between
> PermGen and the other generations.
>
> 2. Java has a distressing habit of throwing out of memory errors when it
> runs out of any resources, including file descriptors or sockets.
> You'll have one heck of a log file to analyse, but as a last ditch
> effort I'd try running a system call tracer on the process and look for
> failed calls.
>
> However, I'm a novice in these areas.  I've no doubt you'll get better
> advice from those more experienced with large production apps.
>
>                - Peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

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