[ http://jira.jboss.com/jira/browse/JBREM-30?page=history ]
Tom Elrod resolved JBREM-30:
-----------------------------
Resolution: Done
Updated so server invoker implementations will be registered with mbean server
upon startup of connector.
> Better integration for registering invokers with MBeanServer
> ------------------------------------------------------------
>
> Key: JBREM-30
> URL: http://jira.jboss.com/jira/browse/JBREM-30
> Project: JBoss Remoting
> Type: Task
> Components: transport
> Versions: 1.0.1 beta
> Reporter: Tom Elrod
> Assignee: Tom Elrod
> Priority: Minor
> Fix For: 1.0.1 final
>
>
> All the invokers (socket, rmi, http) need to be registered with an
> MBeanServer so can be configured and managed via JMX. Configuration has been
> added to the invokers via service.xml, but is not direct, meaning that it is
> the Connector that is really the service mbean, so the invokers have to be
> registered separately. This is fine if running within JBoss and can lookup
> the JBoss MBeanServer (same one used by the microkernel via the
> MBeanServerLocator.locateJBoss() call). The problem arises when running
> stand alone and not within JBoss AS. Need to figure out a way to handle this
> case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
