Darran Lofthouse created REMJMX-47:
--------------------------------------
Summary: Refactor the RemotingConnectorServer / JMXConnectorServer to pull
initial comms earlier
Key: REMJMX-47
URL:
https://issues.jboss.org/browse/REMJMX-47
Project: Remoting JMX
Issue Type: Task
Components: Connection
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 1.0.4.CR1
The JMXConnectorServer implementation is supposed to associate incoming connections with a
single MBean server - with the addition of an MBeanServerLocator in addition to the
possibility of proxied requests to a remote MBeanServer there is also the possibility of
multiple MBeanServers in the same process.
Once a connection is established the connection is associated with the
RemotingConnectorServer so the selection of MBeanServer / RemotingConnectorServer needs to
happen before this.
For version 2 of the protocol this association should happen after begin() is called i.e.
the initial message exchange allows for the key/value pairs to be set to select the
MBeanServer and then when begin is called the final association occurs. For version 1 we
will be assuming only one MBeanServer or the MBeanServerLocator will need to select one
with no properties, in this case will will assume begin has been called as soon as the
connection is established.
Although this change will move some of the initial negotiation of the connection out of
the RemotingConnectorServer it is MANDATORY that for the initial version negotiation and
for version 1 that there are no alterations to the protocol - version 2 however is a new
protocol so AFTER it has been selected the protocol can diverge.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira