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

Kloadgen components are not visible in JMeter #117

Closed
rathishks opened this issue Aug 22, 2021 · 8 comments
Closed

Kloadgen components are not visible in JMeter #117

rathishks opened this issue Aug 22, 2021 · 8 comments

Comments

@rathishks
Copy link

Built master branch (Java11) and copied the plugin jar to /bin/ext and restaretd JMeter. But the KLoadgen components are not visible in JMeter. Not sure what went wrong. Any suggestions?

@rathishks rathishks changed the title Kloadgen component are not visible in JMeter Kloadgen components are not visible in JMeter Aug 22, 2021
@github-actions
Copy link

Thank you for collaborate with the project giving us feedback!!' You will help us a lot if you can attach and example AVRO and an example Test Plan in order to be able to reproduce the error. If that is the case. Cheers

@kszosze
Copy link
Contributor

kszosze commented Aug 23, 2021

Hi @rathishks,
the right folder is '/lib/ext' not '/bin/ext'. It should appear the components as we show in the README.md.

Do you mind double check on which folder you are dropping the jar?

Cheers!!

@M3lkior
Copy link
Contributor

M3lkior commented Aug 31, 2021

hi @kszosze ;

We also try to install KLoadGen on jMeter 5.4 ; building the master branch we deploy your plugin into lib/ext but the KLoadgen plugin don't appear in the plugin manager list and the Producer/Consumer Sampler are not presents

image

But the config components are available ... any idea ?

image

Also, reproducible with the 3.0.0 tag

Thanks in advance

@M3lkior
Copy link
Contributor

M3lkior commented Aug 31, 2021

ok @kszosze this about the name of you sample ;
@rathishks you should use the Java Request Sampler which is in fact a Keyloadgen Sampler :

image

@kszosze
Copy link
Contributor

kszosze commented Sep 2, 2021

Hi @M3lkior,

answering your question about plugin manager:

Developing a plugin under the scope of Plugin Manager is quite different from developing a normal plugin for JMeter. In the start of the project we consider following that path, but deadlines where so tight so we choose the basic one. But we still have this question over the table. Is an open discussion if we should move to this way of development.

Do you want collaborate with any thougths?

Cheers

@M3lkior
Copy link
Contributor

M3lkior commented Sep 2, 2021

I think that provided your plugin into a PluginManager is not so important but provided your artifacts into a public Maven registry (without authentication) like Maven Central seems to be more important to avoid team rebuilding your project :)
Or if it is not possible, provided your version artifacts attached to the Github releases artifacts.

@kszosze
Copy link
Contributor

kszosze commented Sep 2, 2021

Well, this is something to discuss, since you can, generate 2 different artifacts from our code meaning that I need to set up a complex action (not too complex, really).
Actually the Plugin jar is generated and uploaded into the Github Package like this one , it has security I know, but was a temporary solutions previous my holidays leave. This is still a work in progres,

In a few days I'll return and will take a look to your suggestions.

@jemacineiras
Copy link
Contributor

Closing this because will be covered in #237

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

4 participants