Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of rbuck@verisign.com designates
 216.168.239.74 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8850A.C727DF93"
Subject: Beta 2: java.lang.OutOfMemoryError: PermGen space
Date: Thu, 13 Mar 2008 09:04:44 -0400
Message-ID: 
 <B408B6F6E3DEB04681E207B528821D490139F519@DUL1WNEXMB05.vcorp.ad.vrsn.com>
Thread-Topic: Beta 2: java.lang.OutOfMemoryError: PermGen space
Thread-Index: AciFCs68Ih+O7bnXTWOKssaQpkoynA==
From: "Buck, Robert" <rbuck@verisign.com>
To: <ivy-user@ant.apache.org>

------_=_NextPart_001_01C8850A.C727DF93
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I just completed the upgrade to IVY 2 Beta 2. Overall I consider the
release an overall success. I like the new flexible cache management
support over all. However, there is one BIG regression...
=20
I use IVY for both resolving third party dependencies from our secure
ivy repository, as well as to manage inter-project dependencies. Since
using Beta 2 I have been having PermGen space issues. I am now up to
reserving 256M of PermSpace. Guys, there is definitely something wrong
here. For comparison, the global SMS messaging gateways that your
SMS/MMS traffic goes through, only has 64M, and that is running JBoss
with all sorts of stuff loaded. I cannot see any reason to require 256M
of PermGen space.
=20
Again, I just want to emphasize that the overall release is fantastic.
Fixing this one issue would go a long way.
=20
Thanks in advance,
=20
Bob
=20
java.lang.OutOfMemoryError: PermGen space

------_=_NextPart_001_01C8850A.C727DF93--