[BUG] NPE bug at startup

[zqr10159]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Expected Behavior

No response

Steps To Reproduce

No response

Environment

HertzBeat version(s):1.6.1

Debug logs

No response

Anything else?

No response

[ayu-v0]

please assign me

[ZY945]

I found that getNextCollectMetrics is called in two places, which involves obtaining priorMetrics. Only dispatchMetricsTask calls job. reconstructPriorMetrics();

[ayu-v0]

Perhaps the collection task is initialized the first time and does not need to be initialized later. @ZY945 i think

[ZY945]

Perhaps the collection task is initialized the first time and does not need to be initialized later. @ZY945 i think

It seems to be calling here all the time

[ayu-v0]

Perhaps the collection task is initialized the first time and does not need to be initialized later. @ZY945 i think

It seems to be calling here all the time

Thank you very much, I'll check again!

[ayu-v0]

I found that after debugging and checking the code for a long time, there is still no recurrence of the scene that returns null. Could you please give me a step to repeat this situation? Thanks @zqr10159

[zqr10159]

no recurrence of the scene that returns null. Could

It is very likely that the problem is caused by the custom collection interval. This problem occurred after I set a monitoring task to 10 seconds.

[ZY945]

I also encountered it while monitoring, setting the monitoring time to 10 seconds and then debugging it

[ayu-v0]

I also encountered it while monitoring, setting the monitoring time to 10 seconds and then debugging it

Thank you very much for your prompt, I also found that it is the problem caused by the short interval between the two threads.