Jinder Aujla created CASSANDRA-5917:
---------------------------------------

             Summary: NoSuchMethodError when calling 
YamlConfigurationLoader.loadConfig()
                 Key: CASSANDRA-5917
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5917
             Project: Cassandra
          Issue Type: Bug
          Components: API
         Environment: Linux
            Reporter: Jinder Aujla


Hi, when this method is called, I see this:

java.lang.NoSuchMethodError: 
org.yaml.snakeyaml.Yaml.<init>(Lorg/yaml/snakeyaml/constructor/BaseConstructor;)V
        at 
org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:86)
        at 
org.apache.cassandra.config.DatabaseDescriptor.loadConfig(DatabaseDescriptor.java:125)
        at 
org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:101)
        at 
com.globalrelay.cassandra.lib.test.process.CassandraServiceDataCleaner.getDataDirs(CassandraServiceDataCleaner.java:69)
        at 
com.globalrelay.cassandra.lib.test.process.CassandraServiceDataCleaner.makeDirsIfNotExist(CassandraServiceDataCleaner.java:49)
        at 
com.globalrelay.cassandra.lib.test.process.CassandraServiceDataCleaner.prepare(CassandraServiceDataCleaner.java:24)
        at 
com.globalrelay.cassandra.lib.test.process.CassandraTestProcess.ensureCassandraRunning(CassandraTestProcess.java:140)
        at 
com.globalrelay.cassandra.lib.test.process.CassandraTestProcessTest.testNativeServerStop(CassandraTestProcessTest.java:44)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:601)
        at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
        at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
        at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
        at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
        at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
        at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:44)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
        at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
        at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
        at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
        at 
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
        at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
        at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
        at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
        at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
        at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

I believe it's because of an enhancement made in ticket CASSANDRA-5606. The 
version of snakeyaml that 2.0.0-rc1 depends on is 1.6, but this constructor 
doesn't exist in that version but it does in version 1.12.

Coincidentally CASSANDRA-5317 speaks of upgrading the snakeyaml dependency, but 
I'm not sure what was upgraded. 

--
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

Reply via email to