[jira] [Updated] (STORM-927) Storm.cmd on Windows shouldn't exit until deployment complete

["Paul Milliken (JIRA)" <ji...@apache.org>]

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

Paul Milliken updated STORM-927:
--------------------------------
    Labels: windows  (was: )

> Storm.cmd on Windows shouldn't exit until deployment complete
> -------------------------------------------------------------
>
>                 Key: STORM-927
>                 URL: https://issues.apache.org/jira/browse/STORM-927
>             Project: Apache Storm
>          Issue Type: Improvement
>    Affects Versions: 0.10.0
>         Environment: Windows Server 2008 R2
>            Reporter: Paul Milliken
>            Priority: Minor
>              Labels: windows
>
> The storm.cmd script returns before the topology has been deployed. This causes problems when attempting to automate deployments, as detecting failures is made difficult.
> It looks like this is because all storm command are ultimately invoked via "start /b" unless STORM_DEBUG is set. Attempting to workaround by setting STORM_DEBUG doesn't work, as the fix in STORM-322 hasn't been applied to the debug command.
> It looks like a relatively simple fix. Apply the STORM-322 fix to the debug route, and make the jar command use it by default.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)