Worker stays active even though timeout has expired
Distributed load testing framework - Java, Jython, or Clojure scripts.
Brought to you by:
philipa
From the Console - Running multiple processes running multiple threads with a duration set for the process.
I have noticed that most of the time at least one of the processes will continue running the script even though the console reports that all are finished.
Stopping the agent via the console does stop both the process and the agent.
I have not yet tried it with setting the console use to false.
Thanks,
Matt
Logged In: YES
user_id=2117
Originator: NO
I'd like you to take a thread dump of the worker process.
If you are using a UNIX-like operating system, taking the thread dump is simple. Just use ps to identify the process id, then issue a kill -3 <pid> to send the process a SIGQUIT signal. You will find the thread dump in the terminal window that the agent was started with, its probably best to redirect the process output to a file (java net.grinder.Grinder > foo.txt) rather than cutting and pasting from the terminal.
If you are on Windows, things are a little more involved. This is because worker processes are children of agent processes, and Java does not pass on Ctrl-Break signals to child processes. In this case, I would like you to run The Grinder under the SUN Java 6 JVM, and use the jstack command.
Once you have a thread dump, please attach it to this bug.
Thanks,
Logged In: NO
Hi Philip,
I did the test again and this time noticed with the ps -ef command that 3 processes out of the 10 were left running even though grinder.duration had elapsed.
I did a kill -3 on one of the process id's and this is what I got:-
[java] Full thread dump Java HotSpot(TM) Client VM (1.5.0_10-b03 mixed mode, sharing):
Logged In: YES
user_id=2117
Originator: NO
It looks like threads are hanging in SleeperImplementation.doSleep(), and that you are using beta 31. There was a change to the sleeper synchronisation in beta 32 which may well help, and a further change (fixing bug 1638659) coming up in beta 33. Can you try to reproduce with 32 please? (Or wait a few days until I have 33 out of the door and try with that).
Thanks,
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 30 days (the time period specified by
the administrator of this Tracker).