Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NonGUI mode: The JVM should have exited but did not #61

Closed
OlegKashtanov opened this issue Aug 27, 2019 · 7 comments
Closed

NonGUI mode: The JVM should have exited but did not #61

OlegKashtanov opened this issue Aug 27, 2019 · 7 comments
Assignees
Labels

Comments

@OlegKashtanov
Copy link

OlegKashtanov commented Aug 27, 2019

Version 0.5.0
After test i have:

Tidying up ...    @ Tue Aug 27 18:16:35 MSK 2019 (1566918995756)
... end of run
The JVM should have exited but did not.
The following non-daemon threads are still running (DestroyJavaVM is OK):
Thread[pool-2-thread-1,5,main], stackTrace:sun.misc.Unsafe#park
java.util.concurrent.locks.LockSupport#park
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject#await
java.util.concurrent.LinkedBlockingQueue#take
java.util.concurrent.ThreadPoolExecutor#getTask
java.util.concurrent.ThreadPoolExecutor#runWorker
java.util.concurrent.ThreadPoolExecutor$Worker#run
java.lang.Thread#run

Thread[DestroyJavaVM,5,main], stackTrace:

Workaround: set jmeterengine.stopfail.system.exit=true

If i stop to send pull requests from prometheus to jmeter-exporter - all fine (of course, without metrics in prometheus).

threaddump-1566919071184.txt

@johrstrom johrstrom self-assigned this Aug 27, 2019
@johrstrom johrstrom added the bug label Aug 27, 2019
@johrstrom
Copy link
Owner

I'll look into this.

If i stop to send pull requests from prometheus to jmeter-exporter

Not sure what you mean by this.

@OlegKashtanov
Copy link
Author

I mean that threads are locked only when prometheus server send requests to http://jmeter_host:9270/metrics.
If we don't mute prometheus listener in test plan and stop prometheus server then problem is not reproduced.

@GiovanniPaoloGibilisco
Copy link
Collaborator

#63 should fix this.
Tested in an automated environment about 20 times every shutdown was clean. It's hard to reproduce this behavior in CI tests.

@OlegKashtanov
Copy link
Author

OlegKashtanov commented Sep 27, 2019

Env:
Jmeter 5.1.1
jmeter-prometheus-plugin from fix-termination
Retest:
Check on standalone and distributed Jmeter mode.
Result:
All works fine.

@GiovanniPaoloGibilisco
Copy link
Collaborator

As #63 is not yet merged I would keep the issue open.

@johrstrom
Copy link
Owner

Thanks all, I'll close this tonight when I'm able to release 0.5.1.

@johrstrom
Copy link
Owner

This is in 0.5.1 release. Thanks @GiovanniPaoloGibilisco for the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants