org.xml.sax.SAXException when integrating with JIRA
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
Mouse over a JIRA issue key have following error in the atlassian-fisheye-<date>.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
2013-10-04 10:24:02,078 DEBUG [qtp13803350-10115 ] fisheye JiraIssueUtil-handleJiraException - Exception encountered while contacting JIRA Server: org.xml.sax.SAXException: Bad envelope tag: html
com.atlassian.fisheye.jira.RemoteJiraException: org.xml.sax.SAXException: Bad envelope tag: html
at com.atlassian.fisheye.jira.soap.JiraUALSoapInvoker.invokeOperation(JiraUALSoapInvoker.java:51)
at com.atlassian.fisheye.jira.soap.AbstractJiraSoapInvoker.invoke(AbstractJiraSoapInvoker.java:31)
at com.atlassian.fisheye.jira.JiraServerImpl.invoke(JiraServerImpl.java:246)
at com.atlassian.fisheye.jira.JiraServerImpl.getIssue(JiraServerImpl.java:251)
at com.atlassian.fisheye.jira.issue.JiraIssueServiceImpl.retrieveJiraIssue(JiraIssueServiceImpl.java:169)
at com.atlassian.fisheye.jira.issue.JiraIssueServiceImpl.getJiraIssue(JiraIssueServiceImpl.java:97)
at com.atlassian.fisheye.jira.action.JiraIssueAjaxAction.execute(JiraIssueAjaxAction.java:71)
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:601)
at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358)
at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218)
...
Caused by: org.xml.sax.SAXException: Bad envelope tag: html
Diagnosis
Enable Network Traffic debug logging and look for the following error:
1
2013-10-04 10:24:02,037 DEBUG [qtp13803350-10115 ] httpclient.wire.content Wire-wire - << "<html><head><title>Apache Tomcat/7.0.29 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 503 - Remote API not activated for this JIRA installation.</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Remote API not activated for this JIRA installation.</u></p><p><b>description</b> <u>The requested service (Remote API not activated for this JIRA installation.) is not currently available.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.29</h3></body></html>"Cause
Remote API is not enabled in JIRA server.
Solution
Resolution
Enable Accept remote API calls at JIRA Administration > System > General Configuration
Was this helpful?