[
https://issues.apache.org/jira/browse/PHOENIX-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516952#comment-15516952
]
Josh Elser commented on PHOENIX-3287:
-------------------------------------
This appears to be a defect in MiniKDC. When the object is instantiated and the
KDC port is {{0}}, a port is obtained from the ephemeral range and then used
later when the KDC actually binds. This presents a race condition.
We should be able to essentially reduce the likelihood of this happening to
zero by just retrying the logic when we fail to bind.
> SecureUserConnectionsTest is flapping
> -------------------------------------
>
> Key: PHOENIX-3287
> URL: https://issues.apache.org/jira/browse/PHOENIX-3287
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Josh Elser
> Priority: Minor
>
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 99.229 sec
> <<< FAILURE! - in org.apache.phoenix.jdbc.SecureUserConnectionsTest
> org.apache.phoenix.jdbc.SecureUserConnectionsTest Time elapsed: 99.229 sec
> <<< ERROR!
> java.net.BindException: Address already in use
> See https://builds.apache.org/job/Phoenix-master/1404/changes for example
> (and another earlier one). Wild guess, but maybe the port needs to be
> randomized? Can it be?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
