Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Out of Memory on Confluence 7.1 startup after installation

We installed Confluence 7.1 on our server with Ubuntu 18.04 - with PostgreSQL. We are using the Tomcat and JRE shipped with the binary installation package.

After successfully stepping through the Setup-Wizard by browser we tried to access our fresh install but we received an error. So we restartet the service and get this Exception each time:

2019-11-20 13:32:55,098 ERROR [Catalina-utility-1] [atlassian.confluence.event.ConfluenceEventDispatcher] run There was an exception thrown trying to dispatch event [] from the invoker [SingleParameterMethodListenerInvoker{method=public void com.atlassian.sal.confluence.lifecycle.TenantAwareLifecycleManager.onPluginFrameworkStarted(, listener=com.atlassian.sal.confluence.lifecycle.TenantAwareLifecycleManager$$EnhancerBySpringCGLIB$$4970f72c@5e04b198} (timed)]
java.lang.RuntimeException: unable to create new native thread. Listener: com.atlassian.sal.confluence.lifecycle.TenantAwareLifecycleManager$$EnhancerBySpringCGLIB$$4970f72c event:
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(
at com.atlassian.confluence.event.ConfluenceListenerHandlersConfiguration$TimedListenerInvoker.invoke(
at com.atlassian.confluence.event.ConfluenceEventDispatcher$VCacheRequestContextRunnableFactory$1.lambda$run$0(
at com.atlassian.confluence.vcache.VCacheRequestContextOperations.lambda$doInRequestContext$0(
at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContextInternal(
at com.atlassian.confluence.impl.vcache.VCacheRequestContextManager.doInRequestContext(
at com.atlassian.confluence.vcache.VCacheRequestContextOperations.doInRequestContext(
at com.atlassian.confluence.event.ConfluenceEventDispatcher$VCacheRequestContextRunnableFactory$
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(
at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(
at com.atlassian.event.internal.EventPublisherImpl.publish(
at com.atlassian.confluence.event.TimingEventPublisher.publish(
at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(
at com.atlassian.plugin.manager.DefaultPluginManager.broadcastIgnoreError(
at com.atlassian.plugin.manager.DefaultPluginManager.lambda$lateStartup$4(
at com.atlassian.plugin.manager.PluginTransactionContext.wrap(
at com.atlassian.plugin.manager.DefaultPluginManager.lateStartup(
at com.atlassian.confluence.plugin.ConfluencePluginManager.lateStartup(
at com.atlassian.confluence.plugin.PluginFrameworkContextListener.contextInitialized(
at org.apache.catalina.core.StandardContext.listenerStart(
at org.apache.catalina.core.StandardContext.startInternal(
at org.apache.catalina.util.LifecycleBase.start(
at org.apache.catalina.core.ContainerBase$
at org.apache.catalina.core.ContainerBase$
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
at java.util.concurrent.ScheduledThreadPoolExecutor$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
at org.apache.tomcat.util.threads.TaskThread$
Caused by: java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(
at java.util.concurrent.ThreadPoolExecutor.addWorker(
at java.util.concurrent.ThreadPoolExecutor.execute(
at java.util.concurrent.AbstractExecutorService.submit(
at com.atlassian.sal.confluence.lifecycle.ForkAndJoinExecutionStrategy.trigger(
at com.atlassian.sal.confluence.lifecycle.ServiceExecutionStrategyComposite.trigger(
at com.atlassian.sal.confluence.lifecycle.TenantAwareLifecycleManager$
at java.util.concurrent.Executors$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$


We've already adjusted JVM Settings in the but it still seems to produce errors. This is the excerpt form the atlassian-confluece.log where the configuration of the JVM is printed:


JVM Stats
xmx = 4294967296
usedNonHeap = 367299632
availableHeap = 3357571600
availableNonHeap = -1
allocatedHeap = 2147483648
freeAllocatedHeap = 1210087952
maxNonHeap = -1
availablePermGen = 0
maxPermGen = -1
maxHeap = 4294967296
usedHeap = 937395696
usedPermGen = -1
xms = 2147483648

We've also added this commands to the top of

ulimit -u 4096
ulimit -n 4096


Any ideas how to solve this issue?

Best regards

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

221 views 7 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you