Results 1 to 4 of 4

Thread: java.lang.OutOfMemoryError error on 32GB system

  1. #1

    Default java.lang.OutOfMemoryError error on 32GB system


    One of our customer use wowza server that has 32GB RAM and 24 core processor. They have 600 live channels on this machine - each channel consisting of 5 different bitrate streams (max 512 kbps). So in all 3000 streams published to wowza.

    During popular events, they get around 50000 hits per hour. The CPU utilized is around 55%-60% at this load. However the wowza system crashes in some time and gives the outofmemory error as follows:

    java.lang.OutOfMemoryError: unable to create new native thread
    at java.lang.Thread.start0(Native Method)
    at java.lang.Thread.start(
    at org.apache.mina.util.NewThreadExecutor.execute(
    at org.apache.mina.transport.socket.nio.SocketIoProcessor.startupWorker(
    at org.apache.mina.transport.socket.nio.SocketIoProcessor.addNew(
    at org.apache.mina.transport.socket.nio.SocketAcceptor$Worker.processSessions(
    at org.apache.mina.transport.socket.nio.SocketAcceptor$
    They use latest wowza 3.6.3 version. Heap memory allocated to wowza server is 28 GB. All other options are default settings.

    Are they publishing too many streams to wowza? What is the upper limit considering the above machine? Should the heap memory allocated be further increased? Or could the system be running out of threads? Number of open files limit (as shown by ulimit -a) is set at 32000.

    Please help out urgently as there's an event tomorrow.


  2. #2
    Join Date
    May 2013


    What are your garbage collection settings on the system? As far as published streams, our general recommendation is no more than ~250 published streams. If you are doing hls you are likely losing a lot to the packetization process.

  3. #3


    We are using the default file. So haven't tinkered with GC settings. Do we have to change any of the GC settings? We dont know much about GC and we read in wowza tuning guide that its best to let the GC settings unchanged.

    We are not using packetization. We have turned off all http packetizers.

  4. #4
    Join Date
    May 2013


    Restart your Wowza instance and then zip up your [install-dir]/logs and [install-dir]/conf directories and send it to Include a reference link to this post.

Similar Threads

  1. Unexpected exception.: java.lang.OutOfMemoryError: Java heap space
    By sriv.mayank in forum Performance and Tuning
    Replies: 1
    Last Post: 03-26-2014, 02:40 PM
  2. Error: java.lang.OutOfMemoryError: Java heap space
    By Denis_Ukraine in forum Server Administration Discussion
    Replies: 5
    Last Post: 05-20-2013, 03:32 PM
  3. Wowza failed after 10 days - java.lang.OutOfMemoryError: Java heap space
    By tribalhost in forum Performance Tuning Discussion
    Replies: 5
    Last Post: 04-10-2013, 06:30 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts