You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2022/01/25 23:06:34 UTC
[Bug 65847] New: Wrong version of Java in log file
https://bz.apache.org/bugzilla/show_bug.cgi?id=65847
Bug ID: 65847
Summary: Wrong version of Java in log file
Product: JMeter
Version: 5.4.3
Hardware: Macintosh
OS: other
Status: NEW
Severity: critical
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: mmodi@activecampaign.com
Target Milestone: JMETER_5.5
Hi,
Just installed JMeter 5.4.3 version. I am not able to create a HTML report from
jtl file.
It gives me following error:
An error occurred: Error while processing samples: Consumer failed with message
:Consumer failed with message :Consumer failed with message :Consumer failed
with message :Begin size 0 is not equal to fixed size 5
Looking at the jmeter.log file it shows me java.version=17.0.1 but my machine
has only one JDK installation and it's 11.0.5
I have attached screenshots for logs and java version on machine.
Thank you
Mihir Modi
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 65847] Wrong version of Java in log file
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=65847
Felix Schumacher <fe...@internetallee.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Severity|critical |normal
Status|NEW |RESOLVED
--- Comment #1 from Felix Schumacher <fe...@internetallee.de> ---
As JMeter contains no JDK (at least the official distribution from the ASF
site) and the JDK will (most probably) not lie about its version number, I
suspect, that you have another JDK on your machine and that either the path or
JAVA_HOME is pointing to it.
This question is better placed on the mailing list, as it is not a bug in
JMeter (as far as I can tell).
You can try to look at the process, when JMeter runs and find the path to the
JDK that way, or you could log/print the system property java.home
The latter could be achieved by adding a JSR-223 sampler (groovy) with a single
line "System.getProperty('java.home')" in it and looking at the result of that
sampler after running it.
Further discussion of this should be held on the users mailing list.
--
You are receiving this mail because:
You are the assignee for the bug.