[ 
https://issues.apache.org/jira/browse/STORM-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518348#comment-14518348
 ] 

ASF GitHub Bot commented on STORM-745:
--------------------------------------

Github user ptgoetz commented on the pull request:

    https://github.com/apache/storm/pull/506#issuecomment-97262501
  
    This is a regression that affects 0.9.4, and I've confirmed this patch 
fixes it.
    
    I'm +1 for merging as well as applying it to the 0.9.x branch and releasing 
0.9.5.
    
    @HeartSaVioR, thanks for the fix.


> Second Commandline Parameter passed to the main class is skipped when run in 
> windows
> ------------------------------------------------------------------------------------
>
>                 Key: STORM-745
>                 URL: https://issues.apache.org/jira/browse/STORM-745
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 0.9.3-rc2, 0.9.4
>         Environment: Windows Only
>            Reporter: jishnu
>              Labels: 2nd, command-line, parameter, skipping, windows
>
> Always the second parameter is getting skipped.
> E:\target>storm jar StormZeroMQ.jar com.wipro.bdas.zeromq.ZMQTopology value1 
> value2 value3 value4 value5
> Output
> I=0 value=value1
> I=1 value=value3
> I=2 value=value4
> I=3 value=value5
> public class ZMQTopology {
> public static void main(String[] args) throws AlreadyAliveException,
>                                                 InvalidTopologyException {
>                             for(int i=0;i<(args.length);i++)
>                             {   System.out.println("I=" +i+ " 
> value="+args[i]);
>                             }
> I am using the apache storm pre-built for windows.
> After some amount of debugging I could find that it happens only with windows 
> machine . I was able to reproduce the error in 2 windows machine. With both  
> 0.9.3 and 0.9.4 .In Linux machine I could see command line parameters working 
> perfectly.



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

Reply via email to