I have downloaded J meter on below spec machine , however when clicking on the apache.jar file it runs however it opens into a blank white screen attached Have tried the solution to add env variable J2D_D3D and setting to false...thank you in advance for your assistance
Device name DESKTOP-TFNU4Q1
Processor Intel(R) Core(TM) i7-4800MQ CPU # 2.70GHz 2.70 GHz
Installed RAM 16,0 GB
Device ID 21EA1CAF-A5F9-46D5-930B-73BFD811FC2A
Product ID 00331-60000-00000-AA668
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 10 Pro N
Version 20H2
Installed on 2021/02/05
OS build 19042.1288
Experience Windows Feature Experience Pack 120.2212.3920.0
Operating system per se should be the problem, I would rather check your Java runtime version, most probably it's too new or too old or too specific
Also check jmeter.log file for any suspicious entries, if it doesn't contain any useful information you can increase JMeter logging verbosity by changing this line:
<Root level="info">
to this one:
<Root level="debug">
in log4j2.xml file (lives in "bin" folder of your JMeter installation). JMeter restart will be required to pick up the change.
Another thing to try is changing JMeter's "look and feel" by adding the next line to user.properties file:
jmeter.laf=CrossPlatform
I have the same problem when i open the ApacheJmeter.jar file, but when i open it from the bat file ( jmeter.bat ), it opens correctly.
The bat file is in the same folder where the jar file is. My Jmeter version is 5.4.1 and my java version is 17.0.1
Related
For a few days I cannot open any JMX file in JMeter script. Even after click File->Recently Opened, JMeter opens this file but non of click action on this file doesn't work. I am using JMeter version 5.3.
What I've done:
tried to used another JMeter version (5.5)
unistalled and installed newest JDK version (17.0.4.1)
upgraded all MacOS upgraded
scanned my MACOS in order to find a viruses
opened another applications based on Java and try to open the file (f.e. Intelij)
Increased Heap from 256M to 512M
Killed all denudant processes
Opened the java logs
All these actions were unsuccessful. Slowly my ideas are ran-down. Any idea from you what else can I check?
Best regards.
I cannot reproduce your issue:
so most probably something is wrong with your Java/JMeter/OS/user/whatever.
You can try following troubleshooting steps:
Increase JMeter's logging verbosity to maximum and see whether there are any suspicious entries in jmeter.log file
Check your OS logs using Console application
Try switching to another Look and Feel via Options -> Look and Feel. If this doesn't work as well you can do it using command line i.e.
./jmeter.sh -Jjmeter.laf=CrossPlatform
Try running JMeter and providing the path to the .jmx script via -t command-line argument like:
./jmeter -t /path/to/test.jmx
white screen showing when open JMeter, can anybody help to resolve this error
enter image description here
I cannot reproduce the issue and have never seen this behaviour so I can only recommend checking jmeter.log file for any suspicious entries.
If by default it's not too informative you can increase JMeter logging verbosity by adding the next line to log4j2.xml file (lives in "bin" folder of your JMeter installation)
<Logger name="org.apache.jmeter" level="debug" />
or just launch JMeter as follows:
jmeter -LDEBUG
You might want to try a different version of Java SDK, the minimum version is Java 8
I'm using JMeter 5.2.1 and when I run some test in GUI mode (or even start the GUI mode), the jmeter.log is populated. But when I use non-GUI mode, nothing is happening.
Command line : "M:\Apps\apache-jmeter-5.2.1\bin\jmeter" -Jthreads=1 -Jrampup=20 -n -t "M:\Data.....\test.jmx" -l "M:\Data\test.csv".
Test runs fine and generates csv, but the jmeter.log doesn't get touched. Right after the test completes, JMeter console is closed down so can't even see if there's any further errors.
My understanding is this jmeter.log should be updated from both GUI and non GUI test runs. Am I missing something?
jmeter.log is written in the folder of execution
So if you execute non GUI (CLI) mode it will append/create jmeter.log in your folder
See also related command line log options:
-l, --logfile <argument>
the file to log samples to
-i, --jmeterlogconf <argument>
jmeter logging configuration file (log4j2.xml)
-j, --jmeterlogfile <argument>
jmeter run log file (jmeter.log)
Your understanding is correct, however it might not be the case regarding your understanding regarding where to find the jmeter.log file.
If you're running JMeter from it's "bin" folder - the jmeter.log file will be generated/updated in this folder
If you're running JMeter from another folder, it will be generated in that folder. If this is your case - instead of looking for updated log under M:\Apps\apache-jmeter-5.2.1\bin look for in in %cd%\jmeter.log
If the above hints don't help - most probably your log4j2.xml file got corrupted somewhere somehow, get the brand new version from JMeter GitHub
If you want JMeter to store the log under M:\Apps\apache-jmeter-5.2.1\bin folder no matter where you run it from - replace this line:
<File name="jmeter-log" fileName="${sys:jmeter.logfile:-jmeter.log}" append="false">
with this one:
<File name="jmeter-log" fileName="M:/Apps/apache-jmeter-5.2.1/bin/jmeter.log}" append="false">
and on next start of JMeter you will see the "log update" you're looking for.
More information: How to Configure JMeter Logging
Also be aware that according to JMeter Best Practices you should always be using the latest version of JMeter so it might be a good idea to perform an upgrade
When copying a large file (say 8GB) the destination file shows as 8GB immediately, before the file has finished copying.
This is causing problems with a third party software that is polling the file waiting for the full size to be copied.
Is there a way to change this behavior so the file system reports the file size incrementally as it is being copied?
Additional info:
The Cygwin "cp" command seems to solve the problem, but I need a native Windows solution
This behavior can be seen when using the cmd prompt "copy" command and when using File Explorer to copy files
Windows 10 Version 1909 (OS Build 19363.535)
I am new to GWAS analysis and I've been trying to run the PLINK tutorial sample datasets (hapmap 80K loci) on gPLINK to do some exclusions. I am currently working on a Mac OSX 10.10. I've applied the threshold settings (high missing rate, low MAF etc.) to my file "hapmap1.ped" and prepared to execute the command through gPLINK, however it keeps giving me the error prompt "can not execute command locally".
Is there something wrong with my library or directory settings?
gPlink runs in two modes a remote mode and a local one. It seems you are running the local one. Please check if you are specifying the correct path where PLINK is installed when cofiguring gPlink. For more details refer to gPlink configuration