Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

OutOfMemoryError: unable to create new native thread

Felix Will
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 31, 2020

Hey,

I started setting up a new jira server on a new virtual server.

After trying multiple times (even resetting the virtual server to make sure no "old" failed attempt generated more issues", I'll always end up with the same "OutOfMemoryError: unable to create new native thread" error. 

Specs:

- 16gb of Ram

- Ubuntu 18.04.4 LTS 

- OpenJDK v11.0.6 64-bit

Steps already taken:

- Allocated more memory in the setenv.sh (various tries with up to 10gb)

- Added "-Datlassian.plugins.enable.wait=300" to the jvm args (since it was mostly running into the issue in the plugins stage)

- Set the UserTasksMax=51200 in the /systemd/logind.conf

Log:

java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:717) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:957) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1367) at java.util.concurrent.Executors$DelegatedExecutorService.execute(Executors.java:668) at com.atlassian.jira.startup.JiraStartupLogger.printStartedMessage(JiraStartupLogger.java:197) at com.atlassian.jira.upgrade.ConsistencyCheckerImpl.printJIRAStartupMessage(ConsistencyCheckerImpl.java:200) at com.atlassian.jira.upgrade.ConsistencyCheckerImpl.initialise(ConsistencyCheckerImpl.java:184) at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:166) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:146) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:301) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:196) at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:137) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:104) at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31) at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102) at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154) at java.lang.Thread.run(Thread.java:748)

1 answer

0 votes
Joshua Rammacher
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 15, 2020

Hey Felix,

 

have you solved your Problem yet? Sadly we have exactly the same Problem.

 

Regards,

Joshua

Felix Will
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 23, 2020

Hey Joshua.

 

I am sorry to inform you but I gave up after trying it out a bit longer...

I switched my virtual server to CentOs (the only other choice I had) and since then it is running without an issue. It seems to be that for what ever reason Jira and Confluence don't like Ubuntu. If it is only an issue with Ubuntu 18.04.4 LTS oder any Ubuntu Version I can not say since I never had the possibility to test out another Ubuntu Version.

I didn't like the idea to change to CentOs (since I have been on Ubuntu forever) but it was at some point the better solution in terms of ROTI.... 

 

Best regards,

Felix

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.8.0
TAGS
AUG Leaders

Atlassian Community Events