7 Feb 08:36 2013
Re: Grinder REST Console Service and Remote Agents
Ouray Viney <ouray@...>
2013-02-07 07:36:08 GMT
2013-02-07 07:36:08 GMT
My comments inline
On 2013-02-07, at 2:18, Philip Aston <philipa-O5WfVfzUwx8@public.gmane.org> wrote:
If the worker process isn't logging any tests (I assume its data file is similarly empty), then they'll be no statistics to report back to the console, however it should at least have reported "worker X (m/n threads)".
Los are fine at this point. Exactly as they should be.
What's at the start of the worker process log, does it successfully load an instrumenter?
I will check this tomorrow, but assume yes since the logs are populated correctly.
It smells like the worker threads aren't running correctly. Does the worker process log contain any errors? Are the worker threads forcibly terminated when the worker process is stopped - perhaps they're blocked in the Java code under test? Maybe take a thread dump of the worker process?
No clear sign of anything blocking. No related errors. Console can see the agents, just not the worker bees .
On 07/02/13 07:09, Ouray Viney wrote:
Hi All,I have nailed this issue down to a particular script. This same script works fine in my dev. environment. However, when I try to run the same script in a our perf. environment it causes the communication between the Console and WorkProcessors. This script is not using the http recording model, rather a Java based test, instrumenting the Java fat client API. Evening though the Console doesn't report any stats. The Processes tab doesn't show the running threads, only the Agent process. If I simply swap out the script for a sample script, things also run as expected. This is what leads me to believe that the issue is being caused by the script (which used to work fine).If I run a sample script with the same grinder.properties, the sample scripts behaves correctly i.e. the Console is showing stats from the WorkerProcessors.I am getting close to having exhausted all possible things to try.Any help would be appreciatedOuray VineyOn Thu, Feb 7, 2013 at 1:19 AM, Ouray Viney <ouray-BbpMSQBCDjY@public.gmane.org> wrote:Hi All,OK, so after a bunch of testing/debugging I believe this particular issue that I described has been isolated to a particular environment. I am not able to reproduce the issues in my dev Ubuntu VM.If I can figure out what the issues is in my environment, I'll post the details. What was interesting in all my testing was the fact that a sample script from the examples dir ran fine and gave the desired behavior in the Console.Sorry for the verbose chatter, got a little frustrated today with this one =).Kind Rgds,OurayOn Wed, Feb 6, 2013 at 3:06 PM, Ouray Viney <ouray-BbpMSQBCDjY@public.gmane.org> wrote:Another interesting fact is that the WorkProcessor log doesn't contain the summary table at the end of the log as it usually does:
2013-02-06 14:51:48,445 INFO 1128450-001-0 : elapsed time is 610319 ms2013-02-06 14:51:48,445 INFO 1128450-001-0 : Final statistics for this process:2013-02-06 14:51:48,457 INFO 1128450-001-0 :Tests Errors Mean Test Test Time TPSTime (ms) StandardDeviation(ms)Totals 0 0 - 0.00 0.00Tests resulting in error only contribute to the Errors column.Statistics for individual tests can be found in the data file, including(possibly incomplete) statistics for erroneous tests. Composite testsare marked with () and not included in the totals.On Wed, Feb 6, 2013 at 2:09 PM, Ouray Viney <ouray-BbpMSQBCDjY@public.gmane.org> wrote:
Hi All,What might be causing the WorkProcessors (child proc to the Agent) when running on a remote system to not correctly report back to the Console Service. I am seeing the agents, but when I start the WorkProcessors the Console doesn't see them when I request status on the agents. The call returns the status of the agents, but doesn't show any relevant information about the running WorkerProcessors. I did validate the a child process did spawn.Is there a particular Console setting/grinder.property that I need to set to allow the WorkProcessors (when running from a remote Grinder Agent) to communicate with the Grinder Console.Environment details:==================- separate host for the console service- 9 separate servers hosting two running agents- When my test starts, two WorkerProcessors are invoked.Other Details:============- I can see the WorkerProcess logs shows the test is running correctly.- When I query the Console for--
------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________ grinder-use mailing list grinder-use@... https://lists.sourceforge.net/lists/listinfo/grinder-use