What is the preffered way to detect that a test has ended and cleanup has completed?
This is causing me a few issues. I've tried adding a test listener which detects the end of the test, the problem is that I don't know when clean-up has completed and things like the reporting listener have completed their job(s). I am currently doing the following: 1. Wait for a test end to be reported to the test listener. 2. Wait for a period of jmeter.exit.check.pause + 5000ms (The pause hard coded in Jmeter for listener cleanup) + 500ms (extra pause to provide an error margin). Unfortunately I still seem to be continuing before the .jtl files have finished being written intermittently. I could scan the JMeter log file and wait until it reports the end of the test, but this is really not a very nice solution IMHO. Is anything triggered after JMeter has completed clean up and written the .jtl logs that I can hook a listener into that I have missed?
Re: What is the preffered way to detect that a test has ended and cleanup has completed?
On 19 March 2012 11:52, Mark Collin mark.col...@lazeryattack.com wrote: This is causing me a few issues. I've tried adding a test listener which detects the end of the test, the problem is that I don't know when clean-up has completed and things like the reporting listener have completed their job(s). What are you trying to achieve? I am currently doing the following: 1. Wait for a test end to be reported to the test listener. 2. Wait for a period of jmeter.exit.check.pause + 5000ms (The pause hard coded in Jmeter for listener cleanup) + 500ms (extra pause to provide an error margin). Unfortunately I still seem to be continuing before the .jtl files have finished being written intermittently. I could scan the JMeter log file and wait until it reports the end of the test, but this is really not a very nice solution IMHO. Is anything triggered after JMeter has completed clean up and written the .jtl logs that I can hook a listener into that I have missed? JMeter non-GUI will exit.
RE: What is the preffered way to detect that a test has ended and cleanup has completed?
I'm trying to programmatically determine that a test has finished before processing the JMeter logs. The test listener I create tells me that a test has finished, but I need to wait for clean-up to complete so that the listener that writes to the .jtl file has finished what it's doing. -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: 19 March 2012 12:39 To: dev@jmeter.apache.org Subject: Re: What is the preffered way to detect that a test has ended and cleanup has completed? On 19 March 2012 11:52, Mark Collin mark.col...@lazeryattack.com wrote: This is causing me a few issues. I've tried adding a test listener which detects the end of the test, the problem is that I don't know when clean-up has completed and things like the reporting listener have completed their job(s). What are you trying to achieve? I am currently doing the following: 1. Wait for a test end to be reported to the test listener. 2. Wait for a period of jmeter.exit.check.pause + 5000ms (The pause hard coded in Jmeter for listener cleanup) + 500ms (extra pause to provide an error margin). Unfortunately I still seem to be continuing before the .jtl files have finished being written intermittently. I could scan the JMeter log file and wait until it reports the end of the test, but this is really not a very nice solution IMHO. Is anything triggered after JMeter has completed clean up and written the .jtl logs that I can hook a listener into that I have missed? JMeter non-GUI will exit.
Re: What is the preffered way to detect that a test has ended and cleanup has completed?
On 19 March 2012 13:51, Mark Collin mark.col...@lazeryattack.com wrote: I'm trying to programmatically determine that a test has finished before processing the JMeter logs. In that case, write the code so it calls the JMeter main() entry point and continue when that returns. Or use a script that runs JMeter in non-GUI and then your code. The test listener I create tells me that a test has finished, but I need to wait for clean-up to complete so that the listener that writes to the .jtl file has finished what it's doing. What you are asking for does not exist in the JMeter code. All the listeners and hooks etc. are designed for code that runs as part of a test. -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: 19 March 2012 12:39 To: dev@jmeter.apache.org Subject: Re: What is the preffered way to detect that a test has ended and cleanup has completed? On 19 March 2012 11:52, Mark Collin mark.col...@lazeryattack.com wrote: This is causing me a few issues. I've tried adding a test listener which detects the end of the test, the problem is that I don't know when clean-up has completed and things like the reporting listener have completed their job(s). What are you trying to achieve? I am currently doing the following: 1. Wait for a test end to be reported to the test listener. 2. Wait for a period of jmeter.exit.check.pause + 5000ms (The pause hard coded in Jmeter for listener cleanup) + 500ms (extra pause to provide an error margin). Unfortunately I still seem to be continuing before the .jtl files have finished being written intermittently. I could scan the JMeter log file and wait until it reports the end of the test, but this is really not a very nice solution IMHO. Is anything triggered after JMeter has completed clean up and written the .jtl logs that I can hook a listener into that I have missed? JMeter non-GUI will exit.
Issues 52673 / 52698 / 41545 / 52707 / 52502
Hello, I have few questions regarding current issues: Shall we integrate this sampler: - https://issues.apache.org/bugzilla/show_bug.cgi?id=52673 My opinion regarding it is that as it's difficult to generate data usable by this sampler using it will be hard. So I don't have a definite opinion. Another question, I don't see what's the purpose of Graph Full results, Sebb, Milamber do you use it ? if yes can you explain what's its purpose ? if not should't we remove it ?: - https://issues.apache.org/bugzilla/show_bug.cgi?id=52698 Any thoughts on: - https://issues.apache.org/bugzilla/show_bug.cgi?id=41545 - https://issues.apache.org/bugzilla/show_bug.cgi?id=52707 - https://issues.apache.org/bugzilla/show_bug.cgi?id=52502https://issues.apache.org/bugzilla/show_bug.cgi?id=52502 -- Cordialement. Philippe Mouawad.
Re: Issues 52673 / 52698 / 41545 / 52707 / 52502
On 19 March 2012 20:31, Philippe Mouawad philippe.moua...@gmail.com wrote: Hello, I have few questions regarding current issues: Shall we integrate this sampler: - https://issues.apache.org/bugzilla/show_bug.cgi?id=52673 My opinion regarding it is that as it's difficult to generate data usable by this sampler using it will be hard. So I don't have a definite opinion. If it is implemented, why not implement it as an Access Log Sampler? But I agree - I'm not sure it's worth it. Another question, I don't see what's the purpose of Graph Full results, Sebb, Milamber do you use it ? if yes can you explain what's its purpose ? if not should't we remove it ?: - https://issues.apache.org/bugzilla/show_bug.cgi?id=52698 No idea what it does. Any thoughts on: - https://issues.apache.org/bugzilla/show_bug.cgi?id=41545 The WebService sampler uses an old SOAP implementation and is quite inefficient. I'm inclined to leave it and only fix obvious bugs in it. I don't think further development of it is warranted. The SOAP/XML sampler is a lot easier to work with (at least for a developer). - https://issues.apache.org/bugzilla/show_bug.cgi?id=52707 I'm concerned about changing the default directory; I think this could invalidate existing relative directory names. - https://issues.apache.org/bugzilla/show_bug.cgi?id=52502 Already closed; I don't think it's worth spending any further time on. -- Cordialement. Philippe Mouawad.
