Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362643 - o.e.j.jmx.ConnectorServer starts the RMIRegistry using the wrong part of JMXServiceURL
Summary: o.e.j.jmx.ConnectorServer starts the RMIRegistry using the wrong part of JMXS...
Status: RESOLVED INVALID
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 7.5.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 7.5.x   Edit
Assignee: Greg Wilkins CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-02 05:05 EDT by Simone Bordet CLA
Modified: 2011-11-04 16:53 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simone Bordet CLA 2011-11-02 05:05:56 EDT 
For JMXServiceURL such as rmi://host:1234 the host and port refer to the RMI server, not to the RMIRegistry.

For JMXServiceURL such as rmi://host1:1234/jndi/rmi://host2:4321, host1:1234 refers to the RMI server, and host2:4321 refers to the RMIRegistry.

The current implementation of ConnectorServer does not handle JMXServiceURLs properly.
Comment 1 Simone Bordet CLA 2011-11-04 16:53:57 EDT 
Misread the actual code, ConnectorServer is implemented properly.