Netty Http2 instrumentation can throw an NPE #1947
Assignees
Labels
bug
Something isn't working as designed/intended
GTSE
There is an associated support escalation with this issue.
jul-sep qtr
Represents proposed work item for the Jul-Sep quarter
Milestone
Comments
jbedell-newrelic
added
bug
kford-newrelic
added this to the Java Agent - FY25Q2 KTLO & Core Instrumentation Improvements milestone
kford-newrelic
added
the
jul-sep qtr
github-project-automation
bot
moved this from In Sprint
to Code Complete/Done
in Java Engineering Board
|
The Netty classes weaved to support HTTP/2 have been refactored which resulted in the removal of the weave class that was causing the NPE. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related GTSE: https://new-relic.atlassian.net/jira/software/c/projects/NR/boards/289?selectedIssue=NR-280663
The following line in Http2RequestWrapper can throw an NPE (and thus reporting an invalid error up) when the method is null:
httpRequest = HttpConversionUtil.toHttpRequest(msg.stream().id(), msg.headers(), true)Error message is:
method header cannot be null in conversion to HTTP/1.xWe need to understand when/why the method can be null and what to do in that case.
The text was updated successfully, but these errors were encountered: