I’m trying to run performance tests on my JIRA instance using the JIRA Performance Tools framework but I keep getting connection errors. I followed the documentation and configured my test setup properly but something seems wrong.
Here’s my test configuration in the performance test file:
final URI targetJira = new URI("http://10.0.0.50:8080");
performanceTest.setUserName("testadmin");
performanceTest.setUserPassword("testadmin");
When I execute the test using:
./mvnw clean verify
I get this error output:
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[ERROR] MyJiraPerformanceIT.runPerformanceTest:42 ? Failed to run with [--jira-address, http://...
[INFO] BUILD FAILURE
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.22.0:verify
My JIRA server at http://10.0.0.50:8080 is definitely running and accessible through browser. I can log in normally and everything works fine when accessing it manually. Why is the performance testing tool unable to connect to this address? Could this be related to the fact that this testing framework hasn’t received updates recently?
I’ve hit this same issue setting up JPT in corporate environments. Your JIRA probably has cross-origin restrictions or needs specific headers that the testing framework isn’t sending. First, try the full URL with context - most corporate installs use something like http://10.0.0.50:8080/jira instead of just the root. Also check if REST API access is enabled for your test user. Admins often disable API access for certain roles, which breaks connections while the web UI still works fine. I’d test manually with curl using the same credentials to see what response codes you get.
check your jira settings - make sure they allow access from testing tools. firewalls or network policies sometimes block automated tests even when manual access works fine. also verify if the endpoint needs a specific context path like /jira to connect properly!
I encountered a similar issue after upgrading JIRA. It is often due to authentication changes or an incorrect base URL configuration. Consider adding the full context path to your URI, as many JIRA setups require something like /secure/Dashboard.jspa to establish the connection. Additionally, check if CAPTCHA is enabled for failed logins, as it can interfere with automated testing tools. Your testing framework might be subject to rate limits or security measures that do not affect regular browser access. Enabling debug logging in Maven can help you observe the HTTP responses during connection attempts.