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之类的错误，因此，如果您的测试计划中有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的默认设置适用于测试开发和调试，但不足以容纳或多或少的巨大负载

Answer 2

The JVM should have exited but did not.
The following non-daemon threads are still running (DestroyJavaVM is OK):
Thread[pool-1-thread-1,5,main], stackTrace:
Thread[DestroyJavaVM,5,main], stackTrace:java.lang.Object#wait
java.lang.Thread#join at line:1303
java.lang.Thread#join at line:1371
java.lang.ApplicationShutdownHooks#runHooks at line:107
java.lang.ApplicationShutdownHooks$1#run at line:46
java.lang.Shutdown#runHooks at line:130
java.lang.Shutdown#shutdown at line:186

测试完成后的JMeter异常

2 个答案: