It takes too long time to login to JIRA which is hosted on AWS

お困りですか?

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

コミュニティに質問

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

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

このページの内容はサポート対象外のプラットフォームに関連しています。したがって、アトラシアン サポートではこのページの記載内容のサポートの提供は保証されません。この資料は情報提供のみを目的として提供されています。内容はお客様自身の責任でご利用ください。

問題

It takes too long time to login to JIRA which is hosted on AWS in case source IPs which can access the port which JIRA is running on (default: 8080) are restricted with Security Group.

診断

Confirm if there is the public IP of the EC2 instance itself in the whitelist of the inbound access.
(We tend to forget to configure a rule about the public IP.)

You might also find the following timeout in atlassian-jira.log:

2016-08-24 07:03:49,420 http-nio-8080-exec-4 ERROR test 419x111x1 1kbh968 xxx.xxx.xxx.xxx / [c.a.g.r.internal.http.HttpClientFetcher] Unable to retrieve response
org.apache.http.conn.ConnectTimeoutException: Connect to 54.84.33.176:8080 [/54.84.33.176] failed: Connection timed out
           at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:149)
           at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
           at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
           at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
           at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
           at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
           at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
           at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
           at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
           at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
           at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
           at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher.fetch(HttpClientFetcher.java:85)
           at org.apache.shindig.gadgets.DefaultMessageBundleFactory.fetchBundle(DefaultMessageBundleFactory.java:138)
           at org.apache.shindig.gadgets.DefaultMessageBundleFactory.getNestedBundle(DefaultMessageBundleFactory.java:111)
           at org.apache.shindig.gadgets.DefaultMessageBundleFactory.getBundle(DefaultMessageBundleFactory.java:79)
           at org.apache.shindig.gadgets.DefaultMessageBundleFactory.getParentBundle(DefaultMessageBundleFactory.java:127)
           at org.apache.shindig.gadgets.DefaultMessageBundleFactory.getNestedBundle(DefaultMessageBundleFactory.java:101)
           at org.apache.shindig.gadgets.DefaultMessageBundleFactory.getBundle(DefaultMessageBundleFactory.java:79)
           at org.apache.shindig.gadgets.variables.VariableSubstituter.substitute(VariableSubstituter.java:47)
           at com.atlassian.gadgets.renderer.internal.GadgetSpecFactoryImpl.getGadgetSpec(GadgetSpecFactoryImpl.java:127)
           at com.atlassian.gadgets.renderer.internal.GadgetSpecFactoryImpl.getGadgetSpec(GadgetSpecFactoryImpl.java:79)
           ... 3 filtered


原因

Access to the port from the public IP of the EC2 instance itself is not allowed and it caused the timeout.

ソリューション

Allow the public IP to access the port which JIRA is running on.

Last modified on Mar 30, 2021

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

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