https://bz.apache.org/bugzilla/show_bug.cgi?id=62974
Bug ID: 62974
Summary: Uncaught IllegalStateException at setupTest-phase
makes JMeter hanging and never stopping
Product: JMeter
Version: 5.0
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: mura...@yahoo.com
Target Milestone: JMETER_5.1
Created attachment 36289
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36289&action=edit
Logfile with IllegalStateException at the setupTest-phase
A. Setup:
1. JMeter-testplan checks a REST-API of a server-side software
2. HTTP-Request blocks are used to send REST-calls
3. Every ThreadGroup has a BackendListener to write into a time-series
database.
4. Such a BackendListener uses a JMeter plugin "JMeter-InfluxDB-Writer 1.2" (s.
https://github.com/NovaTecConsulting/JMeter-InfluxDB-Writer/releases)
B. Test execution:
1. JMeter is started with Maven (meter-maven-plugin:2.8.1).
2. If the InfluxDB is not reachable for JMeter then an IllegalStateException is
thrown
3. After that a row of Timeout-errors come
4. JMeter hangs and never stops (as experiment I have waited for 2 hours).
C. My proposal:
1. If something wrong happens in the startup phase with the Sampler-block then
break the test with an error message.
2. If something wrong happens with a supporting "secondary" element like a
Backend-Listener then cathc the exception, report a warning, *deactivate*
Backend-Listener automatically and go on *without* the Backend-Listener.
Reason for (2) is that developers use sometimes JMeter on their local machines
without having set up (or having access to) all "add-ons" like a time-series
database etc. They just want to verify quickly their changes in code and get
simple feedback from JMeter in form of response times without any further
statistic collection
The console output is given below (s. also logs in the attachment):
[INFO] <<< jmeter-maven-plugin:2.8.1:jmeter (jmeter-tests) < :configure @
server-load-test <<<
[INFO]
[INFO]
[INFO] --- jmeter-maven-plugin:2.8.1:jmeter (jmeter-tests) @ server-load-test
---
[INFO]
[INFO] -------------------------------------------------------
[INFO] P E R F O R M A N C E T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO]
[INFO] Executing test: download-dicoms-all-at-once.jmx
[INFO] Starting process with:[java, -Xms512M, -Xmx2048M,
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger,
-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=9010, -jar,
ApacheJMeter-5.0.jar, -d,
C:\Development\sandbox\ForumServerLoadTest\target\jmeter, -e, -j,
C:\Development\sandbox\ForumServerLoadTest\target\jmeter\logs\download-dicoms-all-at-once.jmx.log,
-l,
C:\Development\sandbox\ForumServerLoadTest\target\jmeter\results\20181203-download-dicoms-all-at-once.csv,
-n, -o,
C:\Development\sandbox\ForumServerLoadTest\target\jmeter\reports\download-dicoms-all-at-once_20181203_100209,
-t,
C:\Development\sandbox\ForumServerLoadTest\target\jmeter\testFiles\download-dicoms-all-at-once.jmx,
-L, INFO]
[INFO] Listening for transport dt_socket at address: 9010
[INFO] SLF4J: Class path contains multiple SLF4J bindings.
[INFO] SLF4J: Found binding in
[jar:file:/C:/Development/sandbox/ForumServerLoadTest/target/jmeter/lib/log4j-slf4j-impl-2.11.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[INFO] SLF4J: Found binding in
[jar:file:/C:/Development/sandbox/ForumServerLoadTest/target/jmeter/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[INFO] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
[INFO] SLF4J: Actual binding is of type
[org.apache.logging.slf4j.Log4jLoggerFactory]
[INFO] Creating summariser <summary>
[INFO] Created the tree successfully using
C:\Development\sandbox\ForumServerLoadTest\target\jmeter\testFiles\download-dicoms-all-at-once.jmx
[INFO] Starting the test @ Mon Dec 03 10:02:12 CET 2018 (1543827732262)
[INFO] Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445
[INFO] Uncaught Exception java.lang.IllegalStateException: Failed calling
setupTest. See log file for details.
--
You are receiving this mail because:
You are the assignee for the bug.
