cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ala' Alkhaldi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7503) Windows - better communication on start-up failure
Date Mon, 07 Jul 2014 22:31:34 GMT

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

Ala' Alkhaldi commented on CASSANDRA-7503:
------------------------------------------

The problem can be detected if the sleep time after running cassandra process is increased
to few seconds (as shown in the attached 7503_v1.txt), the script will report 
{code}
D:\Projects\cassandra>bin\cassandra
Detected powershell execution permissions.  Running with enhanced startup scripts.
Setting up Cassandra environment
Starting cassandra server
Error starting cassandra.
Run with -v and -f to get foreground verbose information on the error.
{code}

Similar behavior can be also achieved by using "System.Diagnostics.Process" as in the foreground
case and then waiting for exit for few seconds

> 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
>
>
> 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