Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NullPointerException on Java Agent Lettuce instrumentation #1132

Closed
kford-newrelic opened this issue Jan 27, 2023 · 4 comments
Closed

NullPointerException on Java Agent Lettuce instrumentation #1132

kford-newrelic opened this issue Jan 27, 2023 · 4 comments
Labels
GTSE There is an associated support escalation with this issue.

Comments

@kford-newrelic
Copy link
Contributor

Description

Reported NPE on newrelic java agent 7.9 and 7.11 in the lettuce instrumentation

  java.lang.NullPointerException
    at com.nr.lettuce5.instrumentation.NRHolder.end(NRHolder.java:59)
    at com.nr.lettuce5.instrumentation.NRSignalTypeConsumer.accept(NRSignalTypeConsumer.java:24)
    at com.nr.lettuce5.instrumentation.NRSignalTypeConsumer.accept(NRSignalTypeConsumer.java:13)
    }}{{at reactor.core.publisher.FluxDoFinally$DoFinallySubscriber.runFinally(FluxDoFinally.java:156)
    }}{{at reactor.core.publisher.FluxDoFinally$DoFinallySubscriber.onError(FluxDoFinally.java:132)

It looks like params is null.

Not sure this causing any issues besides the noise.

Expected Behavior

NPE should not be encountered.

It's not clear whether the DB params object that is null is indicative of another issue or not - might need further investigation.

Your Environment

Upgraded from agent version 7.5 to either 7.9 or 7.11
Using java-11-openjdk-devel-11.0.17.0.8 and io.lettuce:lettuce-core:5.2.1.RELEASE

Additional context

Support escalation (GTSE) opened.

@kford-newrelic kford-newrelic added the GTSE There is an associated support escalation with this issue. label Jan 27, 2023
@workato-integration
Copy link

@workato-integration
Copy link

Jira CommentId: 180382
Commented by bellis:

[~relic-ag] The fix will go into a latest release. It will not be back ported to previous releases. To benefit from the fix, customers would need to upgrade to the agent version that the fix goes into.

@workato-integration
Copy link

Jira CommentId: 180383
Commented by bellis:

#1204

@workato-integration
Copy link

Work has been completed on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
GTSE There is an associated support escalation with this issue.
Projects
None yet
Development

No branches or pull requests

1 participant