Closed whitingjr closed 1 year ago
My scenario seems to be the abort command is called during run and then also cleanup script.
Yep. apparently an abort
after an abort
has already caused the run to end does not properly pass execution to the next command and so the run hangs. I'll start working on a solution
FYI: That latch prevents the main thread from ending before the qDup run finishes. It prevents the java -jar ..
from ending while qDup is still running
fixed in 9570c9f0b2e7fcc2d49b033113a36ff11c7b8fd7
I have a qDup process that has hung.
Nanny idle reports this:
the jvm stack dump reveals this
qdup version: 0.6.16 jvm running an uber jar