BlockingQueue and guard adding null #707
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR for:
#621
We intermittently see NPEs from:
at com.newrelic.agent.stats.StatsServiceImpl.doStatsWork(StatsServiceImpl.java:61) ~[newrelic.jar:7.4.2]
at com.newrelic.agent.service.ServiceManagerImpl.replayStartupStatsWork(ServiceManagerImpl.java:585)
Which is preventing application startup with the agent.
They get the following error in newrelic.log when that happens.
We have been unable to replicate the issue. However there is general agreement that we can and should just guard against the NPE in that spot. It's also possible that another thread causes an issue.
This PR changes the List holding StatsWork to a LinkedBlockingQueue and guards against attempting to add a null to the queue (which would throw an NPE for LBQ). Logs that this occurred.
Checks