[
https://issues.apache.org/jira/browse/CASSANDRA-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054284#comment-14054284
]
Joshua McKenzie commented on CASSANDRA-7503:
--------------------------------------------
Will that 1.5 second sleep interfere with starting clusters via ccm and
potentially with dtests?
On the linux side we simply return the exit code of the call to the daemon -
maybe we should do the same and set ERRORLEVEL on Windows as appropriate rather
than putting in arbitrary timings at all?
> 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)
