[jira] [Updated] (CLOUDSTACK-346) Cannot add Vmware cluster with class loader conflict exception

["Rohit Yadav (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rohit Yadav updated CLOUDSTACK-346:
-----------------------------------

    Affects Version/s:     (was: pre-4.0.0)
                       4.1.0
    
> Cannot add Vmware cluster with class loader conflict exception
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-346
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-346
>             Project: CloudStack
>          Issue Type: Bug
>          Components: Management Server
>    Affects Versions: 4.1.0
>            Reporter: Mice Xia
>            Assignee: Rohit Yadav
>             Fix For: 4.1.0
>
>
> [how to reproduce]
> 1) run a nonoss env followed with instructions from this link: 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Building#Building-Packaging
> 2) ant debug
> 3) add a vmware cluster
> 4) exception catched
> loader constraint violation: when resolving field "service" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the referring class, org/apache/axis/client/Stub, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for the field's resolved type, javax/xml/rpc/Service, have different Class objects for that type
> [analysis]
> seems a conflict between ./webapps/client/WEB-INF/lib/vmware-lib-jaxrpc.jar and lib/axis-jaxrpc-1.4.jar
> remove the vmware-lib-jaxrpc.jar, then cluster could be added.
> Please notice here i'm using vsphere 5.1, but this issue seems unlikely related to vcenter version

--
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