Results 1 to 6 of 6

Thread: the server offen crashs

  1. #1
    Join Date
    Nov 2011
    Posts
    3

    Default the server offen crashs

    hi, i have a server that the version is 2.2.4, i usually push one live streaming to server,
    but it always crashs after some durations ,example one day.
    the server is breaking with error message :
    java.lang.OutOfMemoryError: Java heap space
    at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:57)
    at java.nio.ByteBuffer.allocate(ByteBuffer.java:331)
    at org.apache.mina.common.SimpleByteBufferAllocator.allocate(Unknown Source)
    at org.apache.mina.common.ByteBuffer.allocate(Unknown Source)
    at org.apache.mina.transport.socket.nio.SocketIoProcessor.read(Unknown Source)
    at org.apache.mina.transport.socket.nio.SocketIoProcessor.process(Unknown Source)
    at org.apache.mina.transport.socket.nio.SocketIoProcessor.access$600(Unknown Source)
    at org.apache.mina.transport.socket.nio.SocketIoProcessor$Worker.run(Unknown Source)
    at org.apache.mina.util.NamePreservingRunnable.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:722)

    and my setenv.sh is as follows

    #!/bin/sh
    _EXECJAVA=java
    JAVA_OPTS="-Xmx2200M"
    # Uncomment to run server environment (faster), Note: will only work if server VM install, comes with JDL
    JAVA_OPTS="$JAVA_OPTS -server"
    # Can be a better GC setting to avoid long pauses
    #JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+UseParNewGC"
    # Uncomment to fix multicast crosstalk problem when streams share multicast port
    JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true"
    WMSAPP_HOME=/usr/local/WowzaMediaServer
    WMSCONFIG_HOME=/usr/local/WowzaMediaServer
    WMSCONFIG_URL=
    export WMSAPP_HOME WMSCONFIG_HOME JAVA_OPTS _EXECJAVA

    can someone help me, thanks a lot!

  2. #2

    Default

    Try setting JAVA_OPTS="-Xmx1800M".

  3. #3
    Join Date
    Nov 2011
    Posts
    3

    Default

    thanks randall, I will try it

    i forget to say the configuration of my host
    MEMORYDR 4G
    CPU:Intel E4400
    System:CentOS 6.0
    Kernel: 2.6.32-71.el6.x86_64

  4. #4

    Default

    Can you post the initial log or console output when you start Wowza? Post from the beginning up to where it says "Wowza Media Server is started".

  5. #5
    Join Date
    Nov 2011
    Posts
    3

    Default

    [root@localhost bin]# ./startup.sh
    [INFO ][mgmnt ] Local JMX connector started
    Configure logging: file:///usr/local/WowzaMediaServer/conf/log4j.properties
    INFO server server-start Wowza Media Server 2 Perpetual 2.2.4 build27452 -
    INFO server comment - Serial number: XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
    INFO server comment - Maximum connections: Unlimited
    INFO server comment - Hardware Available Processors: 2
    INFO server comment - Hardware Physical Memory: 2696MB/3009MB
    INFO server comment - Hardware Swap Space: 5071MB/5071MB
    INFO server comment - Max File Descriptor Count: 20000
    INFO server comment - Open File Descriptor Count: 44
    INFO server comment - OS Name: Linux
    INFO server comment - OS Version: 2.6.32-71.el6.x86_64
    INFO server comment - OS Architecture: amd64
    INFO server comment - Java Name: Oracle JRockit(R)
    INFO server comment - Java Vendor: Oracle Corporation
    INFO server comment - Java Version: 1.6.0_29
    INFO server comment - Java VM Version: R28.1.5-20-146757-1.6.0_29-20111004-1750-linux-x86_64
    INFO server comment - Java Spec Version: 1.6
    INFO server comment - Java Home: /root/jrockit-jdk1.6.0_29-R28.1.5-4.0.1/jre
    INFO server comment - Java Max Heap Size: 2200MB
    INFO server comment - Java Architecture: 64
    INFO server comment - Java Encoding[file.encoding]: UTF-8
    INFO server comment - Java Args[0]: -Xmx2200M
    INFO server comment - Java Args[1]: -server
    INFO server comment - Java Args[2]: -Djava.net.preferIPv4Stack=true
    INFO server comment - Java Args[3]: -Dcom.sun.management.jmxremote=true
    INFO server comment - Java Args[4]: -Dcom.wowza.wms.AppHome=/usr/local/WowzaMediaServer
    INFO server comment - Java Args[5]: -Dcom.wowza.wms.ConfigURL=
    INFO server comment - Java Args[6]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaMediaServer
    INFO server comment - Java Args[7]: -Dsun.java.launcher=SUN_STANDARD
    INFO server comment - Java GC[0]: Garbage collection optimized for throughput Young Collector
    INFO server comment - Java GC[1]: Garbage collection optimized for throughput Old Collector
    INFO server comment - Server threads[h/t]: 10/10
    INFO server comment - CMDInterface now listening: [any]:8083
    INFO vhost vhost-start _defaultVHost_ -
    INFO server comment - _defaultVHost_ threads[h/t]:120/80 home:/usr/local/WowzaMediaServer
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:1935:4)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
    INFO vhost comment _defaultVHost_ Bind attempt ([any]:8086:1)
    INFO vhost comment _defaultVHost_ Bind successful ([any]:8086)
    INFO server comment - Wowza Media Server is started!

  6. #6

    Default

    Thanks. I wanted to see that you are running the 64-bit Java VM, which you are.

    It is critical that you upgrade to JDK 1.7. Try that step first.

    What is your server load? How many connections? If you have a lot, you could just be running out of memory. Increase the Java heap size to 3000.

    If these steps don't help, implement the Garbage Collection fixes mentioned in step 6(a) and 6(b), of the tuning guide. Try the first one and see if that helps. If not, try the second one.

Posting Permissions

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