Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
The way FishEye handles the data gathered via remote call should be improved. Currently the data are processed via SOAP request, resulting in certain characters are not being parsed in FishEye which leads to error.
When a JIRA issue being linked in the Crucible review, the error below is thrown in the Crucible logs. The error below is thrown because of the availabilty of certain character in the JIRA issue's description.
2014-03-07 18:18:11,736 DEBUG [qtp1788226354-170 ] fisheye JiraIssueUtil-buildJiraException - JIRA Server Your Company JIRA: org.xml.sax.SAXParseException; Premature end of file. com.atlassian.fisheye.jira.RemoteJiraException: org.xml.sax.SAXParseException; Premature end of file. at com.atlassian.fisheye.jira.soap.JiraUALSoapInvoker.invokeOperation(JiraUALSoapInvoker.java:52) at com.atlassian.fisheye.jira.soap.AbstractJiraSoapInvoker.invoke(AbstractJiraSoapInvoker.java:31) at com.atlassian.fisheye.jira.JiraServerImpl.invoke(JiraServerImpl.java:270) at com.atlassian.fisheye.jira.JiraServerImpl.getIssue(JiraServerImpl.java:275) at com.atlassian.fisheye.jira.issue.JiraIssueServiceImpl.retrieveJiraIssue(JiraIssueServiceImpl.java:168) ...
To reproduce the error, perform the following:-
- Create a JIRA issue with the special characters below in the description
GIF89a€ÿÿÿ!ù,@L;
- Try link the issue in Crucible review.
It had been already mentioned that the issue will not be fixed in JIRA : https://jira.atlassian.com/browse/JRA-30495
Attachments
Issue Links
- mentioned in
-
Page Loading...