cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7503) Windows - better communication on start-up failure
Date Fri, 11 Jul 2014 20:21:05 GMT

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

Joshua McKenzie updated CASSANDRA-7503:
---------------------------------------

    Attachment: 7503_v3.txt

Attaching a v3 that does a few extra things I thought of while reviewing:
* Make writing pidfile required since we can't SIGINT procs on Windows without it (overrides
path if they provide -p)
* Pass back return code as 0 or 1 from PowerShell to .bat file
* Set errorlevel in .bat file and immediately exit, transferring control to caller after powershell
launch is complete

This should give us idiomatic scripting behavior on Windows (errorlevel) and still mirror
our behavior on the linux launch scripts.

> Windows - better communication on start-up failure
> --------------------------------------------------
>
>                 Key: CASSANDRA-7503
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7503
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joshua McKenzie
>            Assignee: Ala' Alkhaldi
>            Priority: Minor
>              Labels: Windows
>             Fix For: 2.1.0
>
>         Attachments: 7503_v1.txt, 7503_v2.txt, 7503_v3.txt
>
>
> The Windows launch scripts report successful launch on certain failure conditions.  For
instance, if you try to start a 2nd instance of Cassandra and it fails to bind to the JMX
port:
> {code:title=silent failure}
> D:\src\cassandra\bin>cassandra.bat
> Detected powershell execution permissions.  Running with enhanced startup scripts.
> Setting up Cassandra environment
> Starting cassandra server
> Started cassandra successfully with pid: 6520
> {code}
> {code:title=-f failure}
> D:\src\cassandra\bin>cassandra.bat -f
> Detected powershell execution permissions.  Running with enhanced startup scripts.
> Setting up Cassandra environment
> Starting cassandra server
> Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already
in use: 7199; nested exception is:
>         java.net.BindException: Address already in use: JVM_Bind
> {code}
> Reference CASSANDRA-7254 for linux-based solution to a similar NPE on startup due to
duplicate JMX port-bind.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message