https://bz.apache.org/bugzilla/show_bug.cgi?id=64479

            Bug ID: 64479
           Summary: JVM doesn't exit after successfull test run
           Product: JMeter
           Version: 5.3
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: ho...@urban-cz.eu
  Target Milestone: JMETER_5.3.1

Created attachment 37275
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=37275&action=edit
thread dump

After the upgrade to version 5.3 some of my scripts stopped working (works just
fine on 5.2.1).
I have the same config on both versions of JMeter, also the same plugins.

When running the test I get the following:

Creating summariser <summary>
Created the tree successfully using
..\Scripts\AGReportGeneratorForAutomatization.jmx
Starting standalone test @ Thu May 28 19:07:55 CEST 2020 (1590685675948)
Waiting for possible Shutdown/StopTestNow/HeapDump/ThreadDump message on port
4445
summary =      2 in 00:00:11 =    0.2/s Avg:     0 Min:     0 Max:     1 Err:  
  0 (0.00%)
Tidying up ...    @ Thu May 28 19:08:09 CEST 2020 (1590685689077)
... end of run
The JVM should have exited but did not.
The following non-daemon threads are still running (DestroyJavaVM is OK):
Thread[AWT-Shutdown,5,system], stackTrace:java.lang.Object#wait
sun.awt.AWTAutoShutdown#run
java.lang.Thread#run

Thread[DestroyJavaVM,5,main], stackTrace:
Thread[AWT-EventQueue-0,6,main], stackTrace:sun.misc.Unsafe#park
java.util.concurrent.locks.LockSupport#park
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject#await
java.awt.EventQueue#getNextEvent
java.awt.EventDispatchThread#pumpOneEventForFilters
java.awt.EventDispatchThread#pumpEventsForFilter
java.awt.EventDispatchThread#pumpEventsForHierarchy
java.awt.EventDispatchThread#pumpEvents
java.awt.EventDispatchThread#pumpEvents
java.awt.EventDispatchThread#run

jmeter.log attached.
Also, thread dump attached.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to