Atlassian IDE Connector : Troubleshooting Server Connection in the IntelliJ Connector
This page last changed on Jan 18, 2009 by smaddox.
This page describes some common errors you may encounter when setting up your server connections for the Atlassian IntelliJ Connector. Symptom when Connecting to CrucibleHTTP 404 error when connecting to Crucible even though the URL seems to be correct. See bug PL-242. Cause and SolutionIn 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.
Symptom when Connecting to JIRAHTTP 400 when connecting to JIRA, even though the URL seems to be correct. See bug PL-643. Cause and SolutionIn 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. 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:
Steps required for configuring JIRA SOAP service are described in the JIRA documentation. |
![]() |
Document generated by Confluence on Jun 15, 2009 21:47 |