Bug 64176 - CSV output log contains wrong duplicated samples lines with wrong data (time equal to 0 and url = null)
Summary: CSV output log contains wrong duplicated samples lines with wrong data (time ...
Status: RESOLVED DUPLICATE of bug 64142
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: HTTP (show other bugs)
Version: 5.1.1
Hardware: PC All
: P2 normal (vote)
Target Milestone: JMETER_5.3.0
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-25 14:37 UTC by gucanu.ext
Modified: 2020-03-07 18:13 UTC (History)
1 user (show)



Attachments
example of generated file output (173.75 KB, image/png)
2020-02-25 14:37 UTC, gucanu.ext
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gucanu.ext 2020-02-25 14:37:31 UTC
Created attachment 37043 [details]
example of generated file output

Hello, i was looking for a response to my problem in existing bugs but i didnt find anything. this following problem falsifies the report jmeter of the campagn. it probably caused by a bad usage of the product jmeter but i didn't resolve yet.

i have to redirect view results tree or view results table to csv file in order to generate my report.
everithing is ok in the gui jmeter  where I see the good result but when i open the csv file i can see some weird line inside

below you can find the generated lines in the output file, i expected to get only 

timeStamp,elapsed,label,responseCode,responseMessage,threadName,dataType,success,failureMessage,bytes,sentBytes,grpThreads,allThreads,URL,Latency,IdleTime,Connect
1582562337302,112,acces get config,200,OK,Création Proposition remboursement 1-1,text,true,,11210,276,1,1,http://ihm-ihc-dev.vente.fr.intraorange:8080/adv-ihm/config,112,0,8 ==> line OK with real url 
1582562337414,0,acces get config-0,200,OK,Création Proposition remboursement 1-1,text,true,,8760,0,0,0,null,0,0,0 ==> wrong line with null url and response time =0
1582562339417,129,PROP REMB - Requête JWT,200,OK,Création Proposition remboursement 1-1,text,true,,24479,291,1,1,http://ihm-ihc-dev.vente.fr.intraorange:8080/adv-ihm/security/refreshToken,126,0,8 ==> line OK
1582562339545,1,PROP REMB - Requête JWT-0,200,OK,Création Proposition remboursement 1-1,text,true,,22508,0,0,0,null,0,0,0==> wrong line with null url and response time =0

in attachment, you can find screenshots of this weird behavior:

And my final question is how jmeter can delete this line (which parameter or which option can cause this behavior)?
Thank you for your response, 
best regards,
Guillaume CANU
Comment 1 gucanu.ext 2020-02-25 15:32:46 UTC
for precision : i would like to get only lhe line "ok" and not this type of line :

1582562337414,0,acces get config-0,200,OK,Création Proposition remboursement 1-1,text,true,,8760,0,0,0,null,0,0,0

and the line OK i expected to find for the same sample is :

1582562337302,112,acces get config,200,OK,Création Proposition remboursement 1-1,text,true,,11210,276,1,1,http://ihm-ihc-dev.vente.fr.intraorange:8080/adv-ihm/config,112,0,8 

this problem concerns each request for method GET sample in my jmx script file
Comment 2 Felix Schumacher 2020-02-25 15:59:26 UTC
Thanks for your report. I think this is a question better suited for the users mailing list (https://jmeter.apache.org/mail2.html#JMeterUser).

To enable us to diagnose the issue, it is always best to include the following things in a bug report:
 * version of JMeter
 * version of Java/JDK
 * a minimal test plan that reproduces the behaviour (that we can try out)

A wild guess from me is that you are seeing log entries for a transaction controller.
Comment 3 gucanu.ext 2020-02-25 16:42:05 UTC
Thank you for your response,
my jmeter version is 5.1, java 1.8.0_211-b12

i didn't use any transaction controller only simple controller.


I finally found the root cause of my problem, i used debug post processor under the http sample in my jmx script. for me it's really a bug ( it occurs a response 200 and wrong line in output file) but i can disable it or remove from my script and my result file will be OK.
Comment 4 Philippe Mouawad 2020-02-25 20:52:45 UTC
(In reply to gucanu.ext from comment #3)
> Thank you for your response,
> my jmeter version is 5.1, java 1.8.0_211-b12
> 
> i didn't use any transaction controller only simple controller.
> 
> 
> I finally found the root cause of my problem, i used debug post processor
> under the http sample in my jmx script. for me it's really a bug ( it occurs
> a response 200 and wrong line in output file) but i can disable it or remove
> from my script and my result file will be OK.

Hello,
There was a bug where presence of Debug Post Processor would put 0 for number of threads and number of threads in group.

But regarding this, why do you think it's a bug ?
- Debug Post Processor add a line for the SampleResult is generates with:
1)  Code 200 : It's not a failed sample result
2) null URL as there  is no URL

Does explanation look ok to you ?
Thanks
Comment 5 gucanu.ext 2020-02-25 23:40:40 UTC
ok maybe it 's not a bug in your opinion but the reason is that i've never seen anything in the web tutorials which explained that the debug sample could have any role in response time measure (0 ms at each sample can divide by 2 the real response time if i put the sample at all requests) , so , by the way apache should explain this behavior somewhere(maybe in commentary in the sample)
Comment 6 gucanu.ext 2020-02-25 23:47:43 UTC
it's very important what i try to explain to you, i try to improve jmeter ( i like this product)
Comment 7 Philippe Mouawad 2020-03-07 18:13:02 UTC
Hello,
As I wrote the bug you faced with Debug Post Processor is fixed in upcoming version 5.3.

Comme je l'ai écrit précédemment, s'il s'agit du Debug Post Processor, c'est bien un bug (voir Bug 64142) qui est corrigé dans la master actuelle et sera dans la version à venir 5.3
En attendant vous pouvez tester:
https://ci.apache.org/projects/jmeter/nightlies/

Si vous constatez toujours le problème avec cette version merci de réouvrir le bug.

Merci

*** This bug has been marked as a duplicate of bug 64142 ***
Comment 8 The ASF infrastructure team 2022-09-24 20:38:18 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/5248