-
Bug
-
Resolution: Obsolete
-
Low
-
5.4.3
-
Severity 3 - Minor
-
This one is a little hazy, sorry about that.
A few weeks ago, when CAC was unhealthy, I observed a scenario where a particular page-diff request was running for several (15+) minutes. Unfortunately, because of the bad health of CAC at the time, I was unable to get a heap-dump or determine exactly what URL was requested that lead to this scenario.
What I do know is that the thread was executing for 15+ minutes, and for the entirety of this duration was stuck in org.eclipse.compare.internal.core.LCS. don.willis@atlassian.com has indicated that this should never happen, as page diffs have timeout logic implemented. Is it possible there's some edge-cases, perhaps a page diff that is extremely computationally expensive, that cause the request to exceed its timeout and not be properly interrupted?
- relates to
-
-
- Closed
-
[CONFSERVER-33150] Potential page diff edge-case
Is it possible there's some edge-cases, perhaps a page diff that is extremely computationally expensive, that cause the request to exceed its timeout and not be properly interrupted?
Not so much extremely computationally expensive as having some sort of infinite loop in a part of the algorithm that doesn't check the interruptedness. Totally possible.
Thank you for your interest in this ticket. The Confluence Server and Data Center team released a major upgrade to the editor in 6.14. Due to the age of this ticket and/or lack of updates, we suspect that this issue is no longer relevant or was resolved as a result of the upgrade and are now closing this ticket.
If this issue is still a problem in your Confluence instance in version 6.15 or later, please tag me in your comment and we can reopen this ticket for review.
You can read more about the editor upgrade in the 6.14 Release Notes.
Thanks
Makisa Appleton | Senior Product Manager, Confluence Server and Data Center