Troubleshooting#

The failures that actually happen, and what each one means.

Signing in#

"That email address and password do not match an account"#

Said the same way whether the address is unknown or the password is wrong, deliberately — a message that distinguishes them tells somebody which addresses exist.

If it is a new installation and nobody can sign in, the administrator named in the configuration may never have been created. On the server, run:

python tools\check_accounts.py

It says whether that account exists and whether its password would be accepted by the policy.

A new password is refused#

The policy forbids a password containing your own email address — the part before the @, or your domain. See Accounts.

Uploads#

"The web server in front of JMXPress refused this upload as too large"#

That sentence means the reverse proxy, not JMXPress. nginx defaults client_max_body_size to 1 MB, and every upload JMXPress accepts is larger than that.

Raise it in the server block and reload nginx. JMXPress's own limits are much higher — 512 MB for a results file, 64 MB for a test plan.

The two refusals are told apart by their shape: JMXPress answers with JSON naming the limit; the proxy answers with an HTML error page.

Running#

The run fails immediately with a file error#

On Windows, [WinError 32] The process cannot access the file because it is being used by another process usually means a previous JMeter process is still running and holding the run folder. Stop it and try again.

A test "passes" but measures nothing#

Check the test data. A plan whose CSV is missing sends the literal ${username} to the application. JMXPress names the files a plan needs before the run starts for exactly this reason — do not skip past that list.

A stopped run is reported as stopped#

That is correct, not a bug. A run that was stopped early is never reported as completed.

Monitoring#

The server-side panel says "Waiting for APM data"#

Expected for the first minute or two. Providers publish in buckets and ingest with a delay. See Live results.

If it never fills for a long run, check the connection on the APM Tools page — it will show the provider's own error.

"Dynatrace is not worth asking again for another N seconds"#

The provider's own floor on how often it may be asked, being respected. The readings already on screen stay. Nothing is wrong.

A monitor says "Abandoned"#

The collection never finished: JMXPress stopped before the test did — the server was restarted, or the run ended another way. Nothing was recorded for that run. See APM integrations.

A Dynatrace connection cannot read entities#

Check the environment address. The .apps. address is the OAuth platform domain; the classic Environment API is served from the .live. address. JMXPress corrects the common case and tells you it did.

Diagnostics#

"Diagnostics are switched off on this computer"#

Correct and deliberate. They are enabled in agent.ini on that machine, not from the web page. See Diagnostics.

A heap dump fails to collect#

The machine needs a JDK, not just a JRE — jcmd is a JDK tool. The agent must also be running as a user that can attach to that process; that is the operating system's rule.

Agents#

A paired computer shows as offline#

The agent makes outbound calls; nothing connects to it. Check that the agent is running on that machine and that it can reach the server over HTTPS.

Still stuck#

Write to support@jmxpress.in with the page you were on, what you expected, and what happened instead.