Ask Your Question
0

NoSuchMethodError for registerNotificationListerner

asked 2014-07-03 16:24:06 -0700

henry gravatar image

I have been modifying the learning switch example of the virtualization edition of the openflowplugin project. It was running fine, but once in a while, I run into exception on starting up the bundles.

2014-07-04 01:03:40.699 CEST [pool-8-thread-1] INFO o.o.o.l.internal.Activator - onSessionInitialized() consumer org.opendaylight.controller.md.sal.binding.util.BindingContextUtils$SingleConsumerContextImpl@e7792a 2014-07-04 01:03:40.739 CEST [pool-8-thread-1] ERROR o.o.c.l.b.i.UncaughtExceptionPolicy - Thread Thread[pool-8-thread-1,5,main] died because of an uncaught exception java.lang.NoSuchMethodError: org.opendaylight.controller.sal.binding.api.NotificationService.registerNotificationListener(Lorg/opendaylight/yangtools/yang/binding/NotificationListener;)Lorg/opendaylight/yangtools/concepts/ListenerRegistration;

On Eclipse, the bundle is compiled fine. I am not sure whether there is some timing issue that the API is not available because of boot sequence. Also, the pom file is set up to depend on sal-binding-api. I would expect the sal binding service would be available when my bundle is started.

Any suggestion on how to resolve the problem?

edit retag flag offensive close merge delete

Comments

I'm seeing this two on the most recent 0.1.2 snap shot. I had been working with a snap shot from June 11 and never saw this. With the July 7 snap shot, I am always seeing this.

jim.west ( 2014-07-24 06:35:04 -0700 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-07-30 03:16:35 -0700

Robert Varga gravatar image

This revolves around an API change in the controller, I think -- make sure your compile-time and run-time environment have matching versions. It looks as though your run-time is lagging behind.

edit flag offensive delete publish link more
Login/Signup to Answer

Stats

Asked: 2014-07-03 16:24:06 -0700

Seen: 304 times

Last updated: Jul 30 '14