Results 1 to 7 of 7

Thread: Help! RAM usage crippling the system and requiring reboot twice a day!

  1. #1
    Join Date
    Jan 2014
    Posts
    11

    Default Help! RAM usage crippling the system and requiring reboot twice a day!

    Over the last 3-4 days i have noticed Java using all available RAM, to the point of the system crashing. A system reboot fixes it. I have watched the RAM from a reboot and it starts off very low and escalates quickly.

    I get this error just before loss of video: Unexpected exception.: java.lang.OutOfMemoryError: Java heap space|

    I set the Heap size to 4Gb which is between development and production. It appears that the Wowza server completely ignores this heap size and allocates all RAM to it anyway. I have seen from the usage graph that after about an hour after reboot the heap and the memory are both clipping on the red line.

    The system is a 64-bit Win7 machine, with an i7 3.5Ghz processor and 8Gb of RAM. There are 6 incoming UDP streams of 1.8Mb per stream. Wowza software is 4.0.6.

    It is worth noting that we have a nearly identical system that is running the same script, same parameters, same load, but on an i3/4GB RAM machine (Wowza 4.1.0) and it barely breaks a sweat.

    There is something not right here. Could we be getting garbage video from the encoder in such a volume that the GC cant get rid of it? would there be other symptoms?

  2. #2
    Join Date
    Sep 2011
    Posts
    1,937

    Default

    Hi,
    Please create a ticket by sending an email to support@wowza.com.
    When creating a ticket please include a ZIP file containing the following directories:
    [Wowza-Install]/conf/
    [Wowza-Install]/logs/
    [Wowza-Install]/transcoder/
    [Wowza-Install]/manager/logs/

    Please make sure you provide logs which show Wowza server starting.

    If you are not sure how to get this information please see the following tutorial.
    How to create a compressed zip file in Windows, OS X, and Linux

    - If you have a live stream please outline the type of encoder in use along with the encoding settings for the stream.
    - If you are using a .stream file to start re-streaming please provide this.
    - If you have a on demand stream you may be asked to provide access to the content you are using for further testing. At this stage it is not required.
    - If you are using multiple bitrates (ABR) then please provide the SMIL file associated with your configuration.

    You can also configure Wowza to create a heap-dump when Wowza prints the OutOfMemoryError to the logs.
    To do this edit the [Wowza-Install]/conf/Tune.xml file changing the following line.

    From this:
    <!-- <VMOption>-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath="${com.wowza.wms.AppHome}/logs"</VMOption> -->

    To this:
    <VMOption>-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath="${com.wowza.wms.AppHome}/logs"</VMOption>

    After editing and saving this file, a restart of Wowza is required for the changes to take effect.
    Screenshots of the memory usage in WSEM will also be helpful.

    Regards,
    Jason

  3. #3
    Join Date
    Jan 2014
    Posts
    11

    Default

    thanks Jason, already done.

  4. #4
    Join Date
    Sep 2011
    Posts
    1,937

    Default

    Hi,
    This will now be handled in the ticket you created (116137).

    Regards,
    Jason

  5. #5

    Default

    What was the resolution to this issue?

    Also was the PushPublish module being used in this instance?

    Thanks

  6. #6
    Join Date
    Jan 2010
    Posts
    24

    Default Also interested

    Quote Originally Posted by mando222 View Post
    What was the resolution to this issue?

    Also was the PushPublish module being used in this instance?

    Thanks
    Also interested in the resolution. Going through same thing, and have a ticket raised.

  7. #7
    Join Date
    Jun 2011
    Posts
    1,035

    Default

    Hi
    The problem reported in the ticket above turned out to be an issue with a module that shouldn't have been in put in place.

    Additionally, custom modules can also be the cause of out of memory problems. Check to see what modules are in place, and test without them in place to prove
    whether or not there is an issue in the base case.

    Daren

Similar Threads

  1. Setting up the trial version in EC2 for live streaming. Requiring assitance
    By aman.alam in forum Wowza Streaming Engine in the Cloud
    Replies: 8
    Last Post: 09-30-2014, 01:54 PM
  2. Wowza don`t remove lock file on system reboot
    By churchonrock in forum Server Administration Discussion
    Replies: 7
    Last Post: 09-09-2013, 01:46 AM
  3. Concurrent live streaming limit - 2xE5645+16g ram vs 1xE3-1245+8g ram
    By braliao in forum Performance Tuning Discussion
    Replies: 5
    Last Post: 12-06-2011, 07:02 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
  •