MBean interface for connector servers. A JMX API connector server is attached to an MBean server, and establishes connections to that MBean server for remote clients.
A newly-created connector server is inactive, and does
not yet listen for connections. Only when its
method has been called does it start listening for connections.
Method SummaryModifier and TypeMethodDescriptionThe address of this connector server.The attributes for this connector server.
StringThe list of IDs for currently-open connections to this connector server.
isActive()Determines whether the connector server is active.
voidInserts an object that intercepts requests for the MBean server that arrive through this connector server.
start()Activates the connector server, that is, starts listening for client connections.
stop()Deactivates the connector server, that is, stops listening for client connections.Returns a client stub for this connector server.
startvoid start() throws IOException
Activates the connector server, that is, starts listening for client connections. Calling this method when the connector server is already active has no effect. Calling this method when the connector server has been stopped will generate an
stopvoid stop() throws IOException
Deactivates the connector server, that is, stops listening for client connections. Calling this method will also close all client connections that were made by this server. After this method returns, whether normally or with an exception, the connector server will not create any new client connections.
Once a connector server has been stopped, it cannot be started again.
Calling this method when the connector server has already been stopped has no effect. Calling this method when the connector server has not yet been started will disable the connector server object permanently.
If closing a client connection produces an exception, that exception is not thrown from this method. A
JMXConnectionNotification.FAILEDis emitted from this MBean with the connection ID of the connection that could not be closed.
Closing a connector server is a potentially slow operation. For example, if a client machine with an open connection has crashed, the close operation might have to wait for a network protocol timeout. Callers that do not want to block in a close operation should do it in a separate thread.
IOException- if the server cannot be closed cleanly. When this exception is thrown, the server has already attempted to close all client connections. All client connections are closed except possibly those that generated exceptions when the server attempted to close them.
Determines whether the connector server is active. A connector server starts being active when its
startmethod returns successfully and remains active until either its
stopmethod is called or the connector server fails.
- true if the connector server is active.
Inserts an object that intercepts requests for the MBean server that arrive through this connector server. This object will be supplied as the
MBeanServerfor any new connection created by this connector server. Existing connections are unaffected.
This method can be called more than once with different
MBeanServerForwarderobjects. The result is a chain of forwarders. The last forwarder added is the first in the chain. In more detail:
If this connector server is already associated with an
MBeanServerobject, then that object is given to
mbsf.setMBeanServer. If doing so produces an exception, this method throws the same exception without any other effect.
If this connector is not already associated with an
MBeanServerobject, or if the
mbsf.setMBeanServercall just mentioned succeeds, then
mbsfbecomes this connector server's
The list of IDs for currently-open connections to this connector server.
- a new string array containing the list of IDs. If there are no currently-open connections, this array will be empty.
The address of this connector server.
The address returned may not be the exact original
JMXServiceURLthat was supplied when creating the connector server, since the original address may not always be complete. For example the port number may be dynamically allocated when starting the connector server. Instead the address returned is the actual
JMXConnectorServer. This is the address that clients supply to
Note that the address returned may be
JMXConnectorServeris not yet
- the address of this connector server, or null if it does not have one.
The attributes for this connector server.
- a read-only map containing the attributes for this connector server. Attributes whose values are not serializable are omitted from this map. If there are no serializable attributes, the returned map is empty.
Returns a client stub for this connector server. A client stub is a serializable object whose
connectmethod can be used to make one new connection to this connector server.
A given connector need not support the generation of client stubs. However, the connectors specified by the JMX Remote API do (JMXMP Connector and RMI Connector).
env- client connection parameters of the same sort that can be provided to
JMXConnector.connect(Map). Can be null, which is equivalent to an empty map.
- a client stub that can be used to make a new connection to this connector server.
UnsupportedOperationException- if this connector server does not support the generation of client stubs.
IllegalStateException- if the JMXConnectorServer is not started (see
IOException- if a communications problem means that a stub cannot be created.