[ https://issues.apache.org/jira/browse/KARAF-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reopened KARAF-1149: ----------------------------------------- Assignee: Jean-Baptiste Onofré (was: Guillaume Nodet) We have a similar issue with Docker. I think that we have to use something like: {code} -Dcom.sun.management.jmxremote.local.only=false -Djava.rmi.server.hostname=x.x.x.x {code} Right now, we use something like: {code} -Djava.rmi.server.hostname=x.x.x.x -Dcom.sun.management.jmxremote.port=44444 -Dcom.sun.management.jmxremote.rmi.port=1099 -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false {code} Let me check the code in the Karaf MBeanServer. > Karaf MBeanServer is not usable behind firewall > ----------------------------------------------- > > Key: KARAF-1149 > URL: https://issues.apache.org/jira/browse/KARAF-1149 > Project: Karaf > Issue Type: Bug > Components: karaf-management > Reporter: Jean-Baptiste Onofré > Assignee: Jean-Baptiste Onofré > > If network administrator opens the network ports to use Karaf MBean server > (for instance, by default, 1099 for the RMI Registry and 44444 for the RMI > server), the JVM open random port for JMX communication. > It could be helpful to provide a JMX agent or at least to document how to use > Karaf MBean server behind firewalls. -- This message was sent by Atlassian JIRA (v6.3.4#6332)