Am 21.11.2016 um 05:57 schrieb Thillai Divya:
Hi Felix,
It would be a great, if you can help on this issue asap.
Yeah, that would be great, wouldn't it? But honestly, but you know, that this mailing list is run be volunteers, do you?

Now to the answer:

It depends.

It depends on the way you start JMeter, which java version you use and the os you run it on.

I mostly run on linux where I use command line tools like jstack or jcmd to get the thread dump:

jstack $JMETERPID > threads.txt
jcmd $JMETERPID Thread.print > threads.txt
(or even "kill -3 $JMETERPID" but that will make the JMeter process print the threaddump onto its own STDOUT)

If you want to use a graphical tool, there are jvisualvm and jmc. Taking a threaddump in jvisualvm seems to be a bit simpler: select the jvm you want to analyze, select the Threads tab and click on the button "Thread Dump".

The tools should be available on windows and mac, too. But I have no experience in using them there.

Regards,
 Felix

PS. I changed the adress of this mail to [email protected] as [email protected] is for mails coming from bug reports (out of bugzilla)


Regards,
Divya.

On Sun, Nov 20, 2016 at 4:05 PM, Thillai Divya <[email protected] <mailto:[email protected]>> wrote:

    Hi Felix,
    Couldnt find any exceptions in jmeter.log file.

    Please let me know how to do thread dumps.

    Regards,
    Divya

    On Sun, Nov 20, 2016 at 1:14 AM, Felix Schumacher
    <[email protected]
    <mailto:[email protected]>> wrote:

        Am 18.11.2016 um 10:38 schrieb Thillai Divya:


            Hi,

            Below is the details of my test plan.
            Number of Threads : 700
            Loop Count : Forever
            Scheduler Configuration : Duration : 250seconds

            Inline image 2

            From the above screenshot, you can see threads getting
            stopped, but didnt end completely even after 8mins 17secs.

            At 250th second, threads begin to stop as the scheduled
            duration is reached.
            Even after 30mins, the last 23threads are not stopped and
            the test is not completed.

            Tried to run the same test through non-gui mode as well.
            But the response is same.
            Even after 30mins, the test doesnt stop its execution.

            Can you please help if i have missed any configuration..

        The list strips many images (yours have been stripped), so we
        can't see yours.

        Are there any exceptions being logged? Can you do thread dumps
        when you experience the described behaviour?

        Regards,
         Felix







Reply via email to