JMeter 3.0 - Is it a bug if I can not parse the timestamp with format yyyy/DD/mm HH:mm:ss.SSS?

[hien....@bcs-development.com]

Hi guys,

I am facing a weird behaviour with JMeter 3.0. 

In fact, I configured my user.properties with following options:

#---------------------------------------------------------------------------

# Results file configuration

#---------------------------------------------------------------------------

# This section helps determine how result data will be saved.

# The commented out values are the defaults.

# legitimate values: xml, csv, db.  Only xml and csv are currently supported.

jmeter.save.saveservice.output_format=csv

# true when field should be saved; false otherwise

# assertion_results_failure_message only affects CSV output

jmeter.save.saveservice.assertion_results_failure_message=true

#

# legitimate values: none, first, all

#jmeter.save.saveservice.assertion_results=none

#

jmeter.save.saveservice.data_type=true

jmeter.save.saveservice.label=true

jmeter.save.saveservice.response_code=true

# response_data is not currently supported for CSV output

#jmeter.save.saveservice.response_data=false

# Save ResponseData for failed samples

#jmeter.save.saveservice.response_data.on_error=false

jmeter.save.saveservice.response_message=true

jmeter.save.saveservice.successful=true

jmeter.save.saveservice.thread_name=true

jmeter.save.saveservice.time=true

#jmeter.save.saveservice.subresults=true

jmeter.save.saveservice.assertions=true

jmeter.save.saveservice.latency=true

jmeter.save.saveservice.connect_time=true

#jmeter.save.saveservice.samplerData=false

jmeter.save.saveservice.responseHeaders=false

jmeter.save.saveservice.requestHeaders=false

jmeter.save.saveservice.encoding=true

jmeter.save.saveservice.bytes=true

jmeter.save.saveservice.url=true

jmeter.save.saveservice.filename=true

jmeter.save.saveservice.hostname=true

jmeter.save.saveservice.thread_counts=true

jmeter.save.saveservice.sample_count=true

jmeter.save.saveservice.idle_time=true

# Timestamp format - this only affects CSV output files

# legitimate values: none, ms, or a format suitable for SimpleDateFormat

#jmeter.save.saveservice.timestamp_format=ms

jmeter.save.saveservice.timestamp_format=yyyy/MM/dd HH:mm:ss.SSS

# For use with Comma-separated value (CSV) files or other formats

# where the fields' values are separated by specified delimiters.

# Default:

jmeter.save.saveservice.default_delimiter=,

# For TAB, since JMeter 2.3 one can use:

#jmeter.save.saveservice.default_delimiter=\t

# Only applies to CSV format files:

# Print field names as first line in CSV

jmeter.save.saveservice.print_field_names=true

# Optional list of JMeter variable names whose values are to be saved in the result data files.

# Use commas to separate the names. For example:

#sample_variables=SESSION_ID,REFERENCE

# N.B. The current implementation saves the values in XML as attributes,

# so the names must be valid XML names.

# Versions of JMeter after 2.3.2 send the variable to all servers

# to ensure that the correct data is available at the client.

# Optional xml processing instruction for line 2 of the file:

# Example:

#jmeter.save.saveservice.xml_pi=<?xml-stylesheet type="text/xsl" href="../extras/jmeter-results-detail-report.xsl"?>

# Default value:

#jmeter.save.saveservice.xml_pi=

# Prefix used to identify filenames that are relative to the current base

#jmeter.save.saveservice.base_prefix=~/

# AutoFlush on each line written in XML or CSV output

# Setting this to true will result in less test results data loss in case of Crash

# but with impact on performances, particularly for intensive tests (low or no pauses)

# Since JMeter 2.10, this is false by default

#jmeter.save.saveservice.autoflush=false

and I attached here the file result.

The problem is I could open it normally with JMeter 2.13.See the attached image file.

But with JMeter 3.0 , I got this error message : 2016/08/03 16:38:23 WARN  - jmeter.save.CSVSaveService: Error parsing field 'timeStamp' at line 2 java.text.ParseException: Unparseable date: "2016/08/03 09:54:21.303" 

I already searched in changelog of JMeter 3.0 but it seems that there is no change related to save file settings nor listener graph.

Any help would be appreciated.

Regards.

Hien HOANG.

[Andrey Pokhilko]

Hi,

Does your question relates to any of JMeter custom plugins? If not, main JMeter mailing list might be better place to ask the question, all core JMeter developers are there.

Andrey Pokhilko

--
You received this message because you are subscribed to the Google Groups "jmeter-plugins" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jmeter-plugin...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hien....@bcs-development.com]

Hi,

Actually I just tried with Hits Per Second plugin. Maybe I will check with others plugins in order to find out them behaviors.

I will test with others graph listener and update this topic.

Thanks.

[Andrey Pokhilko]

Try with View Results Tree. This is 100% core component. Will it work?

Andrey Pokhilko