[CONTROLLER-1544] Installing bgpcep/md-sal-all and restconf features in a specific order cause errors Created: 06/Sep/16  Updated: 25/Jul/23  Resolved: 13/Jun/17

Status: Resolved
Project: controller
Component/s: config
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Milos Fabian Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 6644

 Description   

Steps to reproduce:
1. run ODL karaf
2. install:features odl-bgpcep-bgp odl-restconf
3. BGP and restconf did not start well, errors observed:

Exception in thread "config-blank-txn-0" java.lang.IllegalStateException: Error - getInstance() failed for ModuleIdentifier

{factoryName='shutdown', instanceName='shutdown'} in transaction TransactionIdentifier{name='ConfigTransaction-0-1'}
at org.opendaylight.controller.config.manager.impl.ConfigTransactionControllerImpl.secondPhaseCommit(ConfigTransactionControllerImpl.java:444)
at org.opendaylight.controller.config.manager.impl.ConfigRegistryImpl.secondPhaseCommit(ConfigRegistryImpl.java:346)
at org.opendaylight.controller.config.manager.impl.ConfigRegistryImpl.commitConfigSafe(ConfigRegistryImpl.java:285)
at org.opendaylight.controller.config.manager.impl.ConfigRegistryImpl.commitConfig(ConfigRegistryImpl.java:250)
at org.opendaylight.controller.config.manager.impl.osgi.BlankTransactionServiceTracker$1.hit(BlankTransactionServiceTracker.java:45)
at org.opendaylight.controller.config.manager.impl.osgi.BlankTransactionServiceTracker.blankTransactionSync(BlankTransactionServiceTracker.java:79)
at org.opendaylight.controller.config.manager.impl.osgi.BlankTransactionServiceTracker.lambda$blankTransactionAsync$0(BlankTransactionServiceTracker.java:70)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalStateException: Could not register runtime bean in ModuleIdentifier{factoryName='shutdown', instanceName='shutdown'}

under name org.opendaylight.controller:instanceName=shutdown,type=RuntimeBean,moduleFactoryName=shutdown
at org.opendaylight.controller.config.manager.impl.jmx.RootRuntimeBeanRegistratorImpl.sanitize(RootRuntimeBeanRegistratorImpl.java:53)
at org.opendaylight.controller.config.manager.impl.jmx.RootRuntimeBeanRegistratorImpl.registerRoot(RootRuntimeBeanRegistratorImpl.java:40)
at org.opendaylight.controller.config.manager.impl.jmx.RootRuntimeBeanRegistratorImpl.registerRoot(RootRuntimeBeanRegistratorImpl.java:19)
at org.opendaylight.controller.config.yang.shutdown.impl.ShutdownRuntimeRegistrator.register(ShutdownRuntimeRegistrator.java:11)
at org.opendaylight.controller.config.yang.shutdown.impl.ShutdownServiceImpl.<init>(ShutdownServiceImpl.java:29)
at org.opendaylight.controller.config.yang.shutdown.impl.ShutdownModule.createInstance(ShutdownModule.java:66)
at org.opendaylight.controller.config.spi.AbstractModule.getInstance(AbstractModule.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.opendaylight.controller.config.manager.impl.dependencyresolver.DependencyResolverManager$ModuleInvocationHandler.handleInvocation(DependencyResolverManager.java:149)
at com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:87)
at com.sun.proxy.$Proxy92.getInstance(Unknown Source)
at org.opendaylight.controller.config.manager.impl.ConfigTransactionControllerImpl.secondPhaseCommit(ConfigTransactionControllerImpl.java:437)
... 9 more
Caused by: javax.management.InstanceAlreadyExistsException: org.opendaylight.controller:instanceName=shutdown,type=RuntimeBean,moduleFactoryName=shutdown
at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
at org.opendaylight.controller.config.manager.impl.jmx.InternalJMXRegistrator.registerMBean(InternalJMXRegistrator.java:77)
at org.opendaylight.controller.config.manager.impl.jmx.RootRuntimeBeanRegistratorImpl.registerRoot(RootRuntimeBeanRegistratorImpl.java:38)
... 22 more

 Comments   
Comment by Vratko Polak [ 16/Sep/16 ]

This looks line an issue reported by config subsystem (cause either there or in restconf or in bgp). Are there still parts of BGP which use config subsystem?

Comment by Claudio David Gasparini [ 21/Sep/16 ]

Bug seems to come from bgp topology provider, deeper investigation in process.

Comment by Claudio David Gasparini [ 26/Sep/16 ]

BUG related to bgp-topology-provider is handled on BUG-6799, which correspond to IllegalAccessException: Class org.apache.aries.blueprint.utils.ReflectionUtils

This bug is outside of bgp, since it can be replicated installing md-sal-all.

Comment by Dana Kutenicsova [ 13/Jun/17 ]

Tested on Boron-SR3 (with both bgpcep-bgp and mdsal-all features), issue is no longer present. Closing bug.

Generated at Wed Feb 07 19:55:49 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.