in standalone.xml, depending on which interfaces you have set up in your interfaces section, try setting up these socket bindings
<socket-binding name="jmx-connector-registry" interface="management" port="1090"/>
<socket-binding name="jmx-connector-server" interface="management" port="1091"/>
to bind to an externally accessible interface
1 of 1 people found this helpful
The only way I found to connect a jconsole to my JBoss AS 7 on EC2 to pass through a SOCKS proxy.
To start the proxy client :
ssh -vfND 6666 -i .amazon/aws1-sewatech-net.pem firstname.lastname@example.org
To launch jconsole :
jconsole -J-DsocksProxyHost=localhost -J-DsocksProxyPort=6666 aws.sewatech.net:1090
For french speaking people, I described the solution in my personal wiki.
socket-binding allow set TCP port, but what about TCP host (ie: listening adress).
How could we make JBoss to listen only to a specified adress (AWS dual homed case) ?
Support of -Djava.rmi.server.hostname has been added in JBoss AS 7.1.0.CR1. With that version, I just have to add this in bin/standalone.conf