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

[1006] WebSocket Read EOF on Close connection pattern #59

Open
enflout opened this issue Sep 21, 2016 · 0 comments
Open

[1006] WebSocket Read EOF on Close connection pattern #59

enflout opened this issue Sep 21, 2016 · 0 comments

Comments

@enflout
Copy link

enflout commented Sep 21, 2016

I have set Close connection pattern as:

Response pattern: NOT_A_CHANCE_TO_CONTINUE_CLOSE_CONNECTION
Close connection pattern: .*

Is is okay but in multi-thread environment sometimes I get an error in Sampler result:

  • Received message sampler does not appear in list #4 (61 bytes); matched connection close pattern
  • WebSocket session closed by the client
  • WebSocket client closed by the client
  • WebSocket connection closed unexpectedly by the server: [1006] WebSocket Read EOF
  • Leaving streaming connection open

I have found this code in project:

@OnWebSocketClose
public void onClose(int statusCode, String reason) {
    if (statusCode != 1000) {
        log.error("Disconnect " + statusCode + ": " + reason);
        logMessage.append(" - WebSocket conection closed unexpectedly by the server: [").append(statusCode).append("] ").append(reason).append("\n");
        error = statusCode;
    } else {
        logMessage.append(" - WebSocket conection has been successfully closed by the server").append("\n");
        log.debug("Disconnect " + statusCode + ": " + reason);
    }

    //Notify connection opening and closing latches of the closed connection
    openLatch.countDown();
    closeLatch.countDown();
    connected = false;
}

I have read about 1006 Close Code:

1006

  1006 is a reserved value and MUST NOT be set as a status code in a
  Close control frame by an endpoint.  It is designated for use in
  applications expecting a status code to indicate that the
  connection was closed abnormally, e.g., without sending or
  receiving a Close control frame.

https://tools.ietf.org/html/rfc6455#section-7.4.1

And I have no idea how to diagnose the underlying reason of this exception.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant