You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (Jira)" <ji...@apache.org> on 2021/01/15 17:34:00 UTC

[jira] [Updated] (GEODE-8838) Provide some ability to launch ChildVM with specific port for RemoteDUnitVM stub

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

Jens Deppe updated GEODE-8838:
------------------------------
    Description: 
This change is intended to address an issue with port bind conflicts
 specifically when VMs are restarted. Thus this change only specifies a
 specific port when bouncing a VM. In this case we use a RMI port
 outside the usual range of ephemeral ports for MacOS (49152–65535) and
 Linux (32768-60999).

We typically try and use ephemeral ports everywhere. However,
 sometimes an ephemeral port created during a prior start needs to be
 used as a fixed port on subsequent bounces. In this case, ephemeral
 ports that are allocated early may end up conflicting with these fixed
 ports.

> Provide some ability to launch ChildVM with specific port for RemoteDUnitVM stub
> --------------------------------------------------------------------------------
>
>                 Key: GEODE-8838
>                 URL: https://issues.apache.org/jira/browse/GEODE-8838
>             Project: Geode
>          Issue Type: Test
>          Components: tests
>            Reporter: Jens Deppe
>            Priority: Major
>
> This change is intended to address an issue with port bind conflicts
>  specifically when VMs are restarted. Thus this change only specifies a
>  specific port when bouncing a VM. In this case we use a RMI port
>  outside the usual range of ephemeral ports for MacOS (49152–65535) and
>  Linux (32768-60999).
> We typically try and use ephemeral ports everywhere. However,
>  sometimes an ephemeral port created during a prior start needs to be
>  used as a fixed port on subsequent bounces. In this case, ephemeral
>  ports that are allocated early may end up conflicting with these fixed
>  ports.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)