-
Bug
-
Resolution: Fixed
-
High
-
4.0.3, 5.0-OD-24, 5.0.2, 5.1.3
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
I've seen two cases recently where customers have reported that searching Confluence from within JIRA gave them a "The JIRA server was contacted but has returned an error response" message instead of search results. Combing through JIRA's logs, it's reporting the following:
/rest/confluenceIssueLink/1/confluence/search [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service java.lang.RuntimeException: Failed to parse Confluence Remote API response Caused by: org.xml.sax.SAXParseException: Character reference "" is an invalid XML character.
I was able to narrow it down to a Word document somewhere that Confluence had indexed, and it was being returned to JIRA from the search results.
Workaround
- Navigate to the Manage add-ons page
- Choose to display All add-ons
- Look for Office Connector Plugin, and then disable the Word Content Extractor module
- Reindexing Confluence
This workaround would stop the functionality to index the Word document. Once your instance is upgraded to the Fixed Version (5.5.1), ensure that this module has been re-enabled.
- is caused by
-
CONFSERVER-11193 Wrong excerpt field in Confluence search results using remote API
-
- Closed
-
- relates to
-
CONFCLOUD-27572 Invalid XML characters in indexed Word documents cause Confluence to serve up invalid XML to JIRA
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Wiki Page Failed to load
-
Wiki Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
The fix for this made it into master, and it broke the A1 license build. I reverted the commit on master. Please check the fix against a branch build and re-apply to master once it works.
https://stash.atlassian.com/projects/CONF/repos/confluence/commits/495ea4e0a9916e39ae3cce79afb3245d7702d33f