Jai P | 18 Apr 20:02 2013
Picon

Can Grinder overlook ramp up period?

I have re-written my Loadrunner script in Jython and am load testing with Grinder. The test works fine when I use threads alone or a combination of processes and threads split on 2 agents.
When I use processes, I use the following properties:

grinder.processes=5
grinder.runs=0
grinder.duration=900000  #15 min

grinder.processIncrement=1
grinder.processIncrementInterval=24000
grinder.initialProcesses=1
grinder.initialSleepTime=5

Basically, I want to ramp up the # threads over the first 2 minutes of the test, like I would do in Loadrunner. In my script, I have copied the example in the Script gallery for thread ramp up as well.
However, at the end of the test, when I analyze the results using GrinderAnalyzer, I am unable to discard the first 2 minutes since I am only interested in measuring TPS and response times during steady state. I am not sure if GrinderAnalyzer questions would be answered in this forum, but I believe there is a bug when it aggregates results from multiple processes from 2 different machines. It always seems to discard most of the data and produces a graph for just 1 process, i.e. # successful tests are far less than the actual count.

One method I tried was to convert all the *-data.log to .csv and combine them to a single .csv file. I then sorted by the column - Start time (ms since Epoch), manually discarded the first 2 min and then calculate the # tests/13min for TPS. But I am not sure if this is the right approach.

Is there a way to instruct Grinder to overlook the first 2 min before it starts calculating the response times?
Are there better tools than GrinderAnalyzer to view a complete summary of the test like Loadrunner?

Thanks

Jai

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use
Rob Schroder | 10 Apr 21:11 2013

Grinder and OpenTSDB

Does anyone know of an integration of The Grinder with OpenTSDB? We use OpenTSDB for collecting a ton of
metrics. If something already exists, it would be good to know. Otherwise, I'll start looking at what it
would take to get response times, along with other metrics, from The Grinder into OpenTSDB.

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
Jai P | 5 Apr 22:59 2013
Picon

Calling C++ executable using Java's Runtime

Following the tips in my previous post "Cython implementation of Loadrunner based C script to work with Grinder", I re-wrote my C code and compiled it with "cl" (MSVC 2005) into an exe.

The exe takes 1 argument (int) and based on results obtained from the server, it will print a success or failure.

Since I want to performance test this with Grinder, I used Java's Runtime.getRuntime().exec(cmd) to run my exe. Using my custom class, I am able to increment the integer I need for the argument.

 Sure enough it works as expected for a few inputs, however when I increase the # threads in grinder, I see a spike in CPU, followed by a modal dialog box suggesting an issue with the C++ Runtime Library (the error is from the MSVC 2005 C++ redistributable installed on the test machine to run my exe).

In order to ensure that the exe doesn't hang around, I used taskkill /f /im <my.exe> to ensure it is killed. With this hack, the test seems to work for up to 10 threads, but if I increase it beyond that, I then run into  "cmd.exe - Application error" --many of these windows open and it doesn't recover. This is not a good hack because thread#2 may be executing the taskkill when thread#1 is about to launch the exe..

Here is my grinder script:


from net.grinder.script.Grinder import grinder
from net.grinder.script import Test
from java.lang import Runtime
from loadgen import LoadGen

out = grinder.logger.output
log = grinder.logger.output
err = grinder.logger.error
verbose = 0

def authenticate(str):
    #print "Running sync_st.exe"
    getattr(Runtime.getRuntime(), "exec")(str)
  # Hack to kill prior exe..hopefully
    grinder.sleep(4000)
    getattr(Runtime.getRuntime(), "exec")('taskkill /f /im sync_st.exe')    
    
# define all tests here
authenticateTest = Test(1, "SecurID Authentication").wrap(authenticate)    

# The main class for this script
class TestRunner:
     def __init__(self):
        self.loadgen = LoadGen()
        
     def __call__(self):
        statistics = grinder.statistics
        statistics.delayReports = 1

        #get next index value
        index = self.loadgen.getIndex()
       
str = 'cmd /C C:\\Performance\\sync_st.exe %s' % index
if verbose: out("str = %s" % str)
      
  # run test
        authenticateTest(str)


Option #2: 
I created a batch script that calls the exe and the taskkill -- no change in outcome

Option#3:
Find the PID of the current process with tasklist and pass it to taskkill to terminate - Not sure if that is a fix either


Is Grinder suited to running this sort of a test? Right now it doesn't work and I have also seen Grinder blowing memory and it writes a hperf. Any suggestions would be really helpful.


------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use
FMehran | 4 Apr 18:58 2013

Recall: Running a recorded update script - no update happens.

Mehran, Fariba would like to recall the message, "[Grinder-use] Running a recorded update script - no
update happens.".
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
Kiran Sant | 2 Apr 12:08 2013

Parametarization & Correlation in Grinder 3

Hi,

 

      We are doing R&D on Grinder-3.6. We have recorded the script and it is executing fine. Need some help in Parameterization & Correlation in Grinder 3.6. Also,  

we are not able to understand the format of the recorded script.

        Could you please guide us with some detailed documentation on the above topics so that it may help us in understanding the tool better.

 

Looking forward for your co-operation.

 

Thanks in advance.

 

Kiran Sant,
Associate - Quality Control
SYNECHRON - 
- 4,000+ professionals globally.
- USA | Canada | UK | The Netherlands | UAE | India | Singapore | Hong Kong | Japan

 

------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use
FMehran | 29 Mar 17:32 2013

Running a recorded update script - no update happens.

 

Hello,

 

I have recorded the attached Grinder script and have run it.  The action on the web app is to log on,

Pull up a page and click on an icon  on the screen. By clicking this Icon a Work order number will be automatically generated.

This action  is recorded as an event  in the following method in the attached script (mx343 is the click even in the jsp)

 

 

def page8(self):

    """POST maximo.jsp (requests 801-816)."""

    result = request801.POST('/maximo/ui/maximo.jsp',

      ( NVPair('uisessionid', '213'),

        NVPair('csrftoken', 'udqn7spqavdji6gothuc7etrhe'),

        NVPair('currentfocus', 'mx647'),

        NVPair('scrollleftpos', '0'),

        NVPair('scrolltoppos', '1'),

        NVPair('requesttype', 'SYNC'),

        NVPair('responsetype', 'text/xml'),

        NVPair('events', '[{\"type\":\"click\",\"targetId\":\"mx343\",\"value\":\"\",\"requestType\":\"SYNC\",\"csrftokenholder\":\"udqn7spqavdji6gothuc7etrhe\"}]'), ),

      ( NVPair('Content-Type', 'application/x-www-form-urlencoded;charset=UTF-8'), ))

 

The following method shows the text that was inserted at the field right beside it (see below screen shot)

 

 

 

By comparing the above two methods,  I think the automatically generated work order (S11726 – shown in the below screen taken during recording), was not passed as the value in  Page 8 (highlighted in red – no value there)

 

 

 

 

There are other fields on the screen that is populated and then save button is pressed.  When I run this scripts, I should expect it do the action

“Click New Work Order Icon” and generate a new work order.  Correct?   , but that is not happening. After running the script, I don’t see any new

Work Order being generated.   From the log file I see lots of POSTs are happening. Aren’t these transactions actually inserting  data to the database?

 

Please let me know.

 

Thanks for your help.

 

Attachment (Wo-Create.py): application/octet-stream, 84 KiB
Attachment (out_VXPP0038-0.log): application/octet-stream, 83 KiB
------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use
Jai P | 28 Mar 21:18 2013
Picon

Cython implementation of Loadrunner based C script to work with Grinder

I have legacy test scripts written in C (not recorded http scripts. In fact there is no http but just C API) for use with Loadrunner. I would like to use Grinder instead of Loadrunner. 

In order to reuse the test scripts written in C could I wrap them in Cython? (http://en.wikipedia.org/wiki/Cython) Cython is a compiled language which will produce extension modules that can be imported into regular Python or CPython code. Once I have this CPython code, will it work in Grinder or does Grinder specifically need Jython? 

The question is whether Grinder can support C-Python?


------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use
Ravi Joshi | 28 Mar 18:04 2013
Picon

Service /agents/start-workers is returning success even when no agent is connected

Hi All,

Grinder 3.11 REST Service /agents/start-workers is returning success even when no agent is connected. Is this is expected behavior ?

If yes then how can I get to know that Agents are connected or not?
 
-Ravi Joshi
------------------------------------------------------------------------------
Own the Future-Intel&reg; Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game 
on Steam. $5K grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use
Lutfur Rahaman | 26 Mar 09:52 2013

Why my grinder worker process could not spawn

Hi,

While running a very simple script, I am getting the following output in the out.log. There is no data log or error log. It seems that worker process could not spawn. Can anyone help me finding out the reason.

3/22/13 4:00:52 PM (process TCS115344-0): The Grinder version 3.2
3/22/13 4:00:52 PM (process TCS115344-0): Sun Microsystems Inc. Java HotSpot(TM) Client VM 1.5.0_12-b04 on Windows XP x86 5.1
3/22/13 4:00:52 PM (process TCS115344-0): time zone is IST (+0530)

Thanks,
Lutfur Rahaman

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

------------------------------------------------------------------------------
Own the Future-Intel&reg; Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game 
on Steam. $5K grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use
Ouray Viney | 24 Mar 13:32 2013
Picon

Re: Grinder REST Console Service and Remote Agents

Hi Phil,


Agreed.  The strace does show that it is having issues opening a TCP connection to my Grinder Console on port 6372.  

I would like to better understand why this is happening.  Is there any way we can get more information about the connection handling done at the Grinder Console?  I don't understand why the Grinder Agent connects to the Grinder Console with no issues, yet the Grinder WorkerProcessor has issues i.e. generates a "SIGPIPE".  Doesn't this tell us that the Console may be acting up/or the System iteself?  I did some further reading on SIGPIPEs.  I am still a little confused by what is triggering the SIGPIPE at the Grinder WorkerProcess level.   What is particularly odd about this communication issue is that eventually, if I stop/start the test enough times, the problem seems to go away and the Grinder WorkerProcessors connect successfully to the Grinder Console.  Weird!  Perhaps it is time for another tcpdump trace at one of the Grinder agents when the WorkerProcessor fails to connect to the Grinder Console.

Could you elaborate a little on how the comms. works between the Grinder Console -> Grinder Agent -> Grinder WorkerProcessor?  I did look at the website architecture diagrams and the Grinder source code and have understood that the Grinder WorkerProcessor actually opens a pipe to the Grinder Console.

Greatly appreciate your patience with this odd issue.

Ouray

On Tue, Mar 12, 2013 at 2:45 PM, Philip Aston <philipa-O5WfVfzUwx8@public.gmane.org> wrote:

The strace showing the SIGPIPE is further evidence that the problem does not lie within the worker process. The socket its trying to write to has been closed.

Does the other end (the console) log anything?

- Phil


On 12/03/13 14:03, Ouray Viney wrote:
Hi Phil,
 
Thank you for sticking with this, greatly appreciated.
 
Some more details about the test that is being run by Grinder may help.
 
- We are using Grinder to run some Java client side api’s.  
- There are over 128 jars that get loaded during the first run.  
- Profiling the system during the initial run shows that the system is pinned.  I thought that this might be a contributor, but one of 9 agents is functioning correctly.  This particular system is actually a little slower than the other (less bogomips).  
- The test that Grinder instruments makes use of a local CUPs server
- The test that Grinder instruments makes use of local beans for the purpose of mailing and shipping requests being sent to a backend web service (REST).
- I profiled the Grinder agent and WorkerProcessor using visualvm (bundled with Java 1.6), not much to say other than the CPU profile once the test started was flat at 98%.

The current workaround is to start the test the first time.  Expect to see the issue, stop the test.  Start a second run and things *should* work as expected, i.e. no comms. issue from the WorkerProcessor to the Console

Cheers,

Ouray

On Tue, Mar 12, 2013 at 8:19 AM, Philip Aston <philipa-O5WfVfzUwx8@public.gmane.org> wrote:
Something is tearing down a connection, or otherwise blocking communication, on a TCP connection that was previously fine. I suspect the former, since lsof says the connection no longer exists. The trace below is just reporting that the worker could not send data to the console, and doesn't provide anything else of use.

The worker creates the connection when it starts up. It sends a few bytes of data to the console as part of establishing the connection. Then it regularly sends a report message to the console.

The worker process relies on the TCP connection being resilient. It doesn't try to re-connect.

Maybe a tcpdump would help, maybe not.

- Phil



On 11/03/13 17:28, Ouray Viney wrote:
Hi Philip,

No problem at all.  Totally appreciate that you are busy ;-).

I have noticed that when this problem occurs, I see the following exception in the agent output.  Yet, if I re-run this a few times, it eventually goes a way.  The bottom line is the communication from the WorkerProcessor to the Console is unreliable for some reason.  Please keep in mind I am not blaming The Grinder for this.

Environment details:
=================
- when the problem is reproducible, lsof reports no connection to the console
- no firewalls are blocking any of the Grinder console ports 6372/6373
- no clear signs of any issues with ulimits for the account that owns the WorkerProcessor process
- the exception trace below means that something happened, I need to review the source code I don't know what condition is causing this code to fail.

2013-03-11 12:22:22,216 INFO  3582299-001-0: Report to console failed
net.grinder.communication.CommunicationException: Exception whilst sending message
        at net.grinder.communication.AbstractSender.send(AbstractSender.java:57) ~[grinder-core-3.11.jar:na]
        at net.grinder.communication.QueuedSenderDecorator.flush(QueuedSenderDecorator.java:60) ~[grinder-core-3.11.jar:na]
        at net.grinder.engine.process.GrinderProcess.sendStatusMessage(GrinderProcess.java:638) [grinder-core-3.11.jar:na]
        at net.grinder.engine.process.GrinderProcess.access$1100(GrinderProcess.java:110) [grinder-core-3.11.jar:na]
        at net.grinder.engine.process.GrinderProcess$ReportToConsoleTimerTask.run(GrinderProcess.java:615) ~[grinder-core-3.11.jar:na]
        at net.grinder.engine.process.GrinderProcess.run(GrinderProcess.java:465) [grinder-core-3.11.jar:na]
        at net.grinder.engine.process.WorkerProcessEntryPoint.run(WorkerProcessEntryPoint.java:86) [grinder-core-3.11.jar:na]
        at net.grinder.engine.process.WorkerProcessEntryPoint.main(WorkerProcessEntryPoint.java:59) [grinder-core-3.11.jar:na]
Caused by: java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method) ~[na:1.6.0_07]
        at java.net.SocketOutputStream.socketWrite(Unknown Source) ~[na:1.6.0_07]
        at java.net.SocketOutputStream.write(Unknown Source) ~[na:1.6.0_07]
        at java.io.BufferedOutputStream.flushBuffer(Unknown Source) ~[na:1.6.0_07]
        at java.io.BufferedOutputStream.flush(Unknown Source) ~[na:1.6.0_07]
        at java.io.ObjectOutputStream$BlockDataOutputStream.flush(Unknown Source) ~[na:1.6.0_07]
        at java.io.ObjectOutputStream.flush(Unknown Source) ~[na:1.6.0_07]
        at net.grinder.communication.AbstractSender.writeMessageToStream(AbstractSender.java:90) ~[grinder-core-3.11.jar:na]
        at net.grinder.communication.StreamSender.writeMessage(StreamSender.java:70) ~[grinder-core-3.11.jar:na]
        at net.grinder.communication.AbstractSender.send(AbstractSender.java:53) ~[grinder-core-3.11.jar:na]
        ... 7 common frames omitted

Kind Rgds,

Ouray

On Wed, Mar 6, 2013 at 2:57 AM, Philip Aston <philipa-O5WfVfzUwx8@public.gmane.org> wrote:

Sorry for the delay Ouray.

1) A thread dump of the worker process might be useful if it shows the worker process trying to establish a connection. But its a long shot.

What does netstat tell you? Or better, lsof -i tcp -a -p <worker process pid>?

2) If there's no summary table, the worker process isn't shutting down correctly. Can you provide the logs from a worker process?

- Phil


On 26/02/13 16:31, Ouray Viney wrote:
Hi Philip,

I wanted to revisit this thread.  I am back on this problem and would like to review your recommendations for debugging the problem.

As far as I can diagnose, the problem appears to:
======================================
1) The Worker Processor (child of the Grinder Agent JVM process) spawns correctly.  What it fails to do is communicate its tests statistics back to the Console.
2) When a given test run completes, the log has no summary table of tests results.

Suggestions on debugging so far:
==========================
1) This problem appears to be related to the Worker Processors ability to communicate to the Console - no tests stats visible in the Console GUI - no stats available when probing the REST console service for stats.  Thread dump?  I don't see what the thread dump will tell me about the lack of tests statistics making their way back to the console.  IMHO, tcpdump would perhaps be more useful here?  Open to suggestions.
2) What trigger would cause the Work Processor to not correctly create a summary table at the end of the log.  The log is populated with all the test scripts data checks etc., the data log is correctly populated.  I have no idea where to start here.  I am not afraid to review the code, but before I invest the time I thought it would be worth asking for some recommendations first.

Let me know if you require any further details.

Kind Rgds,

Ouray

On Thu, Feb 7, 2013 at 11:41 AM, Ouray Viney <ouray <at> viney.ca> wrote:
Hi Philip,

I have doubts on that.  Here is why.  I ran the problematic script, observed the issues.  Change "grinder.script = problematic.py" to "grinder.script = console.py".   Ran and saw absolutely no issues - Console and worker processors worked as expected.

I have this same setup with the problematic script working in my Ubuntu VM - no issues.

I will take your advice and generate a dump of the WorkerProcessor JVM to see what is is showing.  As well, I guess it might be worth doing a tcpdump of the WorkProcessor to Console traffic on port 6372.

Thank you for your time and advice, greatly appreciated.

Kind Rgds,

Ouray

On Thu, Feb 7, 2013 at 10:44 AM, Philip Aston <philipa <at> mail.com> wrote:
Might be a firewall thing?

The agent reports back to the console over the connection it creates when it starts up. The worker processes create their own connections.

- Phil



On 07/02/13 07:36, Ouray Viney wrote:
Hi Philip,

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 :-).


- Phil

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 appreciated

Ouray Viney

On Thu, Feb 7, 2013 at 1:19 AM, Ouray Viney <ouray <at> viney.ca> 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,

Ouray


On Wed, Feb 6, 2013 at 3:06 PM, Ouray Viney <ouray <at> viney.ca> 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 ms
2013-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    TPS
                                       Time (ms)    Standard
                                                    Deviation
                                                    (ms)


Totals       0            0            -            0.00         0.00

  Tests 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 tests
  are marked with () and not included in the totals.


On Wed, Feb 6, 2013 at 2:09 PM, Ouray Viney <ouray <at> viney.ca> 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  

--
Ouray Viney
http://www.viney.ca






--
Ouray Viney
http://www.viney.ca

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use
Michael Thomsen | 20 Mar 02:17 2013
Picon

grinder.logProcessStreams = false not working in 3.11

Hello,

 

I have been using Grinder 3.6 and had both grinder.logData =false and grinder.logProcessStreams =false in my properties files working great on endurance tests.  I have upgraded to 3.11 to take advantage of parallel script execution, however it seems as though grinder.logProcessStreams no longer works? Is this by design (possibly due to the LogBack change in 3.7)? If so, is there any other way to disable logging for the output /error stream, as on long tests the log files end up quite large?

 

Thanks in advance,

Michael



Michael Thomsen
Phone: +61 2 6206 5021
Oracle Policy Automation


ORACLE Australia | Level 3, 243 Northbourne Avenue | LYNEHAM ACT 2602
"Please consider your environmental responsibility before printing this e-mail"

 

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
grinder-use mailing list
grinder-use@...
https://lists.sourceforge.net/lists/listinfo/grinder-use

Gmane