In latest JMeter there are irrelevant plugins in Plugins Manager (start with jmeter - ) as jmeter - JDBC Support
It display JMeter components which are part of JMeter and can't be uninstalled,
Manager UI allow to uninstalled and if clicking Apply Changes and Restart JMeter it seems to have no real effect, but it's still very confusing.
It seems like a bug, but is it Plugin manager issue or JMeter? is there some purpose for displaying JMeter core features as plugins? can it be removed?
As feature is provided by plugins-manager, it is a plugins-manager issue.
I would suggest you report it on their forum.
The idea was to remove plugins (even core jmeter) that were not used.
As you know, Apache JMeter is built with Plugin Architecture in core, all protocols are plugins even core ones.
Related
I've been using custom plugins for JMeter:
https://jmeter-plugins.org/?search=random-csv
https://jmeter-plugins.org/?search=jpgc-casutg
I wanted to see the code, maybe improve a thing for myself and maybe others too.
For 1st on the page link goes to GitHub with code. But for the second (Custom Thread Groups), link points to https://jmeter-plugins.org/wiki/ConcurrencyThreadGroup/, where there is only a description.
Web search finds maven repo https://mvnrepository.com/artifact/kg.apc/jmeter-plugins-casutg/2.9 which have jar file. Surely it is said about open-source for JMeter, not plugins:
Custom Plugins for Apache JMeter™ This project is an independent set
of plugins for Apache JMeter, the popular Open-Source load and
performance testing tool.
So are Custom Thread Groups open source and if yes, where can I see the code? If not open-source, what is the licence for it?
It's part of JMeter (casutg) plugin, found in package com.blazemeter.jmeter.threads.concurrency
ConcurrencyThreadGroup.java
ConcurrencyThreadGroupGui.java
ConcurrencyThreadStarter.java
JMeter plugin license is Apache License 2.0
A permissive license whose main conditions require preservation of copyright and license notices.
See more about Apache license:
Apache License is a permissive open source software license
Is there any impact/effects in using an older version of JMeter?
Since in the JMeter best practices wiki page, it is advised not to use the versions that are older than 3 versions of the current one.
Provide more input in this regard, since am using an older version which is more than 3 versions of the current one.
Help needed.
It depends on Test Plan nature and what Test Elements you're using. Normally newer JMeter releases contain bug fixes and performance improvements so theoretically you can achieve higher throughput using newer JMeter version.
There is JMeter Performance evolution across versions wiki page where you can see the trend of improving JMeter performance across versions so if the throughput is critical for you in terms of load test lab costs - it's better to consider upgrade asap.
On the other hand if your test works fine you can continue using earlier JMeter version in order to keep consistency of the test results for regression testing purposes. Moreover, if your test relies on JMeter Plugins - some of them simply might stop working with newer JMeter version due to JMeter API change.
So for existing project it is OK to keep previous JMeter version given potential cost of migration, but for the new one it is highly recommended to stick to the latest JMeter version. In both cases make sure to follow JMeter Best Practices and recommendations from the 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure article.
For migration, always read release notes in order to know what to do:
https://jmeter.apache.org/changes.html#Incompatible%20changes
Currently, we are using the JMeter 2.13 version for load testing. I am planning to migrate to JMeter 3.0 version.
I have not started working on the JMeter 3.0 till now.I don't know pros and cons of it.
Please suggest me, Shall I upgrade scripts to 3.0 or shall I continue with Jmeter2.13.
Of course it's better to go with newer version. Apart from new technologies are showing up each day and you need to be able to test them, there are always bug fixes and improvements, performance boost,...
For full list of fixes, improvements and new stuff, refer to change logs:
History of Previous Changes
By the way, if you are planning to move to newer version, why don't go to 3.2 directly?
3.1 to 3.2 Change Log
The general recommendataion is use the latest version of JMeter where possible
Pros: newer JMeter versions normally come with new features, performance improvements, bug fixes, etc.
Cons:
there could be some incompatible changes (normally you will need to override some JMeter Properties to revert JMeter configuration to match previous version behaviour, restore deprecated elements if you are using them in the tests, etc.
results on newer JMeter version might be not inline with what you used to have, i.e. due to aforementioned performance improvements JMeter could generate higher loads
Not able to open Test plan on Jmeter version v3.1 which has been created on JMeter version v2.12 r1636949 . Please provide if there is any solution to this.
Take a look at jmeter.log file, it usually contains enough troubleshooting information so you will be able to figure out the cause of the problem.
I can see 3 reasons for this behavior:
You are using Test Element(s) which was(were) deprecated. If this is the case - check our Incompatible Changes section of JMeter release notes to learn what component(s) should be used instead
You are using JMeter Plugins which were installed on JMeter 2.12 and JMeter 3.1 instance does not have these plugins. In that case use JMeter Plugins Manager to re-install the missing plugins
You are using 3-rd party libraries in JUnit or Beanshell code. In that case copy them from JMeter 2.12 somewhere into Classpath of JMeter 3.1
I have been running JMeter script for a couple of months. My JMeter GUI started freezing for the last couple of days, so I removed the old JMeter and installed it again. Now when I try to open my scripts I get this error (image below). The scripts that I am trying to open are recorded script. I am not able to understand the error message.
You need to install all missing plugins used by your script.
Either use Plugins Manager or old version :
https://jmeter-plugins.org/downloads/all/
Restart JMeter after that.
Most likely this is due to missing JSON Path Extractor plugin so you need to get it back. The easiest way to restore the plugin and keep it up-to-date is using JMeter Plugins Manager
Install JMeter Plugins Manager. Don't forget to restart JMeter after placing the Plugins Manager .jar file to JMeter's "lib/ext" folder
From JMeter's main menu select Options -> Plugins Manager
Switch to the Available tab
Locate JSON Plugins
Click Apply Changes and Restart JMeter button