|
Yang module threadpool@2014-04-09 resides in bundle threadpool-config-api,
netty-timer@2013-11-19 resides in bundle netty-timer-config.
These two bundles are assembled in the same feature features-config-netty
whose feature definition is like the following:
<feature name='odl-config-netty' version='${project.version}' description="OpenDaylight :: Config-Netty">
<feature version='${project.version}'>odl-config-netty-config-api</feature>
<bundle>mvn:org.opendaylight.controller/netty-event-executor-config/${project.version}</bundle>
<bundle>mvn:org.opendaylight.controller/netty-threadgroup-config/${project.version}</bundle>
<bundle>mvn:org.opendaylight.controller/netty-timer-config/${project.version}</bundle>
<bundle>mvn:org.opendaylight.controller/threadpool-config-api/${project.version}</bundle>
<bundle>mvn:org.opendaylight.controller/threadpool-config-impl/${project.version}</bundle>
<feature version='${project.version}'>odl-config-startup</feature>
<configfile finalname="${config.configfile.directory}/${config.netty.configfile}">mvn:org.opendaylight.controller/config-netty-config/${config.version}/xml/config</configfile>
</feature>
In fact, threadpool-config-api should appear before netty-timer-config.
In a particluar execution trace, i.e.,
bundle netty-timer-config is installed and its netty-timer.yang is loaded
into system's yang module space, and just before karaf installing thread
begins to install next bundle of threadpool-config-api in this feature,
config-pusher thread is trying to push 00-netty.xml,
then reported exception will appear and the config-pusher thread
willterminate, so whole odl controller will be out-of-service.
|