Hey there, let’s dig into why your JMeter test runs fine in non-GUI mode on the remote server but isn’t writing any results to your JTL file. I’ve put together targeted checks and fixes based on common issues with this scenario:

1. Double-Check Your Result Collector Configuration in the JMX #

Since you shared a snippet of your JMX, the first thing to verify is your Result Collector (like Summary Report or View Results Tree) setup:

• Ensure the filename property uses an absolute path on the remote server (relative paths can be tricky if JMeter’s working directory isn’t what you expect).
• Confirm the enabled attribute is set to true—it’s easy to accidentally disable the collector in the GUI and forget to re-enable it.
• Make sure the remote server’s JMeter process has write permissions to the output path you specified.

Here’s what a properly configured Result Collector looks like in the JMX:

<ResultCollector guiclass="SummaryReport" testclass="ResultCollector" testname="Summary Report" enabled="true">
  <boolProp name="ResultCollector.error_logging">false</boolProp>
  <objProp>
    <name>saveConfig</name>
    <value class="SampleSaveConfiguration">
      <time>true</time>
      <latency>true</latency>
      <!-- Include other metrics you want to capture -->
    </value>
  </objProp>
  <stringProp name="filename">/opt/jmeter/results/my_test_results.jtl</stringProp>
</ResultCollector>

2. Validate Your Non-GUI Command Syntax #

A common mistake is misformatting the JMeter startup command. Ensure you’re using the correct parameters in the right order:

jmeter -n -t /path/to/your/test_plan.jmx -l /path/to/your/output_results.jtl

• The -l flag is critical—it tells JMeter where to write the JTL results. Don’t confuse it with -j (which sets the log file path).
• If the JTL file already exists, JMeter won’t overwrite it by default. Add the -f flag to force overwrite:

  jmeter -n -t test_plan.jmx -l results.jtl -f
  

• Double-check that the remote server can access both the JMX file path and the output path, and that the user running JMeter has permissions to write to the output directory.

3. Dig Into JMeter Logs for Clues #

The JMeter log file (default: jmeter.log on the remote server) will almost always have hints about what’s going wrong. Search for keywords like:

• Permission denied (indicates write access issues)
• ResultCollector (check for errors loading or writing to the collector)
• filename (verify if JMeter is recognizing your output path correctly)
• Any ERROR or WARN entries related to file I/O—these are goldmines for troubleshooting.

4. Ensure Your JMX File Is Intact #

Your shared JMX snippet is incomplete, so it’s worth checking if the file itself is corrupted:

• Download the JMX from the remote server to your local machine, open it in the JMeter GUI, and confirm the Result Collector settings are saved correctly.
• Use an XML validator to check for syntax errors (like unclosed tags or missing attributes) that might break the configuration.
• Verify the file wasn’t corrupted during transfer to the remote server—compare the MD5 hash of your local JMX with the one on the server.

5. Check the Remote Server Environment #

• Java Version Compatibility: JMeter 3.3 requires Java 8—using a newer or older Java version can cause unexpected behavior.
• Disk Space: If the remote server’s disk is full, JMeter can’t write the JTL file. Run df -h to check available space.
• User Permissions: Ensure the user running JMeter has read access to the JMX file and write access to the output directory.

If you’ve tried all these steps and still have no luck, share the full (redacted) JMX content, your exact non-GUI command, and relevant snippets from the JMeter log—this will help narrow down the issue further.

内容的提问来源于stack exchange，提问作者Satya