测试完成后的 JMeter 异常

Question

我在运行通过 Jenkins 管道从非 GUI 命令执行 JMeter 脚本时观察到以下问题。

The JVM should have exited but did not.
The following non-daemon threads are still running (DestroyJavaVM is OK):
Thread[AWT-EventQueue-0,6,main], stackTrace:sun.misc.Unsafe#park
java.util.concurrent.locks.LockSupport#park at line:175
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject#await at line:2039
java.awt.EventQueue#getNextEvent at line:554
java.awt.EventDispatchThread#pumpOneEventForFilters at line:187
java.awt.EventDispatchThread#pumpEventsForFilter at line:116
java.awt.EventDispatchThread#pumpEventsForHierarchy at line:105
java.awt.EventDispatchThread#pumpEvents at line:101
java.awt.EventDispatchThread#pumpEvents at line:93
java.awt.EventDispatchThread#run at line:82

Thread[AWT-Shutdown,5,system], stackTrace:java.lang.Object#wait
sun.awt.AWTAutoShutdown#run at line:314
java.lang.Thread#run at line:748

Thread[DestroyJavaVM,5,main], stackTrace:

Answer 1

java.awt 代表 Abstract Window Toolkit，你不应该在命令行非 GUI 模式下看到这种形式的消息运行 JMeter。

我只能想到 JMeter 中的错误，例如您的测试计划中的 64479 so if you have a HTTP(S) Test Script Recorder - 尝试完全删除它。

其他尝试：

在user.properties文件中设置jmeterengine.force.system.exit=true属性
确保遵循 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure 文章中的建议，以便为高负载正确配置 JMeter 实例，因为 JMeter 的默认设置适用于测试开发和调试，但不足以承受或多或少的巨大负载

测试完成后的 JMeter 异常

JMeter exception after test completes

jmeter

jenkins-pipeline

jmeter-5.0

jmeter-4.0

jmeter-3.2