Oops, not the same problem. 5408 is out of system memory, different than the one I mentioned about Min¹s fix which is about JVM heap
Kelven On 12/9/13, 2:53 PM, "Kelven Yang" <kelven.y...@citrix.com> wrote: >This issue is caused by trying to solve a mysterious JVM incompatibility >issue in a wrong trying in commit >ed0fbcc81c1928062054190ffcfab8bb59969cc2. Min has already reverted the >commit and this should have fixed the memory issue. > >Kelven > >On 12/7/13, 5:07 PM, "Sateesh Chodapuneedi" ><sateesh.chodapune...@citrix.com> wrote: > >>> -----Original Message----- >>> From: Rayees Namathponnan [mailto:rayees.namathpon...@citrix.com] >>> Sent: 08 December 2013 04:32 >>> To: dev@cloudstack.apache.org >>> Subject: 4.3 vmware automation blocker >>> >>> Vm deployment failing latest 4.3 build in Vmware environment; below >>>defect created >>> >>> https://issues.apache.org/jira/browse/CLOUDSTACK-5408 >>> >>> >>> 4.3 automation blocked due to this; someone possible to look this ? >> >>I also observed this. >>Upgrading SSVM's service offering to accommodate more memory (784MB >>instead of default 256MB) has helped. >> >>Regards, >>Sateesh >> >>> >>> >>> Regards, >>> Rayees >>> >>> >>> >> >
