Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1181318

Summary: Unable to bind to a specific JMX host
Product: [JBoss] JBoss Enterprise Web Server 2 Reporter: Eric Rich <erich>
Component: tomcat7Assignee: Coty Sutherland <csutherl>
Status: CLOSED CURRENTRELEASE QA Contact: Michal Karm Babacek <mbabacek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.1.0CC: dereed, jclere, jdoyle, lfuka, pslavice, rsvoboda, sgehwolf
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1183014 (view as bug list) Environment:
Last Closed: 2017-08-09 15:03:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1183014    

Description Eric Rich 2015-01-12 21:04:30 UTC 
Description of problem:

Using the following I am unable to set a JMX host. 

export CATALINA_OPTS="${CATALINA_OPTS} -Dcom.sun.management.jmxremote.host=127.0.0.1"
export CATALINA_OPTS="${CATALINA_OPTS} -Dcom.sun.management.jmxremote.port=9111"
export CATALINA_OPTS="${CATALINA_OPTS} -Dcom.sun.management.jmxremote.authenticate=false"
export CATALINA_OPTS="${CATALINA_OPTS} -Dcom.sun.management.jmxremote.ssl=false"

Version-Release number of selected component (if applicable): 2.x

How reproducible: Very

Steps to Reproduce:
1. Export varables above (note you may want to try setting JAVA_OPTS and not CATALINA_OPTS however both (in my testing) render the same results. 
2. Start Tomcat
3. netstat -tunap | grep :9111 

Actual results:

Tomcat is bound to 0.0.0.0:9111 and not 127.0.0.1:9991

Expected results:

Tomcat should be bound 127.0.0.1:9991

Additional info:

http://mail-archives.apache.org/mod_mbox/cassandra-user/201108.mbox/%3C4E40B802.2060500@wetafx.co.nz%3E
Comment 1 dereed 2015-01-16 00:27:51 UTC 
"com.sun.management.jmxremote.host" does not exist.

The JDK does not provide a way to set the host when using com.sun.management.jmxremote properties.
It can only be done when creating the JMX connector programatically.

Also, this is a JDK configuration, not related to EWS.
Comment 6 Coty Sutherland 2017-08-09 15:03:04 UTC 
Since the JDK issue was resolved this works fine in JWS 3.x.