Version: Wowza Media Server 2.2.3 build26454

For the most up-to-date information, visit the support section of http://www.wowzamedia.com. To get started, read the online Quick Start Guide.

Release Notes

New Features In Wowza Media Server 2

New Features Introduced in Wowza Media Server 2.2.3

Note: For a complete list of changes see: Wowza Media Server 2.2.3 Release Notes

Comments or Issues

Wowza Media Server Tuning

For up to date tuning instructions, see the following forum thread:

General Tuning Instructions

Connecting over RTMPT or RTMPTE

The default Server.xml file is configured to listen on port 1935 only (the default rtmp port). To connect to the server over rtmpt you can either uncomment the port 80 configuration section in the [install-dir]/conf/VHost.xml file or connect over rtmpt using port 1935 (example: rtmpt://localhost:1935/applicationname).

Memory Settings

If you are running into OutOfMemory errors while running the server, you may want to increase the maximum size of the Java heap. Consult the General Tuning Instructions for more information.

JAVA_HOME environment variable on Windows platform

Wowza Media Server on the Windows platform uses the JAVA_HOME environment variable to determine the location of the Java environment under which to run. If you have problems starting Wowza Media Server on Windows, double check to be sure the JAVA_HOME variable is pointing to a Java 6 (aka 1.6) or greater Java environment. Also when making changes or upgrades to your Java environment that may affect the installation path, be sure to update the JAVA_HOME variable to point to the new location. The JAVA_HOME variable should point to the base folder of the Java installation. This is the folder that contains the bin folder.

Windows Service

By default Wowza Media Server Windows service is set to Manual startup. This is so it does not conflict with the version started from the command prompt. Consult the Starting and Stopping the Server section of the User's Guide for more information on how to change this to Automatic startup.

OS X Service

By default the com.wowza.WowzaMediaServer OS X service is set to Disabled startup. This is so it does not conflict with the version started from the command prompt. To enable the launchd service to startup automatically when the machine is restarted issue the following command in a terminal window:

sudo launchctl load -w /Library/LaunchDaemons/com.wowza.WowzaMediaServer.plist

To disable:

sudo launchctl unload -w /Library/LaunchDaemons/com.wowza.WowzaMediaServer.plist

JMX and the Windows Service

When running Wowza Media Server as a Windows service, the JMX interface will not be available unless the service is running as a named user. To configure the service to run as a named user, go to Settings>Control Panel>Administrative Tools>Services and right click on the Wowza Media Server service and select Properties. Next, click on the Log On tab, change the Log on as radio to This account and enter a user name and password for a local user.

Debug Logging

To turn on Wowza Media Server debug logging, edit the [install-dir]/conf/log4j.properties file and change the log level on the first line from INFO to DEBUG.

Relocating Wowza Media Server

The Mac OS X and Linux installers do not provide an option to choose the location of the installation of the base server files. For Mac OS X this location is /Library/WowzaMediaServer-[version] and for Linux it's /usr/local/WowzaMediaServer-[version]. All the server startup scripts locate the server files through a symbolic link named /Library/WowzaMediaServer (Mac OS X) and /usr/local/WowzaMediaServer (Linux). If you wish to relocate the base server files you can move them where you choose and update this link using the ln -sf command.