Hi Christian, This is very good idea. Once I was looking way to avoid dynamic port allocation and I lost this 'trick'. If we won't put this into Karaf/SMX distribution we must have this described in documentation (like http://servicemix.apache.org/SMX4/remote-jmx-connection.html)
Regards, Lukasz -----Original Message----- From: Christian Mueller [mailto:[email protected]] Sent: Wednesday, October 20, 2010 11:27 PM To: [email protected] Subject: [DISCUSS] changing the default JMX service uri Hello list! Today, I spend some hours to solve a problem we had to connect jconsole to our ServiveMix instance which is running behind a firewall. In short, if you not defide the RMI server port, a RANDOM port will be chosen for you. This doesn't work if your server is behind a firewall. I found the solution here [1]. I propose to change the property 'serviceUrl' in $SERVICEMIX_HOME/etc/org.apache.karaf.management.cfg from 'service:jmx:rmi:///jndi/rmi://localhost:${rmiRegistryPort}/karaf-${karaf.na me}' to 'service:jmx:rmi://localhost:${rmiServerPort}/jndi/rmi://localhost:${rmiRegi stryPort}/karaf-${karaf.name}' and add the new property 'rmiServerPort' with a good default value - maybe 44444. Because ServiceMix is (also) target for the enterprise, it should consider this conditions. What do you think? [1] http://download.oracle.com/javase/6/docs/technotes/guides/management/agent.h tml#gdjou Thank you, Christian -- View this message in context: http://servicemix.396122.n5.nabble.com/DISCUSS-changing-the-default-JMX-serv ice-uri-tp3229446p3229446.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
