[
https://issues.apache.org/activemq/browse/CAMEL-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-553:
------------------------------
Fix Version/s: 1.4.0
(was: 1.5.0)
> Firewall-friendly JMX Connector URL
> -----------------------------------
>
> Key: CAMEL-553
> URL: https://issues.apache.org/activemq/browse/CAMEL-553
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.3.0
> Reporter: christian ohr
> Fix For: 1.4.0
>
>
> InstrumentationAgentImpl (or DefaultInstrumentationagent in the trunk) only
> allows to set the JMX registry port, URL created is
> service:jmx:rmi:///jndi/rmi://<host>:<registryPort>/jmxrmi.
> However, when a connection is established, the remote objects are exchanged
> on a different port. If this is not set, it's chosen by random, which is
> particularly unhelpful if the instrumented Camel server is behind a firewall!
> The appropriate URL is
> service:jmx:rmi://<host>:<remotePort>/jndi/rmi://<host>:<registryPort>/jmxrmi.
>
> Also see
> http://blogs.sun.com/jmxetc/entry/connecting_through_firewall_using_jmx for
> more details.
> The easiest fix would be to define remotePort=registryPort+1 and use the new
> URL in the createJmxConnector method. More flexible would be to have an
> independent property and let the use choose which URL should be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
