Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 26DB6C46E for ; Fri, 19 Jul 2013 14:56:50 +0000 (UTC) Received: (qmail 55780 invoked by uid 500); 19 Jul 2013 14:56:49 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 55758 invoked by uid 500); 19 Jul 2013 14:56:49 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 55668 invoked by uid 500); 19 Jul 2013 14:56:49 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 55599 invoked by uid 99); 19 Jul 2013 14:56:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jul 2013 14:56:49 +0000 Date: Fri, 19 Jul 2013 14:56:49 +0000 (UTC) From: "Rayees Namathponnan (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (CLOUDSTACK-2613) Null Pointer exception while starting Management server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan closed CLOUDSTACK-2613. ------------------------------------------- CLOUDSTACK-1981 still open, closing this > Null Pointer exception while starting Management server > -------------------------------------------------------- > > Key: CLOUDSTACK-2613 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2613 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Install and Setup > Affects Versions: 4.2.0 > Environment: Master build > Reporter: Rayees Namathponnan > Fix For: 4.2.0 > > > Created new build from Master branch and start management server, below null pointer exception in Management server log > 2013-05-21 16:28:38,405 INFO [factory.annotation.AutowiredAnnotationBeanPostProcessor] (main:null) JSR-330 'javax.inject.Inject' annotation found and supported for autowiring > 2013-05-21 16:28:46,184 INFO [factory.annotation.AutowiredAnnotationBeanPostProcessor] (catalina-exec-1:null) JSR-330 'javax.inject.Inject' annotation found and supported for autowiring > 2013-05-21 16:28:46,260 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) ===START=== 10.223.240.193 -- GET apiKey=HdQzBTKgr3qQYraEGb29wL_dxYdR1BlRLrHFzEGxbg6FqCWO0KyM7c5aUafJwhVh0xHr2A78OYwPXztJiUqQVQ&command=listSystemVms&response=json&state=Running&zoneid=bab9b165-41bf-48ed-9c24-94c1219f54c0&signature=HX%2B6uow%2FFiGHwf%2FJl3VmNP%2FwQ9k%3D > 2013-05-21 16:28:46,263 ERROR [cloud.api.ApiServlet] (catalina-exec-1:null) unknown exception writing api response > java.lang.NullPointerException > at com.cloud.user.AccountManagerImpl.getSystemUser(AccountManagerImpl.java:304) > at com.cloud.user.AccountManagerImpl.getSystemUser(AccountManagerImpl.java:148) > at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:238) > 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:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > 2013-05-21 16:28:46,294 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) ===END=== 10.223.240.193 -- GET > API log > 2013-05-21 16:28:46,282 INFO [cloud.api.ApiServer] (catalina-exec-1:null) 10.223.240.193 -- GET apiKey=HdQzBTKgr3qQYraEGb29wL_dxYdR1BlRLrHFzEGxbg6FqCWO0KyM7c5aUafJwhVh0xHr2A78OYwPXztJiUqQVQ&command=listSystemVms&response=json&state=Running&zoneid=bab9b165-41bf-48ed-9c24-94c1219f54c0&signature=HX%2B6uow%2FFiGHwf%2FJl3VmNP%2FwQ9k%3D unknown exception writing api response > 2013-05-21 16:28:46,407 INFO [cloud.api.ApiServer] (catalina-exec-2:null) 10.223.240.193 -- GET apiKey=HdQzBTKgr3qQYraEGb29wL_dxYdR1BlRLrHFzEGxbg6FqCWO0KyM7c5aUafJwhVh0xHr2A78OYwPXztJiUqQVQ&command=listTemplates&listall=true&response=json&templatefilter=featured&signature=dod6EaTfMDX%2BMH1U0qxAi4RYhNU%3D unknown exception writing api response > 2013-05-21 16:29:38,666 INFO [cloud.api.ApiServer] (catalina-exec-14:null) 10.216.133.67 -- GET command=listCapabilities&response=json&sessionkey=oOjShuV5yHPU8iQ7sm5%2FYXe09m8%3D&_=1369179096208 unknown exception writing api response > 2013-05-21 16:29:49,391 INFO [cloud.api.ApiServer] (catalina-exec-2:null) 10.216.133.67 -- POST command=login domain=/ unknown exception writing api response -- 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