Unable to get full response in websocket request response (only get 4082 characters)

Issue #162 resolved
Pravin Bade created an issue

Only get max 4082 characters in WebSocket request-response and next response data transfer into the next request of the response body

Comments (9)

  1. Peter Doornbosch repo owner

    I don’t get it. What does “and next response data transfer into the next request of the response body” mean?

  2. Pravin Bade reporter

    Hi Peter,
    Thanks for the quick response.
    The issue is like not able to get a full response in the response body if the response data more then 4082 characters.
    example
    1.Websocket request-response sampler
    The server sends data to the client (With character count is 10,000)
    but WebSocket request-response sampler I can see only 4082 characters (reaming response data append into next request-response body)
    2.websocket request-response sampler
    I can see reaming response data in the second request

    Thanks

  3. Pravin Bade reporter

    Hi Peter,
    Thanks for pointing a doubt.
    I understood the concepts. I have tried the Fragmentation part that you share and it working.
    but need a full response in a single request-response sampler.
    I have tried to search how to configure the server to create larger messages for java WebSocket using tomcat8 but not found the perfect solution.
    You have reference links on how to configure large messages in server-side if you share it will very help full

    Just 2 questions.
    1.If the server sends the large message is jmeter can able to handle this large message with any configurations
    2. How many WebSocket connection can JMeter support (This for performance test)
    Max open connection limit in thread group of jmeter.

    Thank You

  4. Pravin Bade reporter

    I have tried the same scenario on other 3 different tools but there I can able get full response
    In the Chrome dev tool, advanced rest client and python web socket client I can able to get a full response in single request-response sampler

  5. Peter Doornbosch repo owner

    “but need a full response in a single request-response sampler.”

    Well, that’s too bad, the plugin does not support that. Not directly, that is. Maybe you can use a (beanshell) script to assemble the message from the fragments.

    Your questions:

    1. This depends on your definition of “message”. The plugin can handle websocket frames of arbitrary size (well, to certain limits of course, but these are rather large).
    2. The plugin can handle thousands of websocket connections. Actually, i started developing this plugin because i was frustrated by the other plugin supporting so little concurrent connections; for my use case i needed to tests really large setups. So, it was designed for maximum scalability (specifically: no additional threads are used for a websocket connection). In practice, the number of websocket connections is limited by system resources (memory, network ports) and not so much by the plugin itself. Our experience is that with “normal” hardware (what’s normal?) 5000 connections on one system is no problem.

    Cheers
    Peter

  6. Log in to comment