You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Patrick Rhomberg (JIRA)" <ji...@apache.org> on 2018/06/29 21:30:00 UTC

[jira] [Created] (GEODE-5366) DUnitLauncher does not respect the number of VMs requested in ClusterStartupRule

Patrick Rhomberg created GEODE-5366:
---------------------------------------

             Summary: DUnitLauncher does not respect the number of VMs requested in ClusterStartupRule
                 Key: GEODE-5366
                 URL: https://issues.apache.org/jira/browse/GEODE-5366
             Project: Geode
          Issue Type: Sub-task
            Reporter: Patrick Rhomberg


The ClusterStartupRule has the method
{noformat}
  @Override
  protected void before() throws Throwable {
    DUnitLauncher.launchIfNeeded();
    for (int i = 0; i < vmCount; i++) {
      Host.getHost(0).getVM(i);
    }
    restoreSystemProperties.before();
    occupiedVMs = new HashMap<>();
  }
{noformat}

By calling the no-arg {{launchIfNeeded}}, the number of requested VMs is not properly passed to the DUnitLauncher.  This is not a problem if vmCount > 4, since the following loop will instantiate any extra VMs.  However, if fewer than 4 VMs are requested, the DUnitLauncher will still spin up extra VMs, wasting cycles.



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