测试cloudstack4.0.2对亚马逊AWS接口支持出现错误:
设置全局参数“enable.ec2.api”的值为true,修改完成后重启cloud-management。
在浏览器输入http://192.168.13.12:7080/awsapi/ 
HTTP Status 500 -



type Exception report
message
description The server encountered an internal error () that prevented it from 
fulfilling this request.
exception
java.lang.RuntimeException: javax.servlet.ServletException: Servlet execution 
threw an exception
        
com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:104)
        com.cloud.bridge.service.EC2MainServlet.doGet(EC2MainServlet.java:73)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

root cause
javax.servlet.ServletException: Servlet execution threw an exception
        
com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:102)
        com.cloud.bridge.service.EC2MainServlet.doGet(EC2MainServlet.java:73)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

root cause
java.lang.NoSuchMethodError: 
org.apache.axis2.engine.AxisEngine.<init>(Lorg/apache/axis2/context/ConfigurationContext;)V
        
org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUtil.java:135)
        
org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUtil.java:130)
        
org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.processURLRequest(AxisServlet.java:829)
        org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:255)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        
com.cloud.bridge.service.EC2MainServlet.doGetOrPost(EC2MainServlet.java:102)
        com.cloud.bridge.service.EC2MainServlet.doGet(EC2MainServlet.java:73)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

note The full stack trace of the root cause is available in the Apache 
Tomcat/6.0.24 logs.





zt

Reply via email to