You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the jmeter source get by git,the jmeter version is lastest.
./gradlew.bat runGui is fail.
Getting Build Failed with exception while building using ./gradlew.bat runGui:
PS D:\xxx\jmeter> ./gradlew.bat runGui
Type-safe project accessors is an incubating feature.
Configure project :
Building JMeter 6.0.0-SNAPSHOT
Configure project :src:components
RenderInBrowser is excluded from compilation. If you want to compile it, add -PenableJavaFx
Configure project :src:dist-check
Certain tests will be skipped as they depend on external services and fail too often. Please add -PenableFlaky to enable them: [batchHttp4ImplDigestAuth, batchHttp4ImplPreemptiveBasicAuthJava, batchHttp4ImplPreemptiveBasicAuth, batc
hSlowCharsFeatureHttpClient4, batchSlowCharsFeatureJava, batchTCP_TESTS, batchTestKeepAlive, batchTestRedirectionPolicies, batchJDBC_TESTS, batchResponseDecompression]
Task :src:dist:runGui
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated and will be removed in a future release
================================================================================
Don't use GUI mode for load testing !, only for Test creation and Test debugging.
For load testing, use CLI Mode (was NON GUI):
jmeter -n -t [jmx file] -l [results file] -e -o [Path to web report folder]
& increase Java Heap to meet your test requirements:
Modify current env variable HEAP="-Xms1g -Xmx1g -XX:MaxMetaspaceSize=256m" in the jmeter batch file
Check : https://jmeter.apache.org/usermanual/best-practices.html
================================================================================
An unrecoverable stack overflow has occurred.
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_STACK_OVERFLOW (0xc00000fd) at pc=0x00007ff89b91c5b7, pid=17424, tid=15452
JRE version: Java(TM) SE Runtime Environment (17.0.10+11) (build 17.0.10+11-LTS-240)
Java VM: Java HotSpot(TM) 64-Bit Server VM (17.0.10+11-LTS-240, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
Problematic frame:
C [awt.dll+0xec5b7]
No core dump will be written. Minidumps are not enabled by default on client versions of Windows
An error report file with more information is saved as:
D:\2024\source\jmeter\bin\hs_err_pid17424.log
If you would like to submit a bug report, please visit: https://bugreport.java.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
What went wrong:
Execution failed for task ':src:dist:runGui'.
Process 'command 'D:\ly\sw\jdk-17.0.10\bin\java.exe'' finished with non-zero exit value 1
Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
Steps to reproduce the problem
the jmeter source get by git,the jmeter version is lastest.
./gradlew.bat runGui is fail.
Getting Build Failed with exception while building using ./gradlew.bat runGui:
PS D:\xxx\jmeter> ./gradlew.bat runGui
Type-safe project accessors is an incubating feature.
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_STACK_OVERFLOW (0xc00000fd) at pc=0x00007ff89b91c5b7, pid=17424, tid=15452
JRE version: Java(TM) SE Runtime Environment (17.0.10+11) (build 17.0.10+11-LTS-240)
Java VM: Java HotSpot(TM) 64-Bit Server VM (17.0.10+11-LTS-240, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
Problematic frame:
C [awt.dll+0xec5b7]
No core dump will be written. Minidumps are not enabled by default on client versions of Windows
An error report file with more information is saved as:
D:\2024\source\jmeter\bin\hs_err_pid17424.log
If you would like to submit a bug report, please visit:
https://bugreport.java.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
FAILURE: Build failed with an exception.
Execution failed for task ':src:dist:runGui'.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.5/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 13s
161 actionable tasks: 18 executed, 143 up-to-date
JMeter Version
JMeter 6.0.0-SNAPSHOT
Java Version
17
kotlin Version
1.9.20
gradle Version
8.5
OS Version
windows
The text was updated successfully, but these errors were encountered: