Linux -Dcom.sun.management.jmxremote=true error

Wowza Streaming Engine
1

Hello all:

I’ve just installed an upgraded jdk/jre and Wowza 1.3.3 on Linux 2.6.9-5.EL

After combing through the docs I’ve managed to install the jre in the proper location /user/java/jdk1.6.0_04 and set the class path by adding a custom file in /etc/profile.d. When I execute java -version I get 'java version “1.6.0_04”

When I cd to the wowazapro bin directory and execute ./startup.sh, I get the following error:

line 24: -Dcom.sun.management.jmxremote=true: command not found

I simply wish to get the server up and runnng for demo purposes.

I’ve attached the setenv.sh and the startup.sh files. Is there something I need to edit for these?

Any help is most appreciated.

thanks :cool:

Ken

startup.sh

#!/bin/sh

/usr/local/WowzaMediaServerPro-1.3.3/bin/setenv.sh

#chmod 600 jmxremote.password

#chmod 600 jmxremote.access

NOTE: Here you can configure the JVM’s built in JMX interface.

See the “Server Management Console and Monitoring” chapter

of the “User’s Guide” for more information on how to configure the

remote JMX interface in the [install-dir]/conf/Server.xml file.

JMXOPTIONS=-Dcom.sun.management.jmxremote=true

#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.port=1099"

#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.authenticate=true"

#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.ssl=false"

#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.password.file=$WMSCONFIG_HOME/conf/jmxremote.password"

#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.access.file=$WMSCONFIG_HOME/conf/jmxremote.access"

#JMXOPTIONS="$JMXOPTIONS -Djava.rmi.server.hostname=192.168.1.7"

#ulimit -n 20000

log interceptor com.wowza.wms.logging.LogNotify - see Javadocs for ILogNotify

$_EXECJAVA $JAVA_OPTS $JMXOPTIONS -Dcom.wowza.wms.AppHome="$WMSAPP_HOME" -Dcom.wowza.wms.ConfigURL="$WMSCONFIG_URL" -Dcom.wowza.wms.ConfigHome="$WMSCONFIG_HOME" -cp $WMSAPP_HOME/bin/wms-bootstrap.jar com.wowza.wms.bootstrap.Bootstrap start

=============================================

setenv.sh

#!/bin/sh

_EXECJAVA=java

JAVA_OPTS="-Xmx768M"

WMSAPP_HOME=/usr/local/WowzaMediaServerPro

WMSCONFIG_HOME=/usr/local/WowzaMediaServerPro

WMSCONFIG_URL=

export WMSAPP_HOME WMSCONFIG_HOME JAVA_OPTS _EXECJAVA

2

It looks like you modified the startup.sh script. I would revert back to the original script. I can see where the changes you made are not going to work. Here are the origin script contents:

startup.sh

#!/bin/sh
. ./setenv.sh
#chmod 600 jmxremote.password
#chmod 600 jmxremote.access
# NOTE: Here you can configure the JVM's built in JMX interface.
# See the "Server Management Console and Monitoring" chapter
# of the "User's Guide" for more information on how to configure the
# remote JMX interface in the [install-dir]/conf/Server.xml file.
JMXOPTIONS=-Dcom.sun.management.jmxremote=true
#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.port=1099"
#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.authenticate=true"
#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.ssl=false"
#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.password.file=$WMSCONFIG_HOME/conf/jmxremote.password"
#JMXOPTIONS="$JMXOPTIONS -Dcom.sun.management.jmxremote.access.file=$WMSCONFIG_HOME/conf/jmxremote.access"
#JMXOPTIONS="$JMXOPTIONS -Djava.rmi.server.hostname=192.168.1.7"
#ulimit -n 20000
# log interceptor com.wowza.wms.logging.LogNotify - see Javadocs for ILogNotify
$_EXECJAVA $JAVA_OPTS $JMXOPTIONS -Dcom.wowza.wms.AppHome="$WMSAPP_HOME" -Dcom.wowza.wms.ConfigURL="$WMSCONFIG_URL" -Dcom.wowza.wms.ConfigHome="$WMSCONFIG_HOME" -cp $WMSAPP_HOME/bin/wms-bootstrap.jar com.wowza.wms.bootstrap.Bootstrap start

setenv.sh

#!/bin/sh
_EXECJAVA=java
JAVA_OPTS="-Xmx768M"
WMSAPP_HOME=/usr/local/WowzaMediaServerPro
WMSCONFIG_HOME=/usr/local/WowzaMediaServerPro
WMSCONFIG_URL=
export WMSAPP_HOME WMSCONFIG_HOME JAVA_OPTS _EXECJAVA

Charlie

3

Although a lot of servers let you call startup.sh I needed to call ./startup.sh.

Wow, I’m going back to popcorn vending.

Don’t mean to offend any popcorn vendors out there!! :smiley:

Thanks

4

I don’t understand the comment? What is the problem? Since this folder is not part of the PATH environment variable, then you must specify it’s location. This is pretty common on Linux.

Charlie