activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <gary.tu...@gmail.com>
Subject Re: Changing the ManagmentContext to point to non-localhost
Date Fri, 17 Jul 2009 08:56:28 GMT
I agree, can you open a jira issue to track this. thanks,

2009/7/17 mkonda <knvms@hotmail.com>:
>
> I think (not just in my case), it should be configurable - defaulting to
> localhost.
>
> One of the issues I have is to connect to the server remotely - to monitor
> and manage - which is THE main purpose of JMX. This is not being served if
> you leave the hardcoding.
>
> Thanks
> Madhu
>
>
> bsnyder wrote:
>>
>> On Thu, Jul 16, 2009 at 8:21 AM, mkonda<knvms@hotmail.com> wrote:
>>>
>>> Hello All
>>>
>>> I have changed the managementContext in activemq.xml config to point to a
>>> new port:
>>>
>>>  <managementContext>
>>>            <managementContext connectorPort="10099"
>>> createConnector="true"/>
>>>  </managementContext>
>>>
>>> My broker config is:
>>>
>>> <broker xmlns=".." useJmx="true" brokerName="myhost"
>>> dataDirectory="${activemq.base}/data">
>>> ....
>>> </broker>
>>>
>>> As you can see, I have added brokerName and useJmx tags so that my
>>> serivice
>>> url can be exposed to JMX Clients/console.
>>>
>>> However, when I start up the activemq, I always get the jmxurl being
>>> published at localhost (rather than my brokerName or host)
>>>
>>> INFO ManagementContext- JMX consoles can connect to
>>> service:jmx:rmi:///jndi/rmi://localhost:10099/jmxrmi
>>>
>>> Question: Is there a way that I can create the serviceUrl of the
>>> ManagementContext to use my machine name instead of default localhost?
>>
>> The localhost portion is hard-coded in the ManagementContext class.
>> This could certainly be changed, but I have  reservations about doing
>> this because even a successful resolution of the actual hostname or ip
>> address has some associated overhead that could affect the startup
>> time. Let alone a resolution that goes awry which could actually
>> prevent broker startup. Opinions, thoughts?
>>
>> Bruce
>> --
>> perl -e 'print
>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
>> );'
>>
>> ActiveMQ in Action: http://bit.ly/2je6cQ
>> Blog: http://bruceblog.org/
>> Twitter: http://twitter.com/brucesnyder
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Changing-the-ManagmentContext-to-point-to-non-localhost-tp24517365p24529302.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>



-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

Mime
View raw message