jmeter-websocket | The jmeter plugin for WebSocket protocol | Plugin library

by kawasima Java Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | jmeter-websocket Summary

jmeter-websocket is a Java library typically used in Plugin applications. jmeter-websocket has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. However jmeter-websocket has 2 bugs. You can download it from GitHub.

This is the jmeter plugin for WebSocket protocol.

Support

Quality

Security

License

Reuse

Support

jmeter-websocket has a low active ecosystem.

It has 50 star(s) with 34 fork(s). There are 14 watchers for this library.

It had no major release in the last 6 months.

There are 5 open issues and 0 have been closed. On average issues are closed in 2605 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of jmeter-websocket is current.

Quality

jmeter-websocket has 2 bugs (0 blocker, 0 critical, 2 major, 0 minor) and 10 code smells.

Security

jmeter-websocket has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jmeter-websocket code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jmeter-websocket is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jmeter-websocket releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

jmeter-websocket saves you 324 person hours of effort in developing the same functionality from scratch.

It has 779 lines of code, 59 functions and 5 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed jmeter-websocket and discovered the below as its top functions. This is intended to give you an instant insight into jmeter-websocket implemented functionality, and help decide if they suit your requirements.

Samples a single entry
Returns the query string
Initialize the sampler
Returns the URI for the resource
Sets the path
Add an HTTP argument
Adds an HTTP argument
Parse query arguments
Initialize the panel
Gets the receive message panel
Helper method to retrieve a string from a resource key
Gets the protocol and path
Create a web socket sampler
Sets the name of the component
Modifies web socket test element
Returns true if there are arguments
Gets arguments
Configures the web socket sampler
Apply the given config to the sampler
Returns the default port for the given protocol and protocol
Returns the static label for the test
Add an argument
Set the protocol

Get all kandi verified functions for this library.

jmeter-websocket Key Features

No Key Features are available at this moment for jmeter-websocket.

jmeter-websocket Examples and Code Snippets

No Code Snippets are available at this moment for jmeter-websocket.

Community Discussions

Trending Discussions on jmeter-websocket

JMeter & socket.io - I can see the message I want, but the socket plugin is not showing what I expect

QUESTION

JMeter & socket.io - I can see the message I want, but the socket plugin is not showing what I expect

Asked 2022-Mar-02 at 15:16

Here is the socket message I see in the browser debugger console:

More illustrative, perhaps:

I call an API operation that triggers this message over a socket.

What I Tried

To preclude inaccuracies, I started 2 instances of JMeter.

REST API call.
Revised version of the GitHub JMeter example of sockets.io, in which I just call a WebSocket Sampler repeatedly on wss://events.dev.myserver.com:443/socket.io/?EIO=4&transport=websocket.

I kicked off (2).

While that was running, I kicked off (1).

Expected

Eventually, (1) should show me a sampler in the View Results Tree with the message in the screenshot ("42" - GAME_STARTED)

Actual

The only messages I see look like this:

This is really all I want to do: run the appropriate sampler, a sufficient time after making the API call, to get the message.

Update

We succeeded in finding the message using python-socketio:

...

ANSWER

Answered 2022-Feb-28 at 07:36

Take a look at other fields of the HTTP Request, in particular HTTP Headers, most probably your JMeter request is missing some essential information.

My expectation is that in order to "start the game" (whatever it means) you need to open the page in the browser, authorize somehow, follow the steps of the protocol upgrade mechanism, etc. to wit exactly mimic what real browser does, all the request sequence which is prior to starting the game.

You might need to correlate dynamic parameters, add HTTP Header Manager, add HTTP Cookie Manager, etc.

Source https://stackoverflow.com/questions/71285624

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jmeter-websocket

You can download it from GitHub.
You can use jmeter-websocket like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the jmeter-websocket component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: