[infinispan-issues] [JBoss JIRA] Commented: (ISPN-443) Errors/typos in startServer.sh

[Manik Surtani (JIRA)]

    [ https://jira.jboss.org/browse/ISPN-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12530928#action_12530928 ] 

Manik Surtani commented on ISPN-443:
------------------------------------

Shouldn't we also follow the rest of the Infinispan configuration file convention of using "-1" to mean "unlimited" for any time-based parameter?

> Errors/typos in startServer.sh
> ------------------------------
>
>                 Key: ISPN-443
>                 URL: https://jira.jboss.org/browse/ISPN-443
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Cache Server
>    Affects Versions: 4.1.0.BETA1
>         Environment: Infinispan 4.1 Beta 1 on opensuse
>            Reporter: John Ament
>            Assignee: Galder Zamarreno
>             Fix For: 4.1.0.CR1
>
>
> There are a couple of errors in the startServer.sh script.
> For 
>     -i, --idle_timeout=<num>           Idle read timeout, in seconds, used to detect stale connections (default: 60 seconds).
>                                        If no new messages have been read within this time, the server disconnects the channel.
>                                        Passing 0 disables idle timeout.
> if I pass -i 0
> ./startServer.sh -r hotrod -p 11311 -i 0
> May 16, 2010 9:17:50 AM org.infinispan.util.logging.AbstractLogImpl info
> INFO: Start main with args: -r, hotrod, -p, 11311, -i, 0
> startServer: invalid option -- i
> There is a typo for -r
>     -r, --protocol=                    Protocol to understand by the server. This is a mandatory option and you should choose one of the two options
>           [memcached|hotrod|websocket]
> There are 3 protocols listed, not two options.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira