You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Richard Zowalla (Jira)" <ji...@apache.org> on 2024/01/16 07:15:00 UTC

[jira] [Assigned] (STORM-4017) isAnyWindowsProcessAlive does not work with multiple pids

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

Richard Zowalla reassigned STORM-4017:
--------------------------------------

    Assignee: Scott Moore

> isAnyWindowsProcessAlive does not work with multiple pids
> ---------------------------------------------------------
>
>                 Key: STORM-4017
>                 URL: https://issues.apache.org/jira/browse/STORM-4017
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-server
>    Affects Versions: 2.3.0, 2.4.0, 2.5.0, 2.6.0
>         Environment: Windows
>            Reporter: Scott Moore
>            Assignee: Scott Moore
>            Priority: Major
>         Attachments: tasklist-multiple-pid-filters.png
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The method isAnyWindowsProcessAlive in ServerUtils.java does not work with 2 or more pids in the supplied pid collection
> The refactor done as part of STORM-3638 has made an incorrect assumption that the 'tasklist' Windows tool can accept multiple arguments of "/fi pid eq <id>" and treat this list as an 'or' list when, in fact, the /fi arguments should be considered an 'and' list.
> e.g. tasklist /fi "pid eq 123" /fi "pid eq 456" means 'give me information on processes where each process has a pid of 123 and 456'
> The effect of this means that isAnyWindowsProcessAlive will always return false when given 2 or more (different) pids.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)