[
https://issues.apache.org/jira/browse/CASSANDRA-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073125#comment-14073125
]
Benedict commented on CASSANDRA-7597:
-------------------------------------
Hmm. I think I would prefer to stop it being setup by a static initializer - we
don't need it to be one, since we don't impose final on any of the values.
Of course the problem there is that we have to track down all of the first
calls to DatabaseDescriptor and ensure they are preceded by a call to our new
initializer. In which case I would prefer to bump this to trunk only.
> System.exit() calls should be removed from DatabaseDescriptor
> -------------------------------------------------------------
>
> Key: CASSANDRA-7597
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7597
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 2.0.9 (earlier version should be affected as
> well)
> Reporter: Pavel Sakun
> Attachments: 7597.txt
>
>
> We're using SSTableSimpleUnsortedWriter API to generate SSTable to be loaded
> into cassandra. In case of any issue with config DatabaseDescriptor calls
> System.exit() which is apparently not the thing you expect while using API.
> Test case is simple:
> System.setProperty( "cassandra.config", "" );
> new YamlConfigurationLoader().loadConfig();
> Thread.sleep( 5000 );
> System.out.println("We're still alive"); // this will never be called
--
This message was sent by Atlassian JIRA
(v6.2#6252)
