Details
-
Bug
-
Resolution: Fixed
-
High
-
4.22.2, 4.20.10, 5.1.0, 4.20.12
-
None
-
2
-
Severity 2 - Major
-
31
-
Description
Issue Summary
When we have a Jira OnPrem connected to Confluence Cloud, it might be possible the connection stops working.
Steps to Reproduce
- Have Jira OnPrem integrating with Confluence Cloud using the Confluence Cloud Integration, which was working previously.
- Try to link a KB to an Issue
- We should see a message like this "There was a problem completing the current request" from the UI.
Expected Results
The KB should be linked with no issues.
Actual Results
A warning message ("There was a problem completing the current request) shows on the UI, and the task will not be completed.
From the logs in the atlassian-jira.log file, we should see several StackOverFlowError while Jira is running some REST APIs against Confluence Cloud. Like the sample below -
2022-09-22 21:53:53,308+0000 http-nio-8080-exec-26465 url: /rest/servicedesk/1/servicedesk/HD/kb/CONFLUENCE_CLOUD/space; user: xxxxx ERROR xxxxx 1313x14878224x1 c17btf xx.xx.xx.xx /rest/servicedesk/1/servicedesk/HD/kb/CONFLUENCE_CLOUD/space [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null java.lang.StackOverflowError at java.base/java.lang.String.toLowerCase(Unknown Source) at java.base/java.lang.String.toLowerCase(Unknown Source) at com.sun.jersey.core.util.StringIgnoreCaseKeyComparator.hash(StringIgnoreCaseKeyComparator.java:53) at com.sun.jersey.core.util.StringIgnoreCaseKeyComparator.hash(StringIgnoreCaseKeyComparator.java:48) at com.sun.jersey.core.util.KeyComparatorHashMap.keyComparatorHash(KeyComparatorHashMap.java:294) at com.sun.jersey.core.util.KeyComparatorHashMap.containsKey(KeyComparatorHashMap.java:359) at com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:102) at com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:105)
We may look at the HTTPBasicAuthFilter class.
This issue is caused by a BUG, where the filter allowing to authenticate the request made to Confluence Cloud is added at each request. This is causing a stack overflow when an exception occurs on Confluence side but also eats up a lot of memory unnecessarily even when the request works fine.
Note that the following error might be thrown in the atlassian-servicedesk.log file:
2023-01-03 15:24:24,861-0500 https-jsse-nio-8443-exec-68 url:/issues/rest/se...les/<ISSUE_KEY> username:someuser ERROR <SANITIZED DATA> /rest/servicedesk/knowledgebase/latest/articles/<ISSUE_KEY> [confluenceknowledgebase.cloud.client.ConfluenceCloudClientImpl] Failed to call Confluence Cloud API for path /rest/api/search com.sun.jersey.api.client.ClientHandlerException: java.lang.IllegalStateException: Stream handler unavailable due to: null at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:155) at com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:105) at com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:105) at com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:105) at com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:105) at com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:105) at com.sun.jersey.api.client.filter.HTTPBasicAuthFilter.handle(HTTPBasicAuthFilter.java:105) ...
Impact of this bug:
For now, there are 2 known symptoms caused by this bug:
- When opening any ticket from the Service Management project in the Agent view, the Related Knowledge base articles will show a red exclamation mark without any error:
- The error There was a problem completing the current request is thrown when trying to select a space while configuring the knowledge base space in a JSM project
- More information in the KB article https://confluence.atlassian.com/jirakb/error-when-trying-to-configure-a-knowledge-base-in-a-service-management-project-1085200961.html
Workaround
Currently, the only workaround is to restart the Jira Service to clean the service object, because the filter is added on every request after the service is constructed (on startup).
Attachments
Issue Links
- is related to
-
-
- Closed
-
- relates to
-
JSMDC-15361 Loading...