cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-5467) isRunning flag set prematurely in org.apache.cassandra.transport.Server
Date Mon, 22 Apr 2013 09:39:16 GMT

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

Sylvain Lebresne reassigned CASSANDRA-5467:
-------------------------------------------

    Assignee: Sylvain Lebresne
    
> isRunning flag set prematurely in org.apache.cassandra.transport.Server
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-5467
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5467
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.2
>            Reporter: John Sanda
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: jmx, server
>
> In org.apache.cassandra.transport.Server, the start() method sets the isRunning flag
before calling the run() method. In the event of an initialization error like a port conflict
an exception will be thrown at line 136 which is,
>     Channel channel = bootstrap.bind(socket);
> It seems like it might make more sense to set the isRunning flag after binding to the
socket. I have a tool that deploys a node and then verifies it is ready to receive CQL requests.
I do this via JMX. Unless I use a delay before making that check, the JMX call will return
true even though there is a port conflict. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message