As of June 1, 2015, the IDE Connector documentation will no longer be maintained by Atlassian. See https://developer.atlassian.com/blog/2015/06/discontinuing-ide-connectors-support/
for more information. We will also be making this documentation available for our open source community here: http://atlassian-docs.bitbucket.org/
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.
Overview
Content Tools
Apps
19 Comments
Anonymous
I am entering http://your.host as the url and still getting the 404. Is there any other cause besides the mis-entered URL? Or is there anyway to debug this further?
-Evan
Anonymous
Figured out that this 404 also happens when you haven't yet enabled the REST API in your fisheye/crucible instance.
Anonymous
I can't get it working when over https.
Piotr Maruszak
I'll check that issue but currently I'm busy. I'll try to investigate this problem ASAP.
Anonymous
HTTP authentication over https:
com.atlassian.connector.commons.jira.rss.JIRAException: (401)Authorization Required
at com.atlassian.connector.commons.jira.JIRAServerFacade2Impl.getProjects(JIRAServerFacade2Impl.java:236)
at com.atlassian.theplugin.commons.jira.IntelliJJiraServerFacade.getProjects(IntelliJJiraServerFacade.java:89)
at com.atlassian.theplugin.commons.jira.cache.JIRAServerCache.getProjects(JIRAServerCache.java:123)
at com.atlassian.theplugin.commons.jira.cache.JIRAServerModelImpl.getProjects(JIRAServerModelImpl.java:160)
at com.atlassian.theplugin.idea.jira.IssueListToolWindowPanel$LocalJiraIssueListModelListener$ModelChangedRunnable.run(IssueListToolWindowPanel.java:1576)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at com.intellij.ide.IdeEventQueue.e(IdeEventQueue.java:652)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:505)
at com.intellij.ide.IdeEventQueue.b(IdeEventQueue.java:404)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:368)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: com.atlassian.theplugin.commons.remoteapi.RemoteApiException: (401)Authorization Required
at com.atlassian.connector.commons.jira.soap.JIRASessionImpl.login(JIRASessionImpl.java:203)
at com.atlassian.connector.commons.jira.JIRAServerFacade2Impl.getSoapSession(JIRAServerFacade2Impl.java:92)
at com.atlassian.connector.commons.jira.JIRAServerFacade2Impl.getProjects(JIRAServerFacade2Impl.java:220)
... 16 more
can someone fix the connector to handle HTTP authentication over https?
Anonymous
I get this error when i try to access my server thru the plugin. I tried loggin into the server as the error suggests but keep getting it
http://myjiraserver.com/rpc/soap/jirasoapservice-v2
com.atlassian.theplugin.commons.remoteapi.RemoteApiLoginException: Due to multiple failed login attempts, you have been temporarily banned from using the remote API.
To re-enable the remote API please log into your server via the web interface
at com.atlassian.connector.commons.jira.soap.JIRASessionImpl.login(JIRASessionImpl.java:196)
at com.atlassian.connector.commons.jira.JIRAServerFacade2Impl.testServerConnection(JIRAServerFacade2Impl.java:140)
at com.atlassian.theplugin.commons.jira.IntelliJJiraServerFacade.testServerConnection(IntelliJJiraServerFacade.java:243)
at com.atlassian.theplugin.idea.config.serverconfig.ProductConnector.connect(ProductConnector.java:31)
at com.atlassian.theplugin.ConnectionWrapper.run(ConnectionWrapper.java:63)
Caused by: com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Attempt to log in user 'snarasimhan' failed. The maximum number of failed login attempts has been reached. Please log into the application through the web interface to reset the number of failed login attempts.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:104)
at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:90)
at com.atlassian.connector.commons.jira.soap.axis.RemoteAuthenticationException.getDeserializer(RemoteAuthenticationException.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84)
at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464)
at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547)
at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157)
at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.atlassian.connector.commons.jira.soap.axis.JirasoapserviceV2SoapBindingStub.login(JirasoapserviceV2SoapBindingStub.java:4507)
at com.atlassian.connector.commons.jira.soap.JIRASessionImpl.login(JIRASessionImpl.java:192)
... 4 more
mir(yam) gillian
You should note that in Crucible the Remote API is turned off by default and will cause an obscure malformed reponse error that does not point you in the right direction (that the Remote API needs to be enabled in the Crucible admin).
Anonymous
Here's a tip: if you receive a (301)Moved Permanently it might be because you need https instead of http. That was a lucky guess for me, as there was no feedback from the plugin that this might have been the cause.
Anonymous
Reading all about the ways and methods of troubleshooting a server connection in the IntelliJ connector was very much knowledgeable to my concern.
website templates
Michael Wheelaghan
Connector is working for JIRA OnDemand but not Bamboo for me (12.1 IntelliJ) getting this exception on Test Connection (No builds display if just acknowledging)
com.atlassian.theplugin.commons.remoteapi.RemoteApiLoginException: Server returned malformed response
at com.atlassian.theplugin.commons.bamboo.api.LoginBambooSession.login(LoginBambooSession.java:132)
at com.atlassian.theplugin.commons.bamboo.BambooServerFacadeImpl.testServerConnection(BambooServerFacadeImpl.java:99)
at com.atlassian.connector.intellij.bamboo.IntelliJBambooServerFacade.testServerConnection(IntelliJBambooServerFacade.java:225)
at com.atlassian.theplugin.idea.config.serverconfig.ProductConnector.connect(ProductConnector.java:35)
at com.atlassian.theplugin.ConnectionWrapper.run(ConnectionWrapper.java:63)
Caused by: org.jdom.input.JDOMParseException: Error on line 14: The element type "link" must be terminated by the matching end-tag "</link>".
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:504)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:807)
at com.atlassian.theplugin.commons.remoteapi.rest.AbstractHttpSession.retrievePostResponseInternalImpl(AbstractHttpSession.java:457)
at com.atlassian.theplugin.commons.bamboo.api.LoginBambooSession.login(LoginBambooSession.java:94)
... 4 more
Caused by: org.xml.sax.SAXParseException; lineNumber: 14; columnNumber: 174; The element type "link" must be terminated by the matching end-tag "</link>".
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:489)
... 7 more
Anonymous
I am having precisely the same issue as Michael. Any news on how to get past this?
Ilia Sretenskii
I have a showstopper issue with the plugin of versions 3.0.11 and 3.0.12-SNAPSHOT
INTPLUG-335 - Getting issue details... STATUS
Ilia Sretenskii
This issue has been fixed!
Anonymous
Last Atlassian JIRA Connector update 3.0.12 broke something. After letting the IntelliJ IDEA 12.1.4 automatically update the connector to this new version I can no longer connect to our Atlassian JIRA v5.2.5 server that I had no problems using before applying the update. Credentials are correct, those are saved to multiple projects which none no longer cna login. OFC I now need to use JIRA via the web UI so I do know my credentials are ok.
om.atlassian.theplugin.commons.remoteapi.RemoteApiException: *******:[password 8 chars]@https://jira.********.**
Login denied
at com.atlassian.connector.commons.jira.rest.JiraRestSessionImpl.wrapWithRemoteApiException(JiraRestSessionImpl.java:801)
at com.atlassian.connector.commons.jira.rest.JiraRestSessionImpl.login(JiraRestSessionImpl.java:178)
at com.atlassian.connector.commons.jira.rest.JiraRestSessionImpl.testConnection(JiraRestSessionImpl.java:760)
at com.atlassian.connector.commons.jira.JiraRESTFacade2Impl.testServerConnection(JiraRESTFacade2Impl.java:329)
at sun.reflect.GeneratedMethodAccessor1223.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.atlassian.connector.commons.jira.JIRAServerFacade2Impl$1.invoke(JIRAServerFacade2Impl.java:91)
at com.sun.proxy.$Proxy37.testServerConnection(Unknown Source)
at com.atlassian.connector.commons.jira.JIRAServerFacade2Impl.testServerConnection(JIRAServerFacade2Impl.java:268)
at com.atlassian.theplugin.commons.jira.IntelliJJiraServerFacade.testServerConnection(IntelliJJiraServerFacade.java:473)
at com.atlassian.theplugin.idea.config.serverconfig.ProductConnector.connect(ProductConnector.java:35)
at com.atlassian.theplugin.ConnectionWrapper.run(ConnectionWrapper.java:63)
Caused by: com.atlassian.jira.rest.client.RestClientException: Login denied
at com.atlassian.jira.rest.client.internal.jersey.AbstractJerseyRestClient.invoke(AbstractJerseyRestClient.java:74)
at com.atlassian.jira.rest.client.internal.jersey.AbstractJerseyRestClient.postAndParse(AbstractJerseyRestClient.java:120)
at com.atlassian.jira.rest.client.internal.jersey.JerseySessionRestClient.login(JerseySessionRestClient.java:54)
at com.atlassian.connector.commons.jira.rest.JiraRestSessionImpl.setSessionCookies(JiraRestSessionImpl.java:817)
at com.atlassian.connector.commons.jira.rest.JiraRestSessionImpl.doCall(JiraRestSessionImpl.java:808)
at com.atlassian.connector.commons.jira.rest.JiraRestSessionImpl.wrapWithRemoteApiException(JiraRestSessionImpl.java:789)
... 12 more
Caused by: com.sun.jersey.api.client.UniformInterfaceException: Client response status: 403
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:607)
at com.sun.jersey.api.client.WebResource.post(WebResource.java:235)
at com.atlassian.jira.rest.client.internal.jersey.AbstractJerseyRestClient$4.call(AbstractJerseyRestClient.java:124)
at com.atlassian.jira.rest.client.internal.jersey.AbstractJerseyRestClient.invoke(AbstractJerseyRestClient.java:60)
... 17 more
Ilia Sretenskii
Probably you should try the new snapshot version of the plugin.
If the bug is also there, then the plugin bug tracker is the place to file the bug.
https://ecosystem.atlassian.net/browse/PL
Sven Carstens
Hi,
I'm having troubles with plugin version 3.0.13, SVN:1312051023.
I can connect fine via HTTP url, but the HTTPS version always fails on the initial connect and a RST is send by the remote server.
com.atlassian.theplugin.commons.remoteapi.RemoteApiException: javax.net.ssl.SSLException: Received fatal alert: bad_record_mac at com.atlassian.connector.commons.jira.soap.JIRASoapSessionImpl.login(JIRASoapSessionImpl.java:193) at com.atlassian.connector.commons.jira.JIRASoapAndXmlServerFacade2Impl.testServerConnection(JIRASoapAndXmlServerFacade2Impl.java:154) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.atlassian.connector.commons.jira.JIRAServerFacade2Impl$1.invoke(JIRAServerFacade2Impl.java:93) at com.sun.proxy.$Proxy33.testServerConnection(Unknown Source) at com.atlassian.connector.commons.jira.JIRAServerFacade2Impl.testServerConnection(JIRAServerFacade2Impl.java:268) at com.atlassian.theplugin.commons.jira.IntelliJJiraServerFacade.testServerConnection(IntelliJJiraServerFacade.java:473) at com.atlassian.theplugin.idea.config.serverconfig.ProductConnector.connect(ProductConnector.java:35) at com.atlassian.theplugin.ConnectionWrapper.run(ConnectionWrapper.java:63)Jacek Jaroczynski
Atlassian Connector for Eclipse suffers from the same issue. Please take a look into following ticket to get some clues how to solve that:
Sven Carstens
This did work for me:
-Dcom.sun.net.ssl.rsaPreMasterSecretFix=true
roded
I'm getting a bunch of these (edit issue, new issue):
(idea 12.1.6, Atlassian JIRA (v4.3.3#617-r149616))
Any ideas?