[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13554461#comment-13554461
 ] 

Sateesh Chodapuneedi commented on CLOUDSTACK-615:
-------------------------------------------------

Hi Hugo,

This is regarding CLOUDSTACK-615.
As mentioned in the below commit message, do we still have to copy the jars to 
WEB-INF/lib directory by hand?

I see that maven repository is loading the jar files from maven proxy and the 
jars are added to classpath as well.
This sounds fine but for some reason the provided jar files seems not picked up 
and we see NoClassDefFoundError.

================================================================================
commit 6a20802640d702c41d342036634bde4cbc12b441
Author: Hugo Trippaers <htrippa...@schubergphilis.com>
Date:   Mon Oct 22 17:57:18 2012 +0200

    Fix runtime dependencies for vmware modules

    The vmware modules should be listed as provided so they are never
    packaged. However this also means that you have to put them in the
    web-inf/lib directory by hand.
================================================================================

Regards,
Sateesh


                
> Adding a VMware Cluster in a CS setup with CS-4.0.1 fails with 
> "java.lang.NoClassDefFoundError: Could not initialize class 
> com.vmware.vim.ManagedObjectReference"
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-615
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-615
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Hypervisor Controller
>    Affects Versions: 4.0.1
>         Environment: MS : Ubuntu 12.04, 
> CS-4.0.1 build : CloudStack-non-OSS-4.0.1-8.tar.bz2
> Host : Xen, Vmware
>            Reporter: Abhinav Roy
>            Assignee: Sateesh Chodapuneedi
>            Priority: Blocker
>             Fix For: 4.0.1
>
>
> Steps :
> ========================
> 1. Create a CS setup with Xen as host.
> 2. Deploy a VM
> 3. Add a VMware cluster.
> Expected Behaviour :
> ========================
> The Cluster should be added successfully.
> Observed behaviour :
> ========================
> The addition of VMware cluster fails with the following error............
> 2012-12-12 17:02:01,913 INFO  [hypervisor.vmware.VmwareServerDiscoverer] 
> (catalina-exec-20:null) Discover host. dc: 1, pod: 1, cluster: 4, uri host: 
> 10.102.125.210
> 2012-12-12 17:02:01,916 DEBUG [vmware.resource.VmwareContextFactory] 
> (catalina-exec-20:null) initialize VmwareContext. url: 
> https://10.102.125.210/sdk/vimService, username: administrator, password: 
> f**********
> 2012-12-12 17:02:01,947 ERROR [cloud.api.ApiDispatcher] 
> (catalina-exec-20:null) Exception while executing AddClusterCmd:
> java.lang.NoClassDefFoundError: Could not initialize class 
> com.vmware.vim.ManagedObjectReference
>         at 
> com.vmware.apputils.vim.ServiceConnection.<init>(ServiceConnection.java:26)
>         at 
> com.vmware.apputils.vim.ServiceConnection.CreateServiceConnection(ServiceConnection.java:32)
>         at com.vmware.apputils.AppUtil.setup(AppUtil.java:81)
>         at com.vmware.apputils.AppUtil.<init>(AppUtil.java:76)
>         at 
> com.vmware.apputils.version.ExtendedAppUtil.<init>(ExtendedAppUtil.java:31)
>         at 
> com.vmware.apputils.version.ExtendedAppUtil.initialize(ExtendedAppUtil.java:11)
>         at 
> com.vmware.apputils.version.ExtendedAppUtil.initialize(ExtendedAppUtil.java:26)
>         at 
> com.cloud.hypervisor.vmware.resource.VmwareContextFactory.create(VmwareContextFactory.java:53)
>         at 
> com.cloud.hypervisor.vmware.VmwareServerDiscoverer.find(VmwareServerDiscoverer.java:145)
>         at 
> com.cloud.resource.ResourceManagerImpl.discoverCluster(ResourceManagerImpl.java:464)
>         at 
> com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
>         at 
> com.cloud.api.commands.AddClusterCmd.execute(AddClusterCmd.java:153)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
>         at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
>         at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
>         at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
>         at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>         at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
>         at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>         at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>         at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>         at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>         at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>         at 
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:615)
>         at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>         at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>         at 
> org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
>         at 
> org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:744)
>         at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to