The JVM memory setting I gave after Javelin merge may be too aggressive if you are running management server inside a VM. -XX:MaxPermSize=512m is for the fact that we have so many java classes (it might work in 256m configuration I think) and -Xmx2g is for the total heap (2G), almost the maximum for a 32-bit process, if you are running inside a VM and don't have much management server load, you may try out with 1G of heap size.
Kelven On 2/4/13 3:44 PM, "Ryan Dietrich" <[email protected]> wrote: >Actually, the build reported success with no errors! I ended up blowing >away my entire cloudstack vm and started over. Things seem to be >working now. >I actually run the management server ON devcloud itself, so the new >memory requirements required me to up my settings (i.e.: export >MAVEN_OPTS="-XX:MaxPermSize=512m -Xmx2g") > >/boot/grub/grub.cfg > >I upped my xen "dom0_mem" so I could get a little more base memory. I >was swapping quite badly when trying to launch jetty, and got memory >errors along the way. > >-Ryan Dietrich > >On Feb 4, 2013, at 3:00 PM, Kelven Yang <[email protected]> wrote: > >> It looks like your first command was actually failed to execute? >> com.cloud.upgrade.DatabaseCreator is packaged in the artifact from the >> first command. >> >> >> Kelven >> >> >> On 2/4/13 9:20 AM, "Ryan Dietrich" <[email protected]> wrote: >> >>> After a pull on the master branch, I am unable to deploy the database. >>> >>> I ran: >>> mvn -P developer,systemvm clean install >>> Then: >>> mvn -P developer -pl developer,tools/devcloud -Ddeploydb >>> I got: >>> java.lang.ClassNotFoundException: com.cloud.upgrade.DatabaseCreator >>> >>> >>> On Feb 4, 2013, at 9:40 AM, Sailaja Mada <[email protected]> >>>wrote: >>> >>>> Hi, >>>> >>>> These are the observations with 4.1 master branch dev environment >>>>today >>>> . >>> >> >
