Edgar P Dollin
Thu, 30 Sep 2004 08:36:55 -0400
Great tip. Could also add some references to the standard ant memory option
This SHOULD make the Troubleshooting FAQ page as it allows me to actually
run my tests again. I had given up on webtest and now I will give it
> -----Original Message-----
> From: Greg Vatman [mailto:firstname.lastname@example.org]
> Sent: Wednesday, September 29, 2004 5:59 PM
> To: email@example.com
> Subject: RE: [Webtest] OutOfMemoryError
> After much painful debugging, I have finally discovered the
> problem and found the solution.
> During one of my OutOfMemoryError messages, I received some
> extra information about the heap:
> compacting perm gen total 65536K, used 65535K [0x14010000,
> 0x18010000, 0x18010000)
> the space 65536K, 99% used [0x14010000, 0x1800fd98,
> 0x1800fe00, 0x18010000)
> It seems the permanent generation is spaced used by Sun's
> HotSpot to optimize performance and is seperate from heap
> sizes set by using Xmx and Xms options. This explains why I
> never reach my maximum heap size before getting OutOfMemoryError.
> Ant is loading a huge number of jars and using many classes
> and methods, all of which are being dumped into the permanent
> space. The default size is 32M for clients and 64M for
> servers. I guess that is why some people solved their issues
> by using the -server option.
> My solution was to use the following option in ANT_OPTS:
> Now I'm able to run the entire suite without error.
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.771 / Virus Database: 518 - Release Date: 9/28/2004