-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
5.8
-
Severity 3 - Minor
-
0
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
As a JIRA and Confluence user, cloning issues with linked Confluence pages results in errors in the Confluence log for
- relates to
-
CONFCLOUD-38058 Link page to cloned issue
- Closed
[CONFSERVER-38058] Link page to cloned issue causes error in log
Thanks Adam! I should tell you that we are on Confluence 6.0.6, JIRA 7.2.7.
I will try upgrading JIRA to see it that makes any difference, but it will be a few weeks before that can happen.
Hi Adam,
The log entries are from both systems; I edited my comment yesterday to show both log entries.
You'll see that Confluence mentions xmlrpc, which is referenced in several other bugs recently.
Like I said, I don't expect the link to copy, and that is fine, but it would be nicer to not write errors to either system's log for what seems to be an expected behavior 
Hi April, i preusme this error is in tye JIRA log, if so, please raise a JIRA suggestion or contact support to have a bug raised. Regarding ng this request, does this apply to both links to cinfluence oages created frok within JIRA and those that are created by me tioning the issue on a confluence page. We vannot expect the links to copy if it is mentioned on a page, as the new issue is not mentioned on that page.
Hi there, I don't personally care if you guys copy these links or not, but whatever you decide, could you just not have confusing errors in the log?
E.g., my user clones an issue that original issue is mentioned on a Confluence page.
Expected result:
No logged errors.
Actual result:
Confluence:
2017-04-11 16:12:22,506 WARN [http-nio-8444-exec-21] [oauth.serviceprovider.internal.AuthenticatorImpl] logOAuthProblem Problem encountered authenticating OAuth client for url "https://confluence.ezesoft.net/rpc/xmlrpc", error was "nonce_used", with parameters "{oauth_problem=nonce_used}"
-- url: /rpc/xmlrpc | traceId: 52b6617f1e544a2c
Jira:
2017-04-11 16:12:22,506 http-bio-8443-exec-10805 ERROR smagdel 972x820495x5 6mcdts 10.207.74.72,10.207.85.65 /rest/viewIssue/1/remoteIssueLink/render/26605 [c.a.j.p.v.issuelink.rest.RemoteIssueLinkResource] Error occurred while generating final HTML for remote issue link: java.lang.RuntimeException: java.io.IOException: Failed to load Confluence Page from remote server Caused by: java.io.IOException: Failed to load Confluence Page from remote server Caused by: com.atlassian.applinks.internal.common.auth.oauth.OAuthMessageProblemException: OAuth authentication failed: nonce_used
Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. If you are able to describe your higher-level goals we may be able to provide better guidance. Thanks again.
Regards,
Confluence Product Management
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center