The maximum number of processes for the user account running is currently , which can cause performance issues. We recommend increasing this to at least 4096.

[root@localhost ~]# vi /etc/security/limits.conf

# /etc/security/limits.conf

#

#Each line describes a limit for a user in the form:

#

#<domain> <type> <item> <value>

#

#Where:

#<domain> can be:

# - a user name

# - a group name, with @group syntax

# - the wildcard *, for default entry

# - the wildcard %, can be also used with %group syntax,

# for maxlogin limit

#

#<type> can have the two values:

# - "soft" for enforcing the soft limits

# - "hard" for enforcing hard limits

#

#<item> can be one of the following:

# - core - limits the core file size (KB)

# - data - max data size (KB)

# - fsize - maximum filesize (KB)

# - memlock - max locked-in-memory address space (KB)

# - nofile - max number of open file descriptors

# - rss - max resident set size (KB)

# - stack - max stack size (KB)

# - cpu - max CPU time (MIN)

# - nproc - max number of processes

# - as - address space limit (KB)

# - maxlogins - max number of logins for this user

# - maxsyslogins - max number of logins on the system

# - priority - the priority to run user process with

# - locks - max number of file locks the user can hold

# - sigpending - max number of pending signals

# - msgqueue - max memory used by POSIX message queues (bytes)

# - nice - max nice priority allowed to raise to values: [-20, 19]

# - rtprio - max realtime priority

#

#<domain> <type> <item> <value>

#

#* soft core 0

#* hard rss 10000

#@student hard nproc 20

#@faculty soft nproc 20

#@faculty hard nproc 50

#ftp hard nproc 0

#@student - maxlogins 4

# Add by Weiru.Quan on 2018-01-01.

jira soft nofile 4096

jira hard nofile 8192

jira soft nproc 4096

jira hard nproc 8192

"/etc/security/limits.conf" 56L, 1979C written

# ========================================================================================

Health Check: Thread Limit

Related content

• Performance Troubleshooting Tools - Best Practice
• Testing disk access speed for a Java application
• Application Links Troubleshooting Guide
• Database Troubleshooting and How-to Guides
• Troubleshooting slow MySQL performance
• Enabling MySQL slow query logs

This Knowledge Base article was written specifically for the Atlassian Server platform. Due to the Restricted functions in Atlassian Cloud apps, the contents of this article cannot be applied to Atlassian Cloud applications.

About the Health Check

This health check looks at the maximum number of processes (threads) the user account running JIRA or Confluence can run at the same time.  The maximum processes is defined by the operating system, and often defaults to 1024 which is too low for Atlassian applications running at scale. If it is too low you may experience performance issues and out of memory errors such as Confluence crashes and throws 'OutOfMemory: unable to create new native thread' error.

Understanding the Results

Icon

Result

What this means

The number of processes for the user account running <Application> is sufficient.  The recommended maximum processes is 4096.

The Health Check has passed and the user running JIRA or Confluence can create an appropriate number of threads.

The maximum number of processes for the user account running <Application> is currently <number>, which can cause performance issues. We recommend increasing this to at least 4096.

The health check has failed. The user running JIRA or Confluence cannot create an appropriate number of threads which can can cause performance issues that are hard to detect, and ultimately crash the application with an OutOfMemoryError.

We couldn't determine the maximum number of processes for the user account running <Application>. We recommend this be set to at least 4096.

The health check was not able to determine the maximum number of processes. If you are experiencing out of behaviour as described in Confluence crashes and throws 'OutOfMemory: unable to create new native thread' error you should manually check this maximum is adequate.

Resolution

We recommend setting the maximum running user processes and number of opened files permanently, the way you do this is operating system specific.

In most Linux distributions this can be set temporarily using ulimit or permanently using limits.conf(e.g. Ubuntu, RedHat) by adding the following:

confluence soft nofile 4096
confluence hard nofile 8192
confluence soft nproc 4096
confluence hard nproc 8192

Replace confluence with the user that runs your instance of JIRA or Confluence.

Last modified on Mar 2, 2017