9.5.1 Limitations of Wrapped Legacy Connectors

The wrapped legacy connectors do not provide the full functionality of either their JMX Remote API or their Java DMK 5.0 counterparts. The limitations of the wrapped legacy connectors are listed below.

• Not all of the methods supported by standard JMXConnector and JMXConnectorServer are supported by the wrapped legacy connectors.

  The following are the only methods supported by the wrapped legacy connector clients.

  • addNotificationListener(ObjectName name, ObjectName listener, NotificationFilter filter, Object handback)

  • removeNotificationListener(ObjectName name, ObjectName listener)

  • removeNotificationListener(ObjectName name, ObjectName listener, NotificationFilter filter, Object handback)

  • removeNotificationListener(ObjectName name, NotificationListener listener, NotificationFilter filter, Object handback)

  The wrapped legacy connector servers only support the getConnectionIds() method.

• A legacy connector can only use the class loader that was used to created that connector.

• Legacy servers do not send out events relating to client connections or failures, but only about state changes: offline, starting, online.

• A client can connect to a legacy connector server created by the JMX Remote API factory only after the server has been registered in an MBean server.

• A legacy connector client has no way of showing its local port number. Calling Client.getConnectionId() will return:

  protocol://host:server_port count

  Where the count is an integer ID that is unique within a Java virtual machine on the client side. For example:

  jdmk-http://host_name:6666 1

• A legacy connector server must be registered as an MBean in the MBean server which is exposed through that connector server, before the server can be started.