Merge pull request #19471 from gsanchezgavier/gsanchez/doc/jmx-troubl…

…eshooting

doc: add jmx troubleshooting

src/install/jmx/whatsNext.mdx

@@ -1097,6 +1097,27 @@ Troubleshooting tips:
   >
     You can use the CLI interactive tool [JMXTerm](https://docs.cyclopsgroup.org/jmxterm) for troubleshooting. Find documentation for JMXTerm in our [`nrjmx` troubleshooting page](https://github.com/newrelic/nrjmx/blob/master/TROUBLESHOOT.md). As of `nrjmx` v1.7.0, JMXTerm is no longer bundled with `nrjmx`, and needs to be downloaded independently. Check the [`nrjmx` installation instructions](https://github.com/newrelic/nrjmx#installation).
   </Collapser>
+
+  <Collapser
+    id="java-not-found"
+    title="Java binary not found on the PATH"
+  >
+    By default the integration looks for the `java` binary into the PATH that the Infrastructure Agent has visibility on. In case `java` is not present in the PATH the `JAVA_HOME` [environment variable](https://docs.newrelic.com/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format/#env) must be set into the nri-jmx config file.
+    ```yaml
+    integrations:
+    - name: nri-jmx
+      env:
+        COLLECTION_FILES: "/etc/newrelic-infra/integrations.d/jvm-metrics.yml"
+        JMX_HOST: jmx-host.localnet
+        JMX_PASS: admin
+        JMX_PORT: 9999
+        JMX_USER: admin
+        JAVA_HOME: "path/to/java/home"
+      interval: 15s
+      labels:
+        env: production
+    ```
+  </Collapser>
 </CollapserGroup>
 
 ## Check the source code [#source-code]