You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: