james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Fondermann <bf_...@brainlounge.de>
Subject Re: Extend JMX support
Date Mon, 03 Jul 2006 16:22:02 GMT
JSR160 support under JSE5 works with HostedSystemManager instead of 
MX4JSystemManager. MBeans are exported fine. So I will skip all this 
MX4J upgrading since it's not really neccessary anymore.

Detailed how-tos have been added to the James wiki.

   Bernd

Bernd Fondermann wrote:
> Alan D. Cabrera wrote:
> 
>> Bernd Fondermann wrote:
>>
>>> Hi,
>>>
>>> I'd like to extend James' JMX operations and attributes. In the first
>>> stage, this would cover the functionalities already covered by the
>>> RemoteManager.
>>>
<snip/>
>>>
>>> Upgrading MX4J would also be cool, but there may be some traps waiting
>>> there since JMX integration is currently handled by the container.
>>> Utilizing JSE5 JMX support would be useful, too.
>>>
>> What does "Upgrading MX4J" mean?  Sorry, not following.
> 
> 
> MX4J is the JMX kernel library used within James.
> 
> Currently distributed version seems to be aged 1.1.1 which for example 
> does not support JSR 160.
> Using James JMX is also not working very well when Java5's built-in JMX 
> support is enabled.
> 
> The whole JMX integration is done by Phoenix. Don't know if there is a 
> way to make changes there.
> 
> I'll have a deeper look at this stuff later but any good advise is welcome.
> 
>   Bernd
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message