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
{{ message }}
This repository was archived by the owner on Apr 13, 2026. It is now read-only.
I am trying to run the cluster in debug mode with the command line. However the custom Elasticsearch --debug-jvm isn't recognized. Am I using it wrong ?
shield-custom-realm-example ± ❯ gradle integTestCluster\#start --debug-jvm
=======================================
Elasticsearch Build Hamster says Hello!
=======================================
Gradle Version : 3.5
OS Info : Mac OS X 10.12.5 (x86_64)
JDK Version : Oracle Corporation 1.8.0_121 [Java HotSpot(TM) 64-Bit Server VM 25.121-b13]
JAVA_HOME : /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home
The executable property on ForkOptions has been deprecated and is scheduled to be removed in Gradle 5.0. Please use javaHome instead.
FAILURE: Build failed with an exception.
* What went wrong:
Problem configuring task :integTestCluster#start from command line.
> Unknown command-line option '--debug-jvm'.
* Try:
Run gradle help --task :integTestCluster#start to get task usage details. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
BUILD FAILED
Total time: 0.908 secs
Actually I'm using a hack to set the debug property on the integ task itself.
I am trying to run the cluster in debug mode with the command line. However the custom Elasticsearch
--debug-jvmisn't recognized. Am I using it wrong ?Actually I'm using a hack to set the debug property on the integ task itself.