[jira] Commented: (CASSANDRA-129) `show config file` in cli causes server to throw NPE

["Jeff Hodges (JIRA)" <ji...@apache.org>]

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

Jeff Hodges commented on CASSANDRA-129:
---------------------------------------

Ah, shoot. Too slow at writing the test for this, I guess.

> `show config file` in cli causes server to throw NPE 
> -----------------------------------------------------
>
>                 Key: CASSANDRA-129
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-129
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: trunk
>         Environment: OS X, Java 1.7 (via soylatte)
>            Reporter: Jeff Hodges
>            Assignee: Sandeep Tata
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: 129.patch, config_file_name.pach
>
>
> Booting up the cli and running the command "show config file" in the lastest from trunk (r771019) on a fresh and empty cassandra instance causes a NullPointerError to be thrown. By looking at the code (but being a not-so-hot java developer), it looks like the problem is simply DatabaseDescriptor.getConfigFileName() returning a null because configFileName_ never gets set anywhere in the code.
> The error in question:
> ERROR - Error occurred during processing of message.
> java.lang.NullPointerException
> 	at java.io.FileInputStream.<init>(FileInputStream.java:133)
> 	at java.io.FileInputStream.<init>(FileInputStream.java:96)
> 	at org.apache.cassandra.service.CassandraServer.getStringProperty(CassandraServer.java:485)
> 	at org.apache.cassandra.service.Cassandra$Processor$getStringProperty.process(Cassandra.java:1294)
> 	at org.apache.cassandra.service.Cassandra$Processor.process(Cassandra.java:860)
> 	at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:252)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> 	at java.lang.Thread.run(Thread.java:713)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.