You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Joshua McKenzie (JIRA)" <ji...@apache.org> on 2014/07/07 16:08:34 UTC
[jira] [Created] (CASSANDRA-7503) Windows - better communication on
start-up failure
Joshua McKenzie created CASSANDRA-7503:
------------------------------------------
Summary: 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
Fix For: 2.1.0
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)