Thank you for this suggestion. Using a different JDK hadn't even crossed my mind. I had already bumped my memory settings up to 1024 in eclipse and it was still failing under the Sun one. After swapping in JRockit, it worked perfectly!
~Dave Shuck /************************************** blog: www.daveshuck.com tweets: www.twitter.com/dshuck cf peeps: www.dfwcfug.org **************************************/ On Wed, Dec 2, 2009 at 5:23 PM, Wing Yew Poon <[email protected]>wrote: > Just an idea: I have sometimes found that using a different JDK helps, > e.g., use JRockit instead of Sun's JDK. > > ------------------------------ > *From:* Dave Shuck [mailto:[email protected]] > *Sent:* Wednesday, December 02, 2009 3:16 PM > *To:* [email protected] > *Subject:* Suggestions for out of memory error on xml bean ant task? > > I am trying to to build a JAR file from a _very_ large XSD file (12K lines) > on a laptop that is (unfortunately) running Windows 7 with 2GB of memory. > Both from within eclipse and from the command line, I am getting "[xmlbean] > java.lang.OutOfMemoryError: Java heap space" errors as it attempts to > compile 7604 source files after parsing the XSD. Within eclipse.ini I have > boosted the memory settings as high as I can without success. > > While I realize that this size XSD is pretty excessive, our company has a > Hudson server that does successfully build this XSD-->JAR nightly, so I know > that it can be compiled given the right environment. > > Does anyone have any suggestions for how I might be able to better manage > the memory to allow me to build on my development laptop? > > Thanks in advance for any help. > > > ~Dave Shuck > /************************************** > blog: www.daveshuck.com > tweets: www.twitter.com/dshuck > cf peeps: www.dfwcfug.org > **************************************/ >
