[Carbon-dev] Enable carbon based product to monitor using a remote JMX client which is behind a firewall
rajika at wso2.com
Mon Jun 21 20:52:07 PDT 2010
In JMX convention the JMX related system properties are named in that
manner, so I used the same convention.
On Mon, Jun 21, 2010 at 10:19 PM, Supun Kamburugamuva <supun at wso2.com>wrote:
> Hi Rajika,
> Why do we have the "com" in com.wso2.rmiserver.port?
> On Mon, Jun 21, 2010 at 3:01 AM, Rajika Kumarasiri <rajika at wso2.com>
> > I have added the support to carbon core which enables any carbon based
> > product to be monitored using a remote JMX client which is behind a
> > firewall. For the purpose you can specify JMX RMIRegistryPort (the JMX
> > and the RMIServer port( the random port generate by RMI stack) in
> > carbon.xml. The configuration looks like follows.
> > <Ports>
> > <!-- The JMX Ports -->
> > <JMX>
> > <!--The port RMI registry is exposed-->
> > <!--<RMIRegistryPort>9999</RMIRegistryPort>-->
> > <!--The port RMI server should be exposed-->
> > <!--<RMIServerPort>11111</RMIServerPort>-->
> > </JMX>
> > </Ports>
> > By default remote monitoring is turn off. You can also pass this ports at
> > server start up time using the two system properties
> > "com.wso2.rmiserver.port" and "com.sun.management.jmxremote.port" for
> > RMIServer port and the RMIRegistry port respectively.
> > Rajika
> > _______________________________________________
> > Carbon-dev mailing list
> > Carbon-dev at wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
> Carbon-dev mailing list
> Carbon-dev at wso2.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Carbon-dev