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

HTTP Query Parameter Loss After Upgrading to New Relic Agent v8.12.0 #2242

Open
dunamu-thor opened this issue Feb 21, 2025 · 1 comment
Open
Labels
bug Something isn't working as designed/intended

Comments

@dunamu-thor
Copy link

After upgrading to New Relic Agent version 8.12.0, our Spring Boot application (version 2.7) intermittently experiences missing HTTP query parameters. This results in a MissingServletRequestParameterException (HTTP 400 error) even though all expected parameters are present in the request. Notably, this issue is very hard to reproduce in a test environment and occurs only sporadically. Additionally, when the New Relic Agent is disabled, the issue does not occur.

Expected Behavior

All query parameters should be correctly passed through to the Spring Boot application so that valid requests do not result in a MissingServletRequestParameterException.

Troubleshooting or NR Diag results

No additional troubleshooting logs or diagnostic information have clarified the root cause of this intermittent issue.

Steps to Reproduce
1. Upgrade the New Relic Agent to version 8.12.0 in an environment running Spring Boot 2.7.
2. Send HTTP requests with all expected query parameters.
3. Very sporadically, the application throws a MissingServletRequestParameterException (HTTP 400 error).
4. Disabling the New Relic Agent prevents the error from occurring.

Your Environment
• Spring Boot Version: 2.7
• New Relic Agent Version: 8.12.0
• JVM Vendor/Version: [Please specify your JVM vendor and version]
• Frameworks/Configurations: Standard Spring Boot setup with no custom filters or interceptors modifying the HTTP request parameters.

Additional Context

This issue appears to be directly related to the upgrade of the New Relic Agent to v8.12.0. Given that the problem occurs very sporadically and is difficult to reproduce in test environments, we suspect that the agent’s internal instrumentation or asynchronous processing might be interfering with the proper handling of query parameters. Any insights or recommendations to diagnose and resolve this intermittent issue would be greatly appreciated.

@dunamu-thor dunamu-thor added the bug Something isn't working as designed/intended label Feb 21, 2025
@workato-integration
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as designed/intended
Projects
Development

No branches or pull requests

1 participant