JIRA Email Finger Print

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: サーバーと Data Center のみ。この記事は、サーバーおよび Data Center プラットフォームのアトラシアン製品にのみ適用されます。

プラットフォームについて: Server、Data Center、および Cloud (状況に応じる) - この記事はアトラシアンのサーバーおよびデータセンター プラットフォーム向けに記載されていますが、Atlassian Cloud のお客様も記事の内容を利用できる可能性があります。この記事で説明されている手順の実施が役立つと考えられる場合、アトラシアン サポートにお問い合わせのうえ、この記事を紹介してください。

tip/resting Created with Sketch.

Do note that Atlassian do not support customization as described on the documentation as outlined in our Atlassian Support Offerings. Please only try if you are confident on doing so and we strongly encourage customers to perform the check on test environment first before applying to production.

問題

The below message appears at atlassian-jira.log. The message you are seeing comes from AbstractMessageHandler in the jira-mail-plugin. In case if JIRA receives an email from another JIRA instance.  It means JIRA sends X-JIRA-FingerPrint included in the mail header.

 Received message with another JIRA instance's fingerprint

原因

This feature is to detect loop and avoiding it.

See the Email class:

 public class Email extends com.atlassian.mail.Email
{
    /**
     * JIRA's custom mail header used to contain a magic fingerprint string "unique" to a JIRA instance, used for
     * identification purposes.
     */
    public static final String HEADER_JIRA_FINGER_PRINT = "X-JIRA-FingerPrint";


Here is where the message comes from:

if (!fingerPrintHeaders.isEmpty())
        {
...
            if (fingerPrintHeaders.contains(instanceFingerPrint))
            {
...
            else
            {
                log.info("Received message with another JIRA instance's fingerprint");
            }
        }


回避策

tip/resting Created with Sketch.

Do note that Atlassian do not support customization as described on the documentation as outlined in our Atlassian Support Offerings. Please only try if you are confident on doing so and we strongly encourage customers to perform the check on test environment first before applying to production.

  • If willing to create issue when another JIRA send to another JIRA's mailbox, it can't be achieved by JIRA's default setting.

  • Workaround is to modify the code which removes your instance from Atlassian Support Offerings.
  • If this issue is critical for your operations, a feature request ticket has been created at JRA-44107 - Getting issue details... STATUS . We would like to encourage you to cast a vote on that issue and share your use-case within the comments, as that has way more impact on our product development than most other efforts. Also add it to your watch list to get notified once it is implemented in a future version.

最終更新日 2018 年 11 月 14 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.