Thanks for the reply Mike. I see though I am now running into the same problem
you did when trying to start the client from eclipse. I have already edited my
eclipse.ini file thusly.....
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20140603-1326
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
2048m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.6
-Xms1024m
-Xmx2048m
And based on one of your emails I found on the web I also set the Environment
variable MAVEN_OPTS to -XX:MaxPermSize=256m -Xmx1g
I am still seeing OutOfMemoryErrors....
NFO [c.c.u.d.GenericDaoBase] (main:null) Cache created: [ name = UserDaoImpl
status = STATUS_ALIVE eternal = false overflowToDisk = false
maxEntriesLocalHeap = 5000 maxEntriesLocalDisk = 0 memoryStoreEvictionPolicy =
LRU timeToLiveSeconds = 300 timeToIdleSeconds = 300 persistence = none
diskExpiryThreadIntervalSeconds = 120 cacheEventListeners:
net.sf.ehcache.statistics.LiveCacheStatisticsWrapper hitCount = 0
memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0
missCountExpired = 0 maxBytesLocalHeap = 0 overflowToOffHeap = false
maxBytesLocalOffHeap = 0 maxBytesLocalDisk = 0 pinned = false ]
2015-01-30 14:32:30.297:WARN:oejw.WebAppContext:main: Failed startup of context
o.e.j.m.p.JettyWebAppContext@14efeb2b{/client,file:/C:/workspaces/Cloudstack/WS1/cloudstack/client/target/generated-webapp/,STARTING}{file:/C:/workspaces/Cloudstack/WS1/cloudstack/client/target/generated-webapp/}
org.springframework.context.ApplicationContextException: Failed to start bean
'cloudStackLifeCycle'; nested exception is java.lang.OutOfMemoryError: PermGen
space
at
org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:170)
at
org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51)
at
org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339)
at
org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143)
at
org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108)
at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:947)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117)
at
org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:79)
at
org.apache.cloudstack.spring.module.factory.ModuleBasedContextFactory.loadModules(ModuleBasedContextFactory.java:37)
at
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.init(CloudStackSpringContext.java:70)
at
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.<init>(CloudStackSpringContext.java:57)
at
org.apache.cloudstack.spring.module.factory.CloudStackSpringContext.<init>(CloudStackSpringContext.java:61)
at
org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListener.contextInitialized(CloudStackContextLoaderListener.java:52)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:798)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:789)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1345)
.......
Has anyone gotten this running from eclipse?
Roger Crerie
-----Original Message-----
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Thursday, January 29, 2015 5:29 PM
To: dev@cloudstack.apache.org
Subject: Re: eclipse build problems
Presumably there are dependencies in that Brocade code that you have to acquire
yourself (not sure where to get them from) and the build command I listed must
not build that project.
On Thu, Jan 29, 2015 at 3:22 PM, Mike Tutkowski < mike.tutkow...@solidfire.com>
wrote:
> I currently see "only" 338 errors when I'm in Eclipse. :)
>
> I'd say the main thing is can you run this successfully from a command
> line (or kicked off from Eclipse)?
>
> mvn -P developer,systemvm clean install
>
> If you use VMware, then
>
> mvn -P developer,systemvm clean install -D noredist
>
> On Thu, Jan 29, 2015 at 2:46 PM, Roger Crerie <roger.cre...@hds.com>
> wrote:
>
>> Hello all,
>> I am a new developer to the cloudstack source base
>> and have been trying to get my development environment setup. I
>> primarily use Eclipse as my IDE of choice but while I have been close
>> at getting eclipse to compile cloudstack without error I am still seeing 757
>> errors to date.
>> Here are a sample of some of the problems I am seeing.
>>
>>
>> BorcadeVcsApi.java
>> Description Resource Path Location
>> Type
>> Activate cannot be resolved to a type BrocadeVcsApi.java
>> /cloud-plugin-network-vcs/src/com/cloud/network/brocade line 134 Java
>> Problem
>>
>> The issue stems from the fact tha
>>
>> import com.cloud.network.schema.* cannot be found.
>>
>> All of the class imports in this package are missing and it is
>> because there isn't a com.cloud.network.schema in my .m2 repository
>> or anywhere else I can thing to look.
>>
>>
>> HypervisorHostHelper.java
>>
>> import com.vmware.vim25.AlreadyExistsFaultMsg;
>>
>> Again this particular class could not be found. I have run the mvn
>> install:install-file command for the vim25_51.jar file I got from the
>> How to build Cloudstack website (
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+C
>> loudStack) and while that cleaned up a lot of the vim25 importing
>> errors there are still several cases of classes that cannot be found
>> such as the AlreadyExistsFaultMsg class.
>>
>> In addition there are several errors saying the
>> VirtualDeviceConfigSpecOperation.ADD field cannot be resolved.
>>
>> My thoughts on both these errors is that the jar library I got from
>> the website above is stale and a newer jar is out there to be found?
>>
>>
>> These are a couple of basic problems I have found in trying to build
>> in the eclipse IDE. Again I am new to developing for cloudstack so
>> any pointers that could be offered would be appreciated. Thanks
>>
>> Roger Crerie
>>
>>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> <http://solidfire.com/solution/overview/?video=play>*™*
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*
