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

New Relic Java Agent 6.2.0 is broken with SpringBoot 2.3.5 if there is no response body. #114

Closed
northyg opened this issue Nov 14, 2020 · 0 comments · Fixed by #115
Closed
Assignees
Labels
bug Something isn't working as designed/intended

Comments

@northyg
Copy link

northyg commented Nov 14, 2020

Filing this on behalf of Lawrence Ong regarding Support ticket #435916 and Community post.

Description

The NewRelic Java agent with SpringBoot 2.3.5 hangs if there is no response body. Tried this with HTTP OK response with zero body and HTTP NoContent response (where we cannot add any body at all).

Sample Code - Hangs with Agent 6.2.0, works with Agent 6.1.0

@Configuration
class Routes {
    @Bean
    fun route() = router {
        ("/api" and accept(MediaType.APPLICATION_JSON)).nest {
            GET("/test") {
                ServerResponse.ok().build()
            }
            GET("/test204") {
                ServerResponse.noContent().build()
            }
        }
    }
}

Expected Behavior

Java agent should work as it did in 6.1.0 and not hang.

Troubleshooting or NR Diag results

Logs and further details are in the support ticket linked below.

Steps to Reproduce

Sample application in support ticket.

Additional context

Internal support ticket with details: https://support.newrelic.com/tickets/435916
https://discuss.newrelic.com/t/new-relic-java-agent-6-2-0-is-broken-with-springboot/121470

@northyg northyg added the bug Something isn't working as designed/intended label Nov 14, 2020
@tspring tspring self-assigned this Nov 16, 2020
@tspring tspring linked a pull request Nov 16, 2020 that will close this issue
jasonjkeller pushed a commit that referenced this issue Jun 4, 2024
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
None yet
Development

Successfully merging a pull request may close this issue.

2 participants