Jira Service Desk 4.11.x upgrade notes
Here are some important notes on upgrading to Jira Service Desk 4.11. For details on the new features and improvements in this release, see the Jira Service Desk 4.11.x release notes.
Summary of changes
Upgrade notes
Known issue: Too many warning messages about RequestCache in the log file
In Jira Service Desk 4.9.1, we introduced additional logging messages to track the use of RequestCache without the context. For some instances, this resulted in a huge number of warning messages in the log file, similar to the one below:
[c.a.j.cache.request.RequestCacheImpl] From Jira 9.0 version creation/usage of RequestCacheImpl will throw the IllegalStateException.If you’re having this problem, you can work around it by changing the logging for RequestCache to ERROR. At the same time, we’re working on a fix for this issue. You can read more about it here.
Changing the logging level for RequestCache
Temporary (will no longer work after restarting Jira)
- In Jira, go to Administration > System > Logging and profiling.
- Scroll down to Default Loggers > Configure logging level for another package.
- Add the com.atlassian.jira.cache.request.RequestCacheImpl package with the ERROR level.
Permanent
- Edit the
<JIRA_INSTALLATION>/atlassian-jira/WEB-INF/classes/log4j.propertiesfile. Add the following lines at the bottom of the file, and save it:
log4j.logger.com.atlassian.jira.cache.request.RequestCacheImpl = ERROR, filelog log4j.additivity.com.atlassian.jira.cache.request.RequestCacheImpl = false- Restart Jira.
Embedded Crowd upgrade
As you might have read in the release notes, we’ve upgraded Embedded Crowd in Jira from version 2.0 to 4.0. This upgrade doesn’t require any actions from you, and the user interface did not change in any way.
Here are some benefits of the new version:
- Performance improvements (improved sync times)
- Clustering support
- Improved directory failover
- A number of bugs fixed
Here’s a list of issues that were solved with the new version:
If you’re an app developer, we recommend that you look at Preparing for Jira 8.11, as this upgrade brings our changes in our APIs.
Apache Tomcat upgrade
We've upgraded Apache Tomcat from 8.5.50 to 8.5.56.
Fetching updates fixed for Jira
If you use Jira with other Atlassian products such as Bamboo, Bitbucket or Fisheye/Crucible, you might have experienced it getting stuck paging over issue updates. This happens when the collective number of results to fetch is bigger than 50. We have worked on a fix and have bundled it in this release, so Jira should update without further issues.
End of support announcements
In Jira Service Desk 4.11, we're making the following changes:
- Deprecating Hipchat
We've stopped supporting Hipchat and unbundled the Hipchat integration for Jira app.
For other announcements, see End of support announcements.
App developers
See Preparing for Jira 8.11 for any important changes regarding apps.
Upgrade procedure
See Upgrading Jira applications for complete upgrade procedures, including all available upgrade methods and pre-upgrade steps that are required for Jira Service Desk 4.11. For a more tailored upgrade, also check our Pre-upgrade planning tool that will recommend a version to upgrade to, run pre-upgrade checks, and provide you with a custom upgrade guide with step-by-step instructions.