This page describes some common errors you may encounter when setting up your server connections for the Atlassian Connector for IntelliJ IDEA.
Captcha authentication requested
Cause and Solution
It means that maximum number of failed login attempts may have been reached. Please log into the web application through the web interface to reset the number of failed login attempts.
Symptom when Connecting to Crucible
HTTP 404 error when connecting to Crucible even though the URL seems to be correct.
See bug PL-242.
Cause and Solution
In the connector configuration panel, you provide a URL for your Crucible server. When attempting to access Crucible, the connector appends the string '/rest-service/' to the URL provided in the connector configuration panel. The resulting URL is the REST endpoint of the Crucible instance. Therefore, you should enter just the base URL for your main Fisheye+Crucible website.
Example:
- Let's say that the URL for your main Fisheye+Crucible website is
http://your.host, and the URL for your Crucible server ishttp://your.host/cru. - In the connector configuration panel, you should enter the following as the connection URL:
http://your.host
- The resulting REST endpoint that the connector tries to reach will be
http://your.host/rest-service.
The situation can become even more complicated when the Crucible server is fronted by Apache acting as a proxy. Mappings for Crucible URLs can be configured in an unpredictable way, resulting in weird '404' errors.
Symptom when Connecting to JIRA
HTTP 400 or 503 when connecting to JIRA, even though the URL seems to be correct.
See bug PL-643.
Cause and Solution
In the connector configuration panel, you provide a URL for your JIRA server. When attempting to access JIRA, the connector uses SOAP and appends the string '/rpc/soap/jirasoapservice-v2' to the URL provided in the configuration panel. In order for such an URL to work, the JIRA server has to have its SOAP RPC enabled and configured to use this URL. Enabling remote API calls in JIRA server is described here.
The simplest way to test if you have your JIRA SOAP endpoint configured correctly is to point your browser at it, with the appended string added at the end. The resulting page should read something along the lines of:
Hi there, this is an AXIS service!
Perhaps there will be a form for invoking the service here...
Example:
- Let's say the URL for JIRA that you provided in the configuration panel is
http://your.jira/ - the resulting URL that the connector will use to connect to JIRA is
http://your.jira/rpc/soap/jirasoapservice-v2
Steps required for configuring JIRA SOAP service are described in the JIRA documentation.