https://bz.apache.org/bugzilla/show_bug.cgi?id=63091
Bug ID: 63091
Summary: CSV Data Set Config: UnsatisfiedLinkError from awt.dll
on Windows Nanoserver despite use of -n
Product: JMeter
Version: 5.0
Hardware: Other
OS: other
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.1
Created attachment 36380
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36380&action=edit
A ZIP file containing a tests.jmx file, a CSV file, and jmeter.log of the error
When running JMeter with the -n (no-gui) flag on Windows Nanoserver, the CSV
Data Set Config element produces an uncaught java.lang.UnsatisfiedLinkError
exception from awt.dll. The message reads, "Can't find dependent libraries. See
log file for details."
I've attached the contents of the jmeter.log file, a sample JMX file, and a
sample CSV file (place in the same directory as the JMX file). To reproduce,
follow the below instructions.
1) On a Windows host, install Docker for Windows from Docker Hub
(https://hub.docker.com/editions/community/docker-ce-desktop-windows).
2) Copy the attached JMX file to a subfolder of the JMeter installation folder.
3) Change Docker's configuration to run Windows containers by right clicking
the Docker icon in the system tray and choosing "Switch to Windows
containers...".
4) Open Powershell and use the command `docker run -it -v
{jmeter-install-dir}:C:\jmeter -m 2g --entrypoint powershell
13-ea-3-jdk-nanoserver-sac2016`
5) The Powershell context will switch. You are now inside the Docker image.
Your JMeter installation folder is mapped to C:\jmeter. Run
C:\jmeter\bin\jmeter from the command line with the -n flag as you normally
would. Also use the -t flag to point to the location of tests.jmx (which is
inside C:\jmeter at the same relative location as on your host machine).
Note the message "Uncaught Exception java.lang.UnsatisfiedLinkError:
C:\openjdk-13\bin\awt.dll: Can't find dependent libraries. See log file for
details."
This message is unexpected mainly because the exception is uncaught. I'm also a
little surprised to see mention of awt.dll, as I'm using the -n flag here.
The tests.jmx file is nothing special. It contains only a thread group with one
instance of the config element "CSV Data Set Config".
--
You are receiving this mail because:
You are the assignee for the bug.
