[DERBY-4700] Add method to obtain a bogus port in TestConfiguration

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.7.1.1
• Fix Version/s: 10.6.2.1, 10.7.1.1
• Component/s: Test
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 15/Jun/10 06:27
• Updated: 29/Nov/10 14:21
• Resolved: 13/Jul/10 13:24

Description

In some cases one needs to obtain a port number on which there is no Derby network server.
Today this is solved in an ad-hoc way, for instance by using the current port minus one. When running tests in parallel, there is a chance that a port where there actually is a Derby network server listening is picked.

As a start, I suggest that the bogus port is allocated to the last port in the port range configured for the run: baseport + MAX_PORTS_USED -1.

Issue Links

• is related to: DERBY-4747 ttestSetPortPriority junit test failing in tinderbox runs with junit.framework.AssertionFailedError: Port 1537 exceeeds expected maximum.