Jmeter5.6.2 quits unexpectedly for my test without any error or exception
Expected behavior
It should start running threads
Actual behavior
quits in few seconds after below message:
Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message on port 4445
Below is what I capture in jmeter.log file:
Last few logs:
2023-11-30 01:40:35,514 INFO o.a.j.r.ClassFinder: Will scan jar /home/pragativ/apache-jmeter-5.6.2/lib/ext/opentelemetry-proto-0.20.0-alpha.jar with filter ExtendsClassFilter [parents=[interface org.apache.jmeter.functions.Function], inner=false, contains=null, notContains=null]. Consider exposing JMeter plugins via META-INF/services, and add JMeter-Skip-Class-Scanning=true manifest attribute so JMeter can skip classfile scanning 2023-11-30 01:40:35,552 INFO o.a.j.r.ClassFinder: Will scan jar /home/pragativ/apache-jmeter-5.6.2/lib/ext/protobuf-java-util-3.23.3.jar with filter ExtendsClassFilter [parents=[interface org.apache.jmeter.functions.Function], inner=false, contains=null, notContains=null]. Consider exposing JMeter plugins via META-INF/services, and add JMeter-Skip-Class-Scanning=true manifest attribute so JMeter can skip classfile scanning 2023-11-30 01:40:35,555 INFO o.a.j.r.ClassFinder: Will scan jar /home/pragativ/apache-jmeter-5.6.2/lib/ext/jmeter-sampler-1.0-SNAPSHOT.jar with filter ExtendsClassFilter [parents=[interface org.apache.jmeter.functions.Function], inner=false, contains=null, notContains=null]. Consider exposing JMeter plugins via META-INF/services, and add JMeter-Skip-Class-Scanning=true manifest attribute so JMeter can skip classfile scanning 35,1
Steps to reproduce the problem
I have 3 jars in lib/ext which are :
- opentelemetry-proto-0.20.0-alpha.jar
- protobuf-java-util-3.23.3.jar
- and a customized jar which contains class extended from AbstractJavaSamplerClient to parse proto and add random fields for load testing.
Note same jars but downgraded versions:
- protobuf-java-3.21.7.jar
- opentelemetry-proto-0.18.0-alpha.jar
- same customized class jar as above
works as expected in older jmeter 5.5 version.
All I do is try to execute the load test using command:
bin/jmeter.sh -t sr-load.jmx -n,
my apache-jmeter-5.6.2 folder contains sr-load.jmx and a test-proto.binary which helps parse the proto in custom jar class.
Let me know if you need more details.
JMeter Version
5.6.2
Java Version
openjdk 17.0.8 2023-07-18
OS Version
MacOS Ventura 13.6.1
Can you share the test plan that reproduces the issue?
The issue might be fixed by https://github.com/apache/jmeter/pull/6193 though, so it would be great if you could try trying the latest jmeter: checkout sources and execute ./gradlew runGui
I had a similar issue with a plugin in 5.6.2. Upgrading to 5.6.3 allowed me to see the plugin exception error