[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895171#comment-15895171
 ] 

Nathan Johnson commented on CLOUDSTACK-9413:
--------------------------------------------

We're seeing the same thing.  I think this might be caused by this line:

    VMInstanceVO vmInstance = _vmInstanceDao.findById(vmId);

returning a null, and then being dereferenced on this line (2221 as of 4.8.0):

    _vmIpFetchThreadExecutor.execute(new VmIpAddrFetchThread(vmId, nicId, 
vmInstance.getInstanceName(),

It would be easy enough to put some sort of guard around the instance name 
fetching, however I'm not sure what it actually means if there is no 
corresponding record in the vm_instance table, and what should happen here.

[~jayapal] do you have any thoughts?


> VmIpFetchTask NullPointerException
> ----------------------------------
>
>                 Key: CLOUDSTACK-9413
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9413
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.8.0
>         Environment: CentOS 6.8 (latest)
>            Reporter: Fabian Stelzer
>            Priority: Minor
>
> I'm getting the following exception in the management server logs exactly 
> every 3 minutes. However i don't see any impact on production or management 
> functionality.
> [c.c.v.UserVmManagerImpl] (UserVm-Scavenger-1:ctx-33f26ddb) Caught the 
> Exception in VmIpFetchTask
> java.lang.NullPointerException
>       at 
> com.cloud.vm.UserVmManagerImpl$VmIpFetchTask.runInContext(UserVmManagerImpl.java:2221)
>       at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>       at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>       at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>       at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>       at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>       at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>       at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
>       at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>       at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>       at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>       at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to