Migrating Confluence and Jira from Atlassian Cloud to Server breaks Jira gadgets on Confluence
プラットフォームについて: Data Center - この記事は、Data Center プラットフォームのアトラシアン製品に適用されます。
このナレッジベース記事は製品の Data Center バージョン用に作成されています。Data Center 固有ではない機能の Data Center ナレッジベースは、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。
*Fisheye および Crucible は除く
要約
Jira gadgets stop working and can throw errors such as HTTP 500 Internal Server Errors. URLs are pointing to the old Jira Base URL.
診断
atlassian-confluence.log に次のメッセージが表示される。
Error rendering macro 'gadget' : The gadget at https://<OLD_URL>/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:filter-results-gadget/gadgets/filter-results-gadget.xml was not added to this Confluence instance yet.
.
OR
.
Unhandled exception occurred whilst decorating page
-- url: /plugins/servlet/gadgets/makeRequest | userName: sysadmin | referer: http://Confluence_URL/plugins/servlet/gadgets/ifr?container=atlassian&mid=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxchart%2Fgadgets%2Fgreenhopper-hour-burndown-chart.xml&libs=auth-refresh
java.lang.NullPointerException
at com.atlassian.gadgets.renderer.internal.http.TrustedAppContentFetcherFactory.createCertificate(TrustedAppContentFetcherFactory.java:70)
at com.atlassian.gadgets.renderer.internal.http.TrustedAppContentFetcherFactory.addTrustedAppHeaders(TrustedAppContentFetcherFactory.java:52)
at com.atlassian.gadgets.renderer.internal.http.TrustedAppContentFetcherFactory.fetch(TrustedAppContentFetcherFactory.java:46)
at org.apache.shindig.gadgets.servlet.MakeRequestHandler.fetch(MakeRequestHandler.java:84)原因
After moving the instances from the Atlassian Cloud to an Atlassian Server environment, the application links continue to make a reference to the CLOUD application link URL, and the gadgets stop working correctly due to corruption on the KEYSTORE table.
回避策
This guide will involve a lot of database manipulation; we strongly advise creating a staging environment for safety measures because, in case of problems, production data will not be affected.
- Delete your application link from both JIRA and Confluence side.
- Confluence を終了します。
- Back up your Confluence database.
次のクエリを実行します。
DELETE FROM keystore WHERE alias LIKE '%confluence%'- Follow the steps in the 'Workaround' section from CONFSERVER-93646 - Page Not Found error when executing JSP file to initialize an empty KEYSTORE table to re-initialize the KEYSTORE table.
NOTE: For older Confluence versions, please see CONFSERVER-11074 - Write JSP to initalise KEYSTORE table and ensure that you are using the correct version of the initKeyStore JSP file for your instance. - After following those steps recreate your application Link.
- Check again if the gadgets are working.
If your Jira Macro Issues are still pointing to the JIRA cloud instance, you will also need to follow the steps outlined in our KB How to bulk update JIRA Issue Macro to point to a different JIRA instance to bulk edit those issues to point to the correct instance.
Please note this issue is also observed when moving instances from one Atlassian Server to another. The gadgets window appears blank, along with the same errors seen in atlassian-confluence.log as documented above.
