From owner-freebsd-java  Sun Jun 27 12:36:23 1999
Delivered-To: freebsd-java@freebsd.org
Received: from systemics.com (menger.ai [209.88.68.41])
	by hub.freebsd.org (Postfix) with ESMTP
	id 08C741507B; Sun, 27 Jun 1999 12:36:14 -0700 (PDT)
	(envelope-from iang@systemics.com)
Received: (from iang@localhost)
	by systemics.com (8.8.8/8.8.8) id PAA09363;
	Sun, 27 Jun 1999 15:35:15 -0400 (AST)
	(envelope-from iang)
Date: Sun, 27 Jun 1999 15:35:15 -0400 (AST)
From: Ian Grigg <iang@systemics.com>
Message-Id: <199906271935.PAA09363@systemics.com>
To: freebsd-java@FreeBSD.ORG, gregw@mortbay.com,
	java-port@FreeBSD.ORG
Subject: Re: JVM Out of memory
Reply-To: iang@systemics.com
In-Reply-To: <3775F247.320AE7DE@mortbay.com>
Sender: owner-freebsd-java@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


> > java TestClass
> **Out of memory, exiting**

Check the limits on the machine by running limits(1) and
see if there is any nasty limitation.  Also use top in
another session and try and figure out what it is consuming.

If you find one too low, then use ulimit(1) to up it, they
are generally soft up to a point.  You may need to bribe
your ISP to get them improved.

Having said all that, I'm not sure what the story is with
FreeBSD 2.2.8, but on FreeBSD 3, the limits are set too low
for ordinary users doing serious activity.

iang


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-java" in the body of the message