You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2019/04/11 13:54:00 UTC

[jira] [Updated] (BEAM-7027) IO tests may get a port conflict due to lack of synchronization

     [ https://issues.apache.org/jira/browse/BEAM-7027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismaël Mejía updated BEAM-7027:
-------------------------------
    Description: IO tests get the port of the next free port via ServerSocket however when the tests run in parallel it could be the case that two build threads get the same port number assigned causing a conflict. We should create a synchronized method to fix this and use it in all IO tests that require to assign a local port.  (was: IO tests get the port of the next free port via ServerSocket however when the thests fun in parallel it could be the case that two build threads get the same port number assigned causing a conflict. We should create a synchronized method to fix this and use it in all IO tests that require to assign a local port.)

> IO tests may get a port conflict due to lack of synchronization
> ---------------------------------------------------------------
>
>                 Key: BEAM-7027
>                 URL: https://issues.apache.org/jira/browse/BEAM-7027
>             Project: Beam
>          Issue Type: Test
>          Components: io-java-utilities
>            Reporter: Ismaël Mejía
>            Priority: Major
>
> IO tests get the port of the next free port via ServerSocket however when the tests run in parallel it could be the case that two build threads get the same port number assigned causing a conflict. We should create a synchronized method to fix this and use it in all IO tests that require to assign a local port.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)