db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4700) Add method to obtain a bogus port in TestConfiguration
Date Tue, 15 Jun 2010 17:13:23 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879031#action_12879031
] 

Knut Anders Hatlen commented on DERBY-4700:
-------------------------------------------

Alternatively, we could initialize it using getNextAvailablePort() in TestConfiguration's
constructor, similar to how we allocate the JMX port. Then we don't need extra logic in getNextAvailablePort()
to prevent collisions with the last port in the allowed range.

> Add method to obtain a bogus port in TestConfiguration
> ------------------------------------------------------
>
>                 Key: DERBY-4700
>                 URL: https://issues.apache.org/jira/browse/DERBY-4700
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.7.0.0
>            Reporter: Kristian Waagan
>            Priority: Minor
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message