Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [kura-dev] develop branch doesn't start anymore – Kura Wires Services fail to resolve
Hi Jens,

That could be a problem I believe. The latest merge of PR #758 would solve it.

Thanks and Regards,


Amit Kumar Mondal
Phone: +49 176 8081 5427  Email: admin@xxxxxxxxxxxxxx
Skype: arsenalnerk   GitHub: amitjoy
Blog: blog.amitinside.com

Am 16. November 2016 um 3:16:45 PM, Jens Reimann (jreimann@xxxxxxxxxx) schrieb:

It also seems that all the wire bundles have not been added to the "distrib" project. Could that be?

On Wed, Nov 16, 2016 at 2:11 PM, Jens Reimann <jreimann@xxxxxxxxxx> wrote:
Ok ... I think I found out what goes wrong ...


On Wed, Nov 16, 2016 at 1:58 PM, Jens Reimann <jreimann@xxxxxxxxxx> wrote:
This seems to be something Kura Wires specific, as most Kura Wire components don't start up with the same issue:

---
14    Active        org.eclipse.kura.clock.ClockService            org.eclipse.kura.emulator.clock(bid=29)
15    Active        org.eclipse.kura.log.LoggerService            org.eclipse.kura.core.log(bid=33)
16    Active        org.eclipse.kura.core.deployment.CloudDeploymentHandlerV2            org.eclipse.kura.core.deployment(bid=36)
17    Active        org.eclipse.kura.gpio.GPIOService            org.eclipse.kura.emulator.gpio(bid=38)
18    Active        org.eclipse.equinox.event            org.eclipse.equinox.event(bid=39)
19    Active        org.eclipse.kura.status.CloudConnectionStatusService            org.eclipse.kura.core.status(bid=40)
20    Active        org.eclipse.kura.emulator.Emulator            org.eclipse.kura.emulator(bid=42)
21    Unsatisfied        org.eclipse.kura.asset.AssetService            org.eclipse.kura.asset.provider(bid=45)
22    Unsatisfied        org.eclipse.kura.asset            org.eclipse.kura.asset.provider(bid=45)
23    Unsatisfied        org.eclipse.kura.driver.DriverService            org.eclipse.kura.asset.provider(bid=45)
24    Active        org.eclipse.kura.camel.KuraCloudComponentResolver            org.eclipse.kura.camel(bid=47)
25    Unsatisfied        org.eclipse.kura.example.beacon.scanner.BeaconScannerExample            org.eclipse.kura.example.beacon.scanner(bid=49)
26    Active        org.eclipse.kura.core.configuration.CloudConfigurationHandler            org.eclipse.kura.core.configuration(bid=52)
27    Active        org.eclipse.kura.configuration.ConfigurationService            org.eclipse.kura.core.configuration(bid=52)
28    Active        org.eclipse.kura.camel.cloud.factory.CamelFactory            org.eclipse.kura.camel.cloud.factory(bid=54)
29    Active        org.eclipse.kura.camel.cloud.factory.CamelManager            org.eclipse.kura.camel.cloud.factory(bid=54)
30    Active        org.eclipse.kura.net.NetworkService            org.eclipse.kura.emulator.net(bid=59)
31    Unsatisfied        org.eclipse.kura.wire.CloudSubscriber            org.eclipse.kura.wire.component.provider(bid=70)
32    Unsatisfied        org.eclipse.kura.wire.DbWireRecordStore            org.eclipse.kura.wire.component.provider(bid=70)
33    Unsatisfied        org.eclipse.kura.wire.CloudPublisher            org.eclipse.kura.wire.component.provider(bid=70)
34    Unsatisfied        org.eclipse.kura.wire.DbWireRecordFilter            org.eclipse.kura.wire.component.provider(bid=70)
35    Unsatisfied        org.eclipse.kura.wire.Logger            org.eclipse.kura.wire.component.provider(bid=70)
36    Unsatisfied        org.eclipse.kura.wire.WireAsset            org.eclipse.kura.wire.component.provider(bid=70)
37    Unsatisfied        org.eclipse.kura.wire.Timer            org.eclipse.kura.wire.component.provider(bid=70)
38    Active        org.eclipse.kura.watchdog.WatchdogService            org.eclipse.kura.emulator.watchdog(bid=78)
39    Active        org.eclipse.kura.usb.UsbService            org.eclipse.kura.emulator.usb(bid=80)
40    Active        org.eclipse.kura.position.PositionService            org.eclipse.kura.emulator.position(bid=81)
41    Active        org.eclipse.kura.web.Console            org.eclipse.kura.web(bid=82)
42    Active        org.eclipse.kura.crypto.CryptoService            org.eclipse.kura.core.crypto(bid=84)
43    Unsatisfied        org.eclipse.kura.wire.WireServiceCommand            org.eclipse.kura.wire.provider(bid=85)
44    Unsatisfied        org.eclipse.kura.wire.WireService            org.eclipse.kura.wire.provider(bid=85)
45    Unsatisfied        org.eclipse.kura.wire.WireHelperService            org.eclipse.kura.wire.provider(bid=85)
46    Active        org.eclipse.kura.deployment.agent            org.eclipse.kura.deployment.agent(bid=91)
---

On Wed, Nov 16, 2016 at 1:18 PM, Jens Reimann <jreimann@xxxxxxxxxx> wrote:
Check out the "develop" branch and run "Eclipse Kura Emulator.launch".

So what I figured out is that one OSGi DS component contains a missing class:

---
<implementation class="org.eclipse.kura.asset.provider.AssetImpl"/>
---

Could that be the issue?

The bundle is active and started.

---
ss asset
"Framework is launched."


id    State       Bundle
45    ACTIVE      org.eclipse.kura.asset.provider_1.0.0.qualifier
osgi> bundle 45
org.eclipse.kura.asset.provider_1.0.0.qualifier [45]
  Id=45, Status=ACTIVE      Data Root=/tmp/osgi/framework_storage/org.eclipse.osgi/bundles/45/data
  "No registered services."
  No services in use.
  Exported packages
    org.eclipse.kura.asset.provider; version="1.0.0"[exported]
  Imported packages
    org.eclipse.kura; version="1.2.1"<org.eclipse.kura.api_1.0.10.qualifier [35]>
    org.eclipse.kura.annotation; version="1.0.0"<org.eclipse.kura.api_1.0.10.qualifier [35]>
    org.eclipse.kura.asset; version="1.0.0"<org.eclipse.kura.api_1.0.10.qualifier [35]>
    org.eclipse.kura.asset.listener; version="1.0.0"<org.eclipse.kura.api_1.0.10.qualifier [35]>
    org.eclipse.kura.configuration; version="1.1.0"<org.eclipse.kura.api_1.0.10.qualifier [35]>
    org.eclipse.kura.configuration.metatype; version="1.0.0"<org.eclipse.kura.api_1.0.10.qualifier [35]>
    org.eclipse.kura.core.configuration; version="1.0.2"<org.eclipse.kura.core.configuration_1.0.9.qualifier [52]>
    org.eclipse.kura.core.configuration.metatype; version="1.0.0"<org.eclipse.kura.core.configuration_1.0.9.qualifier [52]>
    org.eclipse.kura.driver; version="1.0.0"<org.eclipse.kura.api_1.0.10.qualifier [35]>
    org.eclipse.kura.driver.listener; version="1.0.0"<org.eclipse.kura.api_1.0.10.qualifier [35]>
    org.eclipse.kura.localization; version="1.0.0"<org.eclipse.kura.localization_1.0.0.qualifier [23]>
    org.eclipse.kura.localization.resources; version="1.0.0"<org.eclipse.kura.localization_1.0.0.qualifier [23]>
    org.eclipse.kura.type; version="1.0.0"<org.eclipse.kura.api_1.0.10.qualifier [35]>
    org.eclipse.kura.util.base; version="1.0.0"<org.eclipse.kura.util_1.0.0.qualifier [13]>
    org.eclipse.kura.util.collection; version="1.0.0"<org.eclipse.kura.util_1.0.0.qualifier [13]>
    org.eclipse.kura.util.service; version="1.0.0"<org.eclipse.kura.util_1.0.0.qualifier [13]>
    org.osgi.framework; version="1.7.0"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
    org.osgi.service.component; version="1.2.0"<osgi.cmpn_4.3.0.201111022214 [28]>
    org.osgi.util.tracker; version="1.5.1"<org.eclipse.osgi_3.8.1.v20120830-144521 [0]>
    org.slf4j; version="1.7.21"<slf4j.api_1.7.21 [41]>
  No fragment bundles
  Named class space
    org.eclipse.kura.asset.provider; bundle-version="1.0.0.qualifier"[provided]
  No required bundles


---

On Wed, Nov 16, 2016 at 12:28 PM, Amit Kumar Mondal <admin@xxxxxxxxxxxxxx> wrote:
Hi Jens,

After seeing the log, I can only understand that the Provider Bundle for Asset (org.eclipse.kura.asset.provider) is somehow not available in the OSGi runtime or somehow it stopped and hence OSGi Service Component Runtime could not create service components for AssetService and DriverService.

Could you kindly provide further information to replicate?

Thanks and Regards,
Amit Kumar Mondal
Phone: +49 176 8081 5427  Email: admin@xxxxxxxxxxxxxx
Skype: arsenalnerk   GitHub: amitjoy
Blog: blog.amitinside.com

Am 16. November 2016 um 12:16:28 PM, Jens Reimann (jreimann@xxxxxxxxxx) schrieb:

Hi,

I am currently running in a blocking issue on the develop branch. After upgrading and adding a bunch of new bundles, Kura doesn't start up properly anymore.

Failing with a bunch of Kura Wires services:

---
!ENTRY org.eclipse.equinox.ds 4 0 2016-11-16 12:14:07.612
!MESSAGE Exception occurred while creating new instance of component Component[
    name = org.eclipse.kura.driver.DriverService
    activate = activate
    deactivate = deactivate
    modified =
    configuration-policy = optional
    factory = null
    autoenable = true
    immediate = true
    implementation = org.eclipse.kura.internal.asset.DriverServiceImpl
    state = Unsatisfied
    properties = {service.pid=org.eclipse.kura.driver.DriverService}
    serviceFactory = false
    serviceInterface = [org.eclipse.kura.driver.DriverService]
    references = null
    located in bundle = org.eclipse.kura.asset.provider_1.0.0.qualifier [45]
]
!STACK 0
java.lang.NoClassDefFoundError: Could not initialize class org.eclipse.kura.internal.asset.DriverServiceImpl
    at sun.reflect.GeneratedConstructorAccessor4.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at java.lang.Class.newInstance(Class.java:442)
    at org.eclipse.equinox.internal.ds.model.ServiceComponent.createInstance(ServiceComponent.java:493)
    at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.createInstance(ServiceComponentProp.java:272)
    at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:333)
    at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
    at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
    at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
    at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
    at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
    at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
    at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
    at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
    at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
    at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
    at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
    at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
    at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
    at org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473)
    at org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
    at org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:816)
    at org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:783)
    at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
    at java.lang.Thread.run(Thread.java:745)

!ENTRY org.eclipse.equinox.ds 4 0 2016-11-16 12:14:07.614
!MESSAGE Exception occurred while creating new instance of component Component[
    name = org.eclipse.kura.asset.AssetService
    activate = activate
    deactivate = deactivate
    modified =
    configuration-policy = optional
    factory = null
    autoenable = true
    immediate = true
    implementation = org.eclipse.kura.internal.asset.AssetServiceImpl
    state = Unsatisfied
    properties = {service.pid=org.eclipse.kura.asset.AssetService}
    serviceFactory = false
    serviceInterface = [org.eclipse.kura.asset.AssetService]
    references = null
    located in bundle = org.eclipse.kura.asset.provider_1.0.0.qualifier [45]
]
!STACK 0
java.lang.NoClassDefFoundError: Could not initialize class org.eclipse.kura.internal.asset.AssetServiceImpl
    at sun.reflect.GeneratedConstructorAccessor3.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at java.lang.Class.newInstance(Class.java:442)
    at org.eclipse.equinox.internal.ds.model.ServiceComponent.createInstance(ServiceComponent.java:493)
    at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.createInstance(ServiceComponentProp.java:272)
    at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:333)
    at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
    at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
    at org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473)
    at org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
    at org.eclipse.equinox.internal.ds.SCRManager.processConfigurationEvent(SCRManager.java:363)
    at org.eclipse.equinox.internal.ds.SCRManager.processConfigurationEvent(SCRManager.java:303)
    at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:91)
    at java.lang.Thread.run(Thread.java:745)
---

Any ideas?

Thanks

Jens

--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill



--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill



--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill



--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill



--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill

Back to the top