Jira Core 8.0.x upgrade notes

Here are some important notes on upgrading to Jira Core 8.0.

For details on the new features and improvements in this release, see the Jira Core 8.0.x release notes


Apache Tomcat 8.5.35

We've upgraded Apache Tomcat to 8.5.35 in Jira 8.0.2.


Jira 8.0 で導入される変更の 1 つは、Jira のインデックスを担う Lucene ライブラリのアップグレードです。この変更によってインデックス作成 (検索) が改善されますが、ご利用の現在のインデックスには新しいバージョンとの互換性がありません。ただし、通常のアップグレードの完了後に "Jira の再インデックス" によってインデックス全体の再構築を行うことができるため、一般にこれが問題になることはありません。インデックスの再作成後は、インデックスが以降のバージョンとの互換性を持つようになります。


現在のインデックスは <home-directory>/caches/indexes に保持されます (アップグレード後に削除してもかまいません) 。今後、新しいインデックスは以下のディレクトリに格納されます。


The new index will trigger an automatic reindex in Jira just after the upgrade (more precisely, when you start Jira). Because of that, there’s a great chance you’ll reindex twice - after starting Jira and after making some changes that require reindexing, for example, upgrading plugins. Reindexing might be really time consuming in large Jira instances, that’s why we’re recommending that you disable the automatic reindex and run it manually later, when you’re ready.


We’ve included steps needed to disable the automatic reindex in our upgrade procedures. If you’re looking for a quick answer, though, you’ll need to add the following line to the <home-directory>/jira-config.properties file before you start Jira after the upgrade.


(tick) インデックスが 2 回作成されるのを防ぐために自動再インデックスを無効化し、準備が整ったら手動で再インデックスを実行します。

(info) Jira インスタンスが小規模で、追加の再インデックスで問題が発生しないようであれば、無効化する必要はありません。これは時間を短縮するための方法であるため、いずれの手順を利用した場合もアップグレードへの影響はありません。

互換性のないアプリ (アドオン) の無効化

Jira 8.0 と互換性のないアプリを無効化したり、利用可能な場合は互換性があるバージョンにアップグレードしたりする必要があります。互換性のないアプリは、Jira インデックス、API、一部の UI など、利用できなくなった要素や新しいバージョンで変更された要素を使用しているため、Jira のアップグレードや起動を妨げる可能性があります。


(tick) Disable all incompatible apps, or upgrade them if they have compatible versions. For more info on what you should do, see  Preparing for the upgrade.

(info) We always recommend that you test the upgrade in a test environment. Once you upgrade the test environment to Jira 8.0, you can try enabling the incompatible apps and see how they behave with the new version. If they don't affect your Jira instance in a significant way, you can use them with 8.0 even if they haven't been declared as compatible yet.

アップグレード後、Jira の起動に時間がかかる場合があります

One of the improvements we’re shipping in Jira 8.0 is the addition of new indexes to two of the most heavily used database tables (changeitemchangegroup). Thanks to that, issues will load faster, and so will queries executed against the database to retrieve the data that issues contain.

Adding indexes to these tables can take several minutes, and will take place when you start Jira after the upgrade. Learn more

Changes to several configuration properties

In Jira 8.0, we’ve changed default values for some of the properties related to indexing, and also made several properties obsolete. 

Obsolete properties:

  • jira.index.commitpolicy
  • jira.index.batch.maxbuffereddocs
  • jira.index.interactive.maxbuffereddocs
  • jira.index.batch.maxmergedocs
  • jira.index.interactive.maxmergedocs
  • jira.index.batch.mergefactor
  • jira.index.interactive.mergefactor

Properties that have new default values:

  • jira.index.issue.threads (20)
  • jira.index.batch.maxrambuffermb (1024)
  • jira.index.interactive.maxrambuffermb (1024)

You can always view the jpm.xml file to see all supported properties, and their current values.

The maxrambuffermb properties define the maximum size of a memory write buffer for Lucene documents queued to be saved into the index files. We’ve increased it to better handle issues with large number of custom fields. Because of this change, we’ve also increased the default maximum heap size (xmx), as described below.


Because of the increase in maxrambuffermb, we’ve also increased the default maximum heap size (xmx).

プロパティ Jira 7.x Jira 8.0
Xmx 768 2048


100 1024


16 1024

Jira 8.0 should require less memory, however we still need the xmx value to be higher than maxrambuffermb. If you already had xmx set to 2GB, you shouldn’t need to increase this value. 

If you’re running Jira on a 32-bit system, the 2GB heap size will be too high, and you’ll need to decrease it, as described below.

Decreasing heap size for Jira on 32-bit systems

This applies only if you’re installing/upgrading Jira manually by using the archive. Installers will do it for you.

If you’re installing/upgrading Jira on a 32-bit system, you need to decrease the maximum heap size available to Jira. The default for 64-bit systems in Jira 8.0 is 2GB, which is too much for a 32-bit system, and may not fit into the available memory. We’ve created a new setenv32.bat/.sh file that has all the right settings, you just need to put it in the right place.

Tell me how to do this...

Complete these steps after extracting files from the archive, but before starting Jira:

ステップ 1: 既定の setenv ファイルの名前を変更します。

  1. Go to <Jira-install-directory>/bin, and delete the setenv.bat / .sh file (or change its name).

  2. Rename setenv32.bat / .sh to setenv.bat / .sh. Jira will use this file on startup.

Step 2: Add the properties to the jira-config.properties file.

  1. Go to Jira’s home directory, and edit the jira-config.properties file. If the file isn’t there, you can create it.

  2. 次のプロパティを追加します: 


Plugin 1 タイプ アプリのインストール ディレクトリ

Make sure that your P1 apps are installed in <Jira-install-dir>/atlassian-Jira/WEB-INF/lib. If you install these apps along with regular apps from Atlassian Marketplace in <jira-home-dir>/plugins/installed-plugins, they won’t work in Jira 8.0. For more information, see Installing Marketplace apps.

MySQL 5.7 の新しい設定

We've added new configuration steps for MySQL 5.7 to let you use 4-byte characters in Jira. Your old configuration will still work, but you won't be able to use 4-byte characters. For more info, see Connecting to MySQL 5.7.

catalina.out ファイルへのログ作成を削減

Jira applications used to mirror the application log output (atlassian-jira.log) in the Tomcat log file, catalina.out. Since the catalina.out file couldn’t be rotated by Jira using the Log4j configuration (like it happens with the application log), the file grew significantly and didn’t really contain any unique or useful events from Jira. Jira admins could work around this issue by using log-rotation scripts at the OS level, but that complicated the setup.

To fix this issue, we’ve removed mirroring the log output to catalina.out  (process Stdout), leaving only the following basic events that are useful for our Support teams:


We’ll keep logging all events into the atlassian-jira.log file, like it was before. Also, we’ve increased the number of atlassian-jira.log rotated files from 5 to 10.

Apache Tomcat のアップグレード

Apache Tomcat を 8.5.32 バージョンにアップグレードしました。これにより、server.xml ファイルへの変更が必要です。


Apache Tomcat サーバーは特殊文字が含まれるリクエストをフィルタリングするため、このようなリクエストが失敗します。これは、Tomcat がほとんどのブラウザとは異なるエンコーディングおよび URI 標準を採用しているためです (詳細はこちら)。この問題は、多くの特殊文字 ([]<> など) を使用する JQL 検索でもっともよく見られますが、Jira の他のページにも影響を与える可能性があります。 

Versions affected

We've made this change in Jira 7.12.2. If you're upgrading from this version or any later, you should've already done these steps.


この問題を解決するには、server.xml ファイルを編集し、リクエスト内の特殊文字を Tomcat が許可するようにするプロパティを追加します。

  1. <Jira-installation-directory>/conf に移動し、server.xml ファイルを編集します。
  2. Find all connectors your application is using. Just search for Connector in the file, or look at the example below.
  3. Add  relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"  to the connector properties in server.xml. For example:

    <Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true" bindOnInit="false"/>
  4. Jira を再起動します。
  5. (Data Center) 各ノードで以上のステップを繰り返します。


Starting from Jira 8.0, we're ending support for the following databases:

  • PostgreSQL 9.3
  • MySQL 5.5

For more info, see End of support announcements.


See Preparing for Jira 8.0 for any important changes regarding plugins.


See  Upgrading Jira applications  for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps that are required for Jira 8.0.

最終更新日 2019 年 3 月 6 日


Powered by Confluence and Scroll Viewport.