JTL CSV header line contains only a newline (no column names)

[Michael Schwartz <mi...@google.com.INVALID>]

When I set:

jmeter.save.saveservice.print_field_names=true

The first line in the resulting jtl file contains only a newline.  It does
not contain the expected column header labels.  However, the file does
contain all expected thread sample entry lines.  Any ideas on how to fix
this, or is this a bug?

I've grep'd the entire jmeter install for other occurrences of
jmeter.save.saveservice.print_field_names, and there are none.

Running JMeter 3.0 with:

jmeter -n -p ./user.properties.env2 -t ./load.jmx -l ./loadlog.jtl
-Jjmeter.save.saveservice.print_field_names=true

Java: jre1.8.0_102

Thanks,
Mike

Re: JTL CSV header line contains only a newline (no column names)

[Felix Schumacher <fe...@internetallee.de>]

Am 27.09.2016 um 20:38 schrieb Michael Schwartz:
> When I set:
>
> jmeter.save.saveservice.print_field_names=true
>
> The first line in the resulting jtl file contains only a newline.  It does
> not contain the expected column header labels.  However, the file does
> contain all expected thread sample entry lines.  Any ideas on how to fix
> this, or is this a bug?
>
> I've grep'd the entire jmeter install for other occurrences of
> jmeter.save.saveservice.print_field_names, and there are none.
>
> Running JMeter 3.0 with:
>
> jmeter -n -p ./user.properties.env2 -t ./load.jmx -l ./loadlog.jtl
> -Jjmeter.save.saveservice.print_field_names=true
>
> Java: jre1.8.0_102
I tried it with the attached testfile and an empty env-file and jmeter 
produced the header file. Tried it with trunk and 3.0.

Is there anything special inside your env-file, that could influence the 
header fields?

print_field_names has a default value of true, so why do you want to set it?

Regards,
  Felix

>
> Thanks,
> Mike
>