You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Prachi Damle (JIRA)" <ji...@apache.org> on 2013/07/31 03:16:47 UTC
[jira] [Commented] (CLOUDSTACK-3940) NPE when cleaning up accounts
from ActionEventsUtils
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724708#comment-13724708 ]
Prachi Damle commented on CLOUDSTACK-3940:
------------------------------------------
This got fixed by Marcus as part of https://issues.apache.org/jira/browse/CLOUDSTACK-3957
> NPE when cleaning up accounts from ActionEventsUtils
> ----------------------------------------------------
>
> Key: CLOUDSTACK-3940
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3940
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Affects Versions: 4.2.0
> Reporter: Prasanna Santhanam
> Assignee: Prachi Damle
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: mslog
>
>
> During account gc while running automated tests following NPE is observed:
> 2013-07-30 15:26:35,205 WARN [cloud.user.AccountManagerImpl] (AccountChecker-1:null) Failed to cleanup volumes as a part of account id=16 cleanup due to Exception:
> java.lang.NullPointerException
> at com.cloud.event.ActionEventUtils.getDomainId(ActionEventUtils.java:196)
> at com.cloud.event.ActionEventUtils.persistActionEvent(ActionEventUtils.java:136)
> at com.cloud.event.ActionEventUtils.onCompletedActionEvent(ActionEventUtils.java:109)
> at com.cloud.event.ActionEventInterceptor.interceptComplete(ActionEventInterceptor.java:70)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:131)
> at com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:624)
> at com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1513)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:680)
> Attaching vmops.log
--
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