Kedar,
If you connect locally, then you must also manually invoke the bootAMX() method. (2 steps, and not obvious)
If you connect remotely, you're done. (1 step, simple)
Lloyd
On Jan 25, 2010, at 5:20 PM, Kedar Mhaswade wrote:
> Lloyd Chambers wrote:
>> Local mode doesn't use a JMXConnector and won't cause MBeans (AMX) to load.
>
> Well, we already have a bootAMX operation on an amx-support MBean that does this, no?
>
> So IMO, both these tabs are equivalent on the processes that you own.
>
>> On Jan 25, 2010, at 6:48 AM, vince kraemer wrote:
>>> kedar wrote:
>>>>
>>>> vince kraemer wrote:
>>>>
>>>>> I have noticed that we tell people to connect to v3 as a remote process, even when the server is local and appears in the list of local processes.
>>>>>
>>>> I have always connected to the v3 process that was visible on my JConsole
>>>> screen. Works as expected.
>>>>
>>>> What's your real question?
>>> Why do we tell people to use the 'remote' connection mode from jconsole instead of the local mode?
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>> Lloyd Chambers
>> lloyd.chambers_at_sun.com
>> GlassFish Team
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
Lloyd Chambers
lloyd.chambers_at_sun.com
GlassFish Team