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

**URL:** <https://community.wowza.com/t/linux-dcom-sun-management-jmxremote-true-error/294>\
**Category:** Wowza Streaming Engine\
**Created:** [February 14, 2008, 8:34am UTC](https://community.wowza.com/t/linux-dcom-sun-management-jmxremote-true-error/294 "2008-02-14T08:34:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/system/32/447_2.png) [@system](https://community.wowza.com/u/system)\
**Post date:** [February 14, 2008, 8:34am UTC](https://community.wowza.com/t/linux-dcom-sun-management-jmxremote-true-error/294/1 "2008-02-14T08:34:32Z")

</div>

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 🆒

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

---

<div class="post-metadata">

**Author:** ![Charlie\_Good](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/charlie_good/32/383_2.png) [@Charlie\_Good](https://community.wowza.com/u/Charlie_Good)\
**Post date:** [February 14, 2008, 4:28am UTC](https://community.wowza.com/t/linux-dcom-sun-management-jmxremote-true-error/294/2 "2008-02-14T04:28:27Z")

</div>

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

```auto
#!/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

```auto
#!/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

---

<div class="post-metadata">

**Author:** ![AAAA\_BBBBBBB](https://avatars.discourse-cdn.com/v4/letter/a/6bbea6/32.png) [@AAAA\_BBBBBBB](https://community.wowza.com/u/AAAA_BBBBBBB)\
**Post date:** [February 15, 2008, 12:44am UTC](https://community.wowza.com/t/linux-dcom-sun-management-jmxremote-true-error/294/3 "2008-02-15T00:44:06Z")

</div>

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!! 😃

Thanks

---

<div class="post-metadata">

**Author:** ![Charlie\_Good](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/charlie_good/32/383_2.png) [@Charlie\_Good](https://community.wowza.com/u/Charlie_Good)\
**Post date:** [February 14, 2008, 5:07pm UTC](https://community.wowza.com/t/linux-dcom-sun-management-jmxremote-true-error/294/4 "2008-02-14T17:07:36Z")

</div>

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