Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340920 - Dynamically assign RMI registry port for integration testing
Summary: Dynamically assign RMI registry port for integration testing
Status: RESOLVED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: 7.3.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 7.2.x   Edit
Assignee: Michael Gorovoy CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-24 18:31 EDT by Michael Gorovoy CLA
Modified: 2011-05-09 17:57 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 Michael Gorovoy CLA 2011-03-24 18:31:56 EDT 
When performing integration testing of JMX integration, it is necessary to create an RMI connector that needs to register its endpoint in an RMI registry. This RMI registry instance should be started on a non-standard port to avoid interference.
Comment 1 Michael Gorovoy CLA 2011-03-24 18:41:00 EDT 
In the event the JMXServiceURL has the RMI registry port specified as 0, an available port will be allocated for it and the JMX Remote URL will reflect the canonical host name and port number allocated for this RMI registry instance.
Comment 2 Michael Gorovoy CLA 2011-05-09 17:56:48 EDT 
Committed r2911.
Comment 3 Michael Gorovoy CLA 2011-05-09 17:57:24 EDT 
Resolving the ticket.