Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Kura » Mqtt message capacity(KuraStoreCapacityReachedException)
Mqtt message capacity [message #1727843] Mon, 28 March 2016 11:28 Go to next message
Said Ucar is currently offline Said UcarFriend
Messages: 56
Registered: June 2015
Member
Hi,

I started to receive
KuraStoreCapacityReachedException
in my logs. I have very intense data flow over my raspberry, kura. The full exception logs below if you need. My question is, what is the meaning of this exception and how can I avoid that?
AFAIK, mqtt is specially designed for intense data flow for sensor devices etc. I think there are 2-3 thousand (max.) message published and there is an store exception. It doesn't seems reasonable for me.

Best Regards,
Said.


2016-03-28 11:21:04,552 [pool-24-thread-2] INFO  o.e.k.c.d.DataServiceImpl - Storing message on topic :test, priority: 5
2016-03-28 11:21:04,554 [pool-24-thread-2] ERROR o.e.k.c.d.s.DbDataStore - Store capacity exceeded
2016-03-28 11:21:04,555 [pool-24-thread-2] WARN  c.g.k.e.r.ReadSerial - Exception cought in message read/publish cycle 
org.eclipse.kura.KuraStoreCapacityReachedException: "Error performing operation on store. Store capacity exceeded"
	at org.eclipse.kura.core.data.store.DbDataStore.store(DbDataStore.java:198)
	at org.eclipse.kura.core.data.DataServiceImpl.publish(DataServiceImpl.java:441)
	at com.gohmega.kura.excelsior.runnable.ReadSerial.run(ReadSerial.java:76)
	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)
Re: Mqtt message capacity [message #1728059 is a reply to message #1727843] Wed, 30 March 2016 16:27 Go to previous messageGo to next message
David Woodard is currently offline David WoodardFriend
Messages: 420
Registered: July 2014
Senior Member
Hello Said,

Kura buffers messages in a database for cases when you lose connection to the MQTT broker. Once the connection is reestablished, the messages are sent from the database. By default, the number of messages to store is 10,000. This value can be configured in the DataService tab using the 'store.capacity' field. If you exceed this value, you will receive the 'KuraStoreCapacityReachedException' exception. Does your device go through intervals where it is not connected to the broker? At what rate are you sending messages?

Thanks,
--Dave
Re: Mqtt message capacity [message #1728162 is a reply to message #1728059] Thu, 31 March 2016 12:40 Go to previous messageGo to next message
Said Ucar is currently offline Said UcarFriend
Messages: 56
Registered: June 2015
Member
Hi David,

Thanks for you explanation. In my DataService settings, the value was set 1,000. But what I don't understand is, my broker connection never lost while I testing my setup. When I testing my software, I send mqtt message 5 second interval, and I subscribe the topic from another device. I'm sure that the device didn't disconnect from broker. Is it possible that DataService store not only disconnected, but also connected?

Thanks,
Said.
Re: Mqtt message capacity [message #1728463 is a reply to message #1728162] Mon, 04 April 2016 14:14 Go to previous messageGo to next message
David Woodard is currently offline David WoodardFriend
Messages: 420
Registered: July 2014
Senior Member
Hello Said,

All messages are stored in the DB, it doesn't matter if you are connected or not. However, if you are connected, the queue should not be filling up. The only time I could think this would happen in a connected state is if you were sending messages at a very high rate, because the limit counts in-flight messages as well. However, sending messages every 5 seconds should be fine. What QoS are you using for the messages? Are you receiving the messages as expected before you hit the limit exception?

Thanks,
--Dave
Re: Mqtt message capacity [message #1728852 is a reply to message #1728463] Thu, 07 April 2016 21:25 Go to previous messageGo to next message
Said Ucar is currently offline Said UcarFriend
Messages: 56
Registered: June 2015
Member
Hi Dave,

My QoS is 0, and I receive my messages with no problem before the limit exception. I simply increased the limit of stored message (to 1million or something like that) and there is no problem now. I have to complete my project, (deadline issue), so I don't have time to debug this. But I add this to my TODO list, whenever I have time, I test this. If I find something noticeable, I will inform you. Thanks a lot,

Said.
Re: Mqtt message capacity [message #1782002 is a reply to message #1728463] Thu, 15 February 2018 16:57 Go to previous messageGo to next message
Stefano Cuscuna' is currently offline Stefano Cuscuna'Friend
Messages: 13
Registered: November 2017
Junior Member
Hi guys, I am replying to this topic cause I am having the same issue.
I have stressed a raspberry pi-2 sending 10 messages per second and Kura throws the same exception.
I checked in the code and I found two functions: the first that fills the storage and the second that emptys it.
The problem is that the storage doesn't come emptied after the exception.
At this point, I stopped the publisher and after a few minutes I restarted it and it works again, publishing the new messages, but the old ones has been lost.
Why the storage are not emptied after the exception? Is that normal or it is a issue of my device?
Re: Mqtt message capacity [message #1782052 is a reply to message #1782002] Fri, 16 February 2018 13:42 Go to previous messageGo to next message
Pierantonio Merlino is currently offline Pierantonio MerlinoFriend
Messages: 35
Registered: March 2016
Member
Hi Stefano,

starting from Kura 3.1.0, the rate of publishing is limited by default to 1 message/s. So, if you publish at 10 msg/s, you fill up the db and you get that exception.

You can change the behavior of the publisher setting the rate limiter in the DataService tab. Please take a look here [1] and in particular at the following options:

  • enable.rate.limit
  • rate.limit.average
  • rate.limit.time.unit
  • rate.limit.burst.size

You can change the settings accordingly your needs or disable the feature.

Best,
Pier

[1] https://eclipse.github.io/kura/config/data-service-configuration.html

[Updated on: Fri, 16 February 2018 13:43]

Report message to a moderator

Re: Mqtt message capacity [message #1782127 is a reply to message #1782052] Mon, 19 February 2018 10:06 Go to previous messageGo to next message
Stefano Cuscuna' is currently offline Stefano Cuscuna'Friend
Messages: 13
Registered: November 2017
Junior Member
Thanks Pierantonio
Re: Mqtt message capacity [message #1782307 is a reply to message #1727843] Wed, 21 February 2018 14:58 Go to previous messageGo to next message
Ahmad Arif is currently offline Ahmad ArifFriend
Messages: 10
Registered: February 2018
Junior Member
Hi all,
I have faced this issue but it disappeared, don't know how. I am facing some other issues my console logs are

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://19.fwk1179381257:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://19.fwk1179381257:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
19:17:21,444 [Component Resolve Thread] INFO  BluetoothServiceImpl:35  - Activating Bluetooth Service...
!SESSION 2018-03-02 19:17:19.932 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_161
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Command-line arguments:  -dev file:C:/Users/Ahmad.arif/eclipse-workspace/.metadata/.plugins/org.eclipse.pde.core/Kura_Emulator_OSX/dev.properties -os win32 -ws win32 -arch x86_64 -consoleLog -console

!ENTRY org.eclipse.equinox.jsp.jasper 4 0 2018-03-02 19:17:21.493
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.equinox.jsp.jasper [13]
  Unresolved requirement: Import-Package: org.apache.jasper.servlet; version="[0.0.0,8.0.0)"

	at org.eclipse.osgi.container.Module.start(Module.java:444)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1600)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Framework is running in emulation mode
19:17:21,798 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  Activator:96  - Camel activator starting
19:17:21,805 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  Activator:102  - Camel activator started
19:17:21,905 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  log:192  - Logging initialized @2183ms to org.eclipse.jetty.util.log.Slf4jLog
osgi> 19:17:22,062 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  Server:373  - jetty-9.4.7.v20170914
19:17:22,166 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  session:364  - DefaultSessionIdManager workerName=node0
19:17:22,167 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  session:369  - No SessionScavenger set, using defaults
19:17:22,168 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  session:149  - Scavenging every 600000ms
19:17:22,248 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  ContextHandler:788  - Started o.e.j.s.ServletContextHandler@61c39870{/,null,AVAILABLE}
19:17:22,262 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  AbstractConnector:286  - Started ServerConnector@576d7020{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
19:17:22,262 [Start Level: Equinox Container: 1096356b-241e-0018-12eb-de0cdb50802d] INFO  Server:441  - Started @2541ms

!ENTRY  1 0 2018-03-02 19:17:23.298
!MESSAGE [IAgent][VMCommander@17b501a4] [startServer] cannot connect to controller.
!STACK 0
org.tigris.mtoolkit.iagent.mbsa.MBSAException: java.net.ConnectException: Connection refused: connect (caused by java.net.ConnectException: Connection refused: connect)
	at org.tigris.mtoolkit.iagent.mbsa.MBSASessionFactory.serverConnect(MBSASessionFactory.java:41)
	at org.tigris.mtoolkit.iagent.internal.VMCommander.startServer(VMCommander.java:67)
	at org.tigris.mtoolkit.iagent.internal.VMCommander.<init>(VMCommander.java:53)
	at org.tigris.mtoolkit.iagent.internal.rpc.Activator.startController(Activator.java:108)
	at org.tigris.mtoolkit.iagent.internal.rpc.Activator.registerControllerSupport(Activator.java:98)
	at org.tigris.mtoolkit.iagent.internal.rpc.Activator.start(Activator.java:91)
	at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
	at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
	at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:932)
	at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
	at org.eclipse.osgi.container.Module.doStart(Module.java:581)
	at org.eclipse.osgi.container.Module.start(Module.java:449)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1600)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: java.net.ConnectException: Connection refused: connect
	at java.net.DualStackPlainSocketImpl.connect0(Native Method)
	at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
	at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
	at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
	at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
	at java.net.PlainSocketImpl.connect(Unknown Source)
	at java.net.SocksSocketImpl.connect(Unknown Source)
	at java.net.Socket.connect(Unknown Source)
	at java.net.Socket.connect(Unknown Source)
	at java.net.Socket.<init>(Unknown Source)
	at java.net.Socket.<init>(Unknown Source)
	at org.tigris.mtoolkit.iagent.mbsa.MBSASessionFactory.serverConnect(MBSASessionFactory.java:38)
	... 21 more

!ENTRY org.eclipse.equinox.jsp.jasper.registry 4 0 2018-03-02 19:17:23.477
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.equinox.jsp.jasper.registry [99]
  Unresolved requirement: Import-Package: org.eclipse.equinox.jsp.jasper
    -> Export-Package: org.eclipse.equinox.jsp.jasper; bundle-symbolic-name="org.eclipse.equinox.jsp.jasper"; bundle-version="1.0.500.v20150119-1358"; version="1.0.0"
       org.eclipse.equinox.jsp.jasper [13]
         Unresolved requirement: Import-Package: org.apache.jasper.servlet; version="[0.0.0,8.0.0)"

	at org.eclipse.osgi.container.Module.start(Module.java:444)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1600)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)

!ENTRY org.eclipse.equinox.ds 1 0 2018-03-02 19:17:23.551
!MESSAGE Could not bind a reference of component org.eclipse.kura.core.deployment.hook.DeploymentHookManager. The reference is: Reference[name = DeploymentHook, interface = org.eclipse.kura.deployment.hook.DeploymentHook, policy = dynamic, cardinality = 0..n, target = null, bind = bindHook, unbind = unbindHook]
19:17:23,565 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:155  - Loaded URL kura.properties: file:C:\Users\Ahmad.arif\eclipse-workspace/org.eclipse.kura.emulator/src/main/resources/kura.properties
19:17:23,566 [Component Resolve Thread (Bundle 155)] WARN  SystemServiceImpl:218  - File does not exist: \tmp\kura\kura_custom.properties
19:17:23,566 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:271  - Kura has net admin? false
19:17:23,566 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:274  - Is Kura web interface enabled? true
19:17:23,566 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:277  - Kura version? KURA_3.1.1
19:17:23,567 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:434  - Kura home directory is /tmp/kura
19:17:23,568 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:440  - Kura snapshots directory is C:\Users\Ahmad.arif\eclipse-workspace/kura/snapshots
19:17:23,568 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:446  - Kura tmp directory is /tmp/kura/tmp
19:17:23,568 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:450  - Kura version KURA_3.1.1 is starting
19:17:23,572 [Component Resolve Thread (Bundle 155)] INFO  HsqlDbServiceImpl:76  - activate...
19:17:23,572 [Component Resolve Thread (Bundle 155)] INFO  HsqlDbServiceImpl:144  - Opening database with url: jdbc:hsqldb:file:C:\Users\Ahmad.arif\eclipse-workspace/kura/data/db/data;hsqldb.lock_file=false
19:17:23,927 [Component Resolve Thread (Bundle 155)] INFO  CloudConnectionStatusServiceImpl:88  - Activating CloudConnectionStatus service...
19:17:23,941 [pool-5-thread-1] INFO  LogStatusRunnable:44  - Notification LED off
19:17:23,952 [Component Resolve Thread (Bundle 155)] INFO  BluetoothLeServiceImpl:33  - Activating Bluetooth Le Service...
19:17:23,955 [Component Resolve Thread (Bundle 155)] ERROR BluetoothLeServiceImpl:82  - Failed to start linux systemd bluetooth
java.io.IOException: Cannot run program "systemctl": CreateProcess error=2, The system cannot find the file specified
	at java.lang.ProcessBuilder.start(Unknown Source)
	at java.lang.Runtime.exec(Unknown Source)
	at java.lang.Runtime.exec(Unknown Source)
	at java.lang.Runtime.exec(Unknown Source)
	at org.eclipse.kura.internal.ble.BluetoothLeServiceImpl.startBluetoothSystemd(BluetoothLeServiceImpl.java:79)
	at org.eclipse.kura.internal.ble.BluetoothLeServiceImpl.activate(BluetoothLeServiceImpl.java:34)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
	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.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 org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
	at java.lang.ProcessImpl.create(Native Method)
	at java.lang.ProcessImpl.<init>(Unknown Source)
	at java.lang.ProcessImpl.start(Unknown Source)
	... 21 more
19:17:23,956 [Component Resolve Thread (Bundle 155)] ERROR BluetoothLeServiceImpl:100  - Failed to start linux init.d bluetooth
java.io.IOException: Cannot run program "/etc/init.d/bluetooth": CreateProcess error=2, The system cannot find the file specified
	at java.lang.ProcessBuilder.start(Unknown Source)
	at java.lang.Runtime.exec(Unknown Source)
	at java.lang.Runtime.exec(Unknown Source)
	at java.lang.Runtime.exec(Unknown Source)
	at org.eclipse.kura.internal.ble.BluetoothLeServiceImpl.startBluetoothInitd(BluetoothLeServiceImpl.java:92)
	at org.eclipse.kura.internal.ble.BluetoothLeServiceImpl.activate(BluetoothLeServiceImpl.java:34)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
	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.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 org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
	at java.lang.ProcessImpl.create(Native Method)
	at java.lang.ProcessImpl.<init>(Unknown Source)
	at java.lang.ProcessImpl.start(Unknown Source)
	... 21 more
19:17:23,957 [Component Resolve Thread (Bundle 155)] ERROR BluetoothLeServiceImpl:110  - Failed to start linux bluetooth service
java.io.IOException: Cannot run program "bluetoothd": CreateProcess error=2, The system cannot find the file specified
	at java.lang.ProcessBuilder.start(Unknown Source)
	at java.lang.Runtime.exec(Unknown Source)
	at java.lang.Runtime.exec(Unknown Source)
	at java.lang.Runtime.exec(Unknown Source)
	at org.eclipse.kura.internal.ble.BluetoothLeServiceImpl.startBluetoothDaemon(BluetoothLeServiceImpl.java:108)
	at org.eclipse.kura.internal.ble.BluetoothLeServiceImpl.activate(BluetoothLeServiceImpl.java:35)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
	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.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 org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
	at java.lang.ProcessImpl.create(Native Method)
	at java.lang.ProcessImpl.<init>(Unknown Source)
	at java.lang.ProcessImpl.start(Unknown Source)
	... 21 more
Native code library failed to load.
java.lang.UnsatisfiedLinkError: no tinyb in java.library.path
19:17:23,965 [Component Resolve Thread (Bundle 155)] ERROR BluetoothLeServiceImpl:40  - Failed to start bluetooth service
java.lang.UnsatisfiedLinkError: tinyb.BluetoothManager.getNativeAPIVersion()Ljava/lang/String;
	at tinyb.BluetoothManager.getNativeAPIVersion(Native Method)
	at tinyb.BluetoothManager.getBluetoothManager(BluetoothManager.java:217)
	at org.eclipse.kura.internal.ble.BluetoothLeServiceImpl.activate(BluetoothLeServiceImpl.java:38)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
	at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
	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.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 org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
19:17:23,969 [Component Resolve Thread (Bundle 155)] INFO  BluetoothLeBeaconManagerImpl:62  - Activating Bluetooth Le Beacon Manager...
19:17:23,972 [Component Resolve Thread (Bundle 155)] INFO  BluetoothLeIBeaconServiceImpl:38  - Activating Bluetooth Le IBeacon Service...
19:17:23,974 [Component Resolve Thread (Bundle 155)] INFO  BluetoothLeEddystoneServiceImpl:38  - Activating Bluetooth Le Eddystone Service...

!ENTRY osgi.annotation 4 0 2018-03-02 19:17:23.990
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: osgi.annotation [160]
  Unresolved requirement: Require-Capability: osgi.compile.time.only; filter:="(&(must.not.resolve=*)(!(must.not.resolve=*)))"

	at org.eclipse.osgi.container.Module.start(Module.java:444)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1600)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
19:17:24,029 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:209  - activate...
19:17:24,030 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:1335  - Loading init configurations from: 1519990836589...
19:17:24,236 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:1290  - Creating configuration with pid: org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport and factory pid: org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport
19:17:24,236 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:408  - Creating new configuration for factory pid org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport and pid org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport
19:17:24,237 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:411  - Updating newly created configuration for pid org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport
19:17:24,257 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport....
19:17:24,257 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport....Done
19:17:24,257 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:1290  - Creating configuration with pid: org.eclipse.kura.cloud.CloudService and factory pid: org.eclipse.kura.cloud.CloudService
19:17:24,257 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:408  - Creating new configuration for factory pid org.eclipse.kura.cloud.CloudService and pid org.eclipse.kura.cloud.CloudService
19:17:24,257 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:411  - Updating newly created configuration for pid org.eclipse.kura.cloud.CloudService
19:17:24,262 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.cloud.CloudService....
19:17:24,262 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.cloud.CloudService....Done
19:17:24,262 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:1290  - Creating configuration with pid: org.eclipse.kura.data.DataService and factory pid: org.eclipse.kura.data.DataService
19:17:24,262 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:408  - Creating new configuration for factory pid org.eclipse.kura.data.DataService and pid org.eclipse.kura.data.DataService
19:17:24,263 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:411  - Updating newly created configuration for pid org.eclipse.kura.data.DataService
19:17:24,268 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.data.DataService....
19:17:24,268 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.data.DataService....Done
19:17:24,276 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:1290  - Creating configuration with pid: org.eclipse.kura.db.H2DbService and factory pid: org.eclipse.kura.core.db.H2DbService
19:17:24,276 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:408  - Creating new configuration for factory pid org.eclipse.kura.core.db.H2DbService and pid org.eclipse.kura.db.H2DbService
19:17:24,276 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:411  - Updating newly created configuration for pid org.eclipse.kura.db.H2DbService
19:17:24,281 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.db.H2DbService....
19:17:24,281 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.db.H2DbService....Done
19:17:24,294 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:223  - Trackers being opened...
19:17:24,294 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:226  - Only tracking relevant services
19:17:24,295 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:659  - Registering SelfConfiguringComponent - org.eclipse.kura.wire.WireService....
19:17:24,295 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:667  - Registering SelfConfiguringComponent - org.eclipse.kura.wire.WireService....Done
19:17:24,433 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.cloud.CloudService ...
19:17:24,435 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.cloud.CloudService
19:17:24,442 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.cloud.CloudService
19:17:24,442 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.cloud.app.command.CommandCloudApp ...
19:17:24,442 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.cloud.app.command.CommandCloudApp
19:17:24,447 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.cloud.app.command.CommandCloudApp
19:17:24,452 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.web.Console ...
19:17:24,452 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.web.Console
19:17:24,457 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.web.Console
19:17:24,476 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.broker.artemis.xml.BrokerInstance ...
19:17:24,476 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.broker.artemis.xml.BrokerInstance
19:17:24,480 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.broker.artemis.xml.BrokerInstance
19:17:24,499 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport ...
19:17:24,504 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport
19:17:24,504 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.core.db.H2DbService ...
19:17:24,508 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.db.H2DbService
19:17:24,508 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.data.DataService ...
19:17:24,512 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.data.DataService
19:17:24,513 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.core.db.H2DbServer ...
19:17:24,513 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.ssl.SslManagerService ...
19:17:24,513 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.ssl.SslManagerService
19:17:24,518 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.ssl.SslManagerService
19:17:24,524 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.camel.xml.XmlRouterComponent ...
19:17:24,524 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.camel.xml.XmlRouterComponent
19:17:24,529 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.camel.xml.XmlRouterComponent
19:17:24,543 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.internal.rest.provider.RestService ...
19:17:24,543 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.internal.rest.provider.RestService
19:17:24,547 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.internal.rest.provider.RestService
19:17:24,555 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.position.PositionService ...
19:17:24,555 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.position.PositionService
19:17:24,560 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.position.PositionService
19:17:24,601 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.CloudSubscriber ...
19:17:24,601 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.RegexFilter ...
19:17:24,601 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.Logger ...
19:17:24,602 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.DbWireRecordFilter ...
19:17:24,602 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.Fifo ...
19:17:24,602 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.Timer ...
19:17:24,602 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.CloudPublisher ...
19:17:24,602 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.DbWireRecordStore ...
19:17:24,606 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.watchdog.WatchdogService ...
19:17:24,611 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.watchdog.WatchdogService
19:17:24,616 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.clock.ClockService ...
19:17:24,621 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.clock.ClockService
19:17:24,625 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.H2DbWireRecordStore ...
19:17:24,625 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.wire.H2DbWireRecordFilter ...
19:17:24,628 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.broker.artemis.simple.mqtt.BrokerInstance ...
19:17:24,628 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.broker.artemis.simple.mqtt.BrokerInstance
19:17:24,633 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.broker.artemis.simple.mqtt.BrokerInstance
19:17:24,638 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.core.deployment.CloudDeploymentHandlerV2 ...
19:17:24,638 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.core.deployment.CloudDeploymentHandlerV2
19:17:24,643 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.core.deployment.CloudDeploymentHandlerV2
19:17:24,648 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.camel.cloud.factory.CamelFactory ...
19:17:24,658 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:610  - Registering metatype pid: org.eclipse.kura.demo.heater.Heater ...
19:17:24,658 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:693  - Merging configuration for pid: org.eclipse.kura.demo.heater.Heater
19:17:24,663 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:852  - Seeding updated configuration for pid: org.eclipse.kura.demo.heater.Heater
19:17:24,667 [Component Resolve Thread (Bundle 155)] INFO  H2DbHelper:49  - activating...
19:17:24,667 [Component Resolve Thread (Bundle 155)] INFO  H2DbHelper:41  - Default H2DbService instance configuration found
19:17:24,667 [Component Resolve Thread (Bundle 155)] INFO  H2DbHelper:51  - activating...done

!ENTRY org.eclipse.equinox.ds 1 0 2018-03-02 19:17:24.671
!MESSAGE Could not bind a reference of component org.eclipse.kura.core.configuration.CloudConfigurationHandler. The reference is: Reference[name = CloudService, interface = org.eclipse.kura.cloud.CloudService, policy = dynamic, cardinality = 0..1, target = (kura.service.pid=org.eclipse.kura.cloud.CloudService), bind = setCloudService, unbind = unsetCloudService]
19:17:24,674 [Component Resolve Thread (Bundle 155)] INFO  CertificatesManager:66  - Bundle org.eclipse.kura.core.certificates.CertificatesManager has started!
19:17:24,686 [Component Resolve Thread (Bundle 155)] INFO  H2DbServiceImpl:87  - activating...
19:17:24,686 [Component Resolve Thread (Bundle 155)] INFO  H2DbServiceImpl:96  - updating...
19:17:24,687 [Component Resolve Thread (Bundle 155)] INFO  H2DbServiceImpl:305  - Opening database with url: jdbc:h2:mem:kuradb

!ENTRY org.eclipse.osgi 4 0 2018-03-02 19:17:24.690
!MESSAGE Bundle initial@reference:file:org.eclipse.equinox.jsp.jasper_1.0.500.v20150119-1358.jar was not resolved.

!ENTRY org.eclipse.osgi 4 0 2018-03-02 19:17:24.690
!MESSAGE Bundle initial@reference:file:org.eclipse.equinox.jsp.jasper.registry_1.0.300.v20130327-1442.jar was not resolved.

!ENTRY org.eclipse.osgi 4 0 2018-03-02 19:17:24.691
!MESSAGE Bundle initial@reference:file:../../../common/repository/plugins/osgi.annotation_6.0.1.201503162037.jar was not resolved.
19:17:24,788 [Component Resolve Thread (Bundle 155)] INFO  H2DbServiceImpl:145  - updating...done
19:17:24,788 [Component Resolve Thread (Bundle 155)] INFO  H2DbServiceImpl:91  - activating...done
19:17:24,794 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.watchdog.WatchdogService....
19:17:24,794 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.watchdog.WatchdogService....Done
19:17:24,797 [Component Resolve Thread (Bundle 155)] INFO  ClockServiceImpl:57  - Activate. Current Time: Fri Mar 02 19:17:24 PKT 2018
19:17:24,797 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.clock.ClockService....
19:17:24,797 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.clock.ClockService....Done
19:17:24,822 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.position.PositionService....
19:17:24,823 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.position.PositionService....Done
19:17:24,830 [Component Resolve Thread (Bundle 155)] INFO  Console:127  - activate...
19:17:25,302 [Component Resolve Thread (Bundle 155)] INFO  FileServlet:93  - Servlet org.eclipse.kura.web.server.servlet.FileServlet initialized
19:17:25,304 [Component Resolve Thread (Bundle 155)] INFO  FileServlet:104  - DiskFileItemFactory.DEFAULT_SIZE_THRESHOLD: 10240
19:17:25,304 [Component Resolve Thread (Bundle 155)] INFO  FileServlet:105  - DiskFileItemFactory: using size threshold of: 10240
19:17:25,321 [Component Resolve Thread (Bundle 155)] INFO  Console:174  - postInstalledEvent() :: posting KuraConfigReadyEvent
19:17:25,322 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.web.Console....
19:17:25,322 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.web.Console....Done
19:17:25,326 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.broker.artemis.xml.BrokerInstance....
19:17:25,327 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.broker.artemis.xml.BrokerInstance....Done
19:17:25,329 [Component Resolve Thread (Bundle 155)] INFO  H2DbServiceImpl:96  - updating...
19:17:25,329 [Component Resolve Thread (Bundle 155)] INFO  H2DbServiceImpl:145  - updating...done
19:17:25,336 [Component Resolve Thread (Bundle 155)] INFO  SslManagerServiceImpl:121  - activate...
19:17:25,338 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.ssl.SslManagerService....
19:17:25,338 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.ssl.SslManagerService....Done
19:17:25,344 [Component Resolve Thread (Bundle 155)] INFO  MqttDataTransport:170  - Activating org.eclipse.kura.core.data.transport.mqtt.MqttDataTransport...
19:17:25,345 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:541  - executing: InetAddress.getLocalHost windows
19:17:25,408 [Component Resolve Thread (Bundle 155)] INFO  SystemServiceImpl:554  - macAddress A0:B3:CC:F7:F1:07
19:17:25,417 [Component Resolve Thread (Bundle 155)] INFO  DataServiceImpl:116  - Activating org.eclipse.kura.data.DataService...
19:17:25,417 [Component Resolve Thread (Bundle 155)] INFO  DataServiceImpl:669  - Get Throttle with burst length 1 and send a message every 1000 millis
19:17:25,420 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
19:17:25,421 [Component Resolve Thread (Bundle 155)] INFO  DataServiceImpl:158  - H2DbService instance found
19:17:25,448 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
19:17:25,452 [Component Resolve Thread (Bundle 155)] INFO  CloudCallServiceImpl:76  - Activating...
19:17:25,456 [Component Resolve Thread (Bundle 155)] INFO  CloudServiceImpl:179  - activate org.eclipse.kura.cloud.CloudService...
19:17:25,458 [Component Resolve Thread (Bundle 155)] INFO  Cloudlet:88  - Getting CloudApplicationClient for CONF-V1...
19:17:25,468 [Component Resolve Thread (Bundle 155)] INFO  Cloudlet:88  - Getting CloudApplicationClient for ASSET-V1...
19:17:25,473 [Component Resolve Thread (Bundle 155)] INFO  CommandCloudApp:85  - Cloudlet CMD-V1 has started with config!
19:17:25,473 [Component Resolve Thread (Bundle 155)] INFO  Cloudlet:88  - Getting CloudApplicationClient for CMD-V1...
19:17:25,473 [Component Resolve Thread (Bundle 155)] INFO  CommandCloudApp:95  - updated...: org.eclipse.equinox.internal.ds.impl.ReadOnlyDictionary@71baf89f
19:17:25,474 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.cloud.app.command.CommandCloudApp....
19:17:25,474 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.cloud.app.command.CommandCloudApp....Done
19:17:25,478 [Component Resolve Thread (Bundle 155)] INFO  AbstractCamelComponent:40  - Starting camel router
19:17:25,484 [Component Resolve Thread (Bundle 155)] INFO  CamelRunner:433  - Starting...
19:17:25,484 [Component Resolve Thread (Bundle 155)] INFO  CamelRunner:464  - Stopping...
19:17:25,658 [Component Resolve Thread (Bundle 155)] INFO  OsgiDefaultCamelContext:2800  - Apache Camel 2.17.2 (CamelContext: camel-1) is starting
19:17:25,659 [Component Resolve Thread (Bundle 155)] INFO  ManagedManagementStrategy:191  - JMX is enabled
19:17:25,857 [Component Resolve Thread (Bundle 155)] INFO  DefaultRuntimeEndpointRegistry:203  - Runtime endpoint registry is in extended mode gathering usage statistics of all incoming and outgoing endpoints (cache limit: 1000)
19:17:25,858 [Component Resolve Thread (Bundle 155)] INFO  OsgiDefaultCamelContext:3039  - AllowUseOriginalMessage is enabled. If access to the original message is not needed, then its recommended to turn this option off as it may improve performance.
19:17:25,858 [Component Resolve Thread (Bundle 155)] INFO  OsgiDefaultCamelContext:3049  - StreamCaching is not in use. If using streams then its recommended to enable stream caching. See more details at http://camel.apache.org/stream-caching.html
19:17:25,858 [Component Resolve Thread (Bundle 155)] INFO  OsgiDefaultCamelContext:2840  - Total 0 routes, of which 0 are started.
19:17:25,859 [Component Resolve Thread (Bundle 155)] INFO  OsgiDefaultCamelContext:2841  - Apache Camel 2.17.2 (CamelContext: camel-1) started in 0.201 seconds
19:17:25,859 [Component Resolve Thread (Bundle 155)] INFO  CamelRunner:618  - Setting routes...
19:17:26,347 [Component Resolve Thread (Bundle 155)] INFO  OsgiDefaultCamelContext:3570  - Route: route1 started and consuming from: Endpoint[kura-cloud://myapp/xmltopic]
19:17:26,348 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.camel.xml.XmlRouterComponent....
19:17:26,348 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.camel.xml.XmlRouterComponent....Done
19:17:26,359 [Component Resolve Thread (Bundle 155)] INFO  RestService:49  - activating...
19:17:26,359 [Component Resolve Thread (Bundle 155)] INFO  RestService:60  - updating...
19:17:26,364 [Component Resolve Thread (Bundle 155)] INFO  RestService:62  - updating...done
19:17:26,364 [Component Resolve Thread (Bundle 155)] INFO  RestService:51  - activating...done
19:17:26,365 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.internal.rest.provider.RestService....
19:17:26,365 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.internal.rest.provider.RestService....Done
19:17:26,369 [Component Resolve Thread (Bundle 155)] INFO  ClockServiceImpl:68  - Updated...
19:17:26,373 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.broker.artemis.simple.mqtt.BrokerInstance....
19:17:26,373 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.broker.artemis.simple.mqtt.BrokerInstance....Done
19:17:26,380 [Component Resolve Thread (Bundle 155)] INFO  CloudDeploymentHandlerV2:241  - Cloud Deployment v2 is starting
19:17:26,381 [Component Resolve Thread (Bundle 155)] INFO  Cloudlet:88  - Getting CloudApplicationClient for DEPLOY-V2...
19:17:26,384 [Component Resolve Thread (Bundle 155)] INFO  InstallImpl:211  - Ready to send Confirmations
19:17:26,384 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.core.deployment.CloudDeploymentHandlerV2....
19:17:26,384 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.core.deployment.CloudDeploymentHandlerV2....Done
19:17:26,388 [Component Resolve Thread (Bundle 155)] INFO  Heater:93  - Activating Heater...
19:17:26,388 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - component.name: org.eclipse.kura.demo.heater.Heater
19:17:26,388 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - temperature.initial: 10.0
19:17:26,388 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - program.stopTime: 22:00
19:17:26,388 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - objectClass: [Ljava.lang.String;@5cab5f44
19:17:26,388 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - manual.setPoint: 15.0
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - publish.semanticTopic: data
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - program.setPoint: 20.5
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - mode: Program
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - kura.service.pid: org.eclipse.kura.demo.heater.Heater
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - CloudService.target: (kura.service.pid=org.eclipse.kura.cloud.CloudService)
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - publish.rate: 2
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - service.pid: org.eclipse.kura.demo.heater.Heater
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - temperature.increment: 0.25
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - component.id: 54
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - publish.retain: false
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - publish.qos: 0
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:97  - Activate - program.startTime: 06:00
19:17:26,389 [Component Resolve Thread (Bundle 155)] INFO  Heater:104  - Getting CloudClient for heater...
19:17:26,390 [Component Resolve Thread (Bundle 155)] INFO  Heater:115  - Activating Heater... Done.
19:17:26,391 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:634  - Registering ConfigurableComponent - org.eclipse.kura.demo.heater.Heater....
19:17:26,391 [Component Resolve Thread (Bundle 155)] INFO  ConfigurationServiceImpl:650  - Registering ConfigurableComponent - org.eclipse.kura.demo.heater.Heater....Done
data
19:17:26,421 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:26,433 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:26,433 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@33cf6a03
19:17:26,433 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
19:17:26,438 [HouseKeeperTask] INFO  HouseKeeperTask:41  - HouseKeeperTask started.
19:17:26,438 [HouseKeeperTask] INFO  HouseKeeperTask:52  - HouseKeeperTask: Delete confirmed messages...
19:17:26,441 [HouseKeeperTask] INFO  HouseKeeperTask:61  - HouseKeeperTask ended.
data
19:17:28,391 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:28,393 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:28,394 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@2e0ccaa6
19:17:28,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:30,391 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:30,393 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:30,393 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@52b7f223
19:17:30,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:32,391 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:32,393 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:32,393 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@1021cafa
19:17:32,393 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:34,392 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:34,393 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:34,393 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@58f6258f
19:17:34,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:36,391 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:36,393 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:36,394 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@10678dcd
19:17:36,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:38,391 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:38,394 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:38,394 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@7d2c5308
19:17:38,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:40,391 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:40,393 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:40,393 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@6344204d
19:17:40,393 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:42,391 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:42,393 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:42,394 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@a77bbf7
19:17:42,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:44,392 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:44,394 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:44,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
19:17:44,395 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@26d25691
data
19:17:46,392 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:46,394 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:46,394 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@39f9e550
19:17:46,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:48,392 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:48,394 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:48,394 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@7b7dec6a
19:17:48,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:50,392 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:50,394 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:50,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
19:17:50,394 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@4c6258f1
data
19:17:52,392 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:52,394 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:52,395 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@7830e932
19:17:52,395 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:54,393 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:54,395 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:54,395 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@e155001
19:17:54,395 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:56,392 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:56,395 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:56,395 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@1a1fe315
19:17:56,395 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data
19:17:58,392 [] INFO  DataServiceImpl:531  - Storing message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:58,394 [] INFO  DataServiceImpl:534  - Stored message on topic :#account-name/#client-id/heater/data, priority: 5
19:17:58,394 [] INFO  Heater:274  - Published to data message: org.eclipse.kura.message.KuraPayload@44e48577
19:17:58,394 [DataServiceImpl:Submit] INFO  DataServiceImpl:821  - DataPublisherService not connected
data


If someone knows the solution, Kindly help.

Kind Regards,
Ahmad Arif

[Updated on: Fri, 02 March 2018 14:37]

Report message to a moderator

Re: Mqtt message capacity [message #1797262 is a reply to message #1782307] Mon, 29 October 2018 11:15 Go to previous message
Marco Noto is currently offline Marco NotoFriend
Messages: 10
Registered: November 2017
Location: Turin
Junior Member
Can you explain better this option?
rate.limit.burst.size
Previous Topic:Creating deployment packages
Next Topic:Can this portable Java Device I/O library be of any assistance?
Goto Forum:
  


Current Time: Sun Nov 18 18:30:43 GMT 2018

Powered by FUDForum. Page generated in 0.02594 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top