Jmx closed connection [possible bug]

After a timeout of a single query it seems that all the connections are closed:

func TestJmxNoTimeoutQuery(t *testing.T) {

    defer Close()

    if err := openWait("", "", "", "", openAttempts); err != nil {
        t.Error(err)
    }

    if _, err := Query(cmdTimeout, 0); err != nil {
        t.Error(err)
    }
    if _, err := Query(cmdBigPayload, timeoutMillis); err != nil {
        t.Error(err)
    }
}

This produces:

    jmx_test.go:146: timeout waiting for query: timeout
    jmx_test.go:149: EOF

While the first one is expected, the second one it is not, since the timeout is of the single query and there is no reason to fail the second one. We had users complaining for this behaviour.

However, this could be expected behaviour if we close the connection and we prefer to fail since the library is not able to "trash" the result for the timeout query that is not interesting anymore. Further investigation is needed

newrelic / infra-integrations-sdk

Jmx closed connection [possible bug] #278