- marked as blocker
- edited description
- attached 周报模板.zip
- attached 869EC7F3-132A-4810-BF0B-C9209D45729A.png
unexpected frame type(close)
when test websocket with jmeter , I get below error :
Response code:Sampler error: unexpected frame type (close).
Response message:Received: Close frame with status code null and close reason 'null'
but i can run testplan with postman .
Comments (7)
-
reporter -
repo owner Please, check this out first:
- https://bitbucket.org/pjtr/jmeter-websocket-samplers/issues/110/error-unexpected-frame-type-received-in
- https://bitbucket.org/pjtr/jmeter-websocket-samplers/issues/169/getting-close-frame-with-status-code-null
- https://bitbucket.org/pjtr/jmeter-websocket-samplers/issues/158/sampler-error-unexpected-frame-type
-
thanks for your answer 。 i find more about this error .
first question : this error happen when i use “WebSocket Text Frame Filter”。i also find that result tree don’t show all response if don’t use it . so what should i do ? do you have a better idea
when use jmeter test websocket , server log : “disconnected: transport error”
WebSocket Text Frame Filter :
use “WebSocket Text Frame Filter”
don’t use “WebSocket Text Frame Filter”
second question : server log
-
repo owner Your question about whether not to use a frame filter is a matter of test plan design the involves deep knowledge of the protocol (on top of websockets) use in your case. This is an issue tracker, not a Q&A forum. Try stackoverflow.
And read the documentation https://bitbucket.org/pjtr/jmeter-websocket-samplers/src/master/README.md. The answer to your question is literally in there: “f you do not close the WebSocket connection yourself, it will stay open at the end of the test.”
-
why server log : “disconnected: transport error” ( what should to do to resolve transport error )
-
repo owner I don’t know why your server concludes there is a transport error. Note that “transport error” is a very generic term, it could mean everything.
However
, the line above gives a clue: “disconnected: ping timeout”. So, it could be that the server closes the connection because of a ping timeout and than some other part of the server does not know it closed the connection itself and reports that the connection is gone. But this is all pure speculation of course.
Hint: to make JMeter reply to ping’s, use a PingPong filter and enable the reply to ping option.
-
repo owner - changed status to invalid
- Log in to comment