You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "shweta agarwal (JIRA)" <ji...@apache.org> on 2013/06/25 10:52:26 UTC
[jira] [Created] (CLOUDSTACK-3184) updatevirtual machine api gives
java NPE
shweta agarwal created CLOUDSTACK-3184:
------------------------------------------
Summary: updatevirtual machine api gives java NPE
Key: CLOUDSTACK-3184
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3184
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: API
Affects Versions: 4.2.0
Environment: build:
CloudPlatform-4.2-117-rhel6.3
Reporter: shweta agarwal
Priority: Blocker
Fix For: 4.2.0
Repro steps:
1.Create a VM
2.Stop the VM
3.Call Update Virtual machine API
Bug:
Hitting java NPE as soon as calling update virtual machine api
MS log snippet :
2013-06-25 14:19:01,179 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null) ===START=== 10.147.59.212 -- GET apiKey=zU9ue1DN5vmeJW1FukFqGAXZinL5LM55YemhbQmX9dOiSf9C4nCx6nzPH7lcIIoxnqbKi7qOLU1OmcmPWTzCfw&command=updateVirtualMachine&id=9184d82e-916e-4651-b069-c2a12d757592&response=json&signature=NNrooPcd3nYvYj6Iqxz9SFLK7x4%3D
2013-06-25 14:19:01,223 ERROR [cloud.api.ApiServer] (catalina-exec-15:null) unhandled exception executing api command: updateVirtualMachine
java.lang.NullPointerException
at com.cloud.vm.UserVmManagerImpl.updateVirtualMachine(UserVmManagerImpl.java:1776)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.vm.UpdateVMCmd.execute(UpdateVMCmd.java:130)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
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:555)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2274)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-06-25 14:19:01,227 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null) ===END=== 10.147.59.212 -- GET apiKey=zU9ue1DN5vmeJW1FukFqGAXZinL5LM55YemhbQmX9dOiSf9C4nCx6nzPH7lcIIoxnqbKi7qOLU1OmcmPWTzCfw&command=updateVirtualMachine&id=9184d82e-916e-4651-b069-c2a12d757592&response=json&signature=NNrooPcd3nYvYj6Iqxz9SFLK7x4%3D
2013-06-25 14:19:01,934 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-9:null) SeqA 8-51555: Processing Seq 8-51555: { Cmd , MgmtId: -1, via: 8, Ver: v1, Flags: 11, [{"ConsoleProxyLoadReportCommand":{"_proxyVmId":4,"_loadInfo":"{\n \"connections\": []\n}","wait":0}}] }
--
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