Hi Philippe, I am using Graphite DB Listener with JMeter 3.1 as JAVA8 is not installed on our loadgen machines. PFA the JMX file I am using. Also attaching Jmeter.log and Jmeter.out files.
Note: The test was not able to shut down so I have aborted the job in Jenkins, thats why you may see lot of difference in time for last 2 lines in Jmeter.log 2017/05/22 18:58:36 INFO - jmeter.reporters.ResultCollector: Shutdown hook started 2017/05/22 18:58:36 INFO - jmeter.reporters.ResultCollector: Shutdown hook ended *Thanks * *Jayesh Guru | (314)609-6046 * *Email : [email protected] <[email protected]>* On Sun, May 21, 2017 at 8:34 AM, Philippe Mouawad < [email protected]> wrote: > Hello > How do you report to InfluxDB ? > - Using Graphite BackendListener ? > - Using JMeter 3.2 Influx DB Client > - Using something else ? > > Would it be possible to run this using plain JMeter (no taurus) ? > If issue persists, could you provide plain jmeter.log file ? > > Thanks > Regards > > On Sun, May 21, 2017 at 2:31 PM, Jayesh Guru <[email protected]> > wrote: > > > The test runs fine without any issue without Backend listener.I am > running > > the test through Jenkins with taurus(blazemeter) yaml file. > > Let me know if you need any more details. > > > > What do you mean by without plugins? > > > > Sent from my iPhone > > > > > On May 21, 2017, at 6:26 AM, Felix Schumacher <felix.schumacher@ > > internetallee.de> wrote: > > > > > >> Am 18.05.2017 um 19:16 schrieb Jayesh Guru: > > >> Here is the similar kind of error observed earlier in bugzilla ticket > > >> https://bz.apache.org/bugzilla/show_bug.cgi?id=60053 > > > That bug report (which is fixed), is about JMeter threads, that weren't > > stopped at the end of the program. Your stacktraces show an Executor, > that > > is not being stopped. > > > > > > The question here is, who has started the Executor and why is it not > > stopped. Please try your tests without any plugins and see, if it is > still > > reporting the stacktrace. > > > > > > Regards, > > > Felix > > > > > >> > > >> > > >> *Thanks * > > >> *Jayesh Guru | (314)609-6046 * > > >> *Email : [email protected] <[email protected]>* > > >> > > >>> On Thu, May 18, 2017 at 1:15 PM, Jayesh Guru <[email protected] > > > > wrote: > > >>> > > >>> I am getting below error in JMeter out file. > > >>> > > >>> I am currently having Jmeter 3.1 with DummySampler Script with "jp@gc > > - Redis Data" set with CSV file fed from Github Branch. > > >>> > > >>> Also I have Backend Listener to write the data to Influx DB, when i > > run the test it runs indefinitely reporting to InfuxDB but see below > error > > in Jmeter out > > >>> > > >>> Starting remote engines > > >>> Starting the test @ Thu May 18 17:01:44 UTC 2017 (1495126904974) > > >>> Remote engines have been started > > >>> Waiting for possible Shutdown/StopTestNow/Heapdump message on port > 4445 > > >>> Tidying up remote @ Thu May 18 17:01:48 UTC 2017 (1495126908618) > > >>> ... end of run > > >>> The JVM should have exitted but did not. > > >>> The following non-daemon threads are still running (DestroyJavaVM is > > OK): > > >>> Thread[pool-1-thread-1,5,RMI Runtime], stackTrace:sun.misc.Unsafe# > park > > >>> java.util.concurrent.locks.LockSupport#parkNanos at line:226 > > >>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ > ConditionObject#awaitNanos > > at line:2082 > > >>> java.util.concurrent.ScheduledThreadPoolExecutor$ > DelayedWorkQueue#take > > at line:1090 > > >>> java.util.concurrent.ScheduledThreadPoolExecutor$ > DelayedWorkQueue#take > > at line:807 > > >>> java.util.concurrent.ThreadPoolExecutor#getTask at line:1068 > > >>> java.util.concurrent.ThreadPoolExecutor#runWorker at line:1130 > > >>> java.util.concurrent.ThreadPoolExecutor$Worker#run at line:615 > > >>> java.lang.Thread#run at line:745 > > >>> > > >>> Thread[DestroyJavaVM,5,main], stackTrace: > > >>> > > >>> > > >>> *Thanks * > > >>> *Jayesh Guru | (314)609-6046 <(314)%20609-6046> * > > >>> *Email : [email protected] <[email protected]>* > > >>> > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > -- > Cordialement. > Philippe Mouawad. >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
