[
https://issues.apache.org/jira/browse/CASSANDRA-15383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962157#comment-16962157
]
Benedict Elliott Smith commented on CASSANDRA-15383:
----------------------------------------------------
Maybe, though there might be other tests in future that might require a
different initialisation sequence - it feels a little too heavy handed to
impose it on them all, as I'm not sure it's easy to override the behaviour. I
agree it's a bit suboptimal as stands though.
> Unable to init Verb in jvm-dtest
> --------------------------------
>
> Key: CASSANDRA-15383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15383
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest
> Reporter: Yifan Cai
> Assignee: Benedict Elliott Smith
> Priority: Normal
> Fix For: 4.0-alpha
>
>
> Verb cannot be initialized in dtest. The test cases that has references to
> Verb get the following error
> {code:java}
> java.lang.ExceptionInInitializerError
> at org.apache.cassandra.net.Verb.<clinit>(Verb.java:87)
> at
> org.apache.cassandra.distributed.test.DistributedReadWritePathTest.failingReadRepairTest(DistributedReadWritePathTest.java:134)
> Caused by: java.lang.NullPointerException
> at
> org.apache.cassandra.config.DatabaseDescriptor.getConcurrentReaders(DatabaseDescriptor.java:1611)
> at org.apache.cassandra.concurrent.Stage.<clinit>(Stage.java:48)
> {code}
> It is caused by the DatabaseDescriptor being uninitialized and NPE was
> thrown. The dtest initializes the DatabaseDescriptor at instance-level with
> the isolated InstanceClassLoader. Since test code is not loaded by the
> InstanceClassLoader, it does not know the already initialized
> DatabaseDescriptor.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
