[kepler-users] Trouble with VM when starting Kepler

[Derik Barseghian]

Glad you got it working. It looks like our "min" argument is actually used for setting Xms, initial heap size. We ought to rename it. It's not clear to me why you had to do this. Thanks for letting us know.
Derik

On Dec 21, 2011, at 1:39 PM, Jonathan Boright wrote:

> Derik, 
> 
> Success! Changing the "min" entry in the memory.xml from 5m to 256m finally did the trick.
> 
> Thanks for your help!
> 
> Jon
> 
> On Wed, Dec 21, 2011 at 4:17 PM, Derik Barseghian <barseghian at nceas.ucsb.edu> wrote:
> I'm not sure what's causing this. What OS are you using? Are you within cygwin? Are you passing any memory arguments to java?
> Kepler uses a max of 512m by default. When starting in a suite utilizing the provenance module, max is adjusted to 768m.
> You can try adjusting max in build-area/settings/memory.xml. If Kepler hasn't already created this file for you, you can:
> 
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
> <properties>
> <comment>Default Memory Properties</comment>
> <entry key="max">512m</entry>
> <entry key="min">5m</entry>
> </properties>
> 
> You could also try passing JVM memory options (e.g. -Xmx) by editing and then launching using kepler.sh, which is created with ant make-startup-scripts.
> 
> I haven't had to do any of this in Windows XP. Let us know what you find out.
> 
> Derik
> 
> On Dec 21, 2011, at 12:16 PM, Jonathan Boright wrote:
> 
> > All,
> > I'm having trouble running Kepler on my laptop... I have installed and run Kepler on this machine in the past (the last time was probably a year ago) but have recently done an update... Now, when I try to run it (ant run) I get the following message:
> >
> > ...
> > run:
> >       [run] JVM Memory = 5m 512m
> >       [run] Set environment variable: PATH = C:\cygwin\usr\local\bin;C:\cygwin\bin;C:\cygwin\bin;[...long path list here...]
> >       [run] Set environment variable: R_HOME = C:\Program Files\R\R-2.10.1
> >       [run] Error occurred during initialization of VM
> >       [run] Too small initial heap for new size specified
> >
> > BUILD FAILED
> > C:\kepler\svn\build-area\build.xml:52: Java returned: 1
> >
> > ...which looks to me like a JMV memory error (not that I know much about them...). In prior versions of Kepler we were able to set the max memory allotment before opening up Kepler itself, but now there is a tool on the user-interface to do this... which doesn't do much good if you can't get to the interface.
> >
> > Any thoughts on:
> > 1, Why the default memory allotment is insufficient to start Kepler?, and/or
> > 2, How can I allot more memory to Kepler prior to opening it up?
> >
> > Thanks!
> >
> > Jon
> >
> > ---------------------------------------
> > Jonathan Boright
> > Research Scientist
> > ISciences, LLC
> > 61 Main Street, Suite 200
> > Burlington, VT 05401
> >
> > _______________________________________________
> > Kepler-users mailing list
> > Kepler-users at kepler-project.org
> > http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
> 
> 
> 
> 
> -- 
> ---------------------------------------
> Jonathan Boright 
> Research Scientist
> ISciences, LLC
> 61 Main Street, Suite 200
> Burlington, VT 05401
> 802 864-2999
> boright at isciences.com
> http://www.isciences.com 
> http://www.terraviva.net