https://issues.apache.org/bugzilla/show_bug.cgi?id=56821

            Bug ID: 56821
           Summary: Stuck Threads
           Product: JMeter
           Version: 2.11
          Hardware: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Main
          Assignee: [email protected]
          Reporter: [email protected]

Hi, i created a simple test plan plugin, which does:

@Override
public SampleResult runTest(JavaSamplerContext context) {
        try {
            Thread.currentThread().sleep(25);
        } catch (InterruptedException e) {
            // stuff to log
        }

        SampleResult sampleResult = new SampleResult();
        sampleResult.setSampleLabel(Thread.currentThread().getName());
        sampleResult.setResponseOK(); 
        return sampleResult;
    }
}


Very simple as you see, with Thread Group definitions:
- Number of threads = 1000;
- Rump-up-Period = 0;
- Loop-count = 2;

When i run this Test Plan, mostly performs well. As expected in Summary Report
i have 2000 samples. But sometimes, i only have 1998 samples and 1 thread that
never ends, even if i request Stop Test in Jmeter GUI. When that situation
happen i noticed this lines appears in jmeter log:

2014/08/06 17:35:37 INFO  AWT-EventQueue-0     jmeter.gui.action.Start:
Stopping test 
2014/08/06 17:35:37 INFO  Thread-7             jmeter.threads.JMeterThread:
Stopping: Thread Group 1-834 
2014/08/06 17:35:37 WARN  Thread-7             jmeter.threads.JMeterThread:
Sampler is not Interruptible: Java Request 
2014/08/06 17:35:42 WARN  Thread-7             jmeter.threads.ThreadGroup:
Thread won't exit: Thread Group 1-834 


I even tried to perform this test using jmeter-server in a linux based OS, with
same consequences. I already increased jmeter memory parameters with any sucess
and tried the exactly test plan in jmeter 2.10. 

After all tests i have done, i m forced to concluded that this situation can be
some kind of jmeter bug.


Best regards,
Ricardo Silva.

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

Reply via email to