[
https://jira.jboss.org/jira/browse/JBREM-827?page=com.atlassian.jira.plug...
]
Trustin Lee commented on JBREM-827:
-----------------------------------
Here's the draft:
http://anonsvn.jboss.org/repos/jbossremoting/remoting3/trunk/jboss-remoti...
There are two MXBeans: EndpointMXBean and ConnectionMXBean. They are almost identical
except that ConnectionMXBean has close/forceClose operations while EndpointMXBean does not
and that you can list the registered services with EndpointMXBean while you can't with
ConnectionMXBean. They both provide some counters via the Counters object.
Once agreed, I will finish documentation.
One missing piece though is how we register an MBean for a connection. We could register
all EndpointMXBeans automatically but we can't do that for Connections because there
will be much more connections and registering that many connections will probably pollute
the JMX console with overinformation. What user wants might be to register only the
ConnectionMXBeans that meet some criteria..? Long time ago, I wrote a JMX operation that
accepts some expression so that only the MBeans that meets the specified condition, but
I'm not sure it's a good idea since it's a lot of work.
Define a management interface for JBoss Remoting
------------------------------------------------
Key: JBREM-827
URL:
https://jira.jboss.org/jira/browse/JBREM-827
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Components: r3 core
Reporter: David Lloyd
Assignee: Trustin Lee
Fix For: 3.1.0.Beta3
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira