Hi,
Including any 1.4.0 "old" sets will most likely result in an unpredictable state of plugins. Those plugins are outdated for several years. The only correct way is to use Plugins Manager.
The real question is: is there "*udp*.jar" file inside lib/ext after install or not? Another thing is that modern Plugins Manager has "install-for-jmx" command to make sure all plugins are installed.
Finally, some of less popular plugins, like Hadoop, conflict with
other plugins in terms of libraries installed. So it is risky
practice to blindly install all plugins.
--
You received this message because you are subscribed to the Google Groups "jmeter-plugins" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jmeter-plugin...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Add "jpgc-oauth" to excludes also, it is deprecated plugin
Andrey,
Using install-for-jmx is not an option here as our image is built for distributed testing. The master node sees the JMX file, but the slave never sees it. I am attempting to build a Docker Image that anyone could use with at least the most popular plugins. Your information is very helpful for me to understand the challenges on plugin dependencies.
It turns out the UDP plugin was not installed in my image. There is possibly an issue calling `PluginsManagerCMD.sh install-all-except` on a clean machine (image). Running this in the Dockerfile:
RUN PluginsManagerCMD.sh install-all-except jpgc-hadoop \
&& PluginsManagerCMD.sh status
results in:
Step 13/18 : RUN PluginsManagerCMD.sh install-all-except jpgc-hadoop && PluginsManagerCMD.sh status---> Running in 1495a6d89bdcERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'log4j2.debug' to show Log4j2 internal initialization logging.Mar 19, 2018 4:55:06 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
16:55:08.232 [main] INFO org.jmeterplugins.repository.PluginManager - Plugins Status: [jpgc-plugins-manager=0.19, jmeter-core=4.0, jmeter-ftp=4.0, jmeter-http=4.0, jmeter-jdbc=4.0, jmeter-jms=4.0, jmeter-junit=4.0, jmeter-java=4.0, jmeter-ldap=4.0, jmeter-mail=4.0, jmeter-mongodb=4.0, jmeter-native=4.0, jmeter-tcp=4.0, jmeter-components=4.0]2018-03-19 16:55:08,232 INFO o.j.r.PluginManager: Plugins Status: [jpgc-plugins-manager=0.19, jmeter-core=4.0, jmeter-ftp=4.0, jmeter-http=4.0, jmeter-jdbc=4.0, jmeter-jms=4.0, jmeter-junit=4.0, jmeter-java=4.0, jmeter-ldap=4.0, jmeter-mail=4.0, jmeter-mongodb=4.0, jmeter-native=4.0, jmeter-tcp=4.0, jmeter-components=4.0]16:55:08.308 [main] INFO org.jmeterplugins.repository.JARSourceHTTP - Downloading: https://search.maven.org/remotecontent?filepath=com/yammer/metrics/metrics-core/2.2.0/metrics-core-2.2.0.jar2018-03-19 16:55:08,308 INFO o.j.r.JARSourceHTTP: Downloading: https://search.maven.org/remotecontent?filepath=com/yammer/metrics/metrics-core/2.2.0/metrics-core-2.2.0.jar
[installing lots of plugins]
16:55:33.852 [main] INFO org.jmeterplugins.repository.JARSourceHTTP - Downloading: https://search.maven.org/remotecontent?filepath=kg/apc/jmeter-plugins-udp/0.3/jmeter-plugins-udp-0.3.jar2018-03-19 16:55:33,852 INFO o.j.r.JARSourceHTTP: Downloading: https://search.maven.org/remotecontent?filepath=kg/apc/jmeter-plugins-udp/0.3/jmeter-plugins-udp-0.3.jar
[installing lots of plugins]
16:55:39.202 [main] INFO org.jmeterplugins.repository.PluginManager - Restarting JMeter...2018-03-19 16:55:39,202 INFO o.j.r.PluginManager: Restarting JMeter...ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'log4j2.debug' to show Log4j2 internal initialization logging.16:55:42.348 [main] INFO org.jmeterplugins.repository.PluginManager - Plugins Status: [jpgc-plugins-manager=0.19, jmeter-core=4.0, jmeter-ftp=4.0, jmeter-http=4.0, jmeter-jdbc=4.0, jmeter-jms=4.0, jmeter-junit=4.0, jmeter-java=4.0, jmeter-ldap=4.0, jmeter-mail=4.0, jmeter-mongodb=4.0, jmeter-native=4.0, jmeter-tcp=4.0, jmeter-components=4.0]2018-03-19 16:55:42,348 INFO o.j.r.PluginManager: Plugins Status: [jpgc-plugins-manager=0.19, jmeter-core=4.0, jmeter-ftp=4.0, jmeter-http=4.0, jmeter-jdbc=4.0, jmeter-jms=4.0, jmeter-junit=4.0, jmeter-java=4.0, jmeter-ldap=4.0, jmeter-mail=4.0, jmeter-mongodb=4.0, jmeter-native=4.0, jmeter-tcp=4.0, jmeter-components=4.0][jpgc-plugins-manager=0.19, jmeter-core=4.0, jmeter-ftp=4.0, jmeter-http=4.0, jmeter-jdbc=4.0, jmeter-jms=4.0, jmeter-junit=4.0, jmeter-java=4.0, jmeter-ldap=4.0, jmeter-mail=4.0, jmeter-mongodb=4.0, jmeter-native=4.0, jmeter-tcp=4.0, jmeter-components=4.0]Removing intermediate container 1495a6d89bdc---> 752e66777c89
If I modify the Dockerfile to install twice, I get all the plugins:
RUN PluginsManagerCMD.sh install-all-except jpgc-hadoop \
&& PluginsManagerCMD.sh install-all-except jpgc-hadoop \
&& PluginsManagerCMD.sh status
What is happening in the Plugins Manager during the state: "Restarting JMeter..."? In this Docker use case, JMeter is not running yet. Is it possible that since JMeter was never run that the plugin manager is not installing the plugins properly?
Also, are there other problematic plugins I should add to the install-all-except line?
Dave
Sorry, I did not fully understand your question. Can you
elaborate?
Appreciate the detail. Thoughts on how we could properly address plugin installation when JMeter is not running? Should I add a feature request for a new command line switch like --no-restart such that this could be considered in the long term?
Dave
ENV JMETER_VERSION=3.0
ENV JMETER_PATH=/opt/jmeter_jp
ENV PLUGINS_PATH=$JMETER_PATH/plugins
....
# get the PluginsManagerCMD.sh from the jar (the PluginsManagerCMD.sh is in the jar)
RUN cd $JMETER_PATH && \
java -cp apache-jmeter-$JMETER_VERSION/lib/ext/jmeter-plugins-manager-0.10.jar org.jmeterplugins.repository.PluginManagerCMDInstaller
RUN cd $JMETER_PATH/apache-jmeter-$JMETER_VERSION/bin && \
chmod u+x PluginsManagerCMD.sh
# a selection of usefull plugins from jmeter-plugins.org
ENV LIST_PLUGINS="jpgc-casutg=2.1,jpgc-csl=0.1,jpgc-dbmon=0.1,jpgc-dummy=0.1,jpgc-functions=2.0,jpgc-jmxmon=0.2,jpgc-perfmon=2.1,jpgc-graphs-basic=2.0,jpgc-graphs-additional=2.0,jpgc-graphs-dist=2.0,jpgc-graphs-vs=2.0,jpgc-cmd=2.1,jpgc-filterresults=2.1,jpgc-ggl=2.0,jpgc-mergeresults=2.0,jpgc-pde=0.1,jpgc-synthesis=2.0,jpgc-sts=2.2"
# Run the PluginsManager to download and install files (jars and scripts files)
RUN cd $JMETER_PATH/apache-jmeter-$JMETER_VERSION/bin && \
JVM_ARGS="-Dhttps.proxyHost=$ARG_https_proxyHost -Dhttps.proxyPort=$ARG_https_proxyPort" ./PluginsManagerCMD.sh install $LIST_PLUGINS && \
JVM_ARGS="-Dhttps.proxyHost=$ARG_https_proxyHost -Dhttps.proxyPort=$ARG_https_proxyPort" ./PluginsManagerCMD.sh status
Regards
Vincent D.